Database Users

OTA 2.2 Update With Root Made Easy

NOTE: For those of you that are looking to root thier Inc and already have the latest 2.2+ OTA released in November, these steps will not work. Changes have been made to the ROM so until a new root application has been developed by the unrEVOked team, I am afraid you are left with a stock phone. Sorry. If new updates come out, I will try to post them here.
NOTE: I have uploaded the 2.1 and 2.2 RUUs to Rapidshare and updated the links.
First, let me say that I did not come up with this nor did I create any of the tools. I am passing all this on in a single thread to let people know how update thier Droid Incredible to the OTA 2.2 and have root access if they have it in any of the following conditions:
1. Stock 2.1 without root or unrEVOked Forever
2. Stock 2.1 with root and no unrEVOked Forever
3. Stock 2.1 with root and unrEVOked Forever
4. Stock 2.2 without root and with unrEVOked Forever
5. Stock 2.2 without root and no unrEVOked Forever
6. Custom ROM with root and S-OFF
7. Getting free WiFi Tethering on 2.2
8. Removing unwanted preloaded applications.
NOTE: This may work with custom ROMs, but I have not verified it.
NOTE: SOME PEOPLE, INCLUDING ME HAVE HAD THE PROBLEM OF BEING STUCK IN HBOOT AFTER LOADING A ROM IMAGE. IF THIS HAPPENS TO YOU AFTER LOADING THE 2.1 OR 2.2 ROM, DO NOT PANIC, JUST REAPPLY THE ROM AND ALL WILL BE FINE. FOR SOME REASON THE ROM DOES NOT LOAD CORRECTLY ON THE FIRST TRY BUT DOES ON THE SECOND.
I am passing this on because I loaded the OTA 2.2 without unrEVOked forever loaded on my phone. What a mess. I tried everything (I thought) to try and downgrade it back to stock 2.1 but with no luck. If you do not know, unrEVOked3 cannot currently root a 2.2 updated Droid Incredable and if you have not used unrEVOked forever, you can not get clockworkmod recovery to reload on the phone. I tried the 2.1 RUU to downgrade, but never could get it to connect to the phone. I then tried to use the 2.1 PB31IMG.zip to load and the HBoot loader would just tell me that it was an older image and not load it. I thought I was hosed until the unrEVOked team breaks the code on the 2.2 HBoot loader until I got pointed in the right direction (sort of).
TNS201 pointed me to the following thread: http://forum.xda-developers.com/showthread.php?t=768295
I gave this a try and still could not downgrade my phone. I searched around and after much trial and error, I was able to put together the correct steps to downgrade my phone and then applied unrEVOked3, unrEVOked forever, the OTA 2.2 update, and then reroot the phone. Anyway, here is what I have come up with:
** NOTE: THIS WILL TOTALY WIPE YOUR PHONE CLEAN!!! BACKUP ANYTHING YOU WANT BACK ON THE PHONE!!! **
Condition 1
1. Go to the following link and follow the instructions: http://forum.xda-developers.com/showthread.php?t=709220 Only do the steps for getting ADB loaded on your computer!
This will get ADB loaded on your computer which you will need when doing customizations to the phone. It will also walk you through rooting your phone and doing a lot of other things. Good thread for us noobs.
2. Download unrEVOked Forever from here: http://unrevoked.com/rootwiki/doku.php/public/forever
3. Copy the file to the root of your sdcard.
4. Reboot your phone into clockworkmod recovery and load the unrEVOked Forever zip file. This will turn S to off and allow unsigned images to be loaded.
When you reboot your phone, you will have a fully rooted and S-OFF stock 2.1 Droid Incredible.
NOTE: If you are having troubles downloading the OTA 2.2 RUU, use this link to download the ROM. Just delete the "_2.2" from the file name and go straight to step 12. http://rapidshare.com/files/418523008/PB31IMG_2.2.zip
To load 2.2, do the following:
5. Download the OTA 2.2 RUU from here: http://rapidshare.com/files/418527589/RUU_Incredible_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_1433.exe
6. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
7. Run the RUU and update your phone to 2.2. If the RUU updates your phone, go on to step 15. If the RUU will not connect to your phone Go to step 8.
8. Start the RUU.
9. Go to your computers temp directory and locate the folder that contains the file rom.zip.
10. Once you locate this file, copy it to any folder (or your desktop).
11. Rename rom.zip to PB31IMG.zip
12. Copy PB31IMG.zip to the root of your phones sdcard.
13. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip. This will take a while, so be patient.
14. Follow the instructions to have HBoot install PB31IMG.zip.
Whether you used the RUU or HBoot and PB31IMG.zip, at this point, you should have 2.2 loaded on your phone, but you will no longer have root. You will have S-OFF.
To regain root access, do the following:
15. Download clockworkmod recovery from here: http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
16. Download the payload update from here: http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
17. Download superuser from here: http://dl.dropbox.com/u/6408470/su-releases/su-2.3.4-ef-signed.zip
18. Copy all three files to the root of the phones sdcard.
19. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip.
20. Follow the instructions to have HBoot install PB31IMG.zip. Since the phone is still S-OFF, this will reload clockworkmod recovery on the phone.
21. Boot the phone into recovery and load the two zip files downloaded in steps 16 and 17. This will root the phone and reload superuser.
If all went well, when the phone reboots, it should now be loaded with 2.2 and have full root and S-OFF. Enjoy.
Condition 2
1. Do steps 2 through 21 under Condition 1.
Condition 3
1. Do steps 5 through 21 under Condition 1.
Condition 4
** NOTE: THIS ONE DOES NOT WIPE YOUR PHONE!! **
1. Do steps 15 through 21 under Condition 1.
Condition 5
This is a tuffer one and requires the phone to be downgraded to 2.1 before upgrading it back to 2.2. Anyway, here are the steps:
NOTE: YOU MUST USE THE 2.1 RUU I HAVE LINKED AND THE MTD0.IMG FILE I HAVE ATTACHED OR THIS MAY NOT WORK!!!
NOTE: If you are having troubles downloading the 2.1 RUU, use this link to download the ROM. Just delete the "_2.1" from the file name and go straight to step 5 after completing step 1 and 2 (skip step 3 and 4). http://rapidshare.com/files/418141003/PB31IMG_2.1.zip.html
1. Do steps 1 and 2 under Condition 1.
2. Download the attached zip file. It contains the files I had a hard time finding.
3. Download the 2.1 RUU file from here: http://rapidshare.com/files/418525132/RUU_Incredible_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_.exe
4. Follow steps 8 through 11 under condition 1 to get a good copy of the 2.1 ROM.
5. Copy the 2.1 ROM to the c:\android-sdk-windows\tools folder.
6. Unzip the files downloaded in step 2 to the c:\android-sdk-windows\tools folder.
7. Copy the unrevoked-forever.zip to the c:\android-sdk-windows\tools folder.
Note: At this point, you should have the following files copied to your c:\android-sdk-windows\tools folder:
PB31IMG.zip (this is the 2.1 ROM)
unrevoked-forever.zip (will set S-OFF)
rageagainstthecage-arm5.bin (this is a root exploit - gives you temperary root)
mtd0.img (need to research this one)
flash_image (this flashes images)
7. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
8. Open a command promt window and change to the c:\android-sdk-windows\tools folder.
9. Enter adb push unrevoked-forever.zip /sdcard/ and then press enter.
10. Enter adb push flash_image /data/local/ and then press enter.
11. Enter adb push rageagainstthecage-arm5.bin /data/local/tmp/ and then press enter.
12. Enter adb push mtd0.img /sdcard/ and then press enter.
13. Enter adb push PB31IMG.zip /sdcard/ and then press enter.
14. Enter adb shell and then press enter.
15. Enter cd /data/local/tmp/ and then press enter.
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
17. Enter cd /data/local/ and then press enter.
18. Enter chmod 777 /data/local/flash_image and then press enter.
19. Enter cd /data/local/tmp/ and then press enter.
20. Enter ./rageagainstthecage-arm5.bin and then press enter. 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>
21. Enter adb shell and then press enter. You will see you now have a # instead of a $ prompt.
22. Enter cd /data/local and then press enter.
23. Enter ./flash_image misc /sdcard/mtd0.img and then press enter. This will flash your misc partition with Toast's mtd-eng.img and should return you to a # prompt.
24. Enter reboot bootloader and press enter.
25. HBoot will load. Select bootloader and HBoot will then load PB31IMG.zip.
26. Follow the instructions to have HBoot install PB31IMG.zip.
Once it is finished, select restart. You now are on the stock 2.1 build of Android. Now you can follow steps 3 through 21 under condition 1 and get your phone loaded back with 2.2 and have root and S-OFF.
Condition 6
1. Do steps 5 through 21 under Condition 1.
Condition 7
The following steps will allow you to use the 3G Mobile Hotspot that comes with the OTA 2.2 update and not have Verizon charge you for using it:
1. On your phone, bring up the dialer and dial ##778. This will load EPST.
2. Select EDIT.
3. Enter 000000 for the password.
4. Select SECURITY.
5. Select the username that has [email protected].
6. Edit the username to read [email protected] (delete "dun.").
7. Click the back button to return to the list.
8. Select M.IP DEFAULT PROFILE.
9. Repeat steps 5 and 6.
10. Click on MENU and select COMMIT.
At this point, your phone will reboot and you will be able to use the 3G Mobile Hotspot application to get free WiFi tethering. Enjoy.
Condition 8
I have so far found three options for removing the preloaded apps. They all require the phone to be rooted. Here they are:
1. The first way is to get Titanium Backup. You will also need to donate (as little as $3.99) to get full functionality of Titanium Backup, but it is well worth it. If you do not want to physically remove the application, you can use the FREEZE function and the application will be removed from the app list, but physically will still be on the phone. If you really want to get it off, you can uninstall and then deleted from the phone. All of this through a user interface that is pretty easy to use. By the way, it also does backups of apps and data.
2. Another option is to get Root Explorer. You have to pay for this one. It will let you mount the system folders on the phone as read/write and allow you to move and/or delete apps from the apps folder on the phone. This is a good app and worth having even if you do not use it to remove apps.
3. The final way is to use ADB and the command prompt to remove or move any application you do not want. This is tried and true, but combersome. You do not have to buy it, but there is no GUI to help you out.
My thanks to all the folks here on XDA that made it possible for us to release the possibilities of the Droid Incredable. As I stated above, I did not create the apps or the steps, I just put them together for others to use. I wish I could thank all the individuals that made this possible, but I did not get thier IDs, so in lew of an individual thank you, I am posting this group THANK YOU. Keep up the good work!

Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?

