Related
i was tolf to move this here this is a question ,,,idk how to do step 5..it has to do with movin file to sd card im guessing..idk help me?
help me root my phone i dont understand this im really f'd up this is like dsa adveture
ok here is the problklmemo
"Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now
Once ready, type these commands in cmd prompt from your adb tools directory.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/"
oksssssss now..one person say i right click on tools and open cmd,,,so i dids that
then i type it in and its doesnt work..it says adb or abd waterver it is is not a command and its not reconixed...help me please!!!thanjs
i have windows 7 64 bit
Did you do ALL of this first?
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.40 here
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Download my evo-root.zip.
It contains a few files necessary to root the EVO.
Unzip the contents of the zip to your android sdk tools folder.
Download the unrevoked-forever.zip
Place this zip in your tools folder as well, as a zip, not extracted.
Download this PC36IMG.zip (This is the same as running an RUU, so it will delete all of your user data when we use it later in the guide, so backup everything you want to save on your phone first)
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of evo-root.zip to your android sdk tools folder and placing the PC36IMG.zip and unrevoked-forever.zip in the folder, move on.
Click to expand...
Click to collapse
You need to change the directory to your tools fold so that the computer can execute advanced commands. Look for a thread about setting up adb. In the thread it will tell you the steps to do so. I would post this for you however I do not have access to a computer and I am use to using advanced on a Mac.
Sent from my PC36100
nebenezer said:
Did you do ALL of this first?
Click to expand...
Click to collapse
yes i did i had no problems untill step 5
Read my post in the thread you created in development.
i have a tmobile g2 and used visionary to root and it did not work right but my s-off and i can not root any way i try,if i have stock rom what do i have to do to reinstall the stom rom and will this make my g2 go back to s-on?
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
renn9420 said:
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
iv tried that and nothing works at all,i was told i needed s-on again because s-off is what i have and no matter what i try i can not root this **** phone!!!!!!im ready to throw it out the window.
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
steviewevie said:
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
Click to expand...
Click to collapse
im about to try it
hightechlive said:
im about to try it
Click to expand...
Click to collapse
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
hightechlive said:
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
Click to expand...
Click to collapse
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
steviewevie said:
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
Click to expand...
Click to collapse
yes i did get forked xxx children message,but i this is different for me
init_module 'wpthis-OTA.ko' failed
i get this
local/tmp/init_module 'wpthis-OTA.ko' failed
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
fastludeh22 said:
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
Click to expand...
Click to collapse
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
hightechlive said:
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
Click to expand...
Click to collapse
*Following instructions in that post includes a wipe. This will delete settings, 3rd party apps, mms etc. Be sure to backup what's needed.
These directions are for windows computers:
Do not unzip the file. It should be clockwork recovery 2.x.x.x.img. just rename it recovery.img. The root of c just means not in any folders. So after naming it recovery.img put it on c. It will then be c:\recovery.img
Then when you open up cmd window, goto sdk folder like when you use adb. With your phone booted into hboot with usb connected. You type this into cmd window: "fastboot flash recovery recovery.img" without the quotes. Then finish following pervious link.
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
i type in command window but it says can not load recovery img
hightechlive said:
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
Click to expand...
Click to collapse
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
fastludeh22 said:
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
Click to expand...
Click to collapse
i type in command window but it says can not load recovery img
im doing everything you said?
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
fastludeh22 said:
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
Click to expand...
Click to collapse
i did that,this i what i did i download and change the name and put the zip file in the c root,open command and went to the tolls folder after the other things to get there in command and this is what it says
says can not load recovery img
What zip file? The recovery should be an img file.
fastludeh22 said:
What zip file? The recovery should be an img file.
Click to expand...
Click to collapse
that what im saying when i down load the file if is zip up and when i unzip it says i can not open it?
when i download it this is the name of the file
recovery-clockwork-2.5.1.2-vision (1)
I went to clockwork thread and clicked link. It dl's as .img file for me. This is the direct link I'm talking about. http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
If your using that, check this. In an open window/folder in windows. Click tools, then folder options. Select view tab. Uncheck "hide extensions of known file types". Then the file extensions should show at the end of every file. Make sure its named right now.
I was trying to do the radio s off with visionary and something went wrong.
I downloaded visionary+ onto my Telus HTC Desire HD no problem, I had rooted it earlier and beleived that to be done correctly. I was getting ready to flash my radio and was going through the steps to do so when my problems began.
Now, all that happens is VISIONary+ keeps on rebooting. I have tried pulling the battery, I have tried to change my settings (re: usb debugging) but nothing seems to help.....all it does is continously shut back off and try to reboot.
Any help would be greatly appreciated.
Update: This issue has been resolved. I am now trying to figure out if my phone is properly rooted...go to page 2 in thread please
What is your build number in settings>about>software information? Anything higher (and including) than 1.7 will cause Visionary to fail. Then you have to downgrade first.
OK, that is my first mistake, my Build # is 1.84.61.2.
I will attempt the downgrade and report back here
I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?
bleagues said:
I am at the downgrade prompt. When I put in the command "adb push psneuter /data/local/tmp" I get a message saying "'adb' is not recognized as an internal or external command, operable program or batch file"
What did I do wrong?
Click to expand...
Click to collapse
download android sdk first
http://developer.android.com/sdk/index.html
put your command to the folder .. for example if u extract to desktop with folder android, then go to command prompt, point to the folder first
e.g: "cd desktop" "cd android"
p/s: put the file inside the folder too
Thanks Hayday, this dosen't seem to help though.
I have the Android SDK in my C: drive and I have placed the "downgrade" folder inside of it. And I still get the same error of "adb' is not recognized as an internal or external command, operable program or batch file" when I type the "adb push psneuter /data/local/tmp"
Any other suggestions?
I believe it still may be a driver problem. I keep getting a message from HTC Sync that says "HTC sync port of ### is not responding. Please disconnect cable and reconnect after 10 seconds"
Can I use the program terminal emulator to do this directly on the phone?
does the folder have adb.exe in it ?
if you place the android sdk folder in c for example the folder name is "android" , you just go to cmd .. then type "cd c:/android/"
and then type "adb" ..
you must use the command inside c:/android .. not c:/android/Downgrade
to be safe, just copy everything in "Downgrade" folder and paste to android sdk folder too ..
btw, here is the full thread by jkoljo himself on how to downgrade.
http://forum.xda-developers.com/showthread.php?t=905003&highlight=downgrade
I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."
I cannot post a question in that other thread because I have fewer than 10 posts. I will as soon as I get up to 10.
Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.
arlrb said:
Download & install htc sync, this should include all the drivers you need.
I think you need net framework 3.xx installed as well.
Then in cmd, go to where you put the downgrade file (cd blah blah) - http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 - & then the command lines should work.
Click to expand...
Click to collapse
oh forgot to mention. download and install htc sync for the driver.
http://www.htc.com/www/supportdownloadlist.aspx?p_id=324&act=sd&cat=all
bleagues said:
I have done exactly as you say, I have the "downgrade" folder inside of the "AndroidSDK" folder....and still get the exact same message of "'adb' is not recognized....."
Click to expand...
Click to collapse
adb.exe is found in platform-tools folder in the android-sdk folder.
Add it to your path. Eg: PATH=c:\android-sdk\platform-tools;%PATH%
Thanks arjunr, after a little bit of tinkering with some files and folders I got it!
Thanks!
Now that I have the proper build #, I want to make sure my phone is properly rooted......or do I have to re-root it?
Is there any way to check and see if my phone is properly rooted?
I had rooted it before I did the build downgrade, does this make a difference?
My phone out of the box was a HTC Desire HD by Telus. The rooting that I followed was the http://forum.xda-developers.com/showthread.php?t=954997"which is the "[GUIDE] Telus Desire HD - Rooting and Flashing" found here on this website
I am good to go, I am rooted and downgraded!
bleagues said:
I am good to go, I am rooted and downgraded!
Click to expand...
Click to collapse
yeah now you can proceed with s-off, and flash new roms if you like.
Heydayat, I seem to be having some issues with anything internet related. I have started another post at http://forum.xda-developers.com/showthread.php?t=1012754 can you take a look at this and see if you can help me?
Thanks
Update: I have fixed the issue at the other thread, it was my APN settings.
Thanks to all for the help
hey everyone
ive been trying to install leedroid v3.3.3 data++ type
it recquires soff and cm7r2 hboot
the thing is that my phone is already soffed but doesnt have cm7r2
i tried some guides to hboot my phone but its useless and i couldnt do it...
can someone link me to a video or detailed steps because im really exhausted i couldnt finish it up to install the rom
i always stop at this step
Now open Terminal on Mac or command prompt on windows and cd into Android-SDK/tools folder.
Click to expand...
Click to collapse
i enter the path but it says adbwinapi.dll is missing frm my computer, and try reinstalling program to fix the problem !
so i try reinstalling but unfortunately same result
so please i wish someone could help me on this one
thanks alot in advance
all appreciations
In a CMD shell you need to add "Path C:\Android-sdk\Platform-Tools" (or whatever the correct path is to that folder where you installed it) then try again.
Alternatively, download Android Flasher (search these forums) and run the commands from the folder that contains ADB and Fastboot.
what are the adb scripts, i keep seeing posts talking about them, all i know is that i installed two files one named android sdk windows and the other installer r12 windows
Go to c:\android-sdk\tools folder, copy "fastboot.exe" and paste it into c:\android-sdk\platform-tools.
Then before issuing fastboot commands type
Code:
cd c:\android-sdk\platform-tools
Once you've done that and want to flash the hboot, put it in your c:\ For simplicity and type
Code:
fastboot flash hboot c:\bravo_alphaspl-cm7r2.img
Fastboot reboot bootloader
If you're really stuck go here :- http://alpharev.nl/ and download the PB99IMG file instead. Rename this to PB99IMG.zip and save it to the root of your SD card. Restart your phone in recovery (vol down + power) and it should flash it for you. Been a long time since I did it that way so I invite anyone to correct me.
Edit: Please delete the PB99IMG.zip file once flashed else it will re-flash it everytime you enter recovery.
Look at step 4
http://forum.xda-developers.com/showthread.php?t=1016084 follow the video eveything you need is on this page.
You can get Bravo CM7 r2 from http://alpharev.nl/
Worked for me
Good luck
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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.
Click to expand...
Click to collapse
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
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.
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.
Click to expand...
Click to collapse
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.