My phone is in an endless boot loop where it wont boot into the ROM. Everytime it's powered on, it goes straight to recovery. When I relock the bootloader to try and restore with the RUU, it says "security warning" and the RUU restore fails for a signature. I searched and couldnt find a similar problem. It fails for both 605.6 and 605.11 RUU's.
EDIT: Also, in recovery, I get this error Cant mount /dev/block/mmcblk0p36 (File exists)
hellhawk741 said:
My phone is in an endless boot loop where it wont boot into the ROM. Everytime it's powered on, it goes straight to recovery. When I relock the bootloader to try and restore with the RUU, it says "security warning" and the RUU restore fails for a signature. I searched and couldnt find a similar problem. It fails for both 605.6 and 605.11 RUU's.
EDIT: Also, in recovery, I get this error Cant mount /dev/block/mmcblk0p36 (File exists)
Click to expand...
Click to collapse
What rom were you on, what kernel did you install and I am not familar with those RUU's is that the complete name. The pre ota RUU started with 1.02.6xxxx..the after OTA RUU started with 2.xxxxxxx
Lol. You gotta flash the boot.img probably.
Sent from my HTC Rezound™ using XDA Premium
What mainver are you on? You can check in fastboot:
fastboot getvar all
If you are on 1.x or 2.x RUU should work.
If you are on 3.x you'll have to do a fix for that. If you go to the thread for Awesome Recovery Tool it should automate it for you. Then you'll probably need to get one of the stock OTA ROMs instead of using the RUU.
That security warning tells you you aren't on the official ROM or something similar, don't worry about that.
But first... if you can unlock the phone again, see what happens, that factory resets. Unless you'd rather run the RUU, it will definitely give you a fresh start as it really wipes the phone, so make sure you don't need anything off it.
You are getting security warning when trying to ruu because you have to relock.
Fastboot OEM lock.
Then ruu
Sent from my ADR6425LVW using XDA App
andrewp3481 said:
Lol. You gotta flash the boot.img probably.
Sent from my HTC Rezound™ using XDA Premium
Click to expand...
Click to collapse
I made a nandroid as soon as I was rooted and flashed the backup system.img and boot.img. Now it's stuck at the white HTC screen.
feralicious said:
What mainver are you on? You can check in fastboot:
fastboot getvar all
If you are on 1.x or 2.x RUU should work.
If you are on 3.x you'll have to do a fix for that. If you go to the thread for Awesome Recovery Tool it should automate it for you. Then you'll probably need to get one of the stock OTA ROMs instead of using the RUU.
That security warning tells you you aren't on the official ROM or something similar, don't worry about that.
But first... if you can unlock the phone again, see what happens, that factory resets. Unless you'd rather run the RUU, it will definitely give you a fresh start as it really wipes the phone, so make sure you don't need anything off it.
Click to expand...
Click to collapse
I'm on 2.01.605.11. I can unlock and relock the phone without a problem, but where it should factory reset, it doesn't and boots and stays stuck on the white HTC screen.
nosympathy said:
You are getting security warning when trying to ruu because you have to relock.
Fastboot OEM lock.
Then ruu
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Problem with that is that when I relock and launch the RUU, it fails for error 132: signature error.
I was able to fix my problem by extracting the firmware.zip file inside otapkg.zip, renaming it to ph98img.zip, installing it in hboot and then flashing Amon Ra recovery and installing a custom ROM.
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
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
There is always something wrong with his ROMs, including the ones he made for the Thunderbolt. . I tried flashing one of his a week ago. The phone would not connect to the network, wifi worked. I ran a different rom still no connection, ran the RUU, no luck. I had a new sim put in, and wound up getting the unit replaced.
Are you S-Off? Are the proper drivers for your computer installed?
http://forum.xda-developers.com/showthread.php?t=1928439
Also did you have the eng hboot and did you switch back to the pre ota hboot before relocking? Cause if you locked with eng then that will definitely brick your phone. If that didn't happen and you can still get into fastboot then it's just your on the new hboot and RUU won't run with the new hboot. Just flash the pre ota hboot then run the RUU that should make it run.
Sent from my 5 Senses of DNA
RLGL said:
There is always something wrong with his ROMs, including the ones he made for the Thunderbolt. . I tried flashing one of his a week ago. The phone would not connect to the network, wifi worked. I ran a different rom still no connection, ran the RUU, no luck. I had a new sim put in, and wound up getting the unit replaced.
Click to expand...
Click to collapse
Hmmm. I've used his ROMs on my last three devices without issue. At all. Including the DNA.
Sent from my Nexus 10
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
Are you on the 2.04 firmware at all?
Sent from my HTC6435LVW using XDA Premium HD app
try this
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
Youre not bricked. As long as you can get to the bootloader menu there is hope. You have to re unlock using the unlock token HTC emailed you through fast boot . fastboot Flash unlocktoken unlock_code.bin I believe is the command. Then after reflash your ROM through recovery
Flash twrp recovery if possible via fastboot if you don't already have it, adb sideload a stock rom
Sent from my HTC6435LVW using xda app-developers app
So, I think I completely messed up my DNA. I did moonshine S-Off, I downloaded GooManager. I was looking on Goo's ROMS compatible with my device, and I tried to install one of the ROMS and my phone is stuck in a bootloop.
ive tried Ruu back to stock, but keep getting "Error 158" which is the wrong image for my phone.
Yes I relocked, or atleast when I attempt to relock it say "Already locked!"
what do I do.
Breaoliver88 said:
So, I think I completely messed up my DNA. I did moonshine S-Off, I downloaded GooManager. I was looking on Goo's ROMS compatible with my device, and I tried to install one of the ROMS and my phone is stuck in a bootloop.
ive tried Ruu back to stock, but keep getting "Error 158" which is the wrong image for my phone.
Yes I relocked, or atleast when I attempt to relock it say "Already locked!"
what do I do.
Click to expand...
Click to collapse
Error 158=need to downgrade to Hboot 1.15
Breaoliver88 said:
So, I think I completely messed up my DNA. I did moonshine S-Off, I downloaded GooManager. I was looking on Goo's ROMS compatible with my device, and I tried to install one of the ROMS and my phone is stuck in a bootloop.
ive tried Ruu back to stock, but keep getting "Error 158" which is the wrong image for my phone.
Yes I relocked, or atleast when I attempt to relock it say "Already locked!"
what do I do.
Click to expand...
Click to collapse
When you get stuck in a bootloop all you should have done was booted back into recovery and restored your backup that you should have created before flashing the Rom that gave you trouble.
Always have a good backup on your device at all times. There is no need to RUU just because of a bootloop. RUU is generally for much larger headaches like no data on sense or something.
Just go back and unlock your bootloader and either sideload a different Rom or if you have a nandroid restore it.
Sent from my dlx using XDA Premium HD app
Before I start off, let me just say that I've searched around for a few days now and have not been able to find a fix for this.
I'm on a TMO HTC one with s-on. My phone was rooted and unlocked. To take the update for 4.3 I relocked my phone (it says relocked on the bootloader screen). I have tried running both RUUs for 1.27.531.11 and 3.24.531.3. I have tried running them from fastboot on the hboot screen and from just having the phone on. I have checked within fastboot (fastboot devices) and my computer does see my phone attached. I run the RUU and both versions get stuck on "sending." I have let them run for hours and still nothing. I have also redownloaded the files thinking maybe something was corrupt.
I'm at a loss here. I have no idea what to do at this point and any help would be appreciated.
I also just found out I cannot do a factory reset or enter recovert from hboot if this helps with anything.
Cyanotic said:
I also just found out I cannot do a factory reset or enter recovert from hboot if this helps with anything.
Click to expand...
Click to collapse
I'm no pro, but do you have stock recovery installed? I think if you're s-on you have to be locked/relocked with stock recovery. That's my only suggestion, good luck.
Sent from my HTC One using Tapatalk 2
eliasadrian said:
I'm no pro, but do you have stock recovery installed? I think if you're s-on you have to be locked/relocked with stock recovery. That's my only suggestion, good luck.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
When I was originally playing around with it I did not. I played around some more today and I have a stock recovery flashed now for my device. I was getting the red triangle when I try to enter recovery, or take the 4.3 update. The thing that finally worked was running the new RUU in fastboot.