Noob questions regarding Hasoon2000's All-in-one toolkit and rooting/installing ICS

Noob questions regarding Hasoon2000's All-in-one toolkit and rooting/installing ICS - HTC Amaze 4G

Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!

Flipnfr3ak said:
First welcome..I use to be an iPhone user also...before even starting update to ics. It should be available ota. Yes it has to be connected to you pc make sure usb debugging is on. Hasoon has the instructions in his post. But you have to be in bootloader screen. Use 4ext for recovery. Then root....you should be good to go. Make sure you make a nandroid backup
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply! Every time I manually search for the OTA update, it says "There are no updates available for your phone.", so I unfortunately can't update it OTA. I'm very new to all of this, so I don't know the terminology for a lot of the things on the forum. How do I make sure usb debugging is on and also what is a nandroid backup? Also, am I supposed to be on the bootloader screen the entire time?

Kashif92k said:
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Click to expand...
Click to collapse
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC http://www.filefactory.com/f/40bba0821a54f264/
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."

badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.

yes so first before rooting or unlcoking anything download your carriers ruu but it in you sd card and boot to boootloder (vol down + power button) it will install then use hasoon tool kit to unlock boot loader then flash 4ext recovery then root then flash rom

Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
Crashdamage:can I use the same process to go back to the original stock ROM prior to any OTAs? And here is why I want to do that.
I got my phone in January 2012. I received a message about an OTA. I did the update. My Plantronics Voyager Pro and 2-Explorers came in. I tried them out on the phone and the reception and range were completely horrible. 1-2 Ft. the Explorers had slightly better sound quality.
After some research on t-mo forum I found that there were others with the same problem. (The first Product Review that complains about Bluetooth issue was December 17, 2011. The first OTA was released on December 12, 2012. Coincidence?) Some of the people said their BT worked fine prior to the first OTA. T-mo's corporate line was "ICS will fix everything." I waited for ICS as long as I could and did the "Leaked ICS."
ICS did not fix the problem....but it did improve it from 1-2 Ft. to 8-10 Ft. It still has quite a bit of static. Therefore because ICS did improve the problem, I want to test the theory that everything was fine with the original ROM. Kind of a "test the theory" and "process of elimination."
Any help form you and the community will be greatly appreciated. I hope at the end of this I can take my findings back to the others that are having this same problem...some of them that have done multiple handset exchanges and still have the problem. -THANKS-

My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.

Dark Nightmare said:
My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.
Click to expand...
Click to collapse
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.

badgerdave said:
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.
Click to expand...
Click to collapse
Not that no one believes in you, but think about this for a minute, many contributors, devs and regular users alike here saw the issue many were having, saw how complicated getting things done were, so we put as much time into making this all simple, I'm talking months of work, endless hours of typing and research to simplify things here, so for you to say you're unable to find things here, that kinda hurts, I myself worked on making the ICS update as simple as possible, I've posted multiple times, more than I can count on how to fix soft bricks and how to restore to complete stock, so you can tell how hard it is to believe when people say we're not helpful and we don't make things simple, if you have a question, ask it flat out, I'll be straight with you that I know what you read and did not read, I can tell you exactly where everything can be found for this device and I've been here a mere month or two, you know what? It's pointless, no point in me saying anything anymore, I guess I should just follow suit of every other contributor around here and just move on to another device like they all did/doing.
So have a nice day, if you can find what you're looking for in the amaze bible thread, PM one of the writers, sure they'd be glad to help, they always have been and always will be very nice helpful individuals.
New motto: I am officially out of the amaze forum.

badgerdave said:
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."
Click to expand...
Click to collapse
Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?

Kashif92k said:
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?
Click to expand...
Click to collapse
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.

Dark Nightmare said:
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.
Click to expand...
Click to collapse
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.

Kashif92k said:
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.
Click to expand...
Click to collapse
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.

Dark Nightmare said:
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.
Click to expand...
Click to collapse
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:

Kashif92k said:
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:
Click to expand...
Click to collapse
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.

Dark Nightmare said:
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.
Click to expand...
Click to collapse
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reason: oem-00...
Also the the background is black with the red triangle error and the text is in yellow.

Kashif92k said:
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reasonem-00...
also the the background is back with the red triangle error and the text is in yellow.
Click to expand...
Click to collapse
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.