Scblacksunshine said:
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Click to expand...
Click to collapse
No, in the case of having 2.2 already loaded and S-OFF, you are correct, the phone will not get wiped. The steps will root the phone and load superuser back on.

confirmation
Can anyone confirm option 4 working??

RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
Those are steps I used to get root back on my phone after I update to 2.2. As I stated, I messed up the first time and did not load unrEVOked forever and could not root the phone, so I had to downgrade to 2.1 first and then go through the rooting process. That time I made sure to load unrEVOKED forever. After that, all went well.
Sent from my HTC Incredible.

RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.

Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?

also Im running Ubuntu 10.04 if that makes a difference

adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked

PimpShit420 said:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
Click to expand...
Click to collapse
I tried this and it did not work for me. It looked as if it did. It gave me the proper prompt, but on reboot, no root access. I had to use chmod 777 instead of chmod 0755.

PimpShit420 said:
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
Click to expand...
Click to collapse
I made a mistake, the line should have had 777 after chmod, not 0755. I have updated the instructions. If other individuals that use 0755 instead of 777 get the above to work, let me know. I do not know what the difference is. All I know is 0755 did not work for me. I had to use 777. I think I will do some research on chmod.
Hope other individuals find this helpful.

well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots

I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue

PimpShit420 said:
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
Click to expand...
Click to collapse
This is the problem I had. Try 777 instead of 0755 after each of the chmod commands. That is what worked for me.

