I have an HTC One. Long story short, I booted to TWRP and selected to wipe everything. Upon reboot, the phone is completely dead... won't turn on, won't charge, won't connect to PC. This is not the first time I wiped the phone from TWRP, as I have done it before. Truth is I don't know much about this stuff and don't really know what TWRP is. The phone came with it, as the previous owner installed it.
Can this be fixed, or is the phone dead?
Related
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Okay, I want to start by saying I am truly sorry if this has already been looked at. I truly spent 20 minutes searching and could not find anything that address this problem.
Im going to give you the long story because, I am actually really in need of help.
My friends owns a droid x2, ?.?.5 (sorry I cant honestly remember but, its the gingerbread ending in .5)
Her husband decided to root her phone for her, and it was in Chinese and only had a partial root. Frustrated she brought it to me because, well I have a working knowledge of google, this forum, and have flashed and rooted many phones.
I managed to change the language, and root the phone (using DX2_batchroot), I installed a custom recovery (its an apk ), I also think I installed the Recovery BSR (that will make sense in a second)
I booted into custom recovery, I made a backup. Then I went about wiping caches so I could install a custom rom. I wiped all the caches, I formatted the internal memory, and then I accidentally hit "boot now".
The phone gets the the "M" and says "Failed to boot 1"
If I try holding the power and down button it just flips off completly.
I cant scroll thru the menu, I cant get the computer to acknowledge its on.
It has been plugged in the hole time.
So what do I do, and what DID I do, so I never do it again.
Thank yo
Update
Since this happened I have left it on the wall charger and checked it out occasionally.
Well it still won't boot into recovery but... It is now willing to play ball when I press volume down and then plug in to the computer. Sadly it then tells me that the battery is too low.
Now, I *guess* it could be, except after rooting and before rebooting into recovery to make my first backup I had the phone off andplugg ed into a wall charger for 2 hours.
Again, any help you can offer
Often if ROM won't boot, charging does not work either.
Will need a charged battery, or a TBH factory cable adaptor.
See my low battery options in my list.
sd_shadow's (themib) [Collection] of Links for Droid X2
Sent from my Amazon Kindle Fire using Tapatalk
I used this guide to install CWM to my phone, the phone was already rooted successfully. I used the following guide:
http://forum.xda-developers.com/showthread.php?t=2486512
Before the first rom flash the system description said the phone was a P705g and the phone itself has it marked as a P708g. I saw this as no consequence and carried on.
*** UPDATE***
So the sticker behind the battery marks the phone as P705g, the plastic case just said P708g. Guess they just didnt want to waste plastic at the company
As soon as I unlocked my bootloader the phone started turning off after 2-3 mins of use. I was able to flash CM10 nightly successfully and it worked, aside the turning off. I thought it might be a problem with CWM so I switched over to TWRP. I installed it through CWM, but to no avail. Still having the same problem. And I yes I wiped cache/dalvik.
After the phone dies it restarts and keeps loading the cyanogenmod load screen, until it eventually restarts again. This happens infinitely.
I have phone now that needs to have the battery popped everytime I want it to load. That would have been ok but it keeps turning off...
Guys I need help! Currently a student and money is scarce so buying a new phone is out of the question for some time.
Thanks for the help :laugh:
Hi guys.
I've encountered an issue very annoying and bad on this phone(i9100)!
If the phone's battery empties to 0% and it's not put to charge right away, the phone won't ever boot anymore the next time you charge it. It just stays on the "Samsung Galaxy" screen.
I go to recovery and reset it to factory, delete cache, etc, still nothing. If I rewrite the firmware it works and boots. But if I repeat the same thing and let the battery drain out to 0% again, it won't boot anymore.
Did anyone had this issue before? For me it is new. And I wanted to sell the phone too... The poor guy who buys it and stumbles upon this ****, will yell at me for giving him a broken phone...
Is there any way to fix this problem? Help me please, just this once.
The phone is on stock rom, 4.1.2.
EDIT:
Cool, and after a couple of factory resets, it finally booted. But now it asks for sim code??! WTF is wrong with this phone? The stock rom is unlocked, why would it ask for the sim code?
Hey guys, so I've gotten myself out of boot loops before but this time I need one of ya'lls superior minds to help me out, if ya'll got the time.
I'm running a rooted, bootloader-unlocked HTC One M8 (TWRP recovery, custom ROM) that I've been using the past couple months with only some battery issues. Yesterday at work, my phone turned off for no reason, and every time I turned it on, it would turn off after reaching the boot logo. Low battery, no biggie. I got home and plugged it in, but this time it would just stay on the HTC One logo.
Wearily, I decided to do a factory reset, but after still no luck, I tried an advanced wipe (cache, data, internal storage [not system]) and took out my SD card, but nothing new yet. While searching for this problem, I came up on a lot of threads saying the factory reset didn't wipe anything from their phone, could this be a possibility?
Is there something I haven't done (or done wrong), or is there any way to fix this without using an RUU?
Bump; I tried to use the RUU I used before, but it got stuck at 28% and after searching for the problem, deemed it safe to terminate the application and start anew, but now my phone can't boot to recovery and just keeps turning on then off.
Halp?