Boot loop....not rooted - HTC Droid DNA

Ok snoot sure if anyone has experienced this but randomly after using my phone this morning I noticed it was getting really warm in my pocket. I took it out only to realize I am stuck in a boot loop. I can hold volume down and power and get into hboot, but none of the options....even factory reset do anything, just sends the phone into another boot loop. The kicker is that I have never even attempted to REIT my phone yet. Any suggestions other than going to Verizon and taking my chances there?

Have you tried holding down the power button for 10 seconds to hard reboot the device?
If that doesn't work, try getting the phone into the bootloader, connect it to your computer and try to flash an RUU from there. There's a link to the download for it in the development section, along with guides on how to use it. If you can't flash the RUU, post back here and we can help with that, but if the RUU flashes successfully and it still boot loops, there's probably not much to do except take it back.

Related

[Q] Tried to flash TWRP, now looks bricked :(

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.

Random reboots and rarely gets past bootloader

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?

[Q] vibrant boot issue

I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
[email protected] said:
I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
Click to expand...
Click to collapse
I have Jtag solve for Hard brick phone
Please PM me or check out at my signature.

Stuck booting.

Today my phone was bring finnicky and locking up, so I restarted it. Lo and behold the thing won't even boot. I don't even get a boot animation. I get a flash of LG for half a second and then blackness. Couldn't boot into recovery, so instead I booted into download mode and LGNPST back to JB stock. Now it won't boot past the AT&T logo. I see LG, AT&T, hear the little jingle, and then the screen stays the same. When I power the phone off it auto powers itself back up and tries to boot again. Endless cycle.
Anyone have any idea what's going on or how to fix it? I'm lost at this point and fear that I may have inadvertently bricked my phone. Really can't afford a new one...
You could try factory reset from stock recovery. The button combo is volume down plus power. There will be a menu screen if you get it to work.
Went in to AT&T support and that's what the guy did. It worked. Thanks, wish I had seen this post before making that drive.

[Q] EVO 4g LTE Stuck in repeating bootloop FIXED new phone

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

Categories

Resources