Dark Nightmare said:
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.
Click to expand...
Click to collapse
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?

Kashif92k said:
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?
Click to expand...
Click to collapse
just PH85IMG, don't worry about the .zip part, it's already there, just not visible, no do not use the same steps, follow the steps I outlined above when I specified the file and what to do with it.

Related

May have bricked my eris

I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).

wolfpack10 said:
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
Click to expand...
Click to collapse
Try installing the engineering Bootloader. Instructions can be found in a sticky called Eris roll-up in the Eris developement section. Even if you can't flash a custom Rom after this you can still flash the official 2.1 ruu which will put your phone back to 100% stock and you can try again.
If your rooted and can still boot to fastboot your not bricked.
Sent from my Eris using XDA App

If the bootloader still appears (power phone on with vol-down+end), your phone is not bricked.
If the recovery boot still appears (power phone on with vol-up+end), your phone is not bricked.
If you don't have a SD card reader on your PC, you can transfer a different ROM to your SD card by booting to recovery and using the USB-MS toggle.
Smart money says that all you failed to do when you installed the ROM was perform a wipe before you flashed the ROM.
Prove this to yourself by installing a conservative ROM such as PlainJane, and when you get it running, for Dog's sake, make an effing Nand backup.
bftb0

I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.

wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
Do you still have ra recovery? If so simply boot to recovery, wipe data and cache and reflash the rom.
All the 1 click root does is flash the custom recovery, so it did work.
Fyi
The Eris can now be rooted no matter what Bootloader version you have so doing the ruu will not prevent you from rooting. I myself was a leaker and had no problem rooting with the 1.49 s-on Bootloader.
As stated by btfb0, ALWAYS wipe data and cache before flashing a new Rom. ALWAYS do or have a nand backup ready just in case.
Sent from my Eris using XDA App

wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Click to expand...
Click to collapse
If you see the text "S-OFF" at the top of the screen, that is the bootloader, not the recovery boot. The one-click rooting method does not touch the bootloader, so, after successfully using "one-click", you will still have the same bootloader (initially).
wolfpack10 said:
Can I actually install alternative bootloaders on an unrooted phone?
Click to expand...
Click to collapse
You can install the Root PB00IMG.ZIP file onto a 1.46.xxxx or 1.47.xxxx bootloader phone - but you don't need to, because your phone already has a custom recovery installed on it (Amon_RA). As I mentioned previously, you get to that recovery facility by one of two ways:
1) Power phone off. Press and hold Vol-Up and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu system should appear 10 seconds after that happens. It will say "Amon_RA" on the bottom of the screen.
2) Make sure there are no files named PB00IMG.ZIP in the root folder of the SD card; either that or eject the SD card. Power the phone off. Press and hold Vol-Down and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu will appear immediately. One of the items will indicate that if you press "Vol-Up", you will boot into recovery. Press Vol-Up, and wait 10 seconds. You should be at the Amon_RA menu. (At this point, you can re-insert the SD card if you previously ejected it).
If you can't get either of these things to work, report back with exactly what you observe - saying "it didn't work" might be correct, but it isn't very informative.
wolfpack10 said:
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Click to expand...
Click to collapse
Not correct. Both the "one-click" and "Dummies" methods (see All Things Root forum over at AF) work for 1.47, 1.49.0000, and 1.49.2000 bootloaders.
wolfpack10 said:
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Click to expand...
Click to collapse
The PB00IMG.ZIP files are not compatible with the Amon_RA "update"-style installs; they are signed using an entirely different method. Not compatible. That's why it didn't work when you tried it (using Amon_RA). They are installed by starting up the bootloader with the PB00IMG.ZIP file in the root folder of the SD card. I am recommending that until you understand things a little better, you avoid this method - it only works with certain combinations of bootloaders and PB00IMG.ZIP file versions.
wolfpack10 said:
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
It did work. You indicated in your first post that you used the Amon_RA recovery, which was installed by that method.
bftb0

Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.

wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Contacts should have been backed up through google. Although I have leaked and rooted some friends phone and their contacts never sync'd to their phones.
Sent from my Eris using XDA App

wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Glad you got it working.
If you were using Gmail instead of the HTC mail app for managing your contacts, all your contacts are still "in the cloud" (so long as you did not define them to be "phone only" when you added them).
If they were phone-only contacts, it would have been a simple matter to get your contacts back if you had made an initial Nandroid backup. I'm not saying that to add insult to injury, but rather (as you said) "Hopefully this thread will be helpful for other people in the future."
Backups are a really good thing.
BTW - You will find that Android Forums is a useful adjunct to this forum. The reason is that the ROM devs over here on XDA have their hands full trying to do both development work and interact with the users/testers reporting issues with their ROMs, so they don't spend much time in here (Q&A or General sub-forums). When they do announce a new hack, or patch, or rooting method, the descriptions are many times written tersely (for subject-matter experts, not newbs). There are a number of very helpful folks over on AF, and some good "sticky" posts that are quite a bit more detailed than what you will find here. I'm not ragging on XDA at all; just saying that by nature of the focus required for development work, the experts can't give much personal attention to individual users, even if they want to.
bftb0

[Q] How can I Factory Restore?

I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.

Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.

http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.

Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)

drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.

Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)

Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.

drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.

eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.

drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"

I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.

Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty

Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.

Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty

Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."

drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?

[Tutorial][S-OFF] How to Use Official OTA files

NOTE: IF YOU ARE ALREADY ON ICS OF EITHER PROVIDER, YOU CANNOT USE THE OTA FILE AS DIRECTED BELOW, SINCE THE UPDATE PROCESS CHECKS YOUR ANDROID/BOOTLOADER VERSION
Now we all have access to the Telus and T-Mobile OTA ICS files but we can't seem to find a way to install them, we only know how to install the modded files that the devs have supplied us with, well search no more.
I'll give you a step by step way to get it done and use the OTA files without the need of a dev modding it for us.
Requirements:
1. Stock GB of whichever provider you choose to install from be it Telus or T-Mobile
do note that you can only install the ICS OTA file of the exact providers who's stock GB you have installed.
2. The OTA corresponding file, I'll provide links to both below.
3. An SD card.
Procedure:
1. Flash back to stock GB of the provider you want to install be it TMO or Telus, if you're already on complete stock, skip this step and go to step 2.
2. Place the OTA file on the external sd card, you do not have to rename this file.
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this.
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
5. select install update.zip from external
6. browse using the volume up or down buttons to the OTA file and press the power button to select it.
7. it's gonna ask you once to select reboot on the menu, do this and let it be for a few more minutes.
8. It's gonna reboot when it done, should reboot twice, once to the upgrade screen, second to android.
Voila! You're on official ICS via the ota file!
T-Mobile ICS OTA file here: http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
Telus ICS OTA file here: http://www.4shared.com/zip/HTGslOiT/OTA_RUBY_ICS_35_S_TELUS_WWE_21.html
Credits to BoomBoom for the telus file upload.
Note to users, if you're getting an error when you try to select the update file as instructed, simply rename the OTA file to update, then try applying update from sd card, let me know if that works for you instead, so I can edit this tutorial accordingly.

An experimental though added, it's theory, too lazy to test it, but hoping someone else confirms it.

Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-

scream514 said:
Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-
Click to expand...
Click to collapse
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.

I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.

garysayer1976 said:
I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.
Click to expand...
Click to collapse
There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared.

Dark Nightmare said:
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.
Click to expand...
Click to collapse
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks

scream514 said:
Sorry, you;re quite right!
It's is as close to stock as i seem to be able to get it...
I dtried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
Thanks
Click to expand...
Click to collapse
Rename the OTA file to update and place it on your external sd card, reboot into recovery, choose the apply update.zip option again and let me know what happens.

Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks

scream514 said:
Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks
Click to expand...
Click to collapse
So basically, you can't update via my methods or just normally via the phone, is your bootloader unlocked by chance? If so, please relock it, that's the reason why it won't update if it's unlocked, only s-off users can update with an unlocked bootloader.

scream514 said:
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks
Click to expand...
Click to collapse
You can't use the nandroid I made or the flashable zip I'm currently uploading due to you being on GB, only ICS users can use that option to return to stock.

Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
---------- Post added 7th June 2012 at 12:04 AM ---------- Previous post was 6th June 2012 at 11:59 PM ----------
well, it dl'd and verified sucessfully... guess its a race now, wish me luck!!!
while wrting that a little yellow progress bar is showing instead of the error message under the update logo... bar is 30% complete...
almost hit 10 posts...
oh shizzle!!!