you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail

chmod 0755 vs chmod 777
PimpShit420 said:
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
Click to expand...
Click to collapse
Well, I looked the chmod 777 and chmod 0755 commands up. Both commands change the read/write state for a file. 0755 changes the permissions for a specific group and user. 777 changes the permissions for everyone. You can find an explanation here: http://ss64.com/bash/chmod.html
0755 did not work for me, but 777 did. I am going to keep the instructions as they are unless I get feedback that 0755 is working for other people. If I do, I will add them as an alternative.

PimpShit420 said:
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
Click to expand...
Click to collapse
Are you using 777 for each chmod command?
Also, I was reading through the steps and found an error with step 16. It said the following:
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
It should have said this:
16. Enter chmod 777 /data/local/rageagainstthecage-arm5.bin and then press enter.
I have updated the steps on post 1.

Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!

BNG303 said:
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
Click to expand...
Click to collapse
Your welcome. I am glad it helped.

bagery77 said:
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Click to expand...
Click to collapse
Glad this helped. I wanted to give everyone a one stop shop for updating and root for 2.2. Also hoped everyone would not have to go though all that I did.

Last ditch root Attempt.

Hey All.
I have a new Aria with a stock 2.2 build, and the associated Bootloader but I want to get root access to see if I can address my Bluetooth issues
All evidence points to me needing to edit /system/etc/bluetooth/audio.conf but without getting root access I can’t even read the file let alone edit it, so this is still a guess.
Any way we have lots of dodgy little phone shops around Melbourne, and odds on at least one will have an XTC clip. So what is it I actually want them to do?
I know I need to end up with a copy of su in system/bin, Is that what I am asking for? Or am is that not what is required?

FALCON-LORD said:
Hey All.
I have a new Aria with a stock 2.2 build, and the associated Bootloader but I want to get root access to see if I can address my Bluetooth issues
All evidence points to me needing to edit /system/etc/bluetooth/audio.conf but without getting root access I can’t even read the file let alone edit it, so this is still a guess.
Any way we have lots of dodgy little phone shops around Melbourne, and odds on at least one will have an XTC clip. So what is it I actually want them to do?
I know I need to end up with a copy of su in system/bin, Is that what I am asking for? Or am is that not what is required?
Click to expand...
Click to collapse
You would like them to turn security off on the phone and put it in a S-OFF state. With S-OFF, you would be able to flash a custom recovery and gain root access.

So does this mean I can't just insert the binaries i require into the existing OS?
There appear to be some one touch solutions for some ROMs (Universal Androot) wouldn't this indicate that you can just apply the binaries?

FALCON-LORD said:
So does this mean I can't just insert the binaries i require into the existing OS?
There appear to be some one touch solutions for some ROMs (Universal Androot) wouldn't this indicate that you can just apply the binaries?
Click to expand...
Click to collapse
The problem with temporary root on the Aria is the Security Flag (S-ON). As long as that is enabled, you cannot mount the /system partition in Read/Write mode so that you can push new binaries. With the Aria you need to mount the /system partition from ClockworkMod in order to push new binaries to it.

tpbklake said:
The problem with temporary root on the Aria is the Security Flag (S-ON). As long as that is enabled, you cannot mount the /system partition in Read/Write mode so that you can push new binaries. With the Aria you need to mount the /system partition from ClockworkMod in order to push new binaries to it.
Click to expand...
Click to collapse
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?

FALCON-LORD said:
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?
Click to expand...
Click to collapse
Once you s-off your phone you would leave it s-off, no need to put it back to s-on and why would you want too?
My phone is s-off, I can flash the official 2.2.2 rom and then turn around and easily get back to a different rooted rom any time I want by flashing a custom recovery followed by the rom of choice.

FALCON-LORD said:
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?
Click to expand...
Click to collapse
You cannot set the security flag on the Aria with HBOOT 1.02 via any software method. That is the reason why you cannot gain permanent root using Unrevoked anymore. On HBOOT 1.02 you can only turn S-OFF by using the XTC Clip hardware. As A$$h5t pointed out, once you get S-OFF, you do not want to turn security back on.
What I was trying to say was even if Universal Androot could get you temporary root on the Aria HBOOT 1.02, it would not be able to turn security off so and mount the /system partition in Read/Write mode.

tpbklake said:
You cannot set the security flag on the Aria with HBOOT 1.02 via any software method. That is the reason why you cannot gain permanent root using Unrevoked anymore. On HBOOT 1.02 you can only turn S-OFF by using the XTC Clip hardware. As A$$h5t pointed out, once you get S-OFF, you do not want to turn security back on.
What I was trying to say was even if Universal Androot could get you temporary root on the Aria HBOOT 1.02, it would not be able to turn security off so and mount the /system partition in Read/Write mode.
Click to expand...
Click to collapse
O.K. I think I have it now.
So you used to be able to mount the system partition on the phone with S-OFF, the change they made in HBOOT 1.02.000 is what stops it. Thus Universal doesn’t work, and you can’t play on the system partition in the same way. So not only do you now need the XTC Clip, but the options open to you even with that are still more limited than they were…
Is that about right?
[EDIT]
O.K. After re-reading I see that assessment is wrong.
It is that The Clip sets S-Off, which mounts system as rw, then anding su is a separate issue…
Wouldn’t this mean that Universal could theroeticaly work on a system where s-off has been set?
[/EDIT]

FALCON-LORD said:
O.K. I think I have it now.
So you used to be able to mount the system partition on the phone with S-OFF, the change they made in HBOOT 1.02.000 is what stops it. Thus Universal doesn’t work, and you can’t play on the system partition in the same way. So not only do you now need the XTC Clip, but the options open to you even with that are still more limited than they were…
Is that about right?
Click to expand...
Click to collapse
Almost.
Prior to HBOOT 1.02, with ClockworkMod recovery installed, it was able to temporary turn security off and on to mount the /system partition. On the Aria we were never able to get permanent S-OFF via a software solution like some of the other HTC models.
With the XTC Clip, you can now get permanent S-OFF on the Aria which will give you more options, not less options than before. With S-OFF, you are able to mount both the /system and the /recovery partition in Read/Write mode, so you can not only install new ROMs, but also different custom recovery.

FALCON-LORD said:
O.K. I think I have it now.
[EDIT]
O.K. After re-reading I see that assessment is wrong.
It is that The Clip sets S-Off, which mounts system as rw, then anding su is a separate issue…
Wouldn’t this mean that Universal could theroeticaly work on a system where s-off has been set?
[/EDIT]
Click to expand...
Click to collapse
Yes and yes.

O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?

FALCON-LORD said:
O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?
Click to expand...
Click to collapse
I believe once you are s-off you can just adb push it to /system/bin.
Also, there are 2.2.2 roms out there which are basically the stock rom already rooted and ATT crap removed if you want to stay close to stock.

A$$h4t said:
I believe once you are s-off you can just adb push it to /system/bin.
Also, there are 2.2.2 roms out there which are basically the stock rom already rooted and ATT crap removed if you want to stay close to stock.
Click to expand...
Click to collapse
The copy I have doesn’t have all the AT&T Crap, it is a generic unlocked build.
That then means the next question is where do I get a adb to push in su?
[EDIT]
O.K. Further research shows that my question makes no sense…
How do I get a copy of su to push onto the phone using adb
Any quick link to a guide to set up a dev environment and adb?
[/EDIT]
[RE-EDIT]
O.K. I now have ADB Sorted and am punting around on the phones system.
Now what?
Obviously get the phone clipped to make the system volume RW.
But that still doesn't give me the rights to push a file onto the phone, so then what? (And where do i get the file to push?)
I note that originally a version of su was on the phones that only worked from adb. for my current purposes this would suffice
[/RE-EDIT]

