5,606,409 Members 33,649 Now Online
XDA Developers Android and Mobile Development Forum

Guide to fixing a soft brick after editing build.prop

Tip us?
 
ibanezbass
Old
(Last edited by ibanezbass; 9th October 2012 at 04:28 PM.)
#1  
ibanezbass's Avatar
Senior Member - OP
Thanks Meter 66
Posts: 261
Join Date: Jan 2009
Location: Oklahoma City
Default Guide to fixing a soft brick after editing build.prop

I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.

I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.

You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/show....php?t=1379875

Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.

Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.

Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Phone: LG G2; 32G
Tablet: HP Touchpad 32G / CM11; Asus MemoPad Smart 10";
Dell Venue 8 Pro 32G; iPad 2 16G
Retired:
Flip Phones->iPhone->AT&T Tilt (WM6/6.5/Android 1.5/1.6)->
iPhone 3GS->iPhone 4->HTC Inspire 4G->iPhone 4S->
Samsung Galaxy S III->HTC One
The Following 14 Users Say Thank You to ibanezbass For This Useful Post: [ Click to Expand ]
 
Beremat
Old
#2  
Member
Thanks Meter 7
Posts: 39
Join Date: Mar 2012
Thanks, worked like a charm on my SII. And I finally have ADB set up for any future hiccups!
 
lyrictenor1
Old
#3  
Member
Thanks Meter 2
Posts: 78
Join Date: Mar 2012
Quote:
Originally Posted by ibanezbass View Post
I've noticed several users having trouble with their phone when editing the build.prop. They will edit the file, reboot, anxious to use Google Wallet, and be greeted with a black screen of death. Their heart will jump in their throat and they think... "Oh no... I didn't nandroid backup... What's a nandroid backup anyway?" No worries! I have the solution for all of you. Hopefully this short guide will get you going again.

I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.

You also need the naked ADB drivers if you're a Windows user... Here http://forum.xda-developers.com/show....php?t=1379875

Once you reboot your phone into recovery: Open start menu, right click on Computer, click properties. This will open the system panel. Top left, click device manager. Somewhere along there, see if you see your device name (something like "Samsung-SGH_I747") with an exclamation point or question mark. Double click it if it does. Click update driver in the window that opened. Click "Browse My Computer...." "Let me pick..." "All devices / next"... "Browse". Now go find where you downloaded and extracted the naked driver zip. Open the folder and double click on one of the available .ini files. You'll get some compatibility warnings, just continue.

Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.

Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
I'm having the same issue; I did the above procedures (using a Mac) but every time I type "adb shell", I get this:

"-bash: adb: command not found"

Help, please....

Thanks!
 
lyrictenor1
Old
#4  
Member
Thanks Meter 2
Posts: 78
Join Date: Mar 2012
Nevermind, I figured it out.
 
countrylife
Old
#5  
countrylife's Avatar
Member
Thanks Meter 18
Posts: 55
Join Date: Nov 2012
Location: Texarkana, Texas
good write up, thank you
 
erstad
Old
#6  
erstad's Avatar
Senior Member
Thanks Meter 46
Posts: 184
Join Date: Dec 2010
Location: Newton, NH

 
DONATE TO ME
Seems to be only when you use a gnex as build prop.
HTC jewel works great
I had two softbricks worked great


Sent from my SAMSUNG-SGH-I747 using xda premium
 
Riggzo
Old
#7  
Junior Member
Thanks Meter 0
Posts: 11
Join Date: Feb 2012
very helpful. Thanks!
 
mknlb50
Old
(Last edited by mknlb50; 5th December 2012 at 04:52 PM.)
#8  
Junior Member
Thanks Meter 1
Posts: 8
Join Date: Aug 2012
This doesn't do anything for me. It still shows rw-rw-rw after running that command in adb. Any other ideas?

It also seems like it doesn't modify any of the files at all. I even tried renaming because i have a build.prop.bak file that i want to use and it doesn't seem to rename it.

[update] I am using the Odin method just to reflash it to the stock rom. I have moved on from this useless method.
 
ballot
Old
#9  
Junior Member
Thanks Meter 0
Posts: 14
Join Date: Nov 2011
Hi i just edited the /system/build.prop

for able to play gameloft games

now my tablet cant boot

i use this room : http://forum.xda-developers.com/show....php?t=1816795

i tried your method
i got this error
>adb shell
error: device not found

what can i do i don't want lose data

i tried to recovery mode and normal booted mode no lucks
 
rattouille
Old
#10  
Junior Member
Thanks Meter 3
Posts: 23
Join Date: Aug 2012
please help. ican't find my device in device manager

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Speed up the ROM or Kernel Build Process

Creating a kernel, ROM, or any other development projectrequires knowledge and tools. While … more

Google Glass Now Open to Anyone… with $1500 to Spend (Update: Not Anymore)

Google Glass, which recently received its official update … more

Android 4.4.2 OTA Now Available for the Verizon Droid DNA

A couple of days ago, we talked about how the Android 4.4.2 upgrade for the HTC … more