Related
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
I'm in the same boat but I'm not able to do a recovery. I went through the update process and when the phone rebooted it got stuck on the white htc screen. I can get it into the bootloader menu but when i choose recovery it starts but then i get an error with a pic of the device and the red yield sign. If i choose factory reset it just gets stuck at the white htc. I read some other posts and I saw that having an unlocked bootloader may cause issues with updates so that may be your issue as for me, I'm not sure what I can do. I may just need the actual update file to redo the update but I'm not sure where to find it.
Same here, but I don't get half way through the ota update before I see the red triangle and exclamation mark. Phone will boot into stock recovery (which I would assume you need instead of modded recovery) and the update starts, but doesn't complete. I pull the battery and the phone boots up normally. Just can't seem to get through the update. Could be something to do with being s-off I would guess.
EJ
madmajd said:
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
Click to expand...
Click to collapse
Same problem but whit s-off
I have been predicting that this would happen... ICS failures with non-standard HBOOTs. Good luck.
Probably will have to wait for an RUU or custom.
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
wikkid said:
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
Click to expand...
Click to collapse
Alright thanks a lot
Just an update on what I did. I was able to reload the stock gb rom for rogers using the exe file, then I went through the 2 updates that came up when checking and ics is now up and running on my phone. However in my attempts of trying to fix the original problem, I managed to re-lock my bootloader before flashing to stock rom and I had s-on the whole time. hope this help.
i switched to stock like.. a week back?
jus got ota on 4th
i WAS rooted and using juopunutbear's hboot *u can jus get the hboot from their website*
so i jus flashed back stock recovery.. and updated.. and success.. lost root though.. and i was back to stock bootloader..
used the PG86IMG with juopunutbear's bootloader and 4ext recovery.. and flashed cwm supersu.. v0.91 i think.. i dunno.. latest one.. and bam.. im on stock.. rooted.. and works perfectly..
Possible sollution
Maybe try flashing one of the customized ROMs that are based on the latest OTA update. I'm sure Anryl's newest rom is blazing-fast and stable. You can find it in the gsm android development forum and flash it via recovery. Make sure you have the latest 4ext recovery installed, though.
where can a i find that stock rogers rom i modified mine and that might be the reason i get a security failure in hboot. s is on. when i run the ruu file in windows to downgrade i get error 155. when i run the the update from about phone. it locks up with blue android guy and yellow exclamation mark. i remove the battery and she boots fine with no changes.
I am trying to do same. Get stuck on HTC screen. I have S-ON. Was on cobra 2.4 prior.
If anyone can give details on how to fix it, it would be great! Please no saying "install exe". I need to know which exe etc.
just wanted to tell everyone that in order for the ota update to work properly, you need to be running stock unrooted firmware with a locked bootloader. Just relock your bootloader, reinstall the stock firmware, upgrade to ics via ota, then re-unlock and re-root.
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Try kingcobra's rom, ota from rogers will not boot due to the fact that your phone is rooted, kingcobra's rom is based on rogers ota, flash it and leave it.
Sent from my HTC EVO 3D X515m using xda premium
Davideichler7 said:
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Click to expand...
Click to collapse
Go to the gsm development forum and download the RUU for the phone, and restore it to stock unrooted OS. Before you do that though, make sure that your phone's BOOTLOADER IS LOCKED. Look up how to re-lock your bootloader. After you relock your bootloader, you can proceed with restoring the phone.
Soooo.... basically, what I'm getting from this is, if you like having a locked bootloader, CWM and root, don't bother trying to install this OTA update because it's a headache. Agree?
The phone's not mine, it's my wife's, and she doesn't want anything special or like the idea of me messing around in her phone.
I was about to install this late last night, just about to hit that button, then I thought, "what about the bootloader? what about root? what about the fact that it's now unlocked and being used on a carrier other than Rogers?"
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
Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
I'm not quite sure where you're at, but just use the RUU and get back to stock, then upgrade the firmware to 2.06, use moonshine to get s-off and root.
androidgg81 said:
Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
Click to expand...
Click to collapse
use the facepalm method to get back to stock, then take the update to 2.06 then moonshine
re-flash a kernel... if you can
.torrented said:
re-flash a kernel... if you can
Click to expand...
Click to collapse
Thanks, I just used this as an excuse to run 10.2 with your sweep2wake, looks pretty fast right now.
as you did
how to deleted this post?
androidgg81 said:
Maybe my mistake was taking part of the moonshine s-off thread when it didn't really apply to me since I was already s-off.
I was on 1.15.604 from December 2012, unlocked bootloader, s-off from first exploit (January?), with Verrine5.9 kernel.
I decided out of curiosity to flash the 2.0.6 fw in the moonshine thread, using adb in Ubuntu.
The terminal showed the zip flashing successfully. I chose to shut down the phone from the bootloader menu.
My DNA rebooted with all my apps, etc, but the firmware was still showing as 1.15.604. When I rebooted a second ti. E
via adb to recovery, now my phone internal sd, and twrp was wiped, I lost my nandroid, and all personal files. I know I should
have backed up the nandroid off pbone.
The end result was a factory fresh phone still running 1.15.604, with a new kernel from the 2.0.6 fw I got from moonshine thread, wi_fi not
working.
Click to expand...
Click to collapse
how to fix this problem ?
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 !
So I really want to install the 4.4.2 update to KitKat, my HTC One is still on the stock T Mobile ROM that came with it.
However, when I try to update it goes to CWM and it aborts the installation all the time.
I then found out I need the phone to be S-OFF, so I tried RumRunner and it is stuck at pouring, eventually after a lot of boot loops I get: Turn on your device, run RumRunner again and pray.
Or something off that nature.
I did everything by the book, everything.
Also the System Update notification pops up every time I open my phone. I need to tell it to notify me later again, every time.
I am lost....
Any answer?....
If you are stock, and unrooted, just flash a stock recovery and relock your bootloader.