FALCON-LORD said:
The copy I have doesn’t have all the AT&T Crap, it is a generic unlocked build.
That then means the next question is where do I get a adb to push in su?
[EDIT]
O.K. Further research shows that my question makes no sense…
How do I get a copy of su to push onto the phone using adb
Any quick link to a guide to set up a dev environment and adb?
[/EDIT]
[RE-EDIT]
O.K. I now have ADB Sorted and am punting around on the phones system.
Now what?
Obviosly get the phone clipped to make the system volume RW.
But that still doesn't give me the rights to push a file onto the phone, so then what? (And where do i get the file to push?
[/RE-EDIT]
Click to expand...
Click to collapse
With the system in an S-OFF state, you can use HBOOT to flash a custom rooted ROM or custom recovery (ClockworkMod) by copying the associated ZIP file to the root of your microSD card and name it LIBEIMG.zip. Next time you boot into HBOOT, it will find the zip file and attempt to install it.
Once you get the Aria clipped, I would pay a visit to the Aria IRC chat room for more specifics and questions. These guys will be able to assist you on the best steps to take.
http://webchat.freenode.net/?channels=#liberatedAria

Follow the directions in this post: http://forum.xda-developers.com/showpost.php?p=13650005&postcount=67
(Not the quoted part, the part that attn1 says to do.) This should install Clockwork on your phone.
Oh, and adb is in the platform-tools folder of the Android SDK and fastboot is in tools folder.

FALCON-LORD said:
O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?
Click to expand...
Click to collapse
S-OFF alone does not make system r/w. You will still have a secure boot image.
The next step will be installing custom recovery, which is a snap once you have S-OFF. From there, you can install whatever you want on system, or flash rooted stock ROMs, or just root routines.
FYI, most people are not happy with just root access; they eventually will want basic busybox services and the ability to customize on the fly.
Come into the IRC channel in my sig if you have questions.
With Radio S-OFF fastboot flash image won't work directly, but this will work to install clockworkmod simply and easily:
Prerequisites:
HTC android usb device driver (if you use windows)
adb and fastboot utilities for your platform
Code:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip clockwork2501.zip
fastboot reboot
Download:
MD5: 5d01f06af3ce99f27d23cf8a2df47926 clockwork2501.zip

Thanks tpbklake, drumist & attn1, I think I am getting close to feeling ready to do this.
So as I see it have to do the following.
Prerequisite items
Install HTC Sync (USB Driver)
Install Oracle JDK (Prerequisite for SDK)( http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.html )
Install SDK (for ADB) (http://developer.android.com/sdk/index.html )
Get copy of clockwork.zip ( http://forum.xda-developers.com/attachment.php?attachmentid=591945&d=1305031790 )
So Once I have all of the ingredients perform the following actions
Find somewhere with an XTC clip to set S-Off
Go home and plug the phone into the PC
Copy clockwork.zip to the root of SD Card
Open a cmd prompt at adb directory (C:\Program Files\Android\android-sdk\platform-tools and enter the following commands
Code:
adb reboot bootloader
cd C:\Program Files\Android\android-sdk\tools
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip clockwork2501.zip
fastboot reboot
So from my reading it appears doing this means I can now load things onto the system partition, by copying them as a zip package onto the SD and then booting into CWM and selecting “install zip from sdcard” and this will allow me to install su.
Is that about the length of it?
So I still need a zip with su in it and then I am able to raise my privileges?

A few corrections:
1) You don't have to install the Oracle JDK for what you are doing, you can skip that step completely.
2) Don't place the clockwork.zip on the SD card. You need to have it on your computer, and it will copy the file over to your phone when you issue the fastboot command. You will want to place it in the tools folder.
3) Before you run the adb/fastboot commands, type the following at the command prompt:
Code:
path %PATH%;C:\Program Files\Android\android-sdk\platform-tools
After doing this you can run all commands from the \tools folder, including adb, until you close that command line box.
4) I believe you need the HBOOT drivers installed on your system (this is in addition to the HTC Sync drivers). Follow the installation directions here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

drumist said:
A few corrections:
1) You don't have to install the Oracle JDK for what you are doing, you can skip that step completely.
2) Don't place the clockwork.zip on the SD card. You need to have it on your computer, and it will copy the file over to your phone when you issue the fastboot command. You will want to place it in the tools folder.
3) Before you run the adb/fastboot commands, type the following at the command prompt:
Code:
path %PATH%;C:\Program Files\Android\android-sdk\platform-tools
After doing this you can run all commands from the \tools folder, including adb, until you close that command line box.
4) I believe you need the HBOOT drivers installed on your system (this is in addition to the HTC Sync drivers). Follow the installation directions here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Thanks Drumist.
The SDK package wouldn’t install without the JDK installed, so that is why I have added that in, I have changed my steps for where to put clockwork, thanks for the line on path (I should have done that initially…)
Once I have done all of this then I take it I follow some instructions like these?
http://geeknizer.com/how-to-root-motorola-droid/
can I use the su package they have linked there? It looks like these instructions were written for a much earlier droid release.
I take it if that is correct it will look more like this..
Code:
cd C:\Program Files\Android\android-sdk\platform-tools
adb push su /data/local
adb shell su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin mv su osu
cat /data/local/su > su
chmod 6755 su

I'm not sure what the best method is to root an unrooted ROM. My personal recommendation is to just install one of the ROMs from this site that already have root. You can always make a Nandroid backup first in case you don't like the subtle differences between those ROMs and the one you're using now.

[GUIDE] Desire Z/G2 Rooting and Flashing Firmware for Noobs

Hey guys, i rooted my Desire Z with these Tutorials out there and i recognized not everything is that clear and easy to understand if you are a noob like me with this stuff. First i want to say that im from austria and so please ignore when my english is not that good.
Now just start here. When you are done with that all you can have any rom running on youre phone, but i recommend the ones designed for the desire z.
>>> Click here to read the full tutorial on my website with fast download links. ;D
!!! BEFORE YOU START YOU MUST CREATE A BACKUP OF ALL YOR DATA YOU HAVE ON YOUR PHONE !!!
Don't worry, youre friut ninja scores are still on feint.
1. First you will have to install ADB. If you have it skip that part.
Just head over here: http://developer.android.com/sdk/index.html
Download the .zip archive and extract "android-sdk-windows" to C:\
Now run SDK Manager.exe and let it install everything. This could take looooong hours...
2. Now you have to check the infocid of your Desire Z. Make sure the developement mode is turned on (USB-Debugging).
Open up a cmd window on your PC (Windows Key + R and type "cmd") and type:
Code:
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
If your INFOCID doesnt match the following you'll need a goldcard to continue (Get it here: http://forum.xda-developers.com/showthread.php?t=832503 ).
Code:
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
3. So now you have to download 3 Files:
>>> http://wede.devftw.com/downloads/psneuter
>>> http://www.multiupload.com/A9PNGVBWBE
>>> http://www.multiupload.com/9L618DJVR6
Broken link? Click here: W3D3 @ devFTW
IMPORTANT! When you save psneuter remove the txt file extention, it should hav none!
4. Extract the file misc_version from misc_version_01.zip (just downloaded in step 3). Just ignore the rest. Put that file to C:\android-sdk-windows\platform-tools.
5. Get the PC10IMG.zip from here: http://www.multiupload.com/GH26HXLLES
6. Now you open the cmd again and type following commands: (type cd C:\android-sdk-windows\platform-tools first if youve closed the window)
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
7. Congrats if you now see a #! You now have root access.
If you see a $ something went wrong here. Just go back to step 1 and check youve done everything right.
8. Beside the # type:
Code:
/data/local/tmp/misc_version -s 1.33.405.5
exit
9. Now copy the 1.34.405.5_PC10IMG.zip to youre phone's SD card (Download in step 5) and rename it PC10IMG.zip
10. Now boot youre phone's bootloader with following commands:
Code:
adb reboot bootloader
Or you can just switch youre phone off. Switch it on again while you press the power button and the trackpad together.
You now see the bootloader screen with the 3 android skaters on the bottom.
11. Select BOOTLOADER.
Wait a few seconds.
Then the Bootloader will load our PC10IMG.zip
When asked for update press VOL UP to confirm.
Now wait and restart your phone when prompted.
12. When you check your version at your phone now it should say "1.34". Youre desire z is now downgroaded.
13. Enable USB-Debugging again.
14. Extract the contents in root.zip to the platform-tools folder.
15. Now type that in cmd:
Code:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
16. Start the new app "Terminal Emulator" on your phone and type:
Code:
/data/local/tmp/rage
After a while you'll see the message: "Forked [number] childs"
Press MENU > reset terminal
The terminal will close.
Start it again. It will force close.
Start it again. You should see the # sign again.
Beside it write following:
Code:
/data/local/tmp/gfree -f
After that type:
Code:
/data/local/tmp/root
sync
This will root your phone. When you get that message "mkdir: /system/xbin already exists", don't worry everything is ok.
After that restart your phone.
17. Install ROM Manager from market. Install The ClockworkMod Recovery.
After that you should go to "restart to recovery-system"(or similar) and from there you chose Backup/Restore and create a backup from your current rom.
(Note that you chose with the trackpad in Clockwork and not with the power button like in the bootloader)
When that's done you can come back to that status everytime you want.
(How to Restore when something isnt working:
- Start the device with trackpad holded.
- Chose Fastboot in Bootmanager. (if he asks for update again you forgot to remove the PC10IMG.zip from your SD)
- Chose Recovery
- ClockworkMod Recovery will show up
- Go to Backup/Restore and chose your Backup to restore
- Done. )
18. In RomManager chose Download ROM or install from SD card when you've found a ROM you like.
19. When it's done loading and there is a small window with 3 points make sure the 3rd AND the 2nd is chosen! if you forget to chose the 2nd point youre phone will make bootloops!
ENJOY your rooted DESIRE Z!
(Credits go to g4rb4g3 for the great solution of downgroading)
Please hit Thanks if you liked the Tut.

