Related
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
Okay, so I'm in a bit of a bind. I'm S-OFF, and I tried updating to the global leak and it seems I've lost boot and recovery. Everytime I boot it goes through the splash screen and then a black screen with the phone and green update symbol, then it turns to a red triangle and exclamation mark. any help would be greatly appreciated. I'm fairly experienced and everything i've tried has failed. I tried going into hboot and flashing the PH98IMG again. It took, but still the same result. I tried flashing the recovery in fastboot but it continues to fail, and I also tried flashing my boot.img but it also failed. Any ideas?
tomtripp21 said:
Okay, so I'm in a bit of a bind. I'm S-OFF, and I tried updating to the global leak and it seems I've lost boot and recovery. Everytime I boot it goes through the splash screen and then a black screen with the phone and green update symbol, then it turns to a red triangle and exclamation mark. any help would be greatly appreciated. I'm fairly experienced and everything i've tried has failed. I tried going into hboot and flashing the PH98IMG again. It took, but still the same result. I tried flashing the recovery in fastboot but it continues to fail, and I also tried flashing my boot.img but it also failed. Any ideas?
Click to expand...
Click to collapse
unlock the bootloader and flash a recovery. you need to unlock since you dont have eng commands.
btw this belongs in q&a
antp121 said:
unlock the bootloader and flash a recovery. you need to unlock since you dont have eng commands.
btw this belongs in q&a
Click to expand...
Click to collapse
Thanks I'll give that a try. Will the firmware and ROM still be in place? Will I have do the update again? BTW Sorry for posting it in the wrong section..
tomtripp21 said:
Thanks I'll give that a try. Will the firmware and ROM still be in place? Will I have do the update again? BTW Sorry for posting it in the wrong section..
Click to expand...
Click to collapse
Its OK. And once you unlock, it'll reboot. Then you just go back into the boot loader and flash a recovery with fast boot.
Sent from my aokp_tenderloin using Tapatalk 2
So got the recovery flashed, but now it only boots into the recovery.
tomtripp21 said:
So got the recovery flashed, but now it only boots into the recovery.
Click to expand...
Click to collapse
Did you try flashig a rom?
Sent from my aokp_tenderloin using Tapatalk 2
i tried to restore my backup that didn't work, I haven't tried a new ROM yet. I'll try that and get back to you. Thanks again for all your help.
antp121 said:
Did you try flashig a rom?
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Tried flashing a ROM, the stock deodexed rooted 4.03.605.02. Still boots to recovery...
tomtripp21 said:
Tried flashing a ROM, the stock deodexed rooted 4.03.605.02. Still boots to recovery...
Click to expand...
Click to collapse
You need to use interface to fastboot boot.img then run firmware update for old firmware n old CWR. BASICALLY GO BACK TO STOCK REZOUND N START THE WHOLE PROCESS OVER LIKE DAY 1!
Good news is you don't need to do the wire trick again. Your phone crashed during the firmware upgrade now its stuck in limbo n doesn't know how to handle the 2 sets of hardware commands its receiving from the CMOS.
[Q] Can only get into recovery after attempting Juopunutbear S-OFF
I wanted to S-OFF after being stock locked, with the OTA ICS update. I performed HTC dev unlock successfully. After that, I may have gone wrong during one of several steps.
-Pushed AmonRa recovery 3.15 to my phone (seemed to be successful)
-Flashed ICE-EnableRoot.img (got an error message saying it was unsuccessful, but when I rebooted my phone, SuperUser was installed).
-Flashed vigorOTAStockRooted.zip (because I wanted to try the S-OFF method from stock GB rom)
-Ran HTC Rezound S-OFF Kit By Hasoon2000
-Made sure HTC Drivers were installed
-Enabled USB Debugging
-Put in blank SD Card
-Run Juopunutbear v.6 If You Are On Gingerbread
After running Juopunutbear v.6 for Gingerbread, my phone screen went blank and HTC's splash screen came up momentarily, and then my phone screen went dark. The cmd box that popped up then gave me an error message saying I had to install the HTC Drivers. I went to HTC's website to download the drivers. When I tried to install them, I was told they were already installed.
I can reboot my phone into Hboot and AmonRa recovery and I can do anything from there. But when I try to start my phone, I get the HTC splash screen and then black screen. The orange LED lights up when my phone is powered off and plugged in via USB. When I try to boot from Hboot, I either get a static HTC splash screen or splash screen going to a black screen.
This is what my Hboot screen reads:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
Open DSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012,16:47:46
Any advise would be greatly appreciated! Thank you!
jtayag said:
I wanted to S-OFF after being stock locked, with the OTA ICS update. I performed HTC dev unlock successfully. After that, I may have gone wrong during one of several steps.
-Pushed AmonRa recovery 3.15 to my phone (seemed to be successful)
-Flashed ICE-EnableRoot.img (got an error message saying it was unsuccessful, but when I rebooted my phone, SuperUser was installed).
-Flashed vigorOTAStockRooted.zip (because I wanted to try the S-OFF method from stock GB rom)
-Ran HTC Rezound S-OFF Kit By Hasoon2000
-Made sure HTC Drivers were installed
-Enabled USB Debugging
-Put in blank SD Card
-Run Juopunutbear v.6 If You Are On Gingerbread
After running Juopunutbear v.6 for Gingerbread, my phone screen went blank and HTC's splash screen came up momentarily, and then my phone screen went dark. The cmd box that popped up then gave me an error message saying I had to install the HTC Drivers. I went to HTC's website to download the drivers. When I tried to install them, I was told they were already installed.
I can reboot my phone into Hboot and AmonRa recovery and I can do anything from there. But when I try to start my phone, I get the HTC splash screen and then black screen. The orange LED lights up when my phone is powered off and plugged in via USB. When I try to boot from Hboot, I either get a static HTC splash screen or splash screen going to a black screen.
This is what my Hboot screen reads:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
Open DSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012,16:47:46
Any advise would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
For starters, you are on ics firmware so you should run the ics version of juopunutbear. I suggest flashing a rooted Rom based on the ota and then try again.
Sent from my ADR6425LVW using Tapatalk 2
topgun1953 said:
For starters, you are on ics firmware so you should run the ics version of juopunutbear. I suggest flashing a rooted Rom based on the ota and then try again.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I successfully flashed one of the stock ICS ROMs! What got me all confused to begin with was the prerequisite that I had to be on a stock Gingerbread ROM or the 3.14.605.5 ICS leak. That's why I tried flashing the original Vigor GB ROM on my phone. I still want to get S-OFF, but I need to read the instructions more carefully. Thanks for your help!
dragonstalker said:
You need to use interface to fastboot boot.img then run firmware update for old firmware n old CWR. BASICALLY GO BACK TO STOCK REZOUND N START THE WHOLE PROCESS OVER LIKE DAY 1!
Good news is you don't need to do the wire trick again. Your phone crashed during the firmware upgrade now its stuck in limbo n doesn't know how to handle the 2 sets of hardware commands its receiving from the CMOS.
Click to expand...
Click to collapse
So I just need to flash my backed up boot.img, and then flash the 3.14.605.12 RUU? Then re-root and retry the OTA Global Update?
tomtripp21 said:
So I just need to flash my backed up boot.img, and then flash the 3.14.605.12 RUU? Then re-root and retry the OTA Global Update?
Click to expand...
Click to collapse
pretty much. From looking at everything looks like you are on ICS, but its not letting you reprogram. usually happens when an update fails. When you run Juonobear and run the ics upgrade over again, it should reboot like 3 or 4 times. Sounds like you never let the process finish. Final note, i'm not sure where you got your firmware from, but your radios do not look familiar. Not saying they are wrong, just not radio's i've ever seen flashed. BUT, I don't usually change radio's unless there is a huge need for it. you should be on radio's 10r/08r that come with the original ICS firmware update. I'll watch the thread throughout the day to lend support where I can. Hope this helps.
dragonstalker said:
pretty much. From looking at everything looks like you are on ICS, but its not letting you reprogram. usually happens when an update fails. When you run Juonobear and run the ics upgrade over again, it should reboot like 3 or 4 times. Sounds like you never let the process finish. Final note, i'm not sure where you got your firmware from, but your radios do not look familiar. Not saying they are wrong, just not radio's i've ever seen flashed. BUT, I don't usually change radio's unless there is a huge need for it. you should be on radio's 10r/08r that come with the original ICS firmware update. I'll watch the thread throughout the day to lend support where I can. Hope this helps.
Click to expand...
Click to collapse
Now I'm a little confused, sorry. I need to run the juopunutbear program again? My radios are 2.22.10.0801r/2.22.10.0803r, Hboot 2.27. I'm downloading the .12 RUU from Android Police. I've tried re-flashing the boot.img from my nand backup, but it keeps saying:
C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
edit: I fixed the flash, I forgot to add the partition in the command, duh... So I flashed my backed up boot.img, now I just need to flash the .12 RUU?
I have the backup img in the file where I have fastboot, adb, etc.. What am I doing wrong?
tomtripp21 said:
Now I'm a little confused, sorry. I need to run the juopunutbear program again? My radios are 2.22.10.0801r/2.22.10.0803r, Hboot 2.27. I'm downloading the .12 RUU from Android Police. I've tried re-flashing the boot.img from my nand backup, but it keeps saying:
C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
edit: I fixed the flash, I forgot to add the partition in the command, duh... So I flashed my backed up boot.img, now I just need to flash the .12 RUU?
I have the backup img in the file where I have fastboot, adb, etc.. What am I doing wrong?
Click to expand...
Click to collapse
I have now tried to flash the .12 RUU in Hboot but it will not flash it, probably because my firmware is newer right? Back to the drawing board....
Still to no avail I am getting nowhere. I flashed the stock recovery and did a factory reset from Hboot. Nothing, I have tried flashing the newest RUU, nothing, I'm flashed back to ra-recovery. Can anybody give me a solution step by step to get a ROM loaded and booting?
Well I finally got it up and working. I loaded the old firmware and was able to restore by backup. Thanks to all who chimed in with helpful advice. I'm hesitant to retry the Global update, but I might go ahead and give it another shot.
Glad you figured to restore the firmware. It's not hard to flash the global. Run the firmware, then run the recovery then flash Rom. Do it right in that order n you don't have any issues. Use 2 sdcards if you need to because the firmware upgrade won't delete the ph98 off your card. You will need to do it manually.
Sent from ICS REZOUND S-OFF
Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
flybub said:
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
Click to expand...
Click to collapse
Hem... that's the current bootloader. Are you s-on or off ?
dottat said:
Hem... that's the current bootloader. Are you s-on or off ?
Click to expand...
Click to collapse
I'm S-On. I downloaded the PH98 file again thinking maybe it was bad, but no dice. I get the same error message. I can't get anything to boot. I was able to flash a recovery so I flashed Infection 2.5 but I keep getting stuck at the Android looking screen (yes boot.img was flashed in fastboot). I flashed a couple different ICS roms but none of them boot up. I figured if I could get back to stock I would just go s-off and be done with it but I think this phone is done.
Edit: Gave the phone to a friend of mine who is much better at this stuff than I am. Maybe he can figure it out. Thanks for the help
Hm, if you flashed the kernel you should be able to boot up.
If you're s-on and on hboot 2.28 there's no RUU as of yet you can run. There's a stock OTA ROM of the lates OTA in the dev section you can run that and see if that helps. You probably can s-off on that but don't take my word for it, especially since you're on 2.28 hboot.
I would make a nandroid before so you can always get back to that if needed.
If you really want to run an RUU you need to s-off, but confirm that it's still going to work on the latest OTA before trying it.
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !