Database Users

[Q] Strange problem

As the title says I have a strange yet very annoying problem. I am running my HD2 with hyperdroid cm7 Nand build (from april 29th). The problem is that when my battery is deleted, as is the case now, and I put my hd2 in the charger it will automatically boot. I think this is due to a setting or something. However since booting drains energy faster than the hd2 charges, the phone will by turned of before it has completely booted. After a while it get's stuck in a pattern of starting to boot and turning of. I don't know why this is the case because I think my phone just used to boot fine before when connected to a charger.
So my questions are:
1. does anyone has a suggestion how to turn on the phone?
2. this automatic booting, can it be turned off?
3. Why is it actually happening?
Maybe it's a very stupid or obvious problem, but I hope someone can help me though.

Do you have installed MGLRD?, it's a Known fact, search in the forum for answer (I'm sorry, I'm with SD Builds and don't use MGLRD, so I can not help you anymore).

I had the same problem with some rom i used earlier. The only way i could solve the issue was to remove the battery and put it back, then I could insert the charger without the phone booting up. Charge it for a while and start it.
Hope this way works for u 2.
Sent from my Desire HD using XDA App

I guess this is what I used to do as well. However now, if I remove the battery and put it back in it keeps automatically booting. Also if I put the charger in the phone and then remove the battery same thing happens. But thanks for the help though.

I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.

slbenz said:
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Well, this cycle I think is caused by the fact that the charger is not strong enough. Normally if plugged in the phone would just boot. The reason that it fails to boot is that is doesn't have enough power to complete the boot cycle even though the phone is plugged in (don't know if booting consumes a lot of power?).
A month ago I bought a new usb cable. Maybe that's where the problem lies? Because I have been using the hyperdroid rom for a while now. Although I don't know if one cable can be stronger than the other.
I have found a solution btw: Though it is a bit hit and miss cause it didn't work a few hours ago. When booting I let it go into mgldr and let it charge there. After a while I'll let it boot when it has enough power to complete the boot.

slbenz said:
Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Humm, now you making me think lol, the 1st time I installed Android on my HTC HD2 was the NexusHd2 rom one and he had the same problem, no battery but once I plug it to the wall charger it would do the full(normal)boot, I thought was the rom so I changed to Hyperdroid Cm7, but, still does the same..
The wipe you talking is the one, wipe data/cache right?

if it happens to you a lot, I think it's time to invest in a third-party battery charger. you can charge it out of the phone for a bit, and then you're safe to put it back in a continue charging using the phone

Tried some different roms and all them do the same.. so I reckon its normal.. Thank You.

[Q] Trying to restore Nexus 4, would shutdown when unplugged… seeking help

Hi folks,
Fortunately I've not had much necessity to post here for help. However, that's now change.
I am looking for suggestions on:
1) What might be the cause of an issue with my N4
2) What I might be able to do about it.
Here's the background:
My N4 was working fine. Stock device, 4.4.2, no rooting, etc.
The other day it spontaneously turned off. I was not able to turn it back on. "Google" would appear on the screen, but a few seconds later would vanish and device was off again.
I did figure out I could turn it on (most of the time) when it was plugged into a power source. But detaching from that power source (whilst it was running) would result in it turning off within a couple of seconds at most.
I managed to back up most of my data, whilst having it plugged in and turned on.
A few days later device tells me there's a 4.4.3 update. I update it.
Issue remains.
I then try to initiate a factory reset.
Device reboots during that process. But fails to restart.
I could no longer restart it whether plugged in or not.
It can sit in bootloader mode without being plugged in, for as long as it takes to run the battery down.
It can't be in recovery mode without ext power.
I load the TWRP recovery image. That is on and working fine.
I can access the device with fastboot command (via Windows 7)... which is how I got the TWRP image on there.
In recovery mode the device is not detected by windows, and adp command can't see the device.
This is about where I have come unstuck. I was attempting to install a clean Android 4.4.3 image onto the device. But I can't get ADB access to it. Tried on a Mac and a Windows 7 PC.
UPDATE: I did manage to complete instructions for installing new Android 4.4.3 image over fastboot mode. But even after completing the steps successfully, device won't start. Just "Google" flashes up, and devices stops after few seconds.
HARDWARE FAILURE?: It's possible this whole issue is hardware related and I'll have to ditch the device. If that likely? I've seen some people mentioning similar issues, which they resolved by replacing the USB port board. Is that likely to cause this kind of issue?
Does some kind person have any suggestions on steps I can from here?
I'd really like to recover this beast... it's my first and only smart phone, and would hate to drop to a cheap replacement cell phone for the foreseeable future.
Thank you...

Somehow my title was blank (just a [Q]). Might explain why I got no replies so far :silly:
Updated.

If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.

