Hi Guys,
Before i move on, my phone literary died today, and randomly, managed to get it back to life.
Let me explain my case first.
I have a Samsung A3 2015 (SM-A300FU) which i have constantly updated with new builds, and lately am on a custom rom (with modem and BL updated). Obviously, rooted, custom recovery, custom kernel.
This setup was perfect so far, no issues, at least nothing majorly resetting my phone or ending on a shutdown.
Today i made it at work with 0% battery, plugged it on my charger, and left it to charge until 46%. Turned it on (yes, i charged with phone off), browsed a bit...and just as i was to hit the power button for sleep, the phone got unresponsive and just powered down. I initially thought that somehow an app in the background is delaying things so i even left it see if it recovers, just to see that the phone completely died.
By DEAD, i mean:
1. It wouldn't cold-reset with Vol Down + Power Button.
2. It wouldn't power on obviously.
3. No download mode...how could it work, if the above two didnt work.
4. No what so ever detection in USB from Windows, no qualcomboot or whatever that boot mode is.
I literary left it in the charger for half an hour, no signs of charging, no heat, nothing. Took it out, tried whatever not method with what ever amount of time required to hold whatever button, nothing worked.
For weird reasons, i thought LET'S CONNECT THE CHARGER, WHILE I AM ACTUALLY HOLDING VOL DOWN + POWER BUTTON, AND VOILA, IT BOOTED.
I booted successfully, to find out that the battery is at 0%.
It is impossible to discharge 46% that fast, so the only possible explanation is that it never charged to begin with. What powered it down, probably the same reason, no juice.
To all the HARD BRICKED lads here, can you try the above in BOLD AND RED?
To mods, feel free to axe the thread if things dont get as expected.
You dont know what a hard brick is. What you encountered wasnt it.
Mind you mate, input needed, it is literary the first words of the subject.
Try to correct, and not belittle, and try at least to elaborate.
Related
I went out for a while with my battery at 20%, when I came back it had drained out. I put it to charge, but when I tried to switch it back on, it refused to boot. On a normal power button press, it would vibrate 3 times and then the red notification light would start blinking. Same thing with power + volume_up. If I press power + volume_down, it would vibrate 5 times and the green notification light would stay lit. Nothing comes on the screen, whatsoever.
I was rooted with S=off, and was using the Operation Inferno ROM (which I have been using comfortably for the past month or so).
I did try some stuff with ADB, such as using it to reboot into bootloader and recovery (same 3 vibrate + red notification light), pushed the Operation Inferno ROM again to the sdcard and tried to restore the ROM from that location (for which I got adb: unable to open file /sdcard/backup.zip).
I haven't yet gotten around to downloading and installing the factory image some have suggested for the eMMC issue (PD15IMG.ZIP) but I wanted additional opinions considering most people with an eMMC issue have been able to open HBOOT at least.
When the phone doesn't power on, neither ADB nor fastboot will help you. There is no device on the other side, so all your attempts went to the drain, and it was expected. Nothing to do with eMMC issue or anything else. Your phone just doesn't power on.
Put your phone to charge, if the light turns orange - just leave it to charge until it's green, then disconnect and try to power on.
If the light doesn't turn orange, or it doesn't power on even after charging - remove the battery for 10 min, press Power button for 1/2 min, release the button, reinsert the battery, put to charge. And again, let it charge before you try to turn it on.
I did charge it earlier (for about half an hour or so) and the orange light does come, but it didn't boot after that either.
I'll just give it a try by charging it through the night and see.
I think a key thing is to take out your battery for 10 min, as Jack_R1 suggested. Then proceed with the charging.
Sent from my HTC Glacier
Still doesn't work. I dissembled it and kept it like that for quite some time, then put everything back and charged it for hours. Still the same issue happening during boot.
Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).
Jack_R1 said:
Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).
Click to expand...
Click to collapse
When its plugged in, its recognised by the ADB (even when powered off), and I can do some basic commands (mentioned in the first post). When I power it on the same thing happens as when it wasn't plugged into USB (ie, the vibration and the blinking LED).
I'm also worried about water damage, since a very tiny amount did come on it as I was sweating profusely. Although the indicators in the battery tray and on the battery itself don't signal damage (they're completely white) I've just decided to try and keep it opened up in a bowl of rice, just in case, until someone is able to come out with some idea.
As I'm in India, taking it to T-Mobile is not an option. If nothing works out, I might take it to HTC and see if they can help out.
Hello guys, first than nothing, sorry for my bad english, isnt my native languaje. I got this problem yesterday in the night of the new year!!!!!!!:crying: I was rooted, using Xylon and Faux Kernel, but the problem appears from nothing!!
The first thing that I detected was, the phone take a WHILE!!! for charge.... then, out of the power, the phone get overheating and discharging so fast, never in life that happends, when N4 got discharged i try to turn on again but download mode appers in the screen, finally I get in the recovery, then I did a wipe cache/system and factory reset. Install again the Xylon... but when phone finally turns off, when I plugged in to AC absolutelly nothing happends, the led just turn in red, and the N4 dont start in FB, dont get charge, dont do a sh*t !!!! I conect it to the PC but also nothing appends, the N4 doesnt appear in my device list.
So... my N4 its broken?
There was possibly something wrong with the kernel and rom combination that caused your phone to overheat. I think eventually the heat may have damaged your hardware. Sorry but, if something was wrong in the first place it was not a good idea to reinstall the same thing that was causing the problem, if I were you I would have flashed a stock ROM. My only advice now would be to RMA it and pray
EDIT: I found this if it helps at all:
If you are unable to access the settings menu of your device, you can still reset your phone by performing a Hard Reset. Here are the instructions:
If your phone is on, power it off.
Press and hold Power until the device powers on, then immediately press and hold Volume Down (while still pressing Power). You will see the word Start with an arrow drawn around it.
Press Volume Down twice to designate Recovery mode.
Press Power to restart into Recovery mode. You will see an image of an Android robot with a red exclamation mark.
While holding down Power, press Volume Up.
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it.
Scroll down to "Yes - erase all user data" and press Power to select it.
Note: If at any point during the above steps your phone becomes unresponsive, you can restart it by holding down the power button for several seconds.
Before you try anything else, try and leaving it plugged in for a while and then try turning it on. Or leave it plugged in to a computer then try turning it on.
joshnichols189 said:
Before you try anything else, try and leaving it plugged in for a while and then try turning it on. Or leave it plugged in to a computer then try turning it on.
Click to expand...
Click to collapse
Try this. I haven't had it happen to me, but I do have a friend who this exact same thing happened and he thought it was bricked. He left it plugged into AC over night, and in the morning it would turn back on.
First than nothing, thanks for reply, I appreciate your intentions to help me.
I will leave it charging all the night and while Im working too... I hope after that, the phone at least turn on.
I dont install the STOCK ROM because I dont have it in my internal memory and I was in my girlfriend house, the night of the 12/31/12, there is not much to do...
I did the same post, but a little bit more explained
Its here: http://forum.xda-developers.com/showpost.php?p=36165434&postcount=2708
(In case you want to know all details about this problem..)
And Thanks againf for your help!
got the same ****
have a look here
http://forum.xda-developers.com/showthread.php?t=2050811&highlight=bricked+
we are not alone with that problem
some more people have the same problem
i did not even overclocked or benchmarked..
read this post, maybe its helpfull for you
http://forum.xda-developers.com/showthread.php?t=2011328
battery
It could be bad battery, how long did bought of you had working phone, how many times did you charge?
Did you use out of the box charger?
Did you have problems with usb jack?
kibox said:
It could be bad battery, how long did bought of you had working phone, how many times did you charge?
Did you use out of the box charger?
Did you have problems with usb jack?
Click to expand...
Click to collapse
I bought it the 13/nov..
I received it 29/nov.
I ALWAYS use stock charger, only 1 time i try to charge it in my car, but it was less thant 5 minutes, I decided dont charge with the car because the energy variates when I accelerate...
After that, I use my phone quiet normal.
I had this problem with my nexus 7. I think my battery died all the way and it couldn't charge. The stick charger wasn't doing anything. But I plugged it into my computer for a few minutes and tried turning it on. Then when the loading screen appeared I ran it to it's stock charger and charged it to full. Your battery probably died. Try different combinations of ways to get it to take a charge. Just long enough to turn on then plug it into its charger. Though the overheating could have fried it
Sent from my SPH-D710 using xda premium
My AT&T LG G2 (plain D800) is rooted, and has Xposed installed on it (I'm not sure if this caused the issue or not), but here's what I'm having problems with:
I was playing a game, when all of a sudden the phone froze (no biggie, it's done it before, I've held the power button to force restart it, and it works), but the phone shut off on it's own, and would/will not turn back on.
Tge LG boot logo comes up intermittently when I hold power and volume up, but only sometimes. The phone has only twice now gotten to the AT&T logo, but freezes immediately and shuts down. I've tried literally every combination of holding buttons, for up to 70 seconds at a time, both on the charger, off the charger, and while plugging into the charger.
I cannot get to download mode, I cannot get to TWRP, and can obviously not boot into the phone. I had made no changes in weeks prior to this happening, so I can't see why or how something with my phone being rooted would cause the problem.
I've left the phone charged overnight before performing the actions (the phone won't even show battery percentage), so I don't think it's a dead battery issue. Everything I've read so far seems to say that the battery chip has died and needs to be replaced. Somehow I don't think it's the problem.
I'm fully willing to completely wipe the rom, and everything on it, as long as I can get the phone working again. However I cannot boot into download mode to use ADB or anything.
Is my phone completely bricked? Or is there a chance that the battery chip really is fried? Please help!
Update!
I left the phone charging some more, and decided to try volume up and power (while plugged in). The phone actually went into download mode for about 5 seconds before shutting off again. I tried doing the same steps, but nothing will come up again. It appears to be an issue with the battery on the device. Does anyone else think otherwise? Or will I have to send it in for a new battery? (The phone is less than a year old so I don't want to void the warranty anymore than rooting, which they wouldn't be able to tell since it won't turn on anyways).
Update Again:
I can get the phone to show the LG logo/download mode on a fairly consistent basis, sometimes showing a static screen (colored noise, not monotone), sometimes a blue screen, but it will shut off after 5-6 seconds every time.
Hey, I do not want to announce bad but by your description it seems that did you mother board, go to the lab to make sure, I had something similar and I replaced the motherboard and my phone came on time, check if the device is still under warranty has a good chance to replace you under warranty, good luck.
--- This may belong in the Xposed forum, I am uncertain. ---
Hello. Please forgive my ignorance regarding the technical aspects of methods discussed on these forums.
I have a Samsung Galaxy S4 GT-I9505 supplied by Vodafone Australia. This was received today as a replacement for a screen issue I had with my previous S4. On the previous S4, I had rooted using a Saferoot method as read about on this forum. Later I had installed Xposed to use Keepchat and everything was fine. Today I have rooted this replacement phone successfully using the same method, and then moved to install Xposed. The Xposed application required an update, the very first option in the app was red and suggested an update or a reboot, and the reboot did nothing, so I pressed update. The phone turned off but didn't restart. I tried the usual button presses and battery pulls and finally a simple power up using the standard power button started the phone up. It got as far as the lock screen I believe, before shutting down again. It is now unresponsive. It wont turn on, enter the boot menu (multi button holding method) or charge. I believe the battery is quite low at this point, and unable to charge, causing me some consternation. It has now been over 30 minutes with no response.
If anyone could provide a resolution to this issue, I would be extremely thankful.
Regards,
CaleS
Try and ask in this forum my friend good luck
http://forum.xda-developers.com/showthread.php?t=2265477
Hello again.
I have an update on my situation.
I left the phone on charge and it eventually turned on by itself. I played around with it for a while and it seemed OK. Eventually it turned off again. I had to pull the battery to get it to turn back on. After starting up again, getting to the lockscreen, it turned off again. This process repeated many times, until I got frustrated.
The next day I thought I'd try a factory reset via volume up + power, and the device managed to stay on long enough for this to complete. After the phone reset, I used it for a while and again it turned off. The same cycle continued.
Perhaps the phone is naturally faulty, despite my rooting attempt, as it was a refurbished model. I am quite happy to return it for another replacement under warranty, however I may not be able to do it as the device is rooted. I would gladly remove the root using stock firmware and Odin, however the phone resets after a few seconds of entering download mode.
Any advice?
Thanks.
Sounds to me you have a faulty power button. It's somehow stuck that's why it even reboots in download mode. It's a common problem for the S4. Try to wedge it or replace it.
if it is refurbished model it might as well be dead battery.
battery sensor detects "low battery" state and shutdown phone saying battery 0% - to protect battery against fully depleted state (damaging to max capacity or even impossible to charge at some point)
if you power it on again it will boot and say it has like 1% left and you will be able to use it for few more moments, but doing so will degrade your battery.
powering it on, going to lock screen for it to shutdown on its own again sounds like weak power source
imagine above scenario happening several times (previous owner of the phone kept "reviving" it after shutdown due to battery 0%)
that would resulted in battery able to hold only fraction of its standard power - allowing you to just boot your phone before it shuts down.
I had similar situation with my laptop battery (this one was on AC all the time) - battery was so damaged that laptop was shutting down at windows login screen - if booted on battery alone.
When booted on AC and unplugged it said 100% battery, that went down to 0% in a matter of around 2 minutes, when laptop shuts down.
So few days ago my phone suddenly turned off and kept rebotting itself (It would reach the samsung galaxy logo and then turn off). I thought it was a battery issue so I removed it for 30mins and tried again, worked fine for an hour then problem started again. I left it over night to charge in the wall socket incase.
Same issue next morning and no solution.
I replaced the battery with a friends and the same issue happened on my phone (i used my battery on his and it works fine on his) so I removed the issue of battery itself.
That evening the phone then just stopped responding at all. It would not respond to pressing the power button (no load, no vibration).
Tried entering download mode using vol down + home + power. Nothing. (So cant use Odin)
Tried entering recovery mode using vol up + power. Nothing
Tried hard reset using vol up + power + home. Nothing.
(All the steps I used a fully charged battery from another s4 phone and removed/re-entered before trying again)
So I check online and notice some people having issues with power button, but even if that is the case - wouldn't my phone still charge? I dont even get the battery chargning icon on the screen when plugged in either PC or wall socket.
I opened it up and changed the motherboard with another samsung s4 and my original problem mobo still does not load on the new s4. (My new mobo worked on the old device though).
The ONLY response I got was when I used my original mobo on new s4 device and plugged it into PC, it popped connect and then disconnect sound and thats it (doesnt recognize usb port).
What are my options apart from getting another motherboard or going to a shop for a JTAG repair? I was contemplating just removing the power button and seeing if that helps in getting a charge response lol
Well your power button is broken for sure. Replace it and then test it.
Lennyz1988 said:
Well your power button is broken for sure. Replace it and then test it.
Click to expand...
Click to collapse
Wouldn't the phone still recognize charging even if the power button is faulty?
penguness said:
Wouldn't the phone still recognize charging even if the power button is faulty?
Click to expand...
Click to collapse
It always takes a few seconds before it starts to charge. So maybe the device reboots before reaching the charging phase. I'm guessing though. But since your problems started with power button issues it would be the logic place to start.
The part only costs a few dollars.
Well I'm exactly in the same situation as you, since this morning on a i9505 running JFLTPE-GPE 5.0 ROM. The screen appears for 1 second or 2 (Samsung logo) then it powers off . I need to remove the battery to try something else.
Same behaviour, even for recovery mode, so Odin is not an option.
I thought that changing some kernel settings have caused that, but as I just put them back to default values, it should not happen.
I didn't have some power button issues, it was just powered off at my wake up this morning. In your case, does your phone vibrate and power up instantly when you put the battery ? That's the case for me, but it should not be the normal.
My problem is actually solved : indeed, it was the power button. I removed all the screws and played a little with this power button (air dust, etc...), enough to make it start correctly !
I managed to do some backups, and now I hope that it won't break again.
Calicodesiles said:
My problem is actually solved : indeed, it was the power button. I removed all the screws and played a little with this power button (air dust, etc...), enough to make it start correctly !
I managed to do some backups, and now I hope that it won't break again.
Click to expand...
Click to collapse
Yeah, that happened before (automatically powering up, vibrating, going to samsung logo and then shutting down and doing it again until I removed battery - putting the battery back in with start it up without pressing the power button).
When it was in that phase, the one thing that did work was doing a soft reset (home+power+down vol, and then holding just power) - however that only worked for like an hour before it went back to the restart phase.
However now it doesn't respond to anything at all. (Any kind of response I got was when I put that mobo in another s4 and plugged in usb, which just gave a connected/disconnect sound on w7, no life on the phone itself).
Be very careful as to what you do, I suggest you do NOT leave the battery on it and charge it (which was the last thing I did before it went unresponsive) - my guess is phone went haywire trying to turn on/off continously.