scream514 said:
Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
Click to expand...
Click to collapse
Hopefully no, if it does give an error, simply relock and try again.

ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me

scream514 said:
ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me
Click to expand...
Click to collapse
Well you're on ICS officially, have fun.

n00b question
First post, and I'm sorry for asking an obvious question and posting in a relatively old thread. I just got an Amaze 4G yesterday, and after many calls and chats with both T-Mobile customer support and HTC support, the consensus is that my phone isn't getting the OTA ICS update because the IMEI block hasn't been activated, yet. Will this method allow me to get it early, while not voiding my warranty, etc? If I stuck with this method, would I still be able to get the usual OTA updates later on?
What I'm trying to ask is, does this method act exactly as if I had gotten it through T-Mobile?
Thanks, everyone! It's much appreciated!

ics ota update videotron on htc amaze from videotron
Hi guys, I was wondering if i was doing doing something wrong trying the method showed up on the frist page , I applied the steps for my videotron amaze 4g with the ota file, and yet i get what everyone seems getting, I get to the point where it cannot find the update file on the sd card. What if I were to put the update file in the internal memeory?. after all, if the OTA gets in via the regular way, wouldn't be placed in the internal memory to start with??
Still , I would require some help from someone who suceeded in upgrading to ICS..
Thanks

1. Sideloading only works with external sd
2. This method only seems to work with s-off devices on gb or a s-on device with a locked bootloader.
Sent from my SGH-T999 using xda app-developers app

Ota update
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.

Flynch3211 said:
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.
Click to expand...
Click to collapse
Lock your bootloader back if you're on gb and try this method again, do note that you have to have the stock recovery.

[S-OFF Only!!!] Install OTA Update and Maintain Root Access

UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!

There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2

Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.

TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk

msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.

Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse

im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.

greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs

bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium

Thanks for taking the time to do a write-up OP!

Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2

Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.

greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.

Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO

i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.

Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.

zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.

Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat

Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.

EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.

A journey into the bowels of S-OFF - A guide for the professional semi-noob

