Hello everyone my brother's Ph-1 keeps shutting down right after powering up, I have tried everything from factory resetting to trying a different charger, nothing seems to work. This happened after he didn't use the phone for almost a month, it worked perfectly before.
It powers off even when on charge or connected to the laptop.
The phone doesn't stay on for more than a minute or two which means i cannot use ADB to side load an update
The phone is running Android P and the April security update patch.
Please do help me out
Thanking you
Kalasingha said:
Hello everyone
Click to expand...
Click to collapse
Hello everyone
Kalasingha said:
Hello everyone my brother's Ph-1 keeps shutting down right after powering up, I have tried everything from factory resetting to trying a different charger, nothing seems to work. This happened after he didn't use the phone for almost a month, it worked perfectly before.
It powers off even when on charge or connected to the laptop.
The phone doesn't stay on for more than a minute or two which means i cannot use ADB to side load an update
The phone is running Android P and the April security update patch.
Please do help me out
Thanking you
Click to expand...
Click to collapse
It could be corrupted though it sounds a bit like a battery issue, to me. If battery discharges too much eg it didn't shut down itself properly when battery was at a low level (they retain more charge than shown to user so it can shut down with proper procedure) & the battery ran down past it's reserve the battery may not be able to be recharged with a normal charger even though you charge it. (Thought a battery specialist could possibly revive it with a boost charge, though I've only seen these used with industrial batteries)
with a "dead battery bootloop" sometimes you can get it going by booting when connected to the charger, but you'll probably need a new battery. Maybe also try boot into safe or recovery mode when connected to Essential charger. (I'm assuming your phone not corrupted, though as you haven't given us much info about exactly what happens & what you are seeing)
IronRoo said:
It could be corrupted though it sounds a bit like a battery issue, to me. If battery discharges too much eg it didn't shut down itself properly when battery was at a low level (they retain more charge than shown to user so it can shut down with proper procedure) & the battery ran down past it's reserve the battery may not be able to be recharged with a normal charger even though you charge it. (Thought a battery specialist could possibly revive it with a boost charge, though I've only seen these used with industrial batteries)
with a "dead battery bootloop" sometimes you can get it going by booting when connected to the charger, but you'll probably need a new battery. Maybe also try boot into safe or recovery mode when connected to Essential charger. (I'm assuming your phone not corrupted, though as you haven't given us much info about exactly what happens & what you are seeing)
Click to expand...
Click to collapse
The phone shuts down even when in recovery or safe mode whilst connected to the charger.
It does sometimes fully boot up and then shutdowns, but mostly shuts down while still on the essential logo.
If I may ask what do you mean by the phone might be corrupt?
Can one month of non usage cause the battery to die out?
Kalasingha said:
The phone shuts down even when in recovery or safe mode whilst connected to the charger.
It does sometimes fully boot up and then shutdowns, but mostly shuts down while still on the essential logo.
If I may ask what do you mean by the phone might be corrupt?
Can one month of non usage cause the battery to die out?
Click to expand...
Click to collapse
by corrupt I mean some data that is part of the boot process causes bootloop so it shuts down, but as your phone is shutting down at different points in boot cycle I think it's probably battery
Leaving the phone turned off unused for longish periods should not be a problem normally even with a few % left in battery. And even if left turned on it should shut itself down when battery low & be able to boot up again after a month due to the battery "reserve" capacity (but possibly a month was too long). And if it was not recharged straight away and/or rebooted multiple times the battery "reserve" could fall too low and not have enough power to start/shutdown properly (possibly causing data corruption ... though l don't know if there is some sort of fail-safe boot procedure ) Then there is a possibility there is a hardware fault with battery/phone that meant battery lost too much power.
There were some tricks ie "boost charge" you could do with removable batteries that were in "deep sleep" as shown here for example
https://m.youtube.com/watch?v=TEXA7qIJ968
But they don't really work without taking your battery out (for us we might as well get a new battery when opening phone up, & there would be some risk that you damage battery as we do not know the exact charge to apply on this battery, which could cause unsafe battery) I wouldn't want to freeze my phone even though it should survive OK, as I'd be alittle concerned about long term effect on our screens small pixels (I remember the guys at popular mechanics put an old flip phone with little LCD screen in liquid nitrogen & it still worked after being warmed up!).
See https://batteryuniversity.com/learn/article/low_voltage_cut_off
for more tech details
firmware issues do not cause the issue you are describing
you have a hardware problem
sounds like a bad battery to me
good news is the battery is not difficult to replace (don't listen to ifixit I am not sure what they where smoking when they did there tear down)
https://www.youtube.com/watch?v=BCKxAQXdTJ8
don't bother with silly and wrong tricks like trying to hack the battery back to life its the wrong way todo
if the battery ever gets to that point then the battery is bad enough said
Legitsu said:
don't listen to ifixit I am not sure what they where smoking when they did there tear down
Click to expand...
Click to collapse
So true! )) As much as I respect the guys from iFixit, they screwed this one up pretty badly - basically, made a tutorial on how to destroy your phone. Fixez.com did much better.
Related
Ok heres my problem,
My phones battery is completely messed up. The phone ALWAYS says that its at %99 battery(and the number never decreases) but after a couple of minutes of use it will turn off by itself, no warning or anything.
I think I know how it happened(as a warning for other ppl). I went on vacation once and I didn't have a charger cuz there were no computers at the hotel, so I brought a random USB wall charger I found laying around(which I later found out it belongs to some spy pen camcorder ).
Unfortunately though it was charging SUUPPERR slow, so I got the crazy idea to charge it while it was off and to my surprise(dramatization) it charged (a lot)faster.
So I kept charging it like that every day and I noticed that every charge took less time than the last. It also started turning off by itself, though not as frequently as now. I thought the problem would fix it self once I charged it on my computer again, but I was wrong. TT_TT
---
Can anyone offer any solutions? I have a G1 with CM5 and clockworks recovery. I know clockworks recovery lets you do something with the battery, but idk how to use that
please help, this is a REAALLY annoying problem thats forced me to go back in time
You need to make sure it's putting out the same amount of power as your regular charger. I'm not 100% sure of this, as all I can do is charge at my computer and I have no idea how that works (as in if computer puts out waaay more power or has a limit of how much to put out) but I've always heard too much can be a bad thing for batterys. Also, don't overcharge.
^^Just posted that in another thread.
sounds like a died battery
After several cycles on WP7 the batt was fully drained and now it won't charge (charge LED goes on for few seconds and then goes off). It won't load either, just switches off on DFT screen. Batt is standard.
Guess it is critical not to allow batt to drain fully on WP7?
Is there any solution to this?
Thanks for any ideas.
Had a similar problem with Android...battery drained completely and wouldn't charge. I solved it by cutting the end off of a spare USB cable, removing the battery, and charging directly from the cable (red wire to positive/black to negative). After about twenty minutes I put the battery back in the phone and it booted Right up. Or, if you have more sense than me, you could just pick up an external battery charger...I'm just the hack apart a cable and do it caveman kinda Guy...
Sent from my HTC HD2 using XDA App
I can confirm a similar experience; I thought it was worth trying the fully-drain-then-fully-recharge regime suggested elsewhere on these forums as a means of extending battery life, which does struggle a bit on WP7.
The fully discharge bit was easy, but it is worth everyone bearing in mind that magldr - as advised, I believe - will not allow the phone to charge. As a result, I was getting into WP7 (just) only for it to almost immediately shut down. But it was at least doing a small amount of charging before it did.
After a sweaty fifteen minutes or so of restarts (I was having to take the battery out to force the restart as it wouldn't start on the power button), it decided it had enough charge to...well, charge and all was well.
My suggestion would be not to risk going beyond the critical warning WP7 gives, at least until magldr is able to offer charging.
Almost the same issue here, without having let the battery fully drained...
I can't charge my hd2 anymore.....if it's turned off.
But, it Can be charged if wp7 is running! I don't know why...
I had This issue when I received the phone. It took me a whole Day to charge the battery the first time : orange LED turning off after 10seconds (HD2 switched off or in wm6.5
Once the led is off, can't turn the phone on or charge it again until I remove and put the battery back.
It was in summer so I thought the phone was too hot, so I cooled the battery with a fan, replaced it, retryed... At least 10times, and it finally charged.
SO weird, I'll test This again with wp7, who knows?
I am wondering whether it is some kind of magldr bug?
I'll try the trick with the cable directly to the batt. It is not very practical though if you drain your batt, where there is no access to spare cabling.
bdkinney said:
Had a similar problem with Android...battery drained completely and wouldn't charge. I solved it by cutting the end off of a spare USB cable, removing the battery, and charging directly from the cable (red wire to positive/black to negative). After about twenty minutes I put the battery back in the phone and it booted Right up. Or, if you have more sense than me, you could just pick up an external battery charger...I'm just the hack apart a cable and do it caveman kinda Guy...
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
This should be put into the sticky rollup thread for people who have let their batteries drain.
Why dont you do some pics bud and create a topic?
I am cutting the cable as I write. Will take some pics.
If your battery drains completely, just remove it, replace it back. Without starting the phone, connect it to your PC. start and enter the bootloader. You'll be then able to charge. I did it like that last week.
Sent from my HD7 using Board Express
Running cable directly to the batt is confirmed to work. Just revived mine with this trick.
jemaho said:
If your battery drains completely, just remove it, replace it back. Without starting the phone, connect it to your PC. start and enter the bootloader. You'll be then able to charge. I did it like that last week.
Click to expand...
Click to collapse
How do you enter the bootloader, if the phone is not responsive at all?
adminlt said:
I am wondering whether it is some kind of magldr bug?
Click to expand...
Click to collapse
Less of a bug and more of an unwanted side-effect of having this excellent capability, I think. I seem to recall that the developers are aware and looking to see what can be done.
adminlt said:
How do you enter the bootloader, if the phone is not responsive at all?
Click to expand...
Click to collapse
I guess it is possible to completely drain the battery, in which case this won't work. But if there is some power, removing the battery and replacing it should kick the phone into life for long enough to do this. This was going to be my first try if persistent rebooting hadn't eventually worked.
having this problem and definitely charging below the amount...
i cant fully charge the battery as well
Like I said, if connected, but not started, to your computer, you'll have enuff time to start it then and entering the bootloader, of course, you gotta be quick for this to work.
If it doesn't respond, don't laugh, confirmed to work, remove your battery like explained and put it for some mins in the fridge before replacing it (it's only chemistry playing here, somehow better than cutting a USB cable in 2).
jemaho said:
Like I said, if connected, but not started, to your computer, you'll have enuff time to start it then and entering the bootloader, of course, you gotta be quick for this to work.
If it doesn't respond, don't laugh, confirmed to work, remove your battery like explained and put it for some mins in the fridge before replacing it (it's only chemistry playing here, somehow better than cutting a USB cable in 2).
Click to expand...
Click to collapse
You know nothing about chemistry at all! Cold kills battery charge if your going to use temperature use your armpit for 5 mins!
double post oops please delete
lilikin said:
double post oops please delete
Click to expand...
Click to collapse
"storing them in the freezer might be more practical. These kinds of batteries lose their charge after a few days when kept at room temperature. But they'll retain a 90% charge for months if you store them in the freezer. Just like alkaline batteries, you'll need to wait until they've warmed up before using them. However, this isn't a problem when you need new batteries for your digital camera or other electronic gadget. "
I suggest you to be more polite when answering and learn your lessons before posting!
I finally made a dual boot Android/WP7.
At first, Android said my battery was fully charged, just like WP7, which is totally impossible as I used MAGLDR to format the SD card (wp7 & android partitions) and that it took me almost 1hour, without any possible way to charge the battery while I'm in bootloader mode.
But when I turned the phone off, plugged into the wall.......TADAA It was finally charging, with phone turned off
So, it seems that dual boot may be a way to solve this issue
jemaho said:
"storing them in the freezer might be more practical. These kinds of batteries lose their charge after a few days when kept at room temperature. But they'll retain a 90% charge for months if you store them in the freezer. Just like alkaline batteries, you'll need to wait until they've warmed up before using them. However, this isn't a problem when you need new batteries for your digital camera or other electronic gadget. "
I suggest you to be more polite when answering and learn your lessons before posting!
Click to expand...
Click to collapse
You're arguing against yourself here aren't you? Cold may be fine for storage but you need heat to coax a little more power out. You even say 'you need to wait until they've warmed up before using them'.
adminlt said:
I am cutting the cable as I write. Will take some pics.
Click to expand...
Click to collapse
If you could do some pics that would be great...I have two, "My computer's broken," calls to deal with today. Visuals might help some...it's appreciated.
Wrong idea, sorry guys.
I thought that HD2 was charging since I installed WP7 and Android in Dual Boot. But it's a fake : if the phone is turned off, and that I plug it, the orange led turns on. But that's all, even if I unplug the phone, the led remains turned on !!
And now, Android as well as WP7 are telling me that the battery is fully charged but I'm sure it's not even 50% full.
Hi all,
I'm having a bizarre problem with my OPT. The thread title doesn't really adequately explain the issue. Basically, if I shut the phone down, it will not turn back on. It won't boot to fastboot, recovery, or system. There is simply no response. If I plug the phone in, then after hours (or minutes, randomly), the battery icon will pop up with a red charging light (indicating a low battery?). However, it does this even if I shut it down with a full charge.
As an example, I shut it down before i went to bed last night (with ~80% charge), and left it plugged in. I got up this morning to no sign of life, not even a charging light. I unplugged it, plugged it into my PC, and an hour later I hear the little "new device" sound, and suddenly the red charge light is on. I wait some time, then attempt to turn on the phone. Then I hear the "device disconnected" sound, and it's dead as a brick again.
It also does this once the battery gets full. Eventually after attempting to power on the phone over and over again, it will randomly decide to turn back on, and then the phone works fine until shut down/rebooted.
Has anyone experienced this or have any advice? I'm hoping I just have something corrupted in my boot files or something software/firmware-related, but it makes the phone essentially unusable (and I certainly can't install a different ROM or anything while it's behaving like this).
Hi
Flashed Bad file ? Power problem ? Dead battery ? Charger problem and / or cable ?
But I already had that on my OnePlus 1 and I just changed the battery ... If it helps . Good luck anyway !
Be tested no choice. Unless you have the guarantee and a lot of time to waste in OnePlus...
Lydroya said:
Hi
Flashed Bad file ? Power problem ? Dead battery ? Charger problem and / or cable ?
But I already had that on my OnePlus 1 and I just changed the battery ... If it helps . Good luck anyway !
Be tested no choice. Unless you have the guarantee and a lot of time to waste in OnePlus...
Click to expand...
Click to collapse
I haven't flashed anything recently. I got the phone in September... unlocked, rooted, flashed TWRP, but haven't done anything since.
It's acting like the battery is completely dead, and it needs some time to charge before it will allow me to turn it on. But the battery is almost full.
niplfsh said:
I haven't flashed anything recently. I got the phone in September... unlocked, rooted, flashed TWRP, but haven't done anything since.
It's acting like the battery is completely dead, and it needs some time to charge before it will allow me to turn it on. But the battery is almost full.
Click to expand...
Click to collapse
You often dumps your O+ thoroughly ?
Because if so, it's not a laptop battery after I could be wrong but from my misadventure with OnePlus 1, it tires more battery than anything else. (On phone) :silly:
That way I'm not saying Fakir but I think if you have the guarantee, you should try to open a ticket to return your Oneplus. :good:
When my OnePlus fully discharged for a while he puts around 10 minutes to re-ignite (Oneplus 1) it is also how I ****ed my first battery on the OnePlus 1. :crying:
Not try to completely unload the O+2 from...
I'm just trying to help. :angel:
( PS : I still want to clarify that OnePlus 1 when it makes a point that the battery is empty it puts at least 10 minutes to light if I have the logo of the empty battery in red, even super you tell you my phone is dead ! And It is not ! If you know how is the process of loading a battery. And if such is your discharge too fast or you have a problem or charging your battery discharges of a sudden, I tell you it's more than problable so that your battery is lame. ) ( Sorry 4 my bad english.... )
The battery wasn't dead, I just shut the phone down. I very rarely discharge it all the way. Battery life is fine when the phone works. It's almost like the charging circuit THINKS the battery is dead and won't let it turn on. I'm not sure if this is a hardware or software issue.
Actually I just turned the phone back on. I just kept pressing and holding power until it finally responded and turned on. But now I'm afraid to reboot it again, or i'll be without a phone for 6+ hours.
niplfsh said:
The battery wasn't dead, I just shut the phone down. I very rarely discharge it all the way. Battery life is fine when the phone works. It's almost like the charging circuit THINKS the battery is dead and won't let it turn on. I'm not sure if this is a hardware or software issue.
Actually I just turned the phone back on. I just kept pressing and holding power until it finally responded and turned on. But now I'm afraid to reboot it again, or i'll be without a phone for 6+ hours.
Click to expand...
Click to collapse
Software yeah maybe but i think its more probable a hardware issue, i dont know.
You should try to open a ticket to return your Oneplus. :good:
Sorry I can't help you any more, hoping that the community and champion these seeds tries to meet you too !
Did you try to do a full wipe and install stock OxygenOS 2.1.2 ? ( Without SU or XPOSED ?)
Good luck anyway ! For me it is 0:23 am in France and I'm k.o :silly:
Good night !
May the force be with you ! ! ! :laugh:
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?
Not sure if it is a bug, or if the screen-pinning is actually working to perfection. IMO it works a bit too well for comfort.
Was playing the most recent riptide game, and to do tricks I usually ended up hitting the hardware touch keys, so I turned on screen-pinning to counter that. Well, apparently you don't receive anything from the system (battery low warning etc...) while it is on, AND the system cannot overrule it. Meaning even if the battery goes to 0%, it won't shutdown/poweroff.
The phone literally turned off in a snap, screen flashed kinda weird colours and puff! Off!
When I tried turning it on, the usual multi-lingual red writing saying battery is low appeared and disappeared in an instant, instead of the usual 1-2 seconds being displayed.
I plugged the Dash charger and the red writing appeared instead of the charging symbol. It took like 3-4 minutes charging before the phone "turned on" to display that lightning/thunder image that informs you it is charging. I think dash charging only activated at that point.
Haven't turned it back on yet. Gonna take advantage of this and charge till 100% for the calibration X_X
I think that the red writing when plugging in your charger actually should be a charging message which however is the same like the low power images (there are two images, one called lowpower, one called charging, both contain the same data)
Running the battery down to completely zero can brick your phone. The phone needs a very slight charge to recharge. The system shuts it down very slightly early because of this. You often see people bricking their phone because they completely discharge in recovery.
B3501 said:
Running the battery down to completely zero can brick your phone. The phone needs a very slight charge to recharge. The system shuts it down very slightly early because of this. You often see people bricking their phone because they completely discharge in recovery.
Click to expand...
Click to collapse
yes, discharging completly your battery wont have a positive effect for you - its the other way round.
but if you think you will get a "recalibration" thing or something.. then go ahead and have fun with your placebo effect