Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
xdaaccount123 said:
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe its a stupid inquiry but does battery work as it should in stock rom? so that you can be absolutely sure its not faulty battery that's creating issues.because two things happen(in my experience when something goes wrong with boot.img) either its stuck at splash screen (hboot) with red text OR it goes blank but not off, just blank
Definitely isnt the battery. I am not experiencing any drain and it functions completely normally when plugged it. When I unplug, it works fine for a few min and then switches off. It will then not turn on, despite it showing 90%+ when I plug it in
but it happens in stock rom also? thats what i wanted to know .if you can full wipe and phone works when connected to usb,maybe you can run ruu and confirm that as well . If you can go to recovery ,make a nandroid backup.and try a ruu.
Yup, happens on stock as well.
Also, I think the recovery is messed up as well since it just crashes now when trying to flash something. It's having issues doing a nanroid backup as well
And no love for exe ruu as well?
Related
So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk
The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium
+1 for the new battery thought.
Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.
GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!
ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.
Hi, i own a HOX, i had alot of problems with it..
Now the problem i got yesterday, my phone just turns off randomly, after a while it will turn on after it booted, i find it weird, dont know if its related but it wont let me flash a kernel also, if i enter into bootloader and fastboot then plug in into the pc, the phone frezzes and the pc wont recognize it, so im stuck with paranoid android, another thing, if i go to the recovery and i try to do something heavy, like backup whole system and data, to see if the phone turns off, it doesnt happen, just when i turn on the phone, if i delete cache then boot up, it will upgrade all my 300+ apps in the start up, but once its finished it will just turns off, it happend me with Miui v 5, though it was the rom, switched to aokp, the same, then paranoin, no change, now i cant switch kernels, any idea why is happening? please help
Seems like a hardware failure of some kind, because it also happens in the recovery
Mr Hofs said:
Seems like a hardware failure of some kind, because it also happens in the recovery
Click to expand...
Click to collapse
it doesnt happen in the recovery, for bein unable to flash a kernel, somehow the drivers were missing, reinstalled, working, since the phone only turns off when android its actually on, but no in bootloader or recovery i assumed it was kernel failure, so i repacked the paranoid with the mx kernel and everything seems fine now.
Sorry i misread that part, completely my mistake ! But good you got the driver thing sorted, hope it stays okey now :thumbup:
First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.