i recommend visionary/gfree no adb but to each his own
pimped out g2

The visionary-gfree no-adb method is awesome.. used it myself. But doesn't really apply to the Desire-Z, which is what the OP has.

killswitch11 said:
The visionary-gfree no-adb method is awesome.. used it myself. But doesn't really apply to the Desire-Z, which is what the OP has.
Click to expand...
Click to collapse
Yes it does, i have one, and it worked perfect for me

oh snap!! my bad..all i saw was g2 root...score 1 for killswitch
pimped out g2

I heard that there is a high brick risk using visonary?
Sent from my HTC Vision using XDA Premium App

only for permroot
pimped out g2

I permrooted my desire z with the tutorial above and everything is working fine - i tried visionary before but didn't worked for me.
Sent from my HTC Vision using XDA Premium App

Thanks, rooted my bell desire z with this guide.

pretty exhausting explanation. A big thank you....

How different is this from the guide in the wiki?

slapshot30 said:
How different is this from the guide in the wiki?
Click to expand...
Click to collapse
Hi!
It's similar to the wiki method but uses older versions of the tools and some tools and procedures are redundant (i.e. using psneuter for temp-root to downgrade but rage for temp-root during the gfree procedure).
If you know how to use adb, follow the wiki, if not follow the visionary temp-root plus gfree guide that is somewhere around here.
Have fun - Guhl

backarelli said:
pretty exhausting explanation. A big thank you....
Click to expand...
Click to collapse
Infact, it is a concise tutorial
You dont need to open many links just to know how to root.. unlike the time before this thread exist
Thanks to the OP

Glad you all like it
Sent from my HTC Vision using XDA Premium App

Hi,
I got a question before I jump off the bridge and root/flash/stress.
My phone is still on the branded bellmobility firmware, but it is unlocked. Since I only want to get rid of bell stuff and install an official HTC WWE ROM, do I have to follow your guide and root the phone to flash it ? Or can I follow only the flash part and flash an official ROM without rooting ?
Thx

I was able to root my girlfriend's G2 that was still on 2.2 by using this method:
http://archive.rootzwiki.com/index.php/Smartphones/HTC-Corporation/HTC-Desire-Z/G2.html
My coworker recently got a replacement G2 and it shipped back to her with 2.3 on it. We're just wondering if we're able to use the same perm root process that we used for my girlfriend's G2 (2.2)

If u dont want to permroot but u want roms I suggest u at least temp root using visionary, z4root, or one of the othrr one click methodz. If u browse the forums people have gottin into trouble not bein rooted. Then if u dont like it u can reboot and itll go back

ElNiNi0 said:
Hi,
I got a question before I jump off the bridge and root/flash/stress.
My phone is still on the branded bellmobility firmware, but it is unlocked. Since I only want to get rid of bell stuff and install an official HTC WWE ROM, do I have to follow your guide and root the phone to flash it ? Or can I follow only the flash part and flash an official ROM without rooting ?
Thx
Click to expand...
Click to collapse
You can also use temproot which means that you can use all the root functions (flashing included) till you reboot.
I thought of that method before but when you wanna play around with the different roms to find out which is the best permroot would be great. (Look @ the guide)
I dont know much about temproot so just head over to another thread in xda to find out more about that method.
Its your choise.
Sent from my HTC Vision using XDA Premium App

letsgophillyingeneral said:
...
My coworker recently got a replacement G2 and it shipped back to her with 2.3 on it. We're just wondering if we're able to use the same perm root process that we used for my girlfriend's G2 (2.2)
Click to expand...
Click to collapse
Hi!
No, the 2.3.3 version that T-Mobile/HTC are shipping as replacement (by accident) are not rootable at all (at the moment).
There is currently no published temp-root method for this release and therefor it can also not be S-OFFed or perm-rooted.
Have fun - Guhl
Sent from my HTC Vision using XDA App

I have been thinking about rooting my desire z for a while now, just made a backup.
got the android sdk, and adb working, but i cant get the infocid, "fastboot oem boot" doesn't work? why? what to do?
well just skipped the part, worked just fine whit out goldcard. i'm rooted now

desire hd build 2.36.405.8 downgrade problem

using method in http://forum.xda-developers.com/showthread.php?t=905003
Uploaded with ImageShack.us
can't do anything else.

Do a factory reset and try again.

Done
i do a factory reset but the same problem

Try using another SD card, make sure to format it first

And don't give up. I had to repeat this procedure many times with three sd cards, and after a few hours it finished successfully

hey ı have same problem but I make this 3 times another SD card but still I didn't downgrade

