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
Related
Ok,
So I was following the ez honeycomb guide. (thanks Globatron!) I got all the way to the error 90, and tried again and it failed with error 13 battery low. So I'm like ok and try rebooting it so I can charge it. Well that didn't work and I realized too little too late that that may have been the wrong thing to do. Its screen is black and the notification led is flashing amber. I did get it to fast boot 1 time but it wouldn't reboot into RUU again to finish the flash. I hope that I didn't brick it because its not reacting to anything. I tried holding the power button and also power + volume down.
Any help would be extremely appreciated.
Thanks,
Justin
EDIT::: Still not working, let it sit on the charger for a while, and got it to go back in to hboot. Tried erasing cache and rebooting again from fast boot on laptop and kept getting a ... FAILED (status malformed (1 bytes)) error
Will the device accept any adb or fastboot commands
Sent from my HTC Flyer P510e using xda premium
What version of hboot is on it now? it's not bricked anyway.
I think my battery might be fried.
When I started this procedure it was on hboot 6 something. I don't remember exactly and it won't come on to check.
It won't accept any commands unless I can get it to turn on, which it doesn't seem do except after sitting on the charger for about 3 or 4 hours maybe more. When it does come on it will only come on for a very short while, and I tried to flash it and it gave me a USB write error.
Thanks again
Looks like you have non-functional Bootloader/recovery firmware combination. The Flyer won't charge if the firmware is messed up. Get in touch with Globaltron here and give him all the details of what model you have and what HBoot, recovery , etc. you have loaded. He can fix you up.
I only need to know the current hboot version to tell you how to proceed.
If you can get it on for long enough to get that I can tell you what to do next.
Got It!
ok Im running 6.11.1111 as my hboot
ok, in that case you need to flash the two files in the zip through fastboot as follows:
boot to fastboot mode
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
This will allow you to charge your flyer properly. After that we can proceed with fixing the situation properly.
OOPS
Ok
It wouldn't let me flash either, it said battery too low as an error.
Update
After letting it sit on its mains charger for about 8 hours, it finally let me flash the recovery images you supplied. It did get stuck in a boot loop but I managed to boot back to hboot switch to cwm and power down. Its now charging as normal!
So what would my next steps be?
jcrouzzo said:
After letting it sit on its mains charger for about 8 hours, it finally let me flash the recovery images you supplied. It did get stuck in a boot loop but I managed to boot back to hboot switch to cwm and power down. Its now charging as normal!
So what would my next steps be?
Click to expand...
Click to collapse
The boot loop was expected. There isn't enough of a ROM to boot normally, but you needed cwm both to charge and to be able to continue with the downgrade.
You need to follow this guide. You can skip steps 1-5 from the preparation steps since it appears you have those already done, if you haven't already done steps 6 and 7 from preparation then start there and then complete the procedure steps.
i have the same problem, i have hboot 6.10.102 or something like that, please help . TIA!
I made an observation when I jizzed my flyer up a couple of days ago. If you try to run an RUU from your PC in hboot mode, the RUU will return a low battery error, but if the RUU is run in fastboot mode it will run, at least to the next error if there is one.
Sent from my HTC Flyer P510e using xda premium
Same fix for you akabeware as for jcrouzzo
hey,
Its been a crazy week and I haven't been able to get back to this. I've run into a snag as adb won't recognize the device in fast boot, and it won't boot to be seen by adb.
Thanks again,
Justin
Can not use adb when in fastboot mode, only fastboot commands. Can use adb in recovery or booted device
Sent from my HTC Flyer P510e using xda premium
ok,
tried booting into recovery and its stuck at the htc screen
IM me on skype, contact details in my profile and I'll walk you though this.
Same Problem as jcrouzzo
I have the same problem as jcrouzzo but it gives me sending 'recovery' (4746 KB)... FAILED(status malformed(1 bytes))
what should I do? battery does not recharge
please help Globaltron..
if i can just get it to the OS
i think i messed up boot so badly that it just stuck at HTC logo first then many attempts of flashing other recovery.img boot.img i kinda need just little more than instruction i might need some pros here i guess
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.
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