I went through the S-OFF, etc process from scratch last weekend (soup to nuts from stock GB), and decided to share my notes.
There is no original information posted here, just a re-organized walkthrough to reference & accommodate what's already out there.
Hopefully a few find it helpful (I know I woulda )
Disclaimer:
this is a Windows-centric walkthrough, that assumes (in parts) that this isn't your first day at the rodeo. Never be scared to use Google or the IRC chat (sorry dsb9938 for the newb flood :laugh
This walkthrough is just an end to a means. You'll find people mention different ways they've accomplish the full process - this post is just a historical document on how I accomplished the same goal.
My methods were definitely successful, though my technique was admittedly ghetto at times. If any uber-pro's notice areas where this is the case, feel free to chime in & i'll update that chunk with credit to you.
I take no responsibility for anything you were inspired to do as a result of reading this post... unless it made you happy, I will take credit for that
The full process in a chronological nutshell:
HTC Unlock
Flash recovery
Root
Juopunutbear S-OFF
Flash latest firmware
Re-flash recovery
Flash ROM
Things to do beforehand:
disable fast boot // settings > power > uncheck
-- this is a universal truth throughout this process, if you have problems booting into the bootloader, check into this.
enable USB debugging - settings > applications > development > check USB debugging
-- this is another universal truth, if something isn't able to communicate with your device, check into this
verify your bootloader / system status
-- power down
-- hold down power & vol- at the same time while booting up
-- it should say Locked & S-ON at the top
backup SD card
backup anything on the internal storage that you care about
*Optional - wipe SD card
*Optional - install an MD5 checker (if you don't already have one)
-- Windows: http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html?tag=mncol;1
-- Android (for later): https://play.google.com/store/apps/details?id=com.fab.md5
BE PATIENT. seriously. I know you want to get back to MW3, but this can take a while. Your device will go through several lengthy processes. If something looks unresponsive and it starts to scare you, just wait it out for a few minutes before going willy nilly with the power button. At times, you will end up having to manually power on again, but give it time before getting antsy. If your ADD is driving you crazy, just bite your lip and power through it.
Steps 1, 2, & 3)
Unlock, Recovery, & Root:
go to htc dev
sign up / confirm from email / log in
install the stuff they tell you to, listed on the right of the page
Install / use the Rezound All-In-One Toolkit on your PC to accomplish the rest
for recovery, I chose Amon RA
The more you know ✩....
-- a dude doing recovery the manual way - http://youtu.be/AvSeLmXSjVI
-- the recovery is accessed through the bootloader menu
Step 4)
S-OFF:
Charge battery full
Make sure fast boot is still off
Make sure USB debugging is enabled
Download the latest juopunutbear for rezound here (Windows, Latest ICS)
*Optional - Verify the MD5
Follow juopunutbear instructions - here, then here
*Optional - Do a backup via recovery
The more you know ✩....
-- controlbear was randomly having a hard time seeing my device, I solved this by:
---- closing controlbear command prompt
---- toggling on HTC Sync as the USB connection type (on the rezound)
---- this caused the device to be recognized differently in windows & installed a driver
---- I started controlbear again, but it hung at "Searching for device"
---- I closed it & ran it again
---- then it worked
-- for the rooting part of this, when it boots you into recovery, check both SD card locations for SuperSU.zip
-- this process froze on me many times, closing and restarting controlbear seemed to fix it
---- seriously did this at least 10 times - it happened randomly at seemingly scary places. (each time getting me further than the last)
-- juopunutbear hboot? - I said yes
-- SD card issues? do a factory reset.
-- Still have SD card issues? you just need to update the firmware, move along.
-- USB debugging path has changed in ICS, you can enable it here: settings > developer options > check USB debugging
-- ATTENTION: Not getting any reception/ signal? put the case back on, broseph
more info:
-- S-off is Official!!! With Instructions...
-- S-OFF FAQ
Step 5)
Latest firmware:
Download the latest RUU (3.14.605.10 as of July 16) to update the firmware to ICS - http://bit.ly/KlRfKZ
-- *Optional - Verify MD5
Rename the RUU to "PH98IMG.zip"
Copy the renamed update to the root of your external SD Card.
Power down / reboot into bootloader / wait 5-10 minutes for it to finish
Step 6)
Fastboot flash recovery:
After s-off and firmware update, you need to re-flash recovery via fastboot, this process is described here -- # < anybody have a link? #
-- *Optional - Do a backup via recovery
The more you know ✩....
-- flashing recovery via fastboot is only necessary if you want to keep the top of the bootloader reading as "Locked" (even though it's already S-OFF'd).
-- I did not want this, (mine reads "Unlocked") so if you don't want that, then just re-unlock using the same method as you did the first time, and then re-flash recovery the same way again.
REPEAT: Not getting a reception/ signal? put the case back on.
Step 7)
ROM
Download ROM of your choice (I used Nils' Business ICS, Sense 4.0, v1.2)
-- *Optional - Verify MD5
Copy the zip to the root of your external SD Card.
Follow the ROM installation instructions (Wipe, etc) & install via recovery
-- *Optional - Do a backup via recovery
Hooray!
-- credit where it's due & thanks to all who came before me.

i came here because the title said BOWELS! 0.o

^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative

Wrote up a similar guide last week at TeamBAMF's site:
http://www.teambamf.net/topic/4122-generic-guide-to-root-and-install-roms-on-the-rezound/

AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.

dustintheweb said:
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Yeah makes sense.

dustintheweb said:
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..

Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
Just to add on to that, a noob who can't use adb and fastboot fully probably has no need for s-off

So no fast boot Ehhh?
I just checked, mine is on, so is that why my 8 hours of s-off attempts failed?
Sent from my ADR6425LVW using Tapatalk 2

Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.

AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
First, this is exactly what I was looking for so thank you. I've read just about every post for unlocking and s-off, but I'm glad you put it all together!
Second, so step #5 should really be #4?
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Thanks again!

dustintheweb said:
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
Click to expand...
Click to collapse
This is how it should be but not all people think like that most just wanna put people on blast
Sent from my ADR6400L using xda app-developers app

BSquaredB2 said:
Second, so step #5 should really be #4?
Click to expand...
Click to collapse
It worked for me, but AshtonTS says there is a better way. Search through the S-OFF FAQ thread (or similar) and see if you can get a consensus of what other people did.
BSquaredB2 said:
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Click to expand...
Click to collapse
If you're on GB, go to settings > applications > development > check USB debugging
Sorry about that, I had the ICS path in the guide (now fixed).

Better Mobile App

welcome