Try this steps:
a. Download 'Downgrade_v2.zip', extract it and place into C:\ (for example, C:\downgrade\).
b.
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
c. If you see "#", you got a temporary root!
d. Enter:
cd /data/local/tmp
./misc_version -s 1.31.405.6
e. Next, you must download PD98IMG.zip and put into SD card (don't extract it or put in folder!)
f. Reboot your Desire HD and hold VOL-
g. Choose 'Yes' and downgrade is begin!
I checked this steps and my Desire HD is downgraded successfully.
-----
Downgrade_v2.zip - multiupload .com / OYKBRXIYT2
ROM for downgrade to 1.32 - multiupload .com / BTJ8KY0KH9

suroegin said:
Try this steps:
a. Download 'Downgrade_v2.zip', extract it and place into C:\ (for example, C:\downgrade\).
b.
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
c. If you see "#", you got a temporary root!
d. Enter:
cd /data/local/tmp
./misc_version -s 1.31.405.6
e. Next, you must download PD98IMG.zip and put into SD card (don't extract it or put in folder!)
f. Reboot your Desire HD and hold VOL-
g. Choose 'Yes' and downgrade is begin!
I checked this steps and my Desire HD is downgraded successfully.
Click to expand...
Click to collapse
I did not see # I made everything but it didnt start i will be record a video to show this problem

youtubecom/watch?v=itf8dWTFqII

same problem!!! dunno what to doo

same here error: device not found
any solutions?

ahmettuncez said:
http://www.youtube.com/watch?v=itf8dWTFqII
Click to expand...
Click to collapse
Just watched this.
Either,
a). Your firmware is not 2.36, likely 2.37/2.42 - you can not downgrade yet.
b). You need to do a full factory reset and try again - same happens --> read a).
c). Your not waiting long enough can take 30 seconds - 5 minutes - try b). then read a).
@johi69 - a "device not found" error simply means,
a). plug in your phone
b). you do not have the android SDK installed - install it
c). you do not have USB debugging enabled - enable it - Settings > Applications > Development.

Does built number 2.36.405.8 means 2.37???
and what happens with the phone if you try to downgrade and fails is everything back as it was?

pahildo said:
Does built number 2.36.405.8 means 2.37???
and what happens with the phone if you try to downgrade and fails is everything back as it was?
Click to expand...
Click to collapse
no, 2.36 is ok, it's not 2.37
if you fail, nothing is gonna happend(before i downgrade, i've tried at least 5 times)
just follow the steps, one by one, and I'm not responsible if you brick your device, do at your own risk but if you follow all steps, and you know what you are doing, it should be safe, for me it was.
before you start downgrade, do a factory reset of your phone.
links to downgrade:
http://forum.xda-developers.com/showthread.php?t=905003

Help Looked at wiki and stickies: Unrooting without Windows or USB?

The USB port on my ph is broken so I need to send it back. In addition, I don't know ANYONE with a windows machine. So far I've restored stock ROM and factory settings with P10IMG.zip, but I still have S-OFF. I think I rooted with Gfree. When I look at the wiki, it looks impossible without a windows machine and working USB port. What are my options? is there a slightly older stock rom that will auto unroot my ph and allow me to upgrade to 2.2. I'm afraid if I try to flash gingerbread in order to gain S-on, they'll take one look and charge me 500 bucks.

generally speaking as long as the problem isnt root related (ie broken usb) they wont charge you.. i didnt do gfree so i cant say exactly how to s-on

Thanks, I'm still trying to get it S-on.... I hope you're right about them not caring but since I'm returning it under warranty and not under insurance... I'm nervous. Me and Murphy's Law don't get along so well.

http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
If you have access to a microsd to sd card adaptor, a different phone with a working usb port, or if you have root explorer (which you should have) you can do everything in that guide to return to stock.
A pc and adb is not required for this guide. Its just convient.
Sent from my HTC Vision using Tapatalk

PanCubano said:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
If you have access to a microsd to sd card adaptor, a different phone with a working usb port, or if you have root explorer (which you should have) you can do everything in that guide to return to stock.
A pc and adb is not required for this guide. Its just convient.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
I've read the portion I would need to do "Alternative: Use gfree to get radio S-ON and the original CID" a gazillion times and honestly, it's like reading greek. I have no idea how I could do that process using my good ph and a sd card. Can you elaborate... with stupid simple instructions

I'm still unable to figure this out. The wiki instructions are:
ON YOUR PC:
Unzip gfree_06.zip to a place on your computer. Open a terminal or command window, navigate to where the files are on your computer, and type:
$ adb push gfree /data/local/tmp/gfree
$ adb shell chmod 777 /data/local/tmp/gfree
gfree should now be in your phone at /data/local/tmp
IN THE ROOT SHELL (in the first terminal/command) : Now run:
# /data/local/tmp/gfree -s on -c T-MOB010
# sync
I put Gfree on the root menu of the sdcard since I can't figure out how to put it /data/local/tmp/gfree without a USB or ADB. Changed the command to
/sdcard/gfree -s on -c T-MOB010
and, I get permission denied *sighs* I don't know what to do.
I have the temp root using visionary instead of psneuter because the wiki said, I needed to Temp root prior to unrooting and the psneuter instructions were for adb. Every seemed okay but I guess not. Any idea where to go from here?