hi!
a friend of mine brought his wfs (gsm) to me that i've unlocked and flashed custom rom before. it froze during the day when the phone was idle and when he tried restarting it was stuck on the white htc splash screen. nothing has been tampered with so i tried the following:
*trying to boot into recovery(which it had cwm and running without problems before): still stuck on white htc splash screen after selecting recovery option.
*trying to re-flash recovery-boot-system (different kinds, custom, stock) from hboot, successfully flashes, doesn't boot
*at last resort, i relocked the bootloader, created a goldcard and flashed "RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe" which successfully flashed, updated hboot, radio and flashed stock everything.
it finally booted into stock after 15 mins of splash screen. but when it gets to the locksreen, it doesn't respond to the touchscreen or the hardware buttons, the screen sleeps after some time, but hardware button lights stay on, and there's nothing i can do except for removing the battery.
i can't use adb logcat at this point since the debugging isn't enabled on the fresh rom.
after removing the battery and trying to reboot, it's stuck on htc splash again, i have to boot into fastboot, do a factory reset, wait another 15 mins to boot into the fresh rom to get stuck again.
my educated guess is that the nand is worn out.
any suggestions or questions about diagnosing what we might have?
thanks in advance!
up
anyone?
Did you try to reflash recovery?
Sent from my bowl of jelly!
i've reflashed cwm, didn't work. flashed stock recovery, but booting to stock recovery also took like 2-3 mins, more than it should have. flashed cwm again, doesn't boot into it, stays at white htc splash.
Well most of the methods that i know involve recovery, so you are pretty much screwed...
Sent from my bowl of jelly!
Related
Hello,
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will try to boot accordingly for a second, then reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store?
Thanks!
Had a friend bring over an Evo 4g with the infamous bootloop of death.
Specs:
Revolutionary
S-Off
HW: 003
Radio: 2.15.0808
HBoot 6.16
*Aftermarket Extended Battery*
First attempt at booting the phone, it would hit the lockscreen and reset. Then it stopped on the boot animation, and then it hit the splash screen after that reboot and it gave up. Trying to get to recovery at that stage resulted in freezing on the splash screen as well. Flashed the Amon-Ra recovery successfully and it would SOMETIMES go to it and then sometimes it would just freeze on the splash screen. Hmm... Tried CWM recovery with similar results. When I was in recovery, I did factory data and cache wipes as well, just to be on the safe side. No luck. Alright, so I figured let's reset everything and start over, maybe there was a bad flash of a rom or kernel. Flashed the hex-edited HBoot 6.17 and then the stock P36IMG.zip for the 4.54 version. Everything went smooth, no error messages, all OK. Now the phone is listed as S-On with the appropriate HBoot and Radio versions. Good deal...and bootloop issue continues. Argh! Figured, I should try running the RUU from the PC just for heck of it. I tried both the 4.54 and 4.67 versions and both provided Error 120 saying the battery was not 30% or more. Odd, since the battery was charged fully according to the charging light, and from the brief times it did hit the lockscreen the battery looked fine. So I took a break from it. I came back to it the next day and thought I would try and, it booted to the lockscreen, and bootloop. Hmm. Seems it only likes to boot when cool or not having messed with it for awhile. Interesting. Let it set for a bit then put it on a fan and tried to boot to recovery...and it was the first time it had went to recovery in awhile. Hmmm. Took the phone and put it in a tupperware and put it in the freezer for like 10-15 minutes and tried to boot again. Booted all the way just like normal! Weird. Running like a champ. Played around with it for a few minutes, then just let it sit for awhile. No reboots at all. Rebooted the phone manually, but there comes the bootloop. So, threw it back in the freezer and tried it again after a bit and now the phone has been on for over 5 hours. Haven't played with it much, but before it just wouldn't even load, but now, obviously the temp has risen to normal levels and no restarts. I'm completely baffled. Would this be an issue with the battery since it is an aftermarket one (don't have a stock one to test unfortunately) since I know it can cause random issues and RUU didn't like it or...some strange hardware malfunction? Previously thought it might be an issue with the NV partition from the MetroPCS flash but since it is up and running OK now, I would think that would not be the case. Any thoughts?
My One X was working perfectly on Leedroid 5.1. I downloaded 6.2, put it on the SD card, held the power button and went to reboot into recovery, but it got stuck on the HTC ONE boot screen and wouldn't go any further. I thought it was a little odd but ignored it. Then I realised I needed to flash the boot.img anyway, so I turned the phone off then booted into bootloader, fastboot, flashed the boot.img. At the end of the process the phone was sent to recovery again, but again, the same thing happened, it wouldn't go past that screen.
I figured my recovery was corrupted, so I went back into bootloader and flashed CWM touch through fastboot.
Rebooted into recovery again, exact same problem. What gives?
Furthermore, every time I turn the phone off from that screen, it turns itself back on. I finally rectified that by turning it off, then holding vol- and powering down from bootloader.
What can I do?
EDIT: RESOLVED
fastboot erase cache fixed the whole thing!
Good evening everyone,
I've been scanning the forums and everyone's problems seems a little different. First of all, i was running CM10 and missed some of the sense features, so i jumped to ViperX.
1. Everything seemed fine on first run, got the snakey tail, but then i noticed it was hanging just after this with the "Htc quietly brilliant" screen and snakey long gone!
2. So i reboot my phone, this time, it just hung on the first start screen and never so much as flinched.
3. I booted into recovery (CWM) and couldn't even get there, it was like a blink of the recovery screen and then it vanished and rebooted, I wiped everything clean by doing a factory reset and tried to reboot again. Same result.
4, Flashed TWRP and managed to get into recovery mode and install ViperX again but on reboot I'm stick at that same ol' "quietly brilliant" screen, this time with no snakey.
I can get into hboot to use fastboot and into recovery in TWRP but cannot get into the OS. I'm not clear as to whether this is a problem with hboot or the way the rom is installed but any suggestions or such about how i've gone about things and how to go about getting around this problem would be great! Gracias! :good:
Did you flash the correct boot.img?
BenPope said:
Did you flash the correct boot.img?
Click to expand...
Click to collapse
Strangely, and by the luck of trial and error, I tried 2 boot images. The first was for CM10 (again, this was trial and error) and now i've just rebooted from the ViperX one and managed to get back in. Back up in progress! Phewww!!!!
You get my thanks for replying anyhow!
Phone seems fine when in recovery, acts totally notmally. Can flash any ROM without issue, but when you go to boot it will just stay on the boot screen indefinately. The result is the same regardless of which ROM I use. I decided to flash the RUU in the end as I was getting nowhere, but the same result... just stuck on the boot screen (relocked bootloader and flashed stock recovery beforehand)
Anyone seen this before or have any ideas what might be wrong?
Finally fixed. For whatever reason, reseating the battery connector kicked it into action