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
Related
I could really do with some help on this - Kinda paniking cos i'm afraid!
I posted it in the thread on modaco too, so hopefully I can get some help
I am on a 16gb Wifi Euoropean Flyer that needs the RUU RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204727_signed
I have downloaded all the necessary things, checked all the MD5 sums etc etc.
I have successfully gotten to step 14, where i successfully unlocked the bootloader with the HTC dev tools.
Once the gui option came on screen to say whether i wanted to unlock the bootloader, i selected yes, and instantly the device rebooted, but stayed on the white HTC logo screen.
It stayed like this for about 5 mins, before i held the power button down, restarted and got back to the bootloader. (It says unlocked at the top in pink)
I ran the adb command to flash the updated recovery image, (fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.hboot0011.img), and it said 'sending' okay and 'writing'okay but once i selected to go to recovery, the decive just stayed on the white splash screen, and i think it is in a bootloop.
I can successfully get back to the bootloader every time, and it is displayed as fastboot USB in red (i can hear the sound as it is connected to my machine), but when i type adb devices, it says device cannot be found.
I can however relock and then subsequently unlock the bootloader using the HTC dev tools, but still get stuck at this point. (when relocked it does say *security warning* as well as locked)
Please please please can somebody help, this would be much appreciated.
(I'm not sure if it is possible to place a recovery image on the SD card and let the bootloader install it as it does the checks at the start?)
Thanks in advance
You can't communicate via adb in fastboot menu
Get back to fastboot
Try to flash recovery again
Fastboot flash recovery "name of recovery file"
Fastboot and adb are two different things
If it fails again, delete the recovery image and redownload and try again
Sent from my HTC Flyer P510e using xda premium
I tired again, i unlocked the bootloader using HTC dev tools, starting through the process instead of using the same email file.
I think the problem is with the HTC dev unlock, cos when i press yes, it gets stuck on the HTC splash screen. (Just out of interest, what should happen when i select yes to unlock on the flyer?)
Flashed the re-downloaded recovery in fastboot (md5 sums match again), this is what was returned:
sending 'recovery' (4746 KB)...
OKAY [ 0.755s]
writing 'recovery'...
OKAY [ 0.612s]
finished. total time: 1.367s
then selected 'bootloader' on the flyer, then 'recovery' and then it still get stucks on the white splash screen.
I double checked all the mb5 sums of all the files i have flashed in this process, and they are all good.
The flyer will not turn off, it just turns itself back on again and again. The only way to make it stay off is to lock the bootloader again
Any reccomendations?
Thanks
I am not sure why the recovery is not flashing
You may want to OEM lock and revert back to gingerbread
Sent from my HTC Flyer P510e using xda premium
thanks, to do that, do i just run fastboot oem lock?
then run the RUU?
That should do it
Sent from my HTC Flyer P510e using xda premium
Phew! That did it, back to GB for now. Thanks ever so much!
Do you recon it is worth my while to try again? I would like to try HC...
I mean you were able to recover so you got that going for you. I am not sure what was causing your problem though.
Yeah, but its a strange one isnt it?
I've just tried to S-OFF with revolutionary, and it reboots to the bootloader, and then stops, with the cmd window just saying, waiting for fastboot..... - it'll stay like this forever untill i turn the device off.
I remember i had this problem the first time i S-OFFed, but cant quite remembver how i fixed it - could this problem be somehow related to the HC install problem?
Maybe try another USB port or uninstall reinstall drivers
how long did you give the htc screen? it may take a lil while for recovery to start. id maybe give it as long as 5 minutes just to make 100% sure its really stuck.
if you wrote the recovery with the unlocked bootloader,im not sure why it wouldnt have worked,other than a bad imagea not compatible image,or possibly a simple fail to start. ive had this happen with TWRP recovery on other devices,and occasionally with clockwork-when booting to recovery it just sticks at the htc screen.
go for it again. assuming youre using all the correct,newest,and matching files,theres no reason it shouldnt work.
if you have the same trouble next time, while the on the white htc screen,when trying to get to recovery,try typing "adb devices" in your command window. if you get your serial number back, try "adb reboot recovery" and see if it starts that time.
the bootloop after unlocking the HC hboot is because that hboot and boot images are not compatible with the GB /system that is still currently on the phone. i was able to "adb reboot bootloader" during the bootloop rather than holding the power button to get back to fastboot so i could flash the recovery.
the *security warning* when you relocked it is becuase the hboot is confused about the firmware that doesnt match it.
hope that helps IMO its worth trying again- honeycomb makes the tablet alot nicer(for me anyway) than gingerbread.
Yeah I left it for at least 10 minutes, and no activity at all, other than the splash screen.
I might give it a go again, I'll report back as to how it goes!
Sent from my HTC Sensation Z710e using XDA App
send me a pm/email if you want me to take a teamviewer look if you get stuck again.
Hi, My rogers Evo 3D (S-ON, unlocked bootloader, Hboot 1.49.0008) is getting bootloops and when I enter fastboot I can flash a recovery image and it says it succeeded yet when I enter recovery it just goes back to the HTC bootloop. I have tried flashing the stock rom by putting PG86IMG.zip on my SD and it installs 'successfully', but when I reboot it goes to the bootloop again... Any help would be appreciated
Sorry, it seems the last person to own this phone had taken it apart to try and fix it (the problem was a faulty battery, so I got it cheep ) but when re-assembling it they forgot to put one of the cables to the screen back, so the phone must have been searching for hardware that wasn't there, resulting in an error, and causing a re-boot. All fixed now
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
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
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