Related
Just wanted to let you guys know that I still have root after I installed the OTA. I will give a few steps what I did in a few minutes.
These are the steps I used. Took a while (seemed like forever) but at least I am updated and with root. I originally came from an ICS rom then I had to flash a stock rom then RUU.
1. Flashed stock recovery (Link below)
2. Locked bootloader (fastboot oem lock)
3. Flashed RUU 1.02.605.6 (link below)
4. Installed OTA (check for new software updates when booted)
5. Unlocked bootloader (http://www.htcdev.com/)
6. Flashed RA recovery (found in forum)
7. Installed su and superuser under Developer menu under RA recovery
8. BAM!!!!!!!
The RUU I used was found at http://www.scottsroms.com/downloads.php?do=file&id=37
Thanks scrosler for having that available!
The stock recovery can be downloaded at http://db.tt/tw5m33ZG. Unzip and flash in Fastboot using command "fastboot flash recovery recovery_signed.img"
Can you post a link to the RUU and stock recovery you used ? Thanks.
ilkevinli said:
Can you post a link to the RUU and stock recovery you used ? Thanks.
Click to expand...
Click to collapse
Yeah. It's at the bottom of the first post now.
Flyhalf205 said:
Just wanted to let you guys know that I still have root after I installed the OTA. I will give a few steps what I did in a few minutes.
These are the steps I used. Took a while (seemed like forever) but at least I am updated and with root.
1. Flashed stock recovery
2. Locked bootloader
3. Flashed RUU
4. Installed OTA
5. Unlocked bootloader
6. Flashed RA recovery
7. Installed su and superuser under Developer menu under RA recovery
8. BAM!!!!!!!
The RUU I used was found at http://www.scottsroms.com/downloads.php?do=file&id=37
Thanks scrosler for having that available!
Click to expand...
Click to collapse
Why did you have to relock the bootloader?
Flyhalf205 said:
Yeah. It's at the bottom of the first post now.
Click to expand...
Click to collapse
FYI, that's not the new RUU file.
hgoldner said:
Why did you have to relock the bootloader?
Click to expand...
Click to collapse
I kept on getting an error with it being unlocked about signature error. So I locked it and it finally worked.
Can you make a very detailed step-by-step process, including commands, adb, etc., that you used?
thx
Do you have a link to the stock recovery ? Thanks
Flyhalf205 said:
Yeah. It's at the bottom of the first post now.
Click to expand...
Click to collapse
ilkevinli said:
Do you have a link to the stock recovery ? Thanks
Click to expand...
Click to collapse
Yeah! Here!
http://db.tt/tw5m33ZG
Everyone that installed an ICS rom is SOL on this right?
mikemullin6 said:
Can you make a very detailed step-by-step process, including commands, adb, etc., that you used?
thx
Click to expand...
Click to collapse
I put very general commands and info beside the steps in the first post. PM me if you have any questions.
So does it seem like it's worth it? How's reception and call quality with the new radios?
What radio versions does your phone list now?
I just rooted. I still have my original stock ruu. It's rooted though. Could I update with that or do I have to unroot?
Sent from my ADR6425LVW using Tapatalk
If it lets you update then go for it. Just make sure your bootloader is unlocked after the update then install su and superuser and you got root back basically.
So if I just uninstall su I can update? I have amon ra as my recovery. What about that??
Sent from my ADR6425LVW using Tapatalk
You would need the stock recovery. RA would cause it to fail.
Flyhalf205 said:
You would need the stock recovery. RA would cause it to fail.
Click to expand...
Click to collapse
Right on! So I'll uninstall su and push the stock recovery and see what happens. No relock required cause it's my og ruu. Cool.
Sent from my ADR6425LVW using Tapatalk
WizeGuyDezignz said:
Everyone that installed an ICS rom is SOL on this right?
Click to expand...
Click to collapse
yea, I put on stock rom, stock recovery, then locked bootloader, and the it just kept rebooting to botoloader so i coulndt get to the rom to accept to try the OTA..
andybones said:
yea, I put on stock rom, stock recovery, then locked bootloader, and the it just kept rebooting to botoloader so i coulndt get to the rom to accept to try the OTA..
Click to expand...
Click to collapse
Did you try the RUU yet?
Flyhalf205 said:
Did you try the RUU yet?
Click to expand...
Click to collapse
It won't work because (I'm assuming) that his mainver was updated. AFAIK the RUU won't run a "newer" mainver.
I just recently switched back from the leaked Ice Cream Sandwich RUU by changing the main ver and uploaded the oldest ruu (1.02 etc) and was going to just update through OTA to the latest version of the htc Rezound. I the found out that when I tried to update it, recovery (amon ra recovery) was still present and it tried updating through that, which failed. Can anyone help me out with removing recovery?
in order to ruu, you need to install stock recovery which amonra recovery will be removed as well. download: http://db.tt/tw5m33ZG
qudwis said:
in order to ruu, you need to install stock recovery which amonra recovery will be removed as well. download: http://db.tt/tw5m33ZG
Click to expand...
Click to collapse
Thank u so much! But which method of flashing do you use to flash the stock recovery?
willsully1221 said:
Thank u so much! But which method of flashing do you use to flash the stock recovery?
Click to expand...
Click to collapse
i use cleanflash 1.0 for boot.img and recovery.img.
http://www.scottsroms.com/downloads.php?do=file&id=57
or use adb and flash using this command "fastboot flash recovery recovery_signed.img"
if you are using cleanflash 1.0, after downloading the stock recovery,
unzip then put the img file in the same folder as the tool the rename it to "recovery.img"
then use the tool and flash
make sure usb debugging is enabled, usb mode is on charging and htc sync on your computer is disabled before using the tool!!!!
willsully1221 said:
I just recently switched back from the leaked Ice Cream Sandwich RUU by changing the main ver and uploaded the oldest ruu (1.02 etc)
Click to expand...
Click to collapse
How in the world did you get that to work?
Sent from my ADR6425LVW using XDA
Snuzzo said:
How in the world did you get that to work?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
i think he meant to say that he were going to do that...
Hmm, well sounds like need more info to help the op then.
If op is doing this to try and get the OTA, it won't happen, due to flashing the .22 leak.
Sent from my ADR6425LVW using XDA
I was thinking the same thing.
Sent from my ADR6425LVW using xda premium
There's a guide in the development section that can get you to switch your main ver to whatever number you want. I put it a 1.00.000.00 and then it automatically switched to the first main ver (when the htc rezound was officially released). Now I've got a problem because my phone won't read my sd card (even though it's working, i plugged it into the computer and it worked), it won't let me flash any RUUs in bootloader, every time i try to turn the phone on it goes straight to fastboot so I can't even access the phone, and where it should say locked or unlocked (in fastboot/bootloader) it has 3 lines that look like this:
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
Also, I was using the original stock rom for a couple of days before this happend, so that part was working fine. But Ive never experienced this before and this is my third or fourth time going through this exact same process.
Edit: I also forgot to mention that the recovery is now stock recovery again, as you could probably tell, it's relocked, I'm pretty sure it's unrooted, but I can't tell, and lastly, after multiple tires, I could not get the OTA update to work at all. I kept getting error/fail messages.
A couple of things. First you can't ruu back. Your hboot was updated. Second that TAMPERED message tells me that are not on the stock recovery, it only says that when a non stock recovery is installed. If you are just looking to get GB back on the phone, I made a guide in the general section. Search for "how to go back to GB from leaked ICS.
Sent from my ADR6425LVW using xda premium
EmerikL said:
A couple of things. First you can't ruu back. Your hboot was updated. Second that TAMPERED message tells me that are not on the stock recovery, it only says that when a non stock recovery is installed. If you are just looking to get GB back on the phone, I made a guide in the general section. Search for "how to go back to GB from leaked ICS.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Thanks, and I did re install the stock recovery and have checked several times and there's no more recovery. But I'm back on GB now, I was just trying to get the OTA. Now I'm trying to get my phone to turn on because every time I power it on, it goes straight to fastboot, so I can't access it. So if you have any ideas on that to help me out, that would be awesome. But thank you for the help, I'm going to go look at your thread now. Thanks!
willsully1221 said:
Thanks, and I did re install the stock recovery and have checked several times and there's no more recovery. But I'm back on GB now, I was just trying to get the OTA. Now I'm trying to get my phone to turn on because every time I power it on, it goes straight to fastboot, so I can't access it. So if you have any ideas on that to help me out, that would be awesome. But thank you for the help, I'm going to go look at your thread now. Thanks!
Click to expand...
Click to collapse
You need to flash amon ra recovery .. then flash a Rom and kernel
Sent from my Dinc... I mean Rezound
yojoe600 said:
You need to flash amon ra recovery .. then flash a Rom and kernel
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
Do I have to do that if my phone's already on GB?
Now it won't let me get into recovery because it keeps trying to update the the software from OTA but that fails and then it gets stuck at phone with a red triangle infront/ontop of it.
Edit: I actually realized it was doing that because the recovery still wasn't there, so i went back to the command prompt and looked and saw that it said that flashing the recovery had failed. so then I went and got the newer amon ra recovery and tried flashing that, still said it failed and still wasn't there. What is going on with my phone?
willsully1221 said:
Now it won't let me get into recovery because it keeps trying to update the the software from OTA but that fails and then it gets stuck at phone with a red triangle infront/ontop of it.
Edit: I actually realized it was doing that because the recovery still wasn't there, so i went back to the command prompt and looked and saw that it said that flashing the recovery had failed. so then I went and got the newer amon ra recovery and tried flashing that, still said it failed and still wasn't there. What is going on with my phone?
Click to expand...
Click to collapse
It's locked you need to unlock the bootloader again
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
superchilpil said:
It's locked you need to unlock the bootloader again
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Haha ya i realized that and then unlocked it, but it wont let me flash the kernel, it says main ver is older
willsully1221 said:
Haha ya i realized that and then unlocked it, but it wont let me flash the kernel, it says main ver is older
Click to expand...
Click to collapse
There's a main ver fix in the development stickies, or just fastboot flash it
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
superchilpil said:
There's a main ver fix in the development stickies, or just fastboot flash it
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
would the command be: fastboot flash kernel (nameofkernel).zip
willsully1221 said:
would the command be: fastboot flash kernel (nameofkernel).zip
Click to expand...
Click to collapse
No, flastboot flash boot (kernel).IMG
So it would need to be extracted out of the zip to get the raw IMG file
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
superchilpil said:
No, flastboot flash boot (kernel).IMG
So it would need to be extracted out of the zip to get the raw IMG file
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Ok command prompt said it was a success, but nothing happened on the phone, I'm still going to infer that it was a success. Now what did the kernel update do? Will i be able to update via OTA?
Could someone please help??
tryed updating through System Update (OTA)
failed to install... said my device may have custom rom
I wasn't using a custom rom, only changed cid to use a custom rom but ended up using stock. Just forgot to change cid back.
Changed cid back to original (HTC__044) and tryed to download OTA again...
It succeeded to download and asked me to install... Accepted.
it rebooted to Recovery and failed to install.
Followed 1st post instructions (status 7)
and installed the OTA through recovery.
Instalation successful!
BUT
When I rebooted the device, it just doesn't boot.
I downloaded anryl files, but it failed to load PG86IMG.zip when I boot to bootloader. Says wrong image.
tried booting into recovery but it won't boot into recovery either.
then tried flashing recovery again and booting into recovery again. No success.
any ideas?
Thanks in advance
Wich H-BOOT do you have? Are you S-OFF or ON? Have you tried an older .img or newest?
wheal said:
Wich H-BOOT do you have? Are you S-OFF or ON? Have you tried an older .img or newest?
Click to expand...
Click to collapse
My hboot is 1.49.0011. I´m S-ON and I tried the newest .img (modded ICS - because of that Status 7 error)
I would relock via adb if you can get it to recognize commands while in the bootloader mode. Then use a gingerbread rru to flash back to stock. Then you hopefully should be able to take the OTA and have it work.
Did you have a custom recovery when you went to do the ota or a stock one?
Sent from my Marvelc using Tapatalk
kagevazquez said:
Did you have a custom recovery when you went to do the ota or a stock one?
Sent from my Marvelc using Tapatalk
Click to expand...
Click to collapse
I had a custom recovery. CWM 5. something (the touch one).
Aronnax said:
I had a custom recovery. CWM 5. something (the touch one).
Click to expand...
Click to collapse
I had an isue with the touch one, just flash CWM 5.0.2.0 flash through fastboot
HIVic_EG6 said:
I had an isue with the touch one, just flash CWM 5.0.2.0 flash through fastboot
Click to expand...
Click to collapse
Ok!
I'll try that and report back!
Thanks in advance!
Aronnax said:
Ok!
I'll try that and report back!
Thanks in advance!
Click to expand...
Click to collapse
Man! Yet you're a GOD!
Recovery working.
trying to restore to my previous gb backup!
As soon as it finishes I'll let you know!
Thanks again!
Aronnax said:
Man! Yet you're a GOD!
Recovery working.
trying to restore to my previous gb backup!
As soon as it finishes I'll let you know!
Thanks again!
Click to expand...
Click to collapse
Man!!
THANKS A LOT!
a question: can I accept the OTA update again?
do I have to do something before accepting the OTA?
or it's better for me to leave it that way?
Aronnax said:
Man!!
THANKS A LOT!
a question: can I accept the OTA update again?
do I have to do something before accepting the OTA?
or it's better for me to leave it that way?
Click to expand...
Click to collapse
You should be good to go, happy to help
Aronnax said:
Man!!
THANKS A LOT!
a question: can I accept the OTA update again?
do I have to do something before accepting the OTA?
or it's better for me to leave it that way?
Click to expand...
Click to collapse
I would just use any ROM other than the official update, I would suggest MEANROM ICS
phone wont update to ics
I just tried the OTA update for ICS on my evo 3d. After it downloads the update it shuts down, shows the installion screen, but reboots to 3.0. My h-boot is 1.5 with S-OFF. Any suggestions that will remedy this problem?
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
rdtmk said:
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
Click to expand...
Click to collapse
Are you S-OFF? If not, you need to flash the boot.img separately.
exSD said:
Are you S-OFF? If not, you need to flash the boot.img separately.
Click to expand...
Click to collapse
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
Look in the thread. If the author has posted the boot.img you can do it fairly easily.
mulhiny said:
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
You most likely need newest firmware if I'm not mistaken. You really need to s-off your phone. Then you won't have all the difficulty your having. Otherwise, you need newest firm ware...
Sent from my EVO using Tapatalk 2
rdtmk said:
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
Click to expand...
Click to collapse
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
mulhiny said:
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
rdtmk said:
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
Click to expand...
Click to collapse
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
exSD said:
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
Click to expand...
Click to collapse
says:
"writing 'zip' ... FAILED (remote: not allowed)"
Try getting a copy of cwm (not the touch version) and flash it via the fast boot method. Use the volume rockers to move, camera to select, power to go back.
It'd be easier to just ruu back to stock and start at square 1. Doesn't take that long to root and s-off anymore. Dirty racun would probably still work too.
Sent from my EVO using xda premium
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
scottspa74 said:
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Twrp 2.4.x.x is compatible with 3.16 +TP
I cant seem to get Viper rom to work. I used superwipe and there was an error. Cleared system and data and cache. Flashed rom, then fastbooted boot.img. Rom is stuck in htc screen and recovery flashes on for a quick moment then goes dark and phone reboots. Ideas please. Thanks
Which recovery did you use? If you used TWRP you should use 2.3.3.0 for the ROMs with aroma installers. Did you try simply reflashing recovery?
Sent from my Incredible 4G LTE using xda app-developers app
somerandomname1 said:
Which recovery did you use? If you used TWRP you should use 2.3.3.0 for the ROMs with aroma installers. Did you try simply reflashing recovery?
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I have tried to resinstall recovery, but it blinks into recovery for a quick second then reboots and again stuck on boot screen. can superwipe do something to my internal sd card to do this?
D.A.N. said:
I have tried to resinstall recovery, but it blinks into recovery for a quick second then reboots and again stuck on boot screen. can superwipe do something to my internal sd card to do this?
Click to expand...
Click to collapse
i had to wipe, restore original, then reflash with new recovery and it worked. thanks.
More Detail Please.
D.A.N. said:
i had to wipe, restore original, then reflash with new recovery and it worked. thanks.
Click to expand...
Click to collapse
Can you please give me more details? Such as steps, I'm having the same problem that you had. I'm kinda new to this stuff.
OldNut5 said:
Can you please give me more details? Such as steps, I'm having the same problem that you had. I'm kinda new to this stuff.
Click to expand...
Click to collapse
I think he did ruu and everything went back to normal, since he says he restored to original and theres no way he could do that from recovery, I have a thread named the brick thread, try the solutions in there, on my case ruu wasn't working either and recovery was looping too , I had to use ruu mode, however I don't know what Dan did and I may be wrong, but this could work
Sent from my ADR6410LVW using xda app-developers app
S-ON/S-OFF Needed?
Since I'm S-OFF Do I have to regain S-ON/S-OFF again, when reflashing this RUU? I don't want to screw up any further.
Sent from my ADR6410LVW using xda app-developers app[/QUOTE]
OldNut5 said:
Since I'm S-OFF Do I have to regain S-ON/S-OFF again, when reflashing this RUU? I don't want to screw up any further
Click to expand...
Click to collapse
Before running the ruu, try just re-flashing recovery from fastboot. Instructions can be found in either the TWRP or ClockworkMod thread.
Also, pay attention to somerandomname1's advice above.
Working again.
Looks like that Re-RUUing Stock, Re S-OFF DirtyRacun (I'm used to this method), then flashing TWRP 2.3.3.0 Got ViperLTE Installed Properly. Thanks.