lolcakes203 said:
If its happening even after a full reset and flashing of the factory image, that most likely means it is a hardware issue, maybe the battery. You can try changing it yourself or getting someone else to do it. This is what I think the issue is.
Click to expand...
Click to collapse
Hi there,
Thanks.
Regarding the battery... I had considered that. Although the battery was working fine right up to the time the N4 started having issues. Even during the issues... I could charge and discharge the battery as per normal. I tested this by discharging it by leaving the N4 in bootloader mode, and unplugged. After about 12 hours it would discharge completely. I was then able to charge it up, as per normal.
So that had me thinking it was not likely the battery at fault. What are your thoughts?

Very strange situation here. It seems somehow that booting into android causes some sort of power delivery issue and that results in the phone shutting down. I don't understand how that power delivery issue can exist within the android os but not within the bootloader if it was a hardware issue, especially after flashing the full factory image. I'm not sure, but I would still bet it a hardware issue, although perhaps not the battery.
Sent from my Nexus 4 using XDA Free mobile app

It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.

DrFredPhD said:
It sounds like the battery to me, running in bootloader mode requires nowhere near the current that the full OS does.
Click to expand...
Click to collapse
I apologise for taking so long to respond. I don't seem to be getting notifications. Will check into that.
With regard to the battery... When the phone is fully charged (and it was just like normal... prior to me toasting the OS in an attempt to refresh the device, AND it charges normally by plugging it in when turned off or in BL mode), it takes perhaps 12 hours or more to discharge, with the screen on permanently, whilst I leave it in BL mode. So if the battery is the issue, it's certainly got nothing to do with the battery being able to receive and take a charge. That happens absolutely per normal.
What I am wondering, however, if perhaps the USB board could be faulty? I actually replaced the USB board a month or two ago, as the connector on the original one died and Google refused to repair it on warranty because there was a crack on the back glass. The replacement is an LG part. I am wondering if there might be something in that logic of that board that is screwing up... such that when the cable is unplugged the device somehow "thinks" it is plugged in and thus in charge mode, rather than drawing from the battery. I am not sure where the logic for the device to determine whether to draw current from battery or USB resides. But is it feasible that this might be going on?
I'd love to revive this little brick back to smart-phone status.

[Q] Samsung Galaxy S4 Will Not Power On or Charge

Hello!
I need some help. While changing batteries, I pulled out the battery with 1% left and replaced it with the battery that was charged on a separate docking charger. From that point on, the phone will not turn on or recognize the charger (no LED light flashing). I tried using different chargers and even a different battery from another S4 but nothing worked. I also cleaned all contacts.
I tried booting in safe mode and nothing. I recently plugged into my computer and got a message saying qhsusb_dload message. After researching that, it looks like that message happens when the phone has been "bricked" after a failed "root". However, my phone is stock and was never rooted. The only software change was the phone updated to Android Lollipop a few days prior to this mess. Please help!
Thank you,
Rob

