*SOLVED* please suggest ....STRUCK IN BOOTLOADER - G1 Android Development

my g1 was running smooth on 1.42 jesus freak rom.
then i have appplied unsigned 1.1 holiday version on it.
it got installed but while making a call it show a error and the dialer crashes.
so i thought of going back to 1.42 jesus freak , but it was not successful.
then i tried to apply rc 29 using dreaming.nbh file ,even it failed .
NOW I AM STRUCK IN BOOTLOADER MODE.
CAN ANYONE HELP ME TO GET OUT OF THIS BOOTLOADER MODE.I HAVE TRIED press CALL + MENU + END to leave the bootloader.IT DID NOT HELP.
THANKS IN ADVANCE.

Hi,
Sounds like your system is corrupted.
You can try the rc 29 using DREAIMG.nbh.
Do the following copy the DREAIMG.nbh to a blank fat 32 memory card.
Turn off your phone.
Put the memory card in your phone.
Hold the camera button in and power on your phone.
See if it will install the rc 29 that way.
By the way DREAIMG.nbh is the correct spelling of the file.
Post the results.

thank you
Yes I m able to load rc29.
Can guide me to load 1.1 holiday developers version ?
Thankz in advance.

Hope this helps you
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
And now, the last step! You are still running an old version of Android, but you want to upgrade to the latest and greatest update! You can do this, and not lose root by downloading modified versions of the updates.
First, choose a modified image from the list below:
ADP Holiday
1. Download the image.
2. Rename it to update.zip.
3. Copy it to your phone's SD card.
4. Turn your phone off.
5. Start up in recovery mode by holding Home and pressing Power.
6. Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
7. Press alt-S to apply the update.
And that's it! Remember to check the links up top to learn how to use root to do the advanced things I mentioned.
Click to expand...
Click to collapse

** breaking news****
Man struck in head by a "BOOTLOADER" g1 users beware.... j/k
I couldn't help it

bhang said:
Man struck in head by a "BOOTLOADER" g1 users beware.... j/k
I couldn't help it
Click to expand...
Click to collapse
Haha!!
Made XDA Headlines

thanks .problem solved'
bestwebs said:
Hi,
Sounds like your system is corrupted.
You can try the rc 29 using DREAIMG.nbh.
Do the following copy the DREAIMG.nbh to a blank fat 32 memory card.
Turn off your phone.
Put the memory card in your phone.
Hold the camera button in and power on your phone.
See if it will install the rc 29 that way.
By the way DREAIMG.nbh is the correct spelling of the file.
Post the results.
Click to expand...
Click to collapse
thank you. the problem is solved.

Hi,
Glad to hear it is working now.

Related

Rooting your G1 made easy.

Download this file RC30 or this one for RC8, extracted all the files to the root of the SD Card. Shut down the phone and turn it on holding the power and camera button. Follow the instructions on the phone to downgrade to RC29/RC7. Once you're on RC29/RC7 it's time to install the test keys.
Reboot the phone, When it has finished booting hit enter twice and type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
Code:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself.
switch off the phone again and then hold down the home key while you switch it on. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install the modified firmware by hitting Alt-S. You should now be on JF 1.41 RC30/RC8. Enjoy...
*Optional but highly recommended*
To install the modified bootloader rename Hard_SPL_update.zip to update.zip and switch the phone off and then hold down the home key while you switch it on again. Keep the home key held down until you see the new recovery menu, hit Alt-S to apply the new bootloader. Congrats you now have the modified bootloader with the skating androids.
You can only see the skating androids when you power up holding the Power and Camera buttons, it replaces the multicolor recovery bootloader. The boot loader allows you to use fastboot in recovery mode. Once you've done with the files on the SD card they can be discarded.
Source
root of the sd card?
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
ritz256 said:
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
Click to expand...
Click to collapse
you can't turn on USB
ritz256 said:
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
Click to expand...
Click to collapse
The root of the sd card is the same as "F:\" in your example. When you transfer the file, put them on the f: drive, without putting them in any subfolders. Only use one update at a time. To check to make sure they are written to the sd card, use one of the file manager apps available from the market and make sure your usb cable is not in the phone. If you are on a wireless network, you may want to look at getting Discover form the market. It will allow you to do wireless file transfers to/from the sd card.
without the links to the files the original post is fairly pointless and confusing. Should have just linked to the other forum and left the copy/paste job out.
i tried this and every single time i turn on my g1 is goes to the tri colored bootloader screen and it wont even go to recovory mode.... any solution?
recovery would be booting holding down home and power key.
Not camera and power

