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! : )
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
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Pretty much have the same exact problem on my thread :S http://forum.xda-developers.com/showthread.php?t=1725027
Take to sprint store and they willgive you a new one
sent from my EVO LTE
cant wait
ddeecc said:
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hopefully one day someone will figure this out with out actual casualties. Thanks all for your help. I'm getting a new one tomorrow.
I wanted to know if you found a solution because im dealing with a similar problem. I can cant access my phone manually or through fastboot
Linux will help you with download mode. There's threads on how to use ubuntu to unbrick. I'd find the thread for you, but am not in a position to do so.
Sent from my EVO using xda app-developers app
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.
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
I had this issue, if you boot into bootloader does it say tampered? If not turn your phone completely off and then boot it into bootloader. Then you should be able to enter recovery. I ciuldnt enter recovery until my bootloader read tampered.
Sent from my HTC One using Tapatalk 4 Beta
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
blackplague1347 said:
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
Click to expand...
Click to collapse
Yeah it took me more then 10 tries until I just shut it off and then went into bootloader and there was the tampered. Glad it worked out for you.
Sent from my HTC One using Tapatalk 4 Beta
I had the same problem. I just did "adb reboot recovery" once and it worked, and it boots to recovery from the phone now every time.
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
im still having the same problem after allot of tries is there some sort of fix ?
Fastboot Tampered?
im still having the same problem after allot of tries is there some sort of fix ?
Click to expand...
Click to collapse
At the top of your devices when at the fastboot screen does it say Tampered?
Corey.C said:
At the top of your devices when at the fastboot screen does it say Tampered?
Click to expand...
Click to collapse
Yes mine says that. I am a new to this, what do i need to do
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again