marylandortho said:
Hello!
I need some help. While changing batteries, I pulled out the battery with 1% left and replaced it with the battery that was charged on a separate docking charger. From that point on, the phone will not turn on or recognize the charger (no LED light flashing). I tried using different chargers and even a different battery from another S4 but nothing worked. I also cleaned all contacts.
I tried booting in safe mode and nothing. I recently plugged into my computer and got a message saying qhsusb_dload message. After researching that, it looks like that message happens when the phone has been "bricked" after a failed "root". However, my phone is stock and was never rooted. The only software change was the phone updated to Android Lollipop a few days prior to this mess. Please help!
Thank you,
Rob
Click to expand...
Click to collapse
It's not bricked. (It shouldn't be)
Remove the battery, press the power button several times to dissipate any remaining charge in the phone, and then insert a fully charged battery. I'd recommend you using a different phone (if available) to charge the said battery.
After that, it should boot up normally.
And if I recall, voltage is supposed to be consistent, regardless of the charge level (unless it's totally dead, then maybe it's different, I don't know)
It's the current you want to look for.

[SGH-I337 AT&T] Unmodified, Stock SGS4 boot loops, freezes, graphical bugs HELP!

Hello everyone!
My parents contacted me asking for help with some phone issues that I thought would be minor but this is now something I have to submit to you guys because I just don't know how to tackle this issue;
I've got an unmodified, completely stock AT&T Samsung Galaxy S4 that has been owned since launch. My parents were initially complaining about how the phone stopped charging and wouldn't turn on. I thought, "Easy, dead battery, it's been 3 years so how could it not? It might not be delivering enough voltage for the SoC..." but i'm not sure that's the full story which is why I want your guys' opinion since this place is a wealth of knowledge.
Things that are known:
When you charge the phone, the basic "battery charging indicator" that is shown when Android is not booted into or powered on freezes, or sometimes does not detect a battery so does not even turn on. Doing battery pulls seems to change how the phone responds. This is what my parents were experiencing. I thought, either dead battery, dead micro-USB cable, AC adapter, or charging circuit within the phone. Since this was obviously a big job, I took the phone back home for this weekend to play with and now this is what i'm experiencing.
So I got the phone to charge using one of my AC adapters for some reason, despite using the supposed broken charging cable to transfer data successfully without corruption using my own phone (LG G2) to confirm if it was just the cable. So now the SGS4 has a battery that is 100% charged, I turn on the phone and tried various methods to get the phone to boot successfully back into android. The first obvious one was to boot into safe mode using PWR, letting go of PWR, and then pressing VOL UP. It booted ONCE or TWICE successfully into safe mode into android, it shut off after 5 seconds being into the system due to low battery. This was BEFORE I was able to successfully charge the battery to 100% with my AC adapter but has failed to boot since.
Now since I've been failing to get into safe mode as when I boot the phone up, the phone freezes or has graphical glitches at the Samsung post/splash logo as seen here:
After some desperation, I considered using KIES/Odin to reflash, but mostly I tried going into download mode to see if the phone would even go into it by doing PWR + VOL DOWN. It did get into download mode but it froze/restarted forcing a battery pull and ever since then I keep getting occasional error messages such as "System software not authorized by AT&T has been found on your phone.", or this screen with a Samsung logo and an open padlock. I notice sometimes that when I'm at this open padlock screen, it sometimes begins to boot into the system but quickly freezes when it plays the boot jingle:
At any rate, I ordered a new battery but I fear this might be EMMC corruption or just something I don't quite understand. The phone has valuable information that I have to recover despite my parents CANCELLING a backup of the phone, they failed to heed my due diligence and are now freaking out about the data (photos, contacts, etc). I just need the phone to boot so I can make a nandroid backup, export the contacts, transfer media off the phone and wipe this thing and start anew. However i've already let them know that it might not be possible. The most important thing is to get this thing out of this soft-brick?
Please help because I have no idea where to steer this ship from here on out aside from waiting to receive that new battery and hope these instability issues are caused by low voltage. I had an SGS2 which had the crazy EMMC bug so I'm hoping its not EMMC corruption.
Thanks for your time everyone! I'll update this thread to reflect new information as I play around with the phone.
Edit: Here is a video, I go through a lot of the same information posted in this thread but here it is.
https://youtu.be/EXUKU68CyQQ

Possible loose connection inside the phone? Was the phone every bumped, dropped, or exposed to moisture?

audit13 said:
Possible loose connection inside the phone? Was the phone every bumped, dropped, or exposed to moisture?
Click to expand...
Click to collapse
Not that I know of. I'm going to check the water damage stickers if I can to ensure that's not the case but i've been told it was sudden. It had been dropped once before but had been working fine for quite some time up until recently.

Maybe the effects of the drop and manifesting themselves now?

Help! Essential PH-1 no longer powers on?

Essential PH-1 has continued to be my daily driver for almost 5 years now.
I haven't backed up the data, not even to GDrive. Yes, quite dumb. I finally found time to start to look into backing up recently, with the ADB route.
For the past 2 or 3 years, rebooting was problematic where it'd take 5+ minutes or required pressing the Power button down for a second buzz from off state, releasing it only when the animation with small circles would start. It'd then boot up to completion.
Recently, after fully charging and booting up from off state, it started showing new symptom where it'd be stuck indefinitely the Essential logo splash screen. At that time, I was still able to go into bootloader/recovery menu.
I rebooted and let it continue stuck on the Essential logo, hoping maybe it'd just take longer. After an hour, I forced it to shut down and rebooted again and put it aside to wait for it.
Within less than 2 hours, I noticed the display went blank/black.
After that, regardless of how long I press the Power button, the phone would never wake up anymore.
Plugging in the Essential OEM power adapter also does not even show the LED turning on. Can't tell if the USB port was busted or not but would be surprised if it did as charging and data transfer had always gone through a magnetic plug that's permanently plugged-in to the USB port.
Bootloader was never unlocked and, as such, also never attempted to gain root access to Android.
It was running the official Android 10 ROM from February 2020 (?).
There was no smoke or any unusual smell.
1. Is this a known/previously reported problem? I'd like to read on what others who experienced the same may have tried to resurrect.
2. If, let us say, the problem is actually with the battery, would the phone not show any signs of life when plugged-in to power adapter?
3. What are the chances some other electronics may either have slowly deteriorated or have gotten fried inside that casing?
4. If it's never powering back on, are there instructions on how to de-solder the internal storage component to try to recover the data?
5. What other possibilities can cause an Android device to not even show any signs of life?
6. Any other ideas?
Appreciate help from the community, including any pointers even if referring to a different Android device.