Related
I've combined toastcfh's and TheBiles how-to's in this tutorial, so if you've already rooted using TheBiles previous method, skip to step 9. I'll make this a bit more presentable when I get home from work today. I just thought this would be helpful to those who aren't comfortable with using adb.
I'm not responsible for damages to your phone, yada yada yada, you know the drill.
IF YOU HAVE A PROBLEM THAT HASN'T BEEN ADDRESSES IN THE SECOND POST, LET ME KNOW. OTHERWISE, SEE SECOND POST FOR FAQ'S. Follow these directions exactly as they are written and you won't run into any snags. It'll save us both a lot of time.This tutorial entails making the root process as fast and easy as possible, that means we won't be backing up any of your stuff (you can if you want, of course) nor will we be doing a nandroid backup, and even better, we won't be using adb to push files. With that being said, let's get started.
Step 1. Connect your phone to your pc via usb, then pull down the notification bar at the top of your screen and open the tab that says Charge Only and select Disk Drive then click done.
Step 2. Download this file http://link.geekfor.me/rootedromzip and put it on the root of your sd card by going to the start menu of your computer and opening up My Computer, then drop the file into the icon that reads Removable Disk. This is the root of your sd card. Remember that if you don't already know.
Step 3. Right click on the Removable Disk icon and select Eject. We're gonna flash the debug image now, say goodbye to any pic's, music, apps, texts, etc that you may have.
Step 4. Power down your phone.
Step 5. Hold down the volume down and power key simultaneously and keep holding it down until you see 3 android dudes on skateboards.
Step 6. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 7. Once you've rebooted you will officially have root access. Congrats, but that's not all. There's a few more steps to gain -full- root access.
Step 8. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. To rename the .zip file, right click on PC36IMG.zip and select rename.
Step 9. Download these files:
PC36IMG.zip -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
mtd-eng.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
flash_image.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
recovery.img - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img
PLEASE NOTE SOME OF THE MIRRORS YOU ARE DOWNLOADING THESE FILES FROM ARE NAMED SOMETHING DIFFERENT, SO YOU WILL HAVE TO RENAME THEM ACCORDINGLY. The only one that I know of was the PC36IMG.zip file, it was named something else when I downloaded it. So name it accordingly. Right click, select Rename, then type in "PC36IMG" only, your pc adds the .zip.
Step 10. Extract the flash_image.zip and mtd-eng.zip files, do so by right clicking on them, then select Extract To flash_image\ and Extract To mtd-eng\ Open the newly extracted folders and take the flash_image file AND the mtd-eng file inside and drop them into the root of your sd card. (we remember how to do that, don't we.)
Step 11. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 12. Make sure your sd card is no longer mounted to the computer, do so by pulling down the notification bar and switching Disk Drive to Charge Only.
Step 13. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 14. Remount your phone, and drop the PC36IMG.zip file onto the root of your sd card. MAKE SURE YOU USE THE CORRECT PC36IMG.ZIP FILE THAT YOU DOWNLOADED FROM STEP 9. Power down your phone.
Step 15.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 16. Once your phone has rebooted, put the recovery.img file you downloaded earlier on the root of your sdcard.
Note: If the recovery image is named something other than "recovery.img" then rename it by right clicking and typing in "recovery" as the name.
Step 17. Still know how to use terminal emulator? Open it up and type in these commands. Make sure your USB connection is in Charge Only mode first.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
*INTERMISSION*
Take uh break, eat uh cookie.
If you've made it this far and you've had no errors, then you now have full root access as well as a legit recovery.
Time to flash a ROM and the latest radio.
Step 18. Power down your phone and power it back on by holding down the Volume Up and Power key.
Step 19. Select BOOTLOADER then select Recovery.
Step 20. Select Wipe: Select wipe data factory reset then select wipe dalvik cache.
Step 21. Downlaod any ROM you'd like, I'm running BuglessPete's Bugless Beast ROM, here's the link if you want to run this one as well http://bit.ly/az4cWq
Step 22. Download the latest radio here http://link.geekfor.me/radio139000531
Step 23. In recovery mode, select the USB-MS toggle option, this mounts your sd card to your pc.
Step 24. Move your newly downloaded ROM and radio to the root of your sd card by dropping them onto the Removable Disk icon on your computer.
Step 25. Press the power key to disable USB-MS toggle.
Step 26. Select Flash Zip From Sdcard.
Step 27. Select the ROM you downloaded and you will be prompted whether or not you want to flash the file, follow through with the power key.
Step 28. Select flash zip from sdcard, then select the latest radio .zip file that you just downloaded and flash that mf'er.
Step 29. Try not to freak out when you see a static image of a phone with green arrows circling around it. Wait...
Step 30. Select Reboot System Now.
And that's it, you're done!
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
Grammatical errors? I just worked a 12 hour shift and got right on this, I have to be in bed in about an hour, so **** you.
Problems flashing a ROM after you've completed the process?
This is more than likely on account of the Dev who made the ROM not signing it, tell them if they sign it that you'll love them forever. Or switch to Koush's recovery. This is pretty much guaranteed to work, as Koush's recovery has a toggle signature verification feature. http://forum.xda-developers.com/showthread.php?t=702214 Or, if you've the know-how, sign it yourself. http://forum.xda-developers.com/showthread.php?t=473580
ATTENTION: To the few getting the not enough space error when flashing the recovery image, Amon Ra has addressed the issue here, to no avail according to those who have tried his alternative recovery. At least we now know what the cause of the error is. Thanks again, Amon Ra.
Amon_RA said:
You have a bad block in your recovery (like a bad sector on your harddisk), these bad blocks are skipped when flashing. A bad block means you have less usable space on your recovery partition, hence the not enough space left to flash this recovery...
I made this recovery specially for you, it's 1MB less than the normal recovery (left out the evo charging stuff), all functions of the normal recovery should still work. Could you please give it a try and let me know?
Code:
fastboot flash recovery tiny-recovery.img
OR
flash_image recovery /sdcard/tiny-recovery.img
Click to expand...
Click to collapse
Bad block? Not enough space on sd error when trying to flash the recovery image? Try these.
Amon_RA said:
Could you please try to flash recovery-RA-evo-v1.7.0.2.img and use fastboot to flash :
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-evo-v1.7.0.2.img
I'll most likely not make my recovery compatible with Koush's rommanger because I would need to almost rewrite it fully.
Click to expand...
Click to collapse
tlisak25 said:
If people are still having problems tell them to unroot and start from scratch without doing system update from Sprint thanks for all or your help
Click to expand...
Click to collapse
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
arozer said:
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
Click to expand...
Click to collapse
Exactly. Also, it's for those who rooted using TheBiles Idiot Proof method and were confused as to whether or not they could follow through with toastcfh's part 2nd part on gaining full root access.
Re: (How-To) FULL ROOT WITHOUT ADB.
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
TheBiles said:
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Totally agreed. But this method is meant to make rooting as fast and easy as possible (for those who don't know how to neither set up, nor use adb, as setting it up as well as familiarizing yourself with it takes time) Although learning adb is a definite must.
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
bdd123456789 said:
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
Click to expand...
Click to collapse
I'm just glad it helped. Lol If there's anyone you should donate to, it's toastcfh. Without him, we wouldn't have root.
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
Just a second, I'll get you a link.
the recovery.img link in step #9 is broken as well...
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
http://www.joeyconway.com/sdx/evo/troot/eng-PC36IMG.zip
Got it from toastcfh's thread. Should work. I'll update the link now.
Go damn it. -.- I'll update them all now. Thanks for the heads up.
thx for the hard work.
Lol Not really doing much but stealing links. They're all updated now.
evo root
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
crpercodani said:
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
Click to expand...
Click to collapse
Exactly! It took me 2 solid days of searching for the required driver for my laptop. I finally got it to work last night. None of the instructions on xda worked. The USB remover listed here didn't work, the driver in the SDK kit didn't work, nothing worked. I finally found another download for the USB remover and another link to a 32-bit driver that finally worked.
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
It's pretty much the fastest/easiest (if you don't have adb set up) way to get full root access on your Evo, so...yes, that'd be a good idea. Lol
S
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
Oh yeah, start from step 9 since you're coming from the first part of TheBiles Idiot Proof guide.
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Note: If you're in Linux, you only need to do Step 4, Step 6, and Step 7.
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe".
If you aren't greeted with a failed to fetch URL error, proceed to Step 3. If you did receive this error, go to Settings in the "Choose Packages to Install" window and check "Force https;//... sources to be fetched using http://..."
Close and re-open "SDK Setup.exe".
Step 3.
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 4.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 5.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 6.
This step is optional, but it may prevent an error later on in the process. If you've never formatted your SD card from a computer, remove it from the phone and format it in Windows or OSX with an external card reader. Then place the formatted card back in your phone, but leave the phone off.
Step 7.
Download the updated Root.zip from eugene373's guide: Root the Slide & Other HTC Devices*6/15/2010* How-To Updated 6/29/2010
Now let's get started...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in Linux) (refer to ice3186's post for Mac instructions)
Note: The loop does nothing but show you the connection status of your phone. It's not technically required, but we'll use it in this guide.
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug the USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please)
Step 10.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
Step 11.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
gtg465x said:
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe"
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 3.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 4.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 5.
Download Root.zip from eugene373's guide: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
Now let's get into it...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding down the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds, until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug your USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold down the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
step 12.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 13.
If successful, you should see Clockwork Recovery and you now have Su & Superuser.apk installed! You can now reboot your phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Click to expand...
Click to collapse
This isn't complete - this just gets you to clockwork and you haven't installed anything yet. You need to add steps to add root acces or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Yes! The secret was formatting the sd card outside of the phone. I am now rooted and liberated! Thanks for plugging along with all the advice guys!
modest_mandroid said:
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
Click to expand...
Click to collapse
Really good tips. I hope you don't mind - I am going to link to this to my original thread.
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
attn1 said:
This isn't complete - this just gets you to clockwork and you having installed anything yet. You need to add steps to root or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Click to expand...
Click to collapse
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
modest_mandroid said:
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Click to expand...
Click to collapse
Excellent troubleshooting tips. I added a note about formatting your SD card to the prerequisites.
ice3186 said:
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
Click to expand...
Click to collapse
Thanks. Added a reference to your post.
attn1 said:
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
Click to expand...
Click to collapse
Noted in the original post.
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
Thanks. Added the workaround.
attn1 said:
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
Click to expand...
Click to collapse
Thanks. Added a note to the top of the prerequisites.
gtg465x said:
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Click to expand...
Click to collapse
In no way, shape or form are you done after set 12.
You need to do more than just get into Clockwork. That alone doesn't root the phone.
gtg465x said:
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
Click to expand...
Click to collapse
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
steezee said:
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
Click to expand...
Click to collapse
Dunno if you can reflash the stock recovery again if you replaced it with clockwork, but you can definitely flash the stock ATT rom again. You can download it from HTC's site: http://member.america.htc.com/download/Web_materials/Manual/HTC_Aria_ATT/HTCAriaOriginalShipROM.exe
Banging my head on the wall. Got it to detect device once on loop. Never again after that. Phone shows up in device manager. Formatted 8gb and 2 gb cards several times.
urge growing. ... want to . . break.. . . .. . .random objects. . .
attn1 said:
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
Click to expand...
Click to collapse
Sorry, I should have mentioned that he updated his update.zip.
You guys are right , there are missing step in the tutorial to fully root Aria.
after i get in to the clockwork from the step above. i have to install the custom rom that can be found in the forum.
when i try to install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . the process goes throught but the recovery is still the same HTC blue color recovery screen.
so before you insert your sd card into the phone after you format the sd card. remember to copy the rooted rom into the sd card so when you successfully get into the clockwork. you want to install the rom then your aria is rooted with superuser icon on the application.
after then you do the "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) step .
There are no steps missing from the first post. I rooted my Aria using that method. Just make sure you have the latest Root.zip from eugene's thread. He updated it the other day and if you try to use the older version of Root.zip with this method it will not work.
What you are doing is installing a custom rom, which is fine, but it's not required to root the Aria.
i was trying to get the clockwork to install and it only work after i load the liberated_aria_b003_signed.zip
before i load liberated_aria_b003_signed.zip , it still give me the default HTC recovery screen.
after i load liberated_aria_b003_signed.zip and install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . i get the clockwork screen as the recovery screen .
i still can't get the side loading to show after i follow the step from here
•COMMON:
•Enable USB debugging (settings > applications > development > USB Debugging)
•adb remount
•adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X:
•echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 settings.db
WINDOWS:
•echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON:
•adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
•Reboot phone and sideloading works. (thanks to fluffyarmada)
.
As the title says i am completely unable to boot into download mode. I gave tried every method other than adb (I can't for the life of me figure out how to use adb) and my device simply WILL NOT boot into download mode. This is a rather discouraging issue for me, since it disables me from flashing kernels with odin3...
I have tried booting while plugged in and turned off with Odin open, tried with the phone unplugged and turned off (volume down + power) and every method simply starts the phone as normal, or loops boot animations until I release the buttons. And both volume buttos +power simply leads to recovery mode.
Please help >.
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Even easier than navigating is shift clicking on the tools folder and opening the prompt that way.
Sent from my SAMSUNG-SGH-I897 using XDA App
masterofthebass said:
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
Click to expand...
Click to collapse
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
rkorzuch said:
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Click to expand...
Click to collapse
You're my hero. Thank you.
djgleebs said:
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Please next time when you have questions, post in the general. Unless you are helping with development, post it in the general with all your questions. Please also learn how to read and learn how to use the search button.
Sent from my GT-I9000 using XDA App
Why doesnt anyone read the stickies anymore??
I think the easiest way is (from rooted phone):
Open Terminal Emulator
>su <ENTER>
>reboot download <ENTER>
Easiset way is to google Android SDK. Open the folder, then open the tools folder. In there you will see adb. Drag adb onto your command window that you've opened to run commnads and then type in what you want it to do, ie: reboot recovery, reboot download then hit enter.
masterofthebass said:
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Click to expand...
Click to collapse
Step 3 is not necessary unless you are using adb push or adb pull.
Open command prompt, type command. Using ADB is not a skill. There are a whole 5 commands. adb shell, adb pull, adb push, adb reboot, and adb remount.
The rooting method for the EVO 4G is close to the same as the Droid 2, just recently created by Sebastian Krahmer at http://c-skills.blogspot.com/, but with a little variation.
Here is the step-by-step I just did on my brother's (dwizzy130) EVO 4G that came with 2.2 from Sprint.
I am NOT responsible for any damages (bricking, not working, basically anything that goes wrong) This has been tested and works. Over the next few days, I will be cleaning this post up and making the steps more clear.
Special thanks to:
Sebastian Krahmer for the exploit
dwizzy130 (my brother) for letting me test on his EVO (since I don't have one)
The unrevoked team for their methods
Toastcfh for his mtd-eng.img
Topgun966 over at evo4g.me for hosting the files
djR3Z over at TheDroidDemos.com just made a GREAT video walkthrough that should make this MUCH easier for all of you. He spent a TON of time making it yesterday, so please give him lots of thanks!
VIDEO WALKTHROUGH (2 parts)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
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.
Windows 7 Users:
Go to your start menu, then control panel. When that is open, (if you are in category view mode) click on "Uninstall a program" and then choose HTC Sync to uninstall. If you are in Icon view mode choose "Programs and Features" and then click on HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Other Windows Version Users:
Go to your start menu, then control panel. When that is open, select Add/Remove Programs, and then choose HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Next,
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 || Mirror(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)
MD5: e52f6ec4f8f5fd6dc251ef19ee19750b
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.
Step 4: Make sure USB Debugging is ON (checked) on your EVO. Go to Settings > Applications > Development > and make sure it is checked.
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.
Step 6: Open up a command promt from your android-sdk/tools folder.
Windows 7 users:
Open up the android sdk folder and hold shift and right click on the tools folder. You will see an option that says "Open command window here" Choose that one and you will be set. the command prompt should read something like C:\android-sdk-windows\tools>
Other Windows Version Users:
Go to the start menu, go to All Programs, then Accessories, and click on command prompt. Once open type
Code:
cd C:\android-sdk-windows\tools
Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.
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/
Note: the PC36IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.
Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/flash_image
Ok now for the root shell.
*
(still in adb shell)
Code:
cd /data/local/tmp
Code:
./rageagainstthecage-arm5.bin
You will now see some text on your cmd prompt screen explaining the exploit.
Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
Once that dumps you out of the shell, type
Code:
adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
now type
Code:
cd /data/local
./flash_image misc /sdcard/mtd-eng.img
that will flash your misc partition with Toast's mtd-eng.img.
This should return you to a blank line with #.
If you get an "Out of memory error" with a huge list of weird lines, here's how to fix it.
Reboot your phone normally.
Open a command prompt and go backwards in this guide until you see the big red * and start from there.
Once it is flashed correctly, move on:
Type
Code:
reboot bootloader
Remember how you pushed that huge PC36IMG.zip to your sdcard earlier? This is where that comes in handy. Once you booted into hboot, Select "bootloader" with your volume up/down buttons and hit the power button. Let it sit for a little bit while it loads the PC36IMG.zip. This can take up to 5 minutes. When it finally asks if you want to apply this zip, choose YES. (Remember, this is the same as running an RUU, so it will delete all of your user data).
If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue.
Once it is finished, select restart. You now are on the stock 2.1 build of Android.
Next step, mount your sdcard on your computer, and delete the PC36IMG.zip from it. This is because the next step requires using hboot, and you don't want to sit and wait while it loads up again, just for you to say "no" to the install. Please follow this step, for it saves 5-10 minutes of waiting ahead.
I worked extensively with Matt Mastracci, so this rooting guide will use the unrevoked method to root 2.1. This is what worked for me testing on my brother's EVO, so if you do end up trying something else to root 2.1 with, PLEASE do not post it here or ask questions, for I will only support the unrevoked team.
Now open up your web browser on your computer and navigate to Unrevoked
Choose the correct operating system to download for.
*
Make sure you install the modified android usb driver that comes with the unrevoked3 install (see the html file included when you extract the exe)
Once downloaded and extracted, run the program on your computer.
Make sure your EVO is plugged in with USB DEBUGGING ON!
It will reboot to the bootloader, and it will wait for you to use volume down to select HBOOT USB. (the last option)
After you have selected it (by pressing the power button) let the unrevoked3 program handle the rest of the flashing.
If you have had any trouble with the bootloader freezing or not moving for over 3 minutes, you most likely forgot to uninstall HTC Sync (as directed at the beginning of this guide), or you need to install the modified hboot drivers that come with the unrevoked3 program, OR a nasty combination of the both.
For the modified drivers and explanation on how to install them, open the "hboot driver.htm" file that gets extracted when you extract the reflash_package.exe. It will explain everything. You will have to reboot your phone after you install the drivers. Once you have repaired this go back to the big blue *
As soon as it is booted into recovery, you are done with that.
Next in recovery go to
Code:
install zip from sdcard
then
Code:
choose zip from sdcard
and choose the
Code:
unrevoked-forever.zip
This will flash the unrevoked forever hboot unlock.
_____________________________________________________________________
Part 2
Note: This section would not have been possible without the amazing testing and help of cilio87. He earns a gold star *
Now it's time to finish up the process and flash the stock 2.2 build of Android. You need to do this before any custom ROM in order to re-update the partitions we downgraded in the rooting process.
Step 1: Download either the update zip with
ClockWorkMod recovery included
or
Amon_RA's recovery included
This is the most up-to-date version of Amon_RA recovery that allows you to back up WiMAX partition.
(Either zip contains the final touches to the root process, one flashes clockworkmod recovery, and the other respectively, Amon_RA's recovery)
Extract the 3 files inside the zip to your desktop.
If you are still in recovery (from part one or the guide) go back to the main menu of recovery on your phone (if you aren't already at the main menu, hit vol up & down at the same time) Select
Code:
Reboot System Now
Let the Rom load, and when it gets to the sign in screen for Google, just skip everything and let the ROM boot.
If you are already on a custom rom, boot into it and follow from here.
Once It is fully booted, mount your sdcard onto your computer, and copy the 3 files you extracted from the zip to the sdcard.
Once copied, Unmount your sdcard from the computer.
Step 2: Unplug your phone from the computer. Power it off completely. Now while holding VOLUME DOWN turn on the phone with the power button, continuing to hold volume down. This will boot into hboot. You can release the buttons once you get to the hboot menu. Then use the power button to click on bootloader. This will scan the sdcard for the new PC36IMG.zip you just copied to the sdcard. When it asks "Do you want to start update?" Hit Volume Up for Yes. It will reload the zip and then start the flash. Once the flash is complete (may take 5 or so minutes) Choose NO when it asks you to reboot.
Step 3: After choosing NO to the reboot, you will see a menu again. Select Bootloader from the menu, then use the Volume Down button to hover over "Recovery" and press Power to click on it.
If your phone gets stuck at the White EVO 4G screen, pull your battery, and then power on while holding volume down again. It should boot to the bootloader again, where you can select recovery.
Once you are booted into this custom recovery, go to
Code:
Install Zip from sdcard / Flash zip from sdcard (Amon_RA)
and then (clockworkmod only)
Code:
choose zip from sdcard
You will then see the 2.2-root.zip. Click on that and accept the flash.
Once that flash is complete, return to the main menu of recovery and Select
Code:
Reboot System Now
You now have stock Android 2.2 with root and all updated partitions!
If you would like the flash_image binanry so you can flash new recovery images quickly from adb shell, flash the zip that is attached below as a normal zip in recovery AFTER you have completed this entire guide.
IN ORDER TO FLASH CM6 OR DAMAGE CONTROL, YOU NOW NEED TO FLASH THE ENG SPL. LOOK FOR IT IN THE EVO 4G ANDROID DEVELOPMENT FORUM.
Here is the ENG SPL
Good Luck!
Dan Wager
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Yes! I look forward to the rest of your post
Sent from my PC36100 using XDA App
Great news everyone!
Eagerly awaiting.
Awesome xD
Sent from my HTC Evo 4G using XDA app.
Oh thanks! Gonna be watching this all night! This is gonna be AWESOME!!
Vandam500 said:
Finally no more people asking about it
Click to expand...
Click to collapse
if only you were right...
I love the xda forums, good job to everyone involved, another reason I love my evo.
Sent from my PC36100 using XDA App
I wish I didn't just take my xanax. Ughhhh
Vandam500 said:
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Click to expand...
Click to collapse
I'll add with another question that will "end"
Will this allow me to have PRI 1.40?
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Details---
I've heard the process is more than a simple click like simple root or unrevoked... But at least we have root.
It will be nice to see the detailed failsafe guide so I don't go around bricking phones and hopefully an automated prog is made to make it a breeze.
A great help!
Having a B-day tomorrow, and have searched the month of August for a complete method to root my froyo 2.2
Thank you in advance for your expertise and assistance..
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Thank you
OMG you guys are the best devs ever ill be stuck to this like glue once again XDA is the best forum on the planet.
edufur said:
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Click to expand...
Click to collapse
no, once you get to that point you have other stuff to do.
just wait til the guide comes out... We've waited how long for this thing? an extra hour or so won't kill you. (hopefully)
Yeah, almost done writing the guide. Try not to give out anymore details yet, I should be posting the full guide shortly.
sprink0281 said:
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Click to expand...
Click to collapse
And your message is wholly important? Yes, the title says "guide" but that means that the original post will contain the guide. This is a forum, not a wiki. (I know my message doesn't help at all either)
Hooray, root on 2.2!
please make it easy for us newbies too please
Greenfieldan said:
please make it easy for us newbies too please
Click to expand...
Click to collapse
I'm getting the basics out tonight and will make it an easy read like my Hero rooting guide tomorrow sometime, because I am exhausted tonight.
i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed
Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz
OP... check your PM inbox.
Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App
scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Yes thank you guys i love u all
check your mp , excepted if you found the solution.
$100? Lol
Sent from my Nexus S using XDA App
crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App