As the subject heading says, I am trying to fix a phone for a friend that is stuck in an infinite white screen HTC logo loop boot.
Background: I'm able to pull the battery and then go into the bootloader. I have tried going into the stock recovery to no avail. I have performed the "Image CRC" and "Factory Reset" several times, eventually I was able to get into the device and it worked, but once I restarted it (thinking it was fixed and testing it) it's back to the same state again. I can't get it to communicate with my PC or MAC to do anything with it through ADB. I've been able to get in and completed booted twice now but cannot get in anymore. Both times I hadn't been able to do anything with it except for "Image CRC" and "Factory Reset" because I wasn't near a computer at the time.
I pulled the SD card out so that factor is eliminated
What options are there left? Any suggestions?
No ideas?
I'm gonna download the .19 RUU and try it, as well as the .05 ruu
If its not rooted an still under warranty take it to verizon. If it is rooted,unlocked and s off then try downloading the most recent stock ruu and fastboot flash it.
Sent from my ADR6400L using Tapatalk 2
Sorry, I didn't include that information.
It's not rooted, possibly not under warranty (not sure yet), it's still S-ON.
Part of the problem is the fact I can't get into the recovery either, when I go to do so, it just loop boots again. This phone was never rooted or even attempted to be rooted before I got it so it's not from any causes like that. It's just a simple issue of loop booting and I wanted to try to attempt to root it as well as fix it.
Is it bricked? It occasionally boots in completely but when I went to turn on debugging mode it rebooted again and is now looping again.
At any point were you able to distinguish what software it is running ? .9 or .19. Maybe it tied to download the new software which is .19 and didn't complete. Jast throwing out some ideas.
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1703455
The HTC tool I was referring too
Sent from my ADR6400L using xda premium
Yeah, it's running .19, and I tried flashing the RUU for .19. I tried that tool but it never was able to connect because I can't get it passed the HTC boot and when it recently finally got fully booted and I went to enable USB debugging it rebooted on me and is now still loop booting lol.
I personally have the EVO 3D and have a MAC and PC and have tried having ADB detect the phone and it doesn't. My only guaranteed way to get it from doing anything other than looping is going into the bootloader or HBOOT. If I try the recovery it loops and then normal boot also loops
EDIT: oh and I also have installed a new SD card and formatted it.
any other ideas?
http://forum.xda-developers.com/showthread.php?p=27078714 I linked to another thread with revolutionary hboot drivers, if you need them.
I'm trying to find the stock recovery for you too, maybe you can get that to flash in bootloader
from my ADR6400L using xda premium
http://db.tt/cIqxle9q
Link to stock recovery. Rename to PG05IMG.zip and see if it will flash.
from my ADR6400L using xda premium
It's having a moment of clarity again! lol
I left it alone sitting on the charger for like an hour and went to check it and it was booted up completely. I'm trying to root it with revolutionary but I'm having a driver issue I believe now.
Check the link above with the revolutionary hboot driver download. I had the same issue with it saying "waiting for device.". I installed those drivers, restarted revolutionary and it found it and rooted and s-off with no problem.
Sent from my ADR6400L using xda premium
I spoke too soon, I plugged it into the MAC and it auto-rebooted again and now it's loop booting again.
Here's a few pictures I took when it was working for those few minutes lol.
http://imageshack.us/g/84/imag1246.jpg/
I'm gonna try that stock recovery zip and see if I can let it sit on the charger again (it's a radioshack cig lighter socket adapter with a cig lighter generic charger that matches the .7A from the original instead of charging off USB) to see if it'll go through again
Yeah, same problem. Whenever I plug it into the computer after installing the HTC ADB drivers it just automatically restarts, regardless of which computer (PC or Mac).
It sounds like a physical defect that I'm not going to be able to circumvent.
incarceration said:
Yeah, same problem. Whenever I plug it into the computer after installing the HTC ADB drivers it just automatically restarts, regardless of which computer (PC or Mac).
It sounds like a physical defect that I'm not going to be able to circumvent.
Click to expand...
Click to collapse
That's what i was thinking
Agreed. May not be fixable unfortunately.
sent from above
Related
A few weeks ago, I decided to install Liberated Aria. I had a few problems with the installation, but eventually it ended up working fine. Last night, I turned my phone off and turned it back on this morning, but now it won't boot. When I turn the phone on, I get:
LIBERTY PVT SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN 21_00
RADIO-7.08.35.06
MAY 8, 2010,03:56:58
FASTBOOT
and then the options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
When I try to boot into recovery, I eventually get:
SD Checking. . .
Loading . . .[LIBEDIAG.zip]
No image!
Loading. . . [LIBEDIAG.nbh]
No image or wrong image!
Loading. . . [LIBEIMG.zip]
No image!
Loading. . . [LIBEIMG.nbh]
No image or wrong image.
and the options change to:
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
The only problem is that I can't select any of the options. None of the buttons - volume, power, whatever - change or select anything. I can't get past either of these screens. I'm kind of a noob when it comes to this kind of thing, so any help would be appreciated.
The phone will automatically boot into FASTBOOT mode if you hold down the trackpad button while pressing the power button. Is it possible that your trackpad button is broken and is being registered as held down? Try messing with it to see if you can fix it. Otherwise you may have to get the phone replaced if it's under warranty.
This issue does not sound like it is related to installing Liberated Aria.
The trackpad button feels the same as it always has when I click it and I don't see anything visibly wrong with it, so I don't see why it would be registered it as clicked. I tried pushing it and all the other buttons a number of times with the same results. I even took off the screen protector thinking maybe that was causing a problem. Is there a way I can just put an image on my SD card and have it automatically boot that so I can fix it?
Doesn't installing a custom bootloader and/or ROM void the warranty?
Well, you probably will be able to simply run the 2.1 RUU on your phone since you can get to FASTBOOT. I'd probably recommend that over doing the SD card method because when you do the SD card method, you have to press a couple buttons to confirm actions which may not work if your phone isn't accepting button presses. The RUU method does not involve any button presses on the phone itself.
However if you want to try the SD card method I can point you in the right direction.
Edit: Link to 2.1 RUU here: http://www.mediafire.com/?cj56c2gfk86k8oe
Rohda said:
Doesn't installing a custom bootloader and/or ROM void the warranty?
Click to expand...
Click to collapse
Installing a custom bootloader would for sure, but you don't have a custom bootloader. Installing a custom ROM does, but you can reverse the process (via RUU) so they can't really tell.
I downloaded the 2.1 RUU, booted to recovery, connected my phone to my computer, and tried to run the RUU but it gave me a USB connection error. Windows also gave me a USB device not recognized error. My phone does say HBOOT USB PLUG, though. Aside from HTC Sync, do I need another driver?
Do you still have the HBOOT driver installed from when you used Unrevoked? If so you should uninstall that driver I believe. That might be interfering.
Also trying running the RUU when your phone is in FASTBOOT, not HBOOT, to see if that works.
I did have the HBOOT driver still installed. I uninstalled it from device manager and deleted the driver folders. Android Phone doesn't show up in device manager anymore. I retried running the RUU in HBOOT and tried running it in FASTBOOT and still get the USB connection error. Any other ideas?
Try reinstalling HTC sync
Sent from my Liberty using XDA App
Also try doing it on a different computer if you have access to one. Preferably one that never had any drivers on it before. Just install HTC Sync, then run the RUU, that's it.
I've always had trouble getting the RUU to run. It's bizarre.
If that doesn't work, and you still want to try the SD card method, you can download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file to LIBEIMG.zip then place it on the SD card. Then it should automatically detect the file next time you're in HBOOT and ask you if you want to proceed with the install. It's pretty self explanatory. Be patient as some steps take a while and it may appear like nothing is happening. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.ZIP file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
I reinstalled HTC Sync and it wouldn't recognize the phone was connected.
It seems to have taken a turn for the worse. Now, it won't even turn on. The screen turns on (but stays black) and off and the notification light flashes red when connected to a computer but won't do anything at all when it's not connected. I'll try to plug it into a wall instead of a computer and let it charge for a while and try the SD card method.
I went in today to get it checked out and got a new SIM card and a new battery and it fixed the problem.
Thanks a ton for all the help.
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
U try running the RUU?
Sent from my EVO using XDA
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Gotta do it...
sent from my EVO LTE
See post edit.. : S
naterz said:
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Click to expand...
Click to collapse
where did you get the 1.12.651.2
all i can find is 1.12.651.1
shipped-roms.com. I guess i could try the .1 version
when i try to run the .1 ruu, it shows im on 1.12.651.1_R2
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
naterz said:
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
Click to expand...
Click to collapse
Navigate to your adb tools folder via terminal and type
adb reboot bootloader
tried adb reboot, error device not found : (
ddeecc
naterz said:
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
Click to expand...
Click to collapse
But you did get to the splash screen and that's a sign of hope..this phone won't even do that. nothing at all screen dead, everything is dead including bootloader. :\
Shutdown the phone and boot into bootloader.
Option 1) do a factory reset and if it doesn't work then,
Option 2) select fastboot then ran Ruu.
Sent from my HTC One X using xda premium
There is no way to boot into bootloader or fastboot, whether through adb or the key combos :S Adb states device not found and the key combos only give me splash then a lightly lit black screen..
Sent from my PC36100 using XDA
Are you positive about not able to boot into bootloader with key combo? Your phone has to pass bootloader before going to the splash screen.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
So you tried booting as instructed as the above link?
Sent from my HTC One X using xda premium
Ive never really pressed the power button a second time after the initial let-off. I'll give it a shot when I get home, but I'm expecting the same results. Just FYI, I DO see the two Orange bars move on the splash screen (upper right) before it goes blank..
Sent from my PC36100 using XDA
Sounds like a case of the looped boot screen
Sent from my HTC One X using xda premium
UPDATE! Phone was completely drained when i got home...plugged into charger, orange light came on! Was able to enter the bootloader through the key combo and successfully entered my TWRP to do a nand restore. Restore went well and am now running again! Brick fixed by draining battery!
Good to hear:good:. brick was fixed by draining battery :what: then why did you need to do a nand restore? Whatever worked for you
why i said it was fixed via drain was that the charge light finally came on after it died and was plugged in, therefore it allowed me to access bootloader which let me into recovery to restore my backed up clean system files. When the nand restore was completed i was actually able to pass my splash screen! : )
At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Ivanov4912 said:
At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Click to expand...
Click to collapse
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
It sounds like your phone is stuck in Download Mode, that is used by the older RUU EXE files... you run it from your PC and just walk through the steps to install the firmware. Perhaps trying one of those, they can be downloaded here: http://mobile-overload.com/topic/53-ruu-htc-rezound-ruu-roundup/ but I think the newest EXE version you will get is 2.1.605.11 which is Gingerbread. It will return your phone to bone stock Gingerbread, S-ON, stock recovery, and all that good stuff, but it might work and get you running again.
It's the glitch that you get when you install cwm on a rezound, you can't charge your battery. Look it up on xda they have a solution.
That's the thing. It doesn't work at all.
Sent from my SCH-I535 using xda premium
Here's the link to save your ass.
http://forum.xda-developers.com/showthread.php?t=1711408
If you need to buy another I can sell you mine 230 + shipping obo
mforminio7 said:
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
Click to expand...
Click to collapse
The phone doesn't work at all. It doesn't even turn on.
so i received two htc eris' from a buddy of mine yesterday so my girlfriend could finally make the move up to a smart phone. neither were ever rooted and were running stock software. one of them works perfect but the other was stuck in an infinite boot cycle so i tried to hard reset it but it gets stuck at the screen with the red triangle and exclamation point.
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
goatxxmastr said:
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
Click to expand...
Click to collapse
You can only push a new Recovery image using Fastboot if the Eris has the S-OFF bootloader (HBOOT version 1.47.2000 S-OFF). Most Erises are HBOOT 1.46.0000, 1.47.0000, or 1.49.0000 with S-ON.
One method is to install HTC's latest 1.51.0000 bootloader, unlock it, which should allow fastboot to push the recovery image. See http://forum.xda-developers.com/showpost.php?p=23034380&postcount=3 for a more elaborate procedure that you can follow if pushing the recovery image still doesn't work.
I strongly recommend using Scary Alien's version of Amon_RA. Stay away from ClockworkMod Recovery as the default recovery on an Eris - it is problematic if flashes fail. Amon_RA is safer and there are no documented bricked phones from people with Amon_RA. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
Stock DNA, never rooted, never s-off. Fell asleep and woke back up with phone in quietly brilliant bootloop. Went into boot loader, cannot access recovery(just bootloops), can't do factory reset(just freezes and have to reboot) . Downloaded and followed all necessary steps to use adb and reboot recovery, when typing adb devices it shows up blank, but when I do fast boot devices my serial number comes up. When in fast boot on the phone it says fast boot USB how it should. As of lately the bottom 3 buttons are starting to flash when holding down power button, before they didn't. Also when I plug it into the wall it never showed the battery icon actually charging, but now it does, when it gets to a certain % it turns itself on and bootloops. What to do what to do??
I can always run the latest ruu file, but won't that pretty much wipe everything?
Yes, ruu will wipe everything. If your pho e isn't accepting any commands, I don't see how it would accept an ruu anyway. You could try it.
Sent from my HTC6500LVW using XDA Free mobile app
Upon further investigation, I'm pretty sure it's the boot loader that's the problem, it can reboot when I do fast boot reboot, but when I do reboot boot loader it just shuts off and doesn't turn back on. Same with trying to run the ruu, connects and everything, but as soon as it reboots back in the boot loader, it doesn't and says there's a USB connection error. So thats where I'm at, any help at all?
What OS is your PC?
Sent from my HTC6500LVW using XDA Free mobile app
Still running windows vista!
It might be a driver issue. can you try to load up a Linux live CD and see if it recognizes the phone? Vista hasn't had any updates or support from Microsoft since 2011 iirc.
Sent from my HTC6500LVW using XDA Free mobile app
Not alot of experience with Linux, anyway you could get me a link to what I need. I also tried the SD option from bootloader and it said Initialization failed.... So not sure if its an SD card issue.
Well, not sure what happened, but I did Fastboot oem task 28 and it accepted and turned right back on! Hell yes.