Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,050 Members 42,876 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Recover or fix build.prop

Tip us?
 
greenmaze
Old
#1  
Member - OP
Thanks Meter 4
Posts: 38
Join Date: Jul 2011
Default [Q] Recover or fix build.prop

I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?

Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
 
abhishek 9650
Old
#2  
Member
Thanks Meter 11
Posts: 87
Join Date: Feb 2014
Location: new delhi

 
DONATE TO ME
Quote:
Originally Posted by greenmaze View Post
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?

Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
first you need same build.prop from same device. ask your friend use xda.
ask them to give you build.prop

after getting build.prop
use adb delete your first build.prop
and then push your build.prop(which you got from your friend)
to /system/



just press me thank if i helped you
 
AbhiLP
Old
#3  
AbhiLP's Avatar
Senior Member
Thanks Meter 60
Posts: 187
Join Date: Nov 2012
Location: Jammu
Quote:
Originally Posted by greenmaze View Post
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?

Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
Whenever you mess up with system files like build.prop, a backup of that file is automatically created in the same location with .bak extension. So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
 
"Donít use a userís thanks count to judge their helpfulness Ė it is by no means an example of how helpful a user is. Many of the most helpful users on XDA-Developers do not have the largest thanks counts, rather they quietly help out where needed, and donít post when they have nothing to say."



 
greenmaze
Old
#4  
Member - OP
Thanks Meter 4
Posts: 38
Join Date: Jul 2011
Thanks for the help. The problem is that I can't get any adb commands to work (i.e. push or pull) in recovery mode. The devices command lists the tablet with the name "sideload". Am I doing something wrong?

Sent from my Nexus 5 using Tapatalk
 
greenmaze
Old
#5  
Member - OP
Thanks Meter 4
Posts: 38
Join Date: Jul 2011
To elaborate a little more, whenever I try an adb command I get the following message:

Code:
error: closed
Is there another way to get the tablet into a mode where it will accept adb commands?
 
greenmaze
Old
#6  
Member - OP
Thanks Meter 4
Posts: 38
Join Date: Jul 2011
Quote:
Originally Posted by AbhiLP View Post
... So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
I wasn't sure what Aroma Filemanager was so I looked it up. Unfortunantly I'm unable to get Aroma Filemanager to work. I downloaded the zip to a SD card, booted into recovery, selected "apply update from ADB" and then selected the Aroma zip file. Some messages scroll on the screen and then tablet reboots. If I try sideloading the Aroma zip I get this output:

Code:
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
 
greenmaze
Old
#7  
Member - OP
Thanks Meter 4
Posts: 38
Join Date: Jul 2011
Default Fixed it

I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
  • Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
  • Boot into recovery and copy /system/build.prop to an SD card.
  • Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
  • Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.

* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
The Following User Says Thank You to greenmaze For This Useful Post: [ Click to Expand ]
 
Kriggs
Old
#8  
Member
Thanks Meter 10
Posts: 83
Join Date: Mar 2011
Quote:
Originally Posted by greenmaze View Post
I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
  • Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
  • Boot into recovery and copy /system/build.prop to an SD card.
  • Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
  • Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.

* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
Can't access SD here, when mounting in CWM it mounts as a CD Rom and can't access it, never seen this...
 
edlabh
Old
#9  
Junior Member
Thanks Meter 4
Posts: 15
Join Date: Nov 2010
I always recommend to flash the whole rom using odin if you don't have a custom recovery

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Add the Xperia Z2 Lock Screen to Your Favorite KitKat ROM

Almost every OEM adds its own unique flair to their stock firmwares. While some of … more

Android App Review: Control Your Phone with Quick Control Panel – XDA Developer TV

Your Android smart device has many features that you … more

Play Music on Android Wear with Stellio Music Player

Android Wear smartwatchesare growing inpopularity every day. Some devices have already … more

Schedule is up for xda:devcon ’14

With xda:devcon ’14 just around the corner, and the venue close to selling out, there is a lot … more