[GUIDE] Rooting and flashing your patched Hero. (Windows) [Updated: 12/19]

Constructive criticism is welcome.
This is my first guide and it's quite late here so I'm going to go through this lightly first, and more in detail later.
Note: I am NOT responsible for any damage your phone may or may not receive. It is your fault for following this guide, not my fault for writing it. Just for the sake of saving you from a headache, I would recommend backing up your contacts before starting this guide.
Phase 1: Prepping your CDMA Hero for rooting/flashing.
1. Ensure that USB debugging and installing apps from unknown sources is enabled. You can do this by going into Settings> Applications Check unknown sources. From there go into Development and ensure that "Enable USB debugging" is checked.
2. Mount your SD card on your computer by plugging in the USB cable, and dragging down the notification area. BACKUP YOUR DATA! ALWAYS!
3. After your data is backed up, Safely remove hardware (I find it annoying to get the "this disk may contains errors" every time i plug it in) your Hero. Using your notification area, unmount your SD card.
4. On your hero, navigate to Settings> SD card and phone storage> unmount SD card. Then format your card. It should Auto re-mount after this.
5. Download FlashRec (great tool!) and Amon-RA's recovery image. Place them onto the root of your SD card (not in any folders, just drag and drop them.) Unmount your SDcard.
6. I used Linda File manager (from the market), but you can use one of your choice. Navigate to the root of your SDcard (you'll probably start there, if you dont just click sdcard.) Open flashrec with the installer, and wait until it's finished.
7. Open FlashRec, and attempt to make a backup (i simply named mine "/sdcard/backup"). If it success proceed to the next step. if not, refer to post 2.
8. In FlashRec, type "/sdcard/recovery-RA-heroc-v1.5.2.img" without the quotes. Linux is Case-sensitive, so the capital letters have to be included. tap "download recovery image". Wait for it to finish, when it does reboot into recovery mode by powering off your phone. After it's off, hold HOME and the power button. You should see some green text on a black background.
9. First things first, Make a nandroid backup. It can, and will save your ass at some point in time. Before you flash ANYTHING to your phone, ALWAYS do a nandroid backup. Congratulations, you can now flash a custom ROM!
Phase 2:Flashing your custom ROM
Since I love Flipz and his work so much I'll be using his ROM in my guide (let me know if you have a problem with it Flipz).
0. Do a nandroid backup before you even think about downloading a ROM
1. Download Fresh 1.0.
2. Do not unzip it, leave it as it is and copy it to the root of your SD card. You can do this either from recovery mode (by enabling usb mode) or through the notification bar. Proceed to recovery mode by holding HOME+END CALL (or just disable USB mode) and select "flash update from .zip" Select the Fresh ROM and wait. It should automatically reboot after it finishes installing.
3. Be patient while it's booting, it took me about 5 minutes for the first boot, after that it gets much faster. Once it loads, everything should be all fine and dandy. If it's not, well aren't you glad you made your backup? Just proceed back into recovery and do a nandroid restore.
4. You can now delete all those .apks and .zips and whatnot. Mount your SD card on the computer, and move your backed up files back onto your card.
5: Enjoy! If you don't like the clear lock, Flipz has a patch on his website (geekfor.me) to replace it with a clear screen. This should keep all of your contacts and settings in place, but I make no promises.
Sources:
The Unlockr
How to unpatch your Sprint CDMA Hero.
Phase 1: Installing the SDK/Drivers
1. Download the SDK from Google. Create a folder at the root of your C:\ drive called android (it doesn't have to be your C:\, you can put it anywhere, but this guide will use "C:\android" as it's path.)
2. If using Windows Vista or earlier, proceed to the next step.
3. Download the driver for your system.
Windows 7 32Bit
Windows 7 64bit
To find out which drivers are right for your system, go into your control panel, and change the view type to small icons. Click on system, and check and see if it says 64-bit Operating System or 32-bit Operating System. Extract the contents into:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x64 (for the Windows 7 64-bit)
or
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x86 (for the Windows 7 32-bit)
4. If you have not plugged your Hero into the computer yet, it's as simple as navigating to where you extracted the contents of the archive, and right clicking androidusb.INF (should be the second from the top) and clicking install.
5. Ensure that USB debugging is enabled by navigating to Settings>Applications>Devolopment. If it does not have a check next to it, tap it. Plug your phone in and wait for the drivers to install.
6. In Windows, navigate to the command prompt.
XP: Start>run type "cmd" and press enter.
Vista or later: Start/"orb" in the search box right above it, type "cmd" and press enter.
if you see a window pop up with "C:\Windows\system32\cmd.exe" if you have done this correctly.
7. type "cd \android\tools" and press enter. now type "adb devices". It should start a daemon, and show you a series of numbers. If it does, then congratulations! your drivers are installed properly! I'll come back and add later how to reinstall the drivers if they do not install correctly.
Phase 2: Unpatching your Hero
Ensure that you have an adaptor to plug your SDcard into your computer. I didn't use an adaptor when i did this, but I highly recomend it just to make things easier. If your phone or SDcard or computer or toaster blows up, catches fire, shoots lazer beams and burns your curtains, or causes any damage to your or anything else I take no responsibility.
1. Backup all of the data from your memory card onto your computer. Navigate to Settings> SD and phone storage. Unmount your SD card and format it.
2. Go to Settings> Applications> Devolopment and ensure USB debugging is enabled.
3. Open command prompt, as you did in Phase 1, and navigate to "C:\android\tools". Type "adb shell" and press enter. Now you're in your phones console. Type "cat /sys/class/mmc_host/mmc1/mmc1:*/cid"
4. Copy down the code you get EXACTLY. Double, triple, and qraduple check. If the code is wrong, you may destroy your SD card.
5. Reverse the code.
Example:
123456789
Would become
987654321
6. replace the first two numbers/letters with zero zero. (007654321). Now on your PC, navigate to Here. Copy the number (with the zeros in place!) to the box that says CID. Click continue and wait for the email with your goldcard key. Save it to your computer.
7. Download this hex editor and install it. run it (requires administrative priveledges), and put your SDcard into your computer, or mount your SDcard.
8. In the hex editor, click on the extra tab, and open both your SDcard and the Goldcard you downloaded earlier. Ensure that "Open as read only" is unchecked when you open your SDcard. Sector size should be at "512 (Hard Disks/Floppy Disks)".
9. Go to the Goldcard tab, and press Ctrl+A to highlight all of it, then press Ctrl+C to copy it. Go to your SDcard tab, and select from 00000000 to 00000170. Now click on the edit>paste write.
10. click File>save. Remove and replace your SDcard, or unmount and remount your phone. If you can navigate into the drive, congratulations you have a Goldcard.
Phase 3: Downgrading your Hero.
1. Download the1.29 RUU. Plug your phone into the USB port with your goldcard inserted. Have your phone powered on when you do this, and ensure that it is not locked.
2. Ensure that you have HTC Sync installed, and that it connects to your phone.
3. Run the RUU and wait for it to finish. After it is finished, proceed to post 1.
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
saintirish said:
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Click to expand...
Click to collapse
As far as I know, you just have to reinstall your programs. This guide will also work for loading ROMs other then Freshhh, but some ROMs require you to do a wipe before you install them. Check to see if that specific ROM requires a wipe before doing an install. Yes, I have used this method to upgrade from RA's 1.2.3 to 1.5.2 with no problems.
@_Chris_Kirkland said:
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
Click to expand...
Click to collapse
I have no idea about Droid modding, as I don't have a Droid. I'm not to fond of the idea of writing a guide for a phone I don't have because I wouldn't be able to verify that it works with minimal problems.
Alright, I've completed the basics of how to do this. I'll add a problems and solutions section once people start having problems.
great job, this should help folks out a good deal.
That's my intention. Just trying to make things easier for those who aren't so good with the console. I think I'm gonna go ahead and do the Win7 driver workaround now.
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
jfoster38122 said:
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
Click to expand...
Click to collapse
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a custom rom that I could downgrade to 1.29 or is there something different now?
mark920 said:
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a customer rom that I could downgrade to 1.29 or is there something different now?
Click to expand...
Click to collapse
This is a guide to try and simplify patching, but it also covers a section on how to downgrade a phone that Sprint/HTC patched so that the 1.29 RUU method wouldn't work.
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
mark920 said:
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
Click to expand...
Click to collapse
Ether get a newer Hero, or run the software update in the phone. I ran the software update >_>
abcdfv said:
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
Click to expand...
Click to collapse
Once I enter the recovery image in, the 2 options are "Flash Recovery Image" and "Restore Backup Image"
There's no download recovery image option.
- JustPyro
It may have been updated since I used it... I'll look into it
EDIT: Click on FlashRecovery image.
Excellent work! I just want to let you know that the link for the RUU 1.29 does not work (at least for me). Great guide though.
Link updated.

OBSOLETE.

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.

New clarified method for rooting the HTC Aria (for those who are having trouble)

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)
.

[GUIDE] How to root Android 2.2 on the EVO 4G Outdated

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.

Categories

Resources