Related
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
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
plaster said:
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
Click to expand...
Click to collapse
Try redownloading Freegee and rerunning it. After the phone boots up download GooManager, hit menu, and then choose install openrecovery script. Once it downloads and installs, power down the device. Hold volume up + power until you see the LG logo and it goes black with text. Press volume down twice and then power. It should boot into TWRP recovery. Once you make sure it's working you can flash Sk8's CWM recovery, I you want too.
It's the black screen with text that won't load. If I don't unlock the bootloader the phone ignores the button commands. Once I unlock the bootloader, the phone will boot fine, until I attempt to load the bootloader. It just loads a black screen and sits there forever. The phone will never boot past this, even while forcing a reboot by holding power. I'll give your method a shot. Worst that can happen is another LGPNST.
EDIT: Nevermind the above. It's the act of unlocking the boot loader that's actually causing the phone to not boot. After typing the above response, I unlocked via freegee and rebooted, it shows the LG Logo, then just a black screen and it's stuck. Running LGPNST again. I have no idea what could have happened to the booatloader that would cause it to be unable to unlock without bricking my phone.
EDIT 2: Just tried the freegee.bat from the PC. Says the phone has been liberated, but does the exact same thing. I am stumped. I hope I don't have to wait for ATT to release an update so I can run something other than stock.
Sent from my LG-E970 using Tapatalk 2
Looking through the freegee thread, this seems to be a common problem with the newest freegee. Gonna try an older version and see if that's the issue. If not, guess I'm stuck with simple root until I have time to get on irc and see if anyone knows how to fix the corrupted partition.
What firmware u flashing back to with lgnpst? 10o or 11c
Sent from my LG-E970 using xda app-developers app
10o
Sent from my LG-E970 using Tapatalk 2
Root with korean root then 0.5 freegee u should be fine
Sent from my LG-E970 using xda app-developers app
You mean LGPNST with Korean firmware? Never saw Korean root.
Sent from my LG-E970 using Tapatalk 2
I'm at work now but send me a pm or get on irc this evening and we can fix this for ya
Sent from my LG-LS970 using xda app-developers app
Ok, will do. Thanks in advance.
BTW, iamtha1, I tried the Korean Root. It took, but I had the same issue. The only upside to this is that I'm still able to use the phone. It's the stock firmware, but it's not so bad once you freeze the excessive AT&T bloat.
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Salsathe4th said:
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Click to expand...
Click to collapse
Why are you posting here then? Go to the Sprint LGOG forum.
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk
I was trying to flash a ROM (not sure exactly which one - I did this like a month or two ago) but I did something wrong and the phone is now in a boot loop. It gets to HTC logo and reboots constantly. When I try booting into recovery, it show CWM on the screen for a split second and then reboots (back into the bootloop). I am, however, able to get into fastboot. It says "tampered" and "unlocked" at the top. It's hboot version 1.44. When I select the factory reset or recovery option, it goes back into the bootloop.
I have read several posts about connecting it to a computer and using adb to reset it while in fastboot but I can't do that. Whenever I connect it to a computer, the phone does not get recognized on the computer whatsoever. When I plug it in, it starts charging but nothing happens on the computer. I have tried installing the drivers on multiple PCs (both Windows 7 and 8) and I have tried using several different USB cables. This was the case long before it was stuck in the boot loop too so it's not a new issue. It just doesn't get recognized on a computer. I've tried going into device manager and everything, nothing shows up. Is there any way I can fix this issue since I seemingly can't use adb?
Thanks in advance for any help!