In the begginings: Buy, enjoy blabla... Unlock bootloader, flash cwm 6.0.3, root, enjoy... and than i want something more! I try to install a customROM and i choose ViperX 4.1.1. . I read a lot of about this, than i flash philz touch, and install the rom. It works for weeks without any problem, and once on a nice morning it was frozen when i want to watch the time on it (one day before this is install tegra overclkock, and set the number of cores to 2, this may be the culprit?) reboot->white htc logo-> and its stucks on the white HTC screen (not boot loop) when i try to turn on (not the "htc quetly brilliant", just white background and green "htc" logo). I can boot into bootloader, but boot into recovery is difficult. A few days ago it was easy, bootloader->recovery and done. But now its stucks on the white htc screen too. Approximately in every tenth time i can boot into recovery (i dont now how, i try it on charger, on pc/usb, without charger, with full battery, with low battery, and sometimes its succeeds. I use Philz Touch 5.15.9 because i read that its recommended to install ViperX 4.1.1. I try to flash CWM recovery but its freezes now on the first "page", before i install ViperX i used this. TWRP recovery simple doesn't works on my phone (i try with and without thouch, but the volume buttons can't scroll, and the touch doesnt works too). So i have to use Philz Touch recovery. So, in recovery i did a backup from the stock ROM with CWM, and now i tried to restore with Philz (it can be a problem?) but its doesnt works, (the first time i can turn on, but after i make a call, it freezes and can't be turned on anymore, just the white htc logo...) i tried to install viperx, but it doesnt works too, but it can reach the boot screen, or even 1-2 times the home screen . After this i tried to install the ViperX or restore the stock in several combinations of wipe cache, data, factory reset, dalvik cache, flash boot image but i cant bring it to life...
Does anybody have any idea what could be wrong? Maybe a solution?
HTC One X (Tegra3)
S-ON
HBOOT: 1.72.0000
mainver: 4.18.401.4
CID: HTC__032
Radio: 5.1024.167.31
Recovery: Philz touch 5.15.9
ps.: on the white htc creen, i see very little fading (i mean it turn into a very-very little bit birghter) after a few ceconds.
and sorry for my "english"
Thanks
Related
Hi
HBOOT 0.80
Radio 5.14.05.17
I have my Desire for over a year and had it rooted with unrevoked and already used several custom ROMs. The current ROM is GingerVillain 1.1, which works beautifully.
I was able to boot into RECOVERY and flash without problems till today. But now when I boot into the RECOVERY in HBOOT (Power + Volume -) or the ROM-manager (if the ROM is launched):
First appears the HTC logo with white background, then the screen stays black forever. When I'm in this state and press the power button, I see the text "ClockworkMod Recovery v. 2.5.0.7", but not more. (I have not SLCD AMOLED)
When I removed the battery, I can start the phone again, and somehow it always starts at the HTC logo exactly twice, then booting up. The ROM is running as normal.
I have already installed the new ClockworkMod with the ROM-manager, which had brought nothing.
I hope someone of you a tip or an idea.
Thank you for your help.
Can anyone help me?
can anyone help me?
Try to reflash CWM using unrevoked again. You can only flash cutom recovery via fastboot if you are S-OFF.
If 2.5.0.7 is not working try a newer version on AmonRA.
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!
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
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!
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!