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
Related
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!
So I was about to flash a ROM (viperone), and while I was in aroma I went to the "flash stock kernel" setting and did that, because I felt it probably wouldn't hurt. Well, turns out it broke my phone's ability to boot into recovery, from what I can tell. I can enter fastboot and I tried reflashing the recovery but it still won't go to it when I select that setting. What happens instead is it flashes to the HTC screen then it goes black for a few seconds, then it goes to the bootloader screen (where it has the red message) and it just sits there forever. Did I just completely brick my phone by doing this?
Actually scratch that, I managed to fix it by flashing the GPE RUU. Now I just hope I can figure out how to switch it back to stock at some point.
Hey there. Something strange has been going on ever since I re-flashed my phone. When I flash the kernel/rom other than the stock one I get a duplicate Samsung logo when the phone boots. (phone displays Samsung logo, goes black for a second then displays again before boot) I've been flashing and reflashing ever since I got the phone and now I'm getting this. I can get into recovery and download mode just fine and other than that there don't seem to be any other problems. This is just weird. I'm wondering if there's a way to fix this. Also, I'm wondering how such a thing can happen in the first place. I've re-flashed twice now and the result is still the same.
[EDIT]
From what I understand, the boot screen file is located in param.lfs. I've read before that you can add a screen but how in the world would a re-flash cause a duplicate screen to appear? I had a failed kernal flash happen where i couldn't access the recovery and had to start over from scratch but that's happened before.
[UPDATE]
Just tried to mod the boot logo and found out it's requesting "gaudi_bootimage.jpg" twice. I have no idea what this means. Gonna go back in and re-flash the old one back in.
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
I did a search and maybe not correctly but I did not find my particular problem.
So I have stock root66 rom flashed with odin 3.11 on my phone goes into boot loop.
I flashed twrp 3.1.1-0 with odin and I can go into recovery but as soon as I select any rom (OCT-N-WEEKLY-20170811-1427-d2tmo) it starts to do something and just reboots the phone and back into the boot loop. I reboots to fast for me to even figure out what it says on the phone.
Has anyone else experienced this? Battery is charged to 80%+
edit: tried CWM same symptoms reboots right away. Only thing I can flash with is odin otherwise with any recovery reboots right away. I was able to flash a modem with twrp and that works but no roms work.
update 2: I finally was able to get root66 installed. Gets to the set up part. Once I finish the setup the phone turned off on its own. It never turns on on its own so leads me to believe the power button isnot stuck but why does it turn off on its own? I turned back on and goes into bootloop.
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
audit13 said:
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
Click to expand...
Click to collapse
Thanks for the reply. I have tried 6.0.1.2_CWM_Touch-recovery-image & twrp-3.0.2-0-d2tmo.img but not 2.87.
However, as I stated above I was able to flash a modem but just not flash any roms which is weird.
If the power button pressed and the phone reboots when i pull the battery and put back in wouldn't the phone turn back on? I'm just finding it odd the phone keeps rebooting but when I pull the battery and put back in it doesnt turn on automatically.
update: So 2.8.6 twrp worked which is odd installing as we speak phone has not rebooted yet so lets see how it does once rom is flashed. I did odin root66 and after that installed it kept rebooting so fingers crossed this works. Using OCT-N-WEEKLY-20170811-1427-d2tmo hopefully this works
so after the flash seems to just back to the bootloop. I'm still not convinced my power button is stuck since it doesnt auto turn on and during the whole process of flashing it didnt reboot on its own only after the flash. Any ideas?
Literally gets to the samsung galaxy siii logo and reboots right away.
Try flashing the latest stock ROM, not a rooted stock ROM.
audit13 said:
Try flashing the latest stock ROM, not a rooted stock ROM.
Click to expand...
Click to collapse
same bootloop. Gets to the tmobile animation and then reboots.
It's possible that the memory chip is damaged. You could take it to a repair shop and have it flashed via jtag.