Last night I tried rooting my phone and all that jazz. The battery has no juice and the phone won't do anything, wont even indicate that it's charging. i can't get ANYTHING from the rezound. I plug it in and here a few beeps, but that's it. I think I need the P58IMG stock for this or something, but nothing is doing anything. I'm sorry for incorrectly posting, but I leave for school in 10 minutes!
You can't let the battery drain all the way down. Leave it on the charger for a bit, then pull the battery. Let it sit for a hot minute, then try booting again.
Ok, It's been on the charger since 7:35 this morning and i'll get home at 3 pm and hopefully it boots up. Do I need a external battery for this? I just need it to boot into hoot and recovery, then i can do it from there. I have the stock htc rezoned battery. I'll let you know when I try to but at 3pm or earlier because that when I get home from school
Also I have clockwork recovery on my rezound and I found out that clockwork doesn't charge a completely dead battery via usb. How would I flash AmanRa recovery when the battery is dead, thanks.
I read on here somewhere that a couple people got theirs going by connecting to PC and using a reboot command in adb. Don't know that command offhand.
Sent from my ADR6425LVW using Tapatalk
You want this post.
IrvChynaman had some troubles and did some pretty extensive troubleshooting on it.
Just came across the adb command:
adb reboot bootloader
One person said they typed that about 5 times before they booted into bootloader. (someone also said they thought the phone was charging even though the light wasn't lighting up so that may be why this works, once there is enough juice the phone can boot into bootloader or something) From there you should be able to reboot phone and then once it's booted you should be able to charge.
Once you are charged you might want to flash Amon Ra recovery to avoid this issue in the future. Otherwise just make sure you never drain the battery to the point of phone shutting off.
Thank you, I will try this out now. Hopefully it works, I'll keep you updated! Thank you guys!
UPDATE: Ok, so I follow the instructions the post says. I type in the command in where everything is ADB, etc and the recovery.img.. it my computers beeps, beeps again and the orange light comes on for 3 seconds and turns off.
If you still don't have it charging you can try looking through this thread:
http://forum.xda-developers.com/showthread.php?p=22370748#post22370748
There are different methods posted in there that have worked.
Look at my comment in the thread. If you can get into the shell with 'adb shell' as I did, there is still hope.
feralicious said:
Just came across the adb command:
adb reboot bootloader
One person said they typed that about 5 times before they booted into bootloader. (someone also said they thought the phone was charging even though the light wasn't lighting up so that may be why this works, once there is enough juice the phone can boot into bootloader or something) From there you should be able to reboot phone and then once it's booted you should be able to charge.
Once you are charged you might want to flash Amon Ra recovery to avoid this issue in the future. Otherwise just make sure you never drain the battery to the point of phone shutting off.
Click to expand...
Click to collapse
i woke up to this this morning. it wouldnt turn on. i did nothing but put touch recovery on it last night before i went to bed. i had to hit it with adb reboot bootloader 5+ times and it finally booted. thank you so much for this. i was freaking out. lol
EDIT:
spoke to soon. its still not working. i managed to get it to boot so im going to try this next http://forum.xda-developers.com/showthread.php?p=22370748#post22370748 if not its going back. its only been 1 day and i already broke it lol.
I had this problem about a month ago on my Rezound. I just pulled the battery and let it sit for a bit. I then put the batter back in and plugged the phone into my laptop. I then used
adb reboot
and my phone turned on and it was able to charge.
excellentnuke said:
I had this problem about a month ago on my Rezound. I just pulled the battery and let it sit for a bit. I then put the batter back in and plugged the phone into my laptop. I then used
adb reboot
and my phone turned on and it was able to charge.
Click to expand...
Click to collapse
Sorry to open this thred again but i a day ago i tried to install twrp 2.2.0 on my rezound and everything works fine and after i install TWRP 2.0.8 and it still having no problem but today i boot my phone to TWRP recovery and selected Reboot System and then my phone powered off and did no reboot my system. i was panicked so i pulled my batery out and pull it back nothing is working it is not recognized by laptop, when plugged in the wall sector or on computer the led didn't even light up.
Please I really need ur help Whatever u hav just tell me. Thanks in advance.
Related
as i mentioned a few days ago, i recently rooted some vibrants for a few of my friends.
one of them decided to switch me phones for a few days just to see if he liked my phone (g2) since he wants to upgrade anyways.
so i unlocked his vibrant using this hex editor method. worked like a charm. popped in my sim and at&t came up, all was well with the world.
i was going to do a nandroid backup of his phone so i used rommanager to boot into recovery.
that didn't happen.
his phone hung at the samsung vibrant screen. i figured no big deal, maybe just a hiccup. pulled the battery and attempted to start the phone again normally, but still stuck on vibrant. tried a few more reboots with no new results. next i booted the phone into download mode which worked just fine. dl mode came up normally and was recognized by odin. still feeling creative, i decided to pull the battery while it was in dl mode then undo the usb cable. put the battery back in, turned it on and voila! phone booted like normal!
i was pretty damn confused. i could get it to boot this way about 1 out of every 3 tries. i thought perhaps changing the nv_data.bin file was what screwed it up so i replaced the modified one with the original and re-locked his phone.
so the phone boots up normally, i go to rommanager, tell it to install clockwork recovery, wait for it to finish and attempt to reboot into recovery mode, this time through adb. the phone still got stuck on the vibrant screen BUT adb still recognized that the phone was attached AND in recovery mode.
still confused. i'm assuming perhaps the adb functionality was due to restoring the original nv_data.bin?
so i rebooted his phone via adb and it turned on like normal, told him not to turn the phone off. i was going to take it with me to work today, but we're generally busy on saturdays and i won't have time to mess with it. gonna take it monday and try some more stuff.
so long story short; unlocked phone, wouldn't reboot into recovery, just hung on vibrant screen. put phone in dl mode, pulled battery, attempted boot and it worked. relocked phone, reflashed cwm in rommanager, rebooted via adb, still hung on vibrant screen but recognized by adb.
anyone ever had anything similar to this happen?
This actually happened to me once. Bit once i odin'ed back to stock it fixed it and it never happened again.
All,
I have been on here for months, but this my 1st post. I have an Atrix that has been rooted, boot loader unlocked, Tenfar's recovery, but running stock ROM 1.8.x. I have not done any "tampering" with or ROM updates or anything like that. The phone in a few weeks and it has been working flawlessly.
However, this morning when I woke up, the phone is just sitting there dead. My wife said she heard a weird beep a few hours earlier. It will not power up via battery and the power button does not appear to work either.
I attached it to the wall charger an it will come up to the motorola and display "unlocked" but will not go past that screen. I also noticed that no charge led is lit up at all ... Strange ? I was able to get into recovery and I tried for a restore using Tenfar's CWM but after it completed and I went for a "reboot phone now" it just went back to the black screen and never booted at all.
Any thoughts ? Thanks in advance !
-Nathan
nathanmurray said:
All,
I have been on here for months, but this my 1st post. I have an Atrix that has been rooted, boot loader unlocked, Tenfar's recovery, but running stock ROM 1.8.x. I have not done any "tampering" with or ROM updates or anything like that. The phone in a few weeks and it has been working flawlessly.
However, this morning when I woke up, the phone is just sitting there dead. My wife said she heard a weird beep a few hours earlier. It will not power up via battery and the power button does not appear to work either.
I attached it to the wall charger an it will come up to the motorola and display "unlocked" but will not go past that screen. I also noticed that no charge led is lit up at all ... Strange ? I was able to get into recovery and I tried for a restore using Tenfar's CWM but after it completed and I went for a "reboot phone now" it just went back to the black screen and never booted at all.
Any thoughts ? Thanks in advance !
-Nathan
Click to expand...
Click to collapse
Could be simply that your battery is dead. If you have a friend with an Atrix the first thing to try is an alternative battery.
If that doesn't help the second thing to try would be a full rom flash and full wipe via fastboot.
This happened to me as well. The phone will not charge during boot so what I did was enter fastboot with hardware(or an option like that) and I got past it started up in a couple minutes.
Hw bypass with bp**
Sent from my MB860 using XDA App
reply
It appears to be the battery ... I tried it with a different one and it booted without issue. Very strange as it appears to have died all of the sudden. Just glad it is not the actual phone. Anyway, thanks for the info, much appreciated !
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.
ViperRom ICS Was using my phone and it froze. Pulled the battery and Restarted. It bootlooped at the HTC Screen. I have tried just about everything. Flashed Recovery, Wont boot into it. Full PG36img, still bootloop. My phone doesnt even charge when its off. The charging indicator light flashes, but it doesnt charge the battery. I had to use a friends battery to keep trying. I have spent 2 days flashing just about everything i could find to no avail. Can get to bootloader and fastboot, but thats about it. I have bricked and unbricked my phones many times over the years, but this one, i cant seem to get it to load anything, even recovery.
troublein420 said:
ViperRom ICS Was using my phone and it froze. Pulled the battery and Restarted. It bootlooped at the HTC Screen. I have tried just about everything. Flashed Recovery, Wont boot into it. Full PG36img, still bootloop. My phone doesnt even charge when its off. The charging indicator light flashes, but it doesnt charge the battery. I had to use a friends battery to keep trying. I have spent 2 days flashing just about everything i could find to no avail. Can get to bootloader and fastboot, but thats about it. I have bricked and unbricked my phones many times over the years, but this one, i cant seem to get it to load anything, even recovery.
Click to expand...
Click to collapse
Use 4ext recovery and it should work and charge your phone while it's off.
I guess you have gsm evo 3d so download and flash the img from this zip via fastboot - www.4ext.net/ddl/shooteru/recovery.zip
EDIT : I see you edited it yourself.
Hello, I have an HTC Amaze for over a year now. It was working fine, I rooted it CWM 5. and I installed Android revolution custom ROM. Until 2 weeks ago my battery was giving me some trouble, so i put away the phone for a bit, I bought a new battery then I notice the phone wasn't coming on. SO i charge for an entire day it still wasn't charging. I carried it to the shop. They said, that they don't know whats wrong with the phone.
I came home and decide am going to fix it my self i tried powering it into recovery mode, hard reset. screen is still blank, at lease that is what I thought. I look closely and then i notice the phone was in recovery mode but no lights were on in the screen. So normally I thought what anyone would of thought, the bulb in the screen or some kind of wiring went bad. The i tried wiping cache davlik install new new rom. Nothing worked. and this was defficult because I had to use a flash light to see on the screen. Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
keronmat said:
Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Find the way to install adb and communicate with the phone via adb and fastboot. If you can do that, you will be able to install anything necessary to get the phone working again.
First however, remove the battery, wait a few seconds, reinsert the battery and charge the phone overnight. Next day, try and start phone usual way--see what happens.
If NOTHING happens and you get a black screen, remove battery again for a few seconds, reinsert, and this time hold the power button in for AT LEAST 20 seconds.
See if that starts the phone.
If you get absolutely nothing again, find the "Unbricking Project" thread, but if you get any kind of screen, see if you can boot to recovery and restore anything. If you get a screen but can't do any kind of restore at all, find instructions for adb and fastboot I mentioned earlier, so you can install a new recovery and flash a new rom..
I did everything you said. Except I complete forget how to flash recovery and custom rom from my pc but when I type command in fastboot "adb devices" it was successful.
However, I charge the phone and I got into the recovery mode again and the wipe everything and then click backup and recovery. I rebooted the phone and it came on as if its a brand new HTC Amaze. I had the phone working i rejoice for a bit and then I realize I forget to put in my sim card. So i turn the phone off, put in the sim card. The same problem again. No led, no light in the screen, the phone atomatically boots into recovery mood.
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
keronmat said:
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
Click to expand...
Click to collapse
I think that is what you should see when you boot into recovery.
Do whatever you did before to get the phone lit up again, then change the display settings to maybe 3/4 brightness for instance. Reboot the phone normal reboot and see if it comes back with light.
If it does, maybe you are fixed enough to install the sim.
Do you possibly have a nandroid backup saved somewhere, you could put it back in the phone via recovery?
The phone is lit up again like you asked me to do. It was hard to see in recovery mode. But i used a flashlight to look on the screen of the AMAZE then i flash a new custom rom. After multiple tries I got it up. SO its up and the brightness is at its highest point. But I dont believe thats the problem. I just need to figure out how the light stays off when in recovery mood but comes on when booted normally. Its as though the recovery is broken. How do I fix it? if its broken