For the past few weeks I had been running ViperOne rom. I liked it very much and it was for the most part stable, but I decided to try out UnsenseOne-KitKat. I tried installing the zip file using TWRP, just as I had done with ViperOne but when I tried rebooting, my phone only went to the bootloader and wouldn't even try booting to system.
I had a problem similar to this before when I was trying to unlock and root my One, so I thought I was fix it the same way I did then. I downloaded the vzw m7 RUU from here and installed it using fastboot. The RUU installs just fine and everything in the command prompt says that it was successful. But when I try to boot my phone now, it hangs on the white htc splash screen.
It also hangs on the white htc splash screen when I try to enter recovery. I'm at a loss, and I am now thinking I may have gained a new paperweight today. Has this ever happened to anyone? Or does anyone know how to fix this?
If it helps, this is what I see on my bootloader:
relocked
m7_wlv pvt ship s-off rh
cid-vzw__001
hboot-1.44.0000
radio-1.12.41.1112_2
opendsp-v33.120.274.0913
emmc-boot
UPDATE: Okay, so I tried installing instead the 2.10.605.1 RUU (I had been using the 1.10 version before) and now instead of hanging at the white htc splash screen, it shows the slpash screen for a few seconds and then goes back to the bootloader saying "Active cmdline overflow! (1073 Bytes)" This is new... any ideas?
UPDATE2: I googled the Active cmdline overflow problem and saw that for some it worked to downgrade hboot to 1.44. I got the hboot zip from here. And now no more Active cmdline problem! YAY! Only now my phone is once again hanging on the white htc slpash screen.
UPDATE3: Haven't done anything else since the last update, but I did just notice that when I try to boot into recovery, I get a black screen with a picture of an phone with a red triangle on it. I get a similar screen when I try to boot into "Factory Reset" but instead of a red triangle there are two green arrows making a circle. Also when my phone is plugged in my phone now once again shows the charging animation (phone turned off). This was not the case before.
-updated original post
That sceeen is the stock recovery. Flash this in ruu mode. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip. That should get you twrp recovery. From there do a factory reset and then flash a rom, and see if it boots. If it does use firewater to unlock the bootloader again.
cmlusco said:
That sceeen is the stock recovery. Flash this in ruu mode. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip. That should get you twrp recovery. From there do a factory reset and then flash a rom, and see if it boots. If it does use firewater to unlock the bootloader again.
Click to expand...
Click to collapse
So I did what you suggested, and the .zip file flashed just fine, no errors, but I'm still stuck at the "Entering Recovery . . ." screen.
rtphysicist said:
So I did what you suggested, and the .zip file flashed just fine, no errors, but I'm still stuck at the "Entering Recovery . . ." screen.
Click to expand...
Click to collapse
Nevermind, I downgraded to hboot 1.44 and I was able to enter recovery. Thanks!
Related
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
The first time I tried to Root my phone, I had the same problem with Toasts Root method. That's stock Recovery you're seeing.
I ended up having to use Unrevoked Linux version and swore I would never unroot again, and I haven't.
I've tried using unrevoked and several other methods. The problem is I think most of them rely on the phone being on with USB debugging enabled. I unfortunately can't get there. The one ray of hope I have is that the device is recognized in my device manager as "Android USB device - HTC bootloader". Is there any other way I could fix this?
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
Are you holding power and volume down at the same time. Sounds like you are just holding volume. When you get to the bootloader I'd you see s-off all you will need to do is flash a PC36IMG of the recovery of your choice(I recommend twrp). Good luck!
Sent from my PC36100 using XDA Premium App
Also, no need to unroot for any rom. Once you are rooted you can flash anything you want. Compatibility wise, you may need to update a radio but that is just flashed in recovery.
Sent from my PC36100 using XDA Premium App
Thanks for the reply. Unfortunately I am holding power and volume down. Powering it on normally and powering it on while holding volume down both go to the same screen.
I had a Desire HD for a year. I just started rooting and using custom roms three months ago.
A few days ago, when I got the phone from charging, I found it frozen. I restarted it to get a looping "force close" for almost all processes. I restarted it again to the same result; the third time I restarted the phone emited 7 short vibrations just after powering it, and after some time in the initial HTC logo it froze in a black screen.
I tried to reflash my last custom rom I used, so I booted to ClockworkMod recovery and tried to reinstall the last ZIP file I kept on my SD card from last time, it installed ok, but then I got the exact same scenario: 7 vibrations, HTC logo, black screen of death.
Later, I tried to flash another custom rom, but now I can't boot to recovery. It does the exact same thing as trying to do a standard boot.
So now I'm stuck in Fastboot. I tried flashing a stock rom (downloaded the lastest official RUU), but while it seems to flash it ok, it still hangs the same. I also tried to flash copying the ROM.ZIP file from the RUU to the root of the SDCARD as PD98IMG.ZIP, but while it also seems to flash the ROM ok, it still fails to boot.
This is what I discovered (Googling):
-The 7 vibrations means bad CPU. What I don't understand is why fastboot works perfectly without any hang but can't boot even in recovery mode.
-I can't use my warranty while the phone is ENG S-OFF.
I think I succeeded to flash a stock ROM, so now the only thing that keeps me to carry my phone to fix is the ENG S-OFF. Is there a way to set ENG S-ON while in fastboot?
spyd77 said:
I had a Desire HD for a year. I just started rooting and using custom roms three months ago.
A few days ago, when I got the phone from charging, I found it frozen. I restarted it to get a looping "force close" for almost all processes. I restarted it again to the same result; the third time I restarted the phone emited 7 short vibrations just after powering it, and after some time in the initial HTC logo it froze in a black screen.
I tried to reflash my last custom rom I used, so I booted to ClockworkMod recovery and tried to reinstall the last ZIP file I kept on my SD card from last time, it installed ok, but then I got the exact same scenario: 7 vibrations, HTC logo, black screen of death.
Later, I tried to flash another custom rom, but now I can't boot to recovery. It does the exact same thing as trying to do a standard boot.
So now I'm stuck in Fastboot. I tried flashing a stock rom (downloaded the lastest official RUU), but while it seems to flash it ok, it still hangs the same. I also tried to flash copying the ROM.ZIP file from the RUU to the root of the SDCARD as PD98IMG.ZIP, but while it also seems to flash the ROM ok, it still fails to boot.
This is what I discovered (Googling):
-The 7 vibrations means bad CPU. What I don't understand is why fastboot works perfectly without any hang but can't boot even in recovery mode.
-I can't use my warranty while the phone is ENG S-OFF.
I think I succeeded to flash a stock ROM, so now the only thing that keeps me to carry my phone to fix is the ENG S-OFF. Is there a way to set ENG S-ON while in fastboot?
Click to expand...
Click to collapse
Ive had multiple vibrations thats when i was deving on something (unreleased)
Take out battery for 30mins then put it back n try recovery mode again, make sure you install a custom rom again after full wiping
EDIT: flashing stock ruu should s-on, then redo s-off that should fix it afaik
Sent from my Desire HD using Tapatalk
shaky156 said:
Ive had multiple vibrations thats when i was deving on something (unreleased)
Take out battery for 30mins then put it back n try recovery mode again, make sure you install a custom rom again after full wiping
Click to expand...
Click to collapse
I already did this (not intentionally). It doesn't change anything.
shaky156 said:
EDIT: flashing stock ruu should s-on, then redo s-off that should fix it afaik
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
If flashing stock RUU should s-on, then the flashes I tried didn't complete. I guess the flash finishes after the first boot, but as the phone hangs before booting, no flash is done?
Anyway, if this helps somehow, this is what shows my fastboot:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.13.04.19_M
eMMC-boot
Oct 11 2010,12:44:14
Click to expand...
Click to collapse
Hey Guys,
I already searched in the whole forum and tried a lot of different tutorials and stuff but i just can't bring my desire back to life... :crying:
I got it today from a friend and tried to update it and after that it was stuck at the white htc screen and wouldn't boot.
However I wasn't able to get into the recovery mode because the phone would jump back to the white htc screen and freeze (sometimes it would vibrate 7 times)
I then tried to recover it with a ruu but i got an 152 error and now i have the black htc screen with the four /!\ in the edges. I tried different ruus, including some from vodafone (because i wasnt sure if my phone is branded or not) but with the vodafone ruus i get a 131 error (so i guess my phone is not branded). i also tried the 2.3 gingerbread image.
When i try to recover it with the gingerbread image it stops at about 55% at system rewriting (or sth. like that)
When i plug it out after this i get the following stats:
BRAVO PVT1 SHIP S-ON
HBOOT-1.02.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Jul 22 2011, 16:19:16
RUU
Parsing... (downloaded ZIP)
Bootloader - Bypassed
Radio V2 - Fail-PU
Radio Cust - ok
Boot - ok
Recovery - ok
System - ok
Userdata - ok
Splash 1 - ok
Splash 2 - ok
Partition update fail!
Update Fail!
I also get the Error 140 from time to time...
I think i might have to downgrade the hboot, but i don't know how, cause i am s-on and can't get any further than the black htc screen (=fastboot)
i also have the adb toolkit, and i tried to force boot it by the command fastboot oem boot... but it froze at the white htc screen and vibrated 7 times
And i dont have a goldcard...
Can anybody help me with this? if you need more information just ask!
this happened to me...try s-off your device with revolutionary...and then get back to stock hboot from alpharev...and then try gingerbread image to install....
good luck...
Thank you for your reply
How can i s-off the device with revolutionary? it doesnt seem to work in the fastboot screen with the /!\ ??? Revolutionary stucks at "Waiting for device..."
ZeitiH said:
Thank you for your reply
How can i s-off the device with revolutionary? it doesnt seem to work in the fastboot screen with the /!\ ??? Revolutionary stucks at "Waiting for device..."
Click to expand...
Click to collapse
You have a radio brick. Few phones are recovered from this state. The only thing you can do is endlessly flash a RUU hoping that sometime it will succeed.
Try the 2.3 RUU in my sig, or the .exe version of it, or some wwe ruu-s.
//Edit: Post 999
Thanks abaaaabbbb63 for your answer, but i think i might found the first part of the solution
I just stumbled across the "fridge/freezer" method and it worked . Simply put your desire into the fridge until its really cold and the ruu will finish the update. (I think its because the radio gets really hot during updating. For example, the more times you try to update it in a row, the hotter it gets and the sooner the ruu stops)
However, now I'm stuck in an Boot circle. Phone vibrates, green htc logo for a few sec, then black screen and the phone boots again.
But i can get into the boot loader with power and volume-.
Hboot is 1.02.0001
i can go into fastboot, but when i try to get into the recovery mode, the phone is stuck in the boot cycle again.
Anyone some suggestions on how to continue this? I think i need to turn s-off to downgrade the hboot if im right but how?
Update: When i try to do fastboot oem boot via adb, the phone vibrates 7 times in is back in the boot cycle
Update 2: Correct me if I'm wrong but I think i have to set up a custom recovery mode like clockwork via pb99.img, right? However dont have time now, will try it tomorrow...
Yesterday I decided to try rooting my phone for the first time and after a long journey I think I may have screwed up my phone. At first, it went fine. I had cwm as a recovery and installed cyanogenmod. I decided to try another rom, so I deleted the data to start anew. At this point, cwm kept rebooting and wouldn't allow me to recover, so after trying a few solutions I stumbled upon this thread- http://forum.xda-developers.com/showthread.php?t=2437436. I followed the instructions but was left with an error; FAILED (Remote: 53 Image Unzipping Fail). When I restarted my phone, my phone has been stuck in what I believe is ruu mode (black screen with silver htc logo, one triangle on each corner). I can't get back to the recovery menu even if I hold the power button and volume down. I can sill run fastboot, though, so I can keep trying to flash the Rom.zip, but it has that same error. It was S Off and Relocked before I encountered this problem. Is there any way to fix the phone?
Sounds like you can get into ruu. Just follow the instructions in the ruu post. If you can fastboot just fastboot flash boot boot.img, that should get recovery back.
BoneStock S-Off Unlocked Verizon One
Htc One M8... was running marshmallow sense rom with elementalx kernel.
- S-off
- running Bell marshmallow firmware
- Twrp recovery latest one.
Randomly the phone rebooted while I was using it last night and after that got stuck in a bootloop.
Now it seems to boot up but it goes to a screen where it says "please enter password to decrypt phone" ... I don't have a password so then it tells me to factory wipe the phone.
I can get into Hboot fine... the issue I am having is for some reason along with the rom, the recovery has crashed too... I have tried reflashing a new twrp or even the stock recovery but the recovery just will not boot. Regardless of me flashing the stock recovery... when I try to boot into it, it shows that I am booting into twrp (which makes me assume that the recovery isnt really being flashed)
I tried the RUU method but when I do rebootRUU from fastboot it just boots my phone and its stuck back in the bootloop and doesnt go to Black HTC screen :S.
Kind of stuck... I dont have a windows device otherwise I would try the exe method and lost on how to recover the device. Feels like maybe the flash memory crashed... but its so random
If anyone can help, would be greatly appreciated.
Thanks
so just tried to run a gpe ruu as well... it did the first step of flashing the bootloader and just rebooted to the normal htc bootloader :S
seems like whatever I do nothing is being flashed to any partition... i found the adb command that fixes encryption for aosp roms... but I cannot run adb because I cant boot into recovery :S