Skip to main content
Tweeted twitter.com/StackAndroid/status/809170820585189376
added 112 characters in body
Source Link

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

I've also tried

>adb root 

but it hangs forever with no output so I have to close the console window.

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

I've also tried

>adb root 

but it hangs forever with no output so I have to close the console window.

added 16 characters in body
Source Link

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

edited body
Source Link

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description hereenter image description here

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

So I've done

# mv /storage/emulated/legacy/build.prop /system/build.prop 

on my SM-T311 (Android 4.4.2) and now it won't boot. The only change I've made was adding one line at the end:

net.hostname=Tableta 

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode. Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)

Is there a way to fix my tablet without losing my data, or am I doomed?

Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions are wrong. Unfortunately it wouldn't let me chmod the file or remount.

enter image description here

deleted 47 characters in body; edited title
Source Link
Loading
added 426 characters in body
Source Link
Loading
Rollback to Revision 2
Source Link
Loading
added 50 characters in body
Source Link
Loading
added 11 characters in body
Source Link
Loading
Source Link
Loading