Note 3 Battery died, now wont boot. - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.

ant6893 said:
So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.
Click to expand...
Click to collapse
have you tried booting with it connected to the charger?

ant6893 said:
So I was at work and my phone had 5% battery left approximately so i shut it down to be able to use it right after my shift ends. So when my shift ended, i tried to boot my phone back up and it makes it to the ATT splash screen but will not go any farther. I rebooted into recovery mode and my phone showed battery at 1%. I placed my phone on the stock usb 3.0 charger and it showed that it was charging. i tried booting again after a while but it wont get past that splash screen. During the time that its stuck on the splash screen, the blue LED pulses.
Its been charging for an hour and the battery logo is showing at least 50% now but it still wont boot past that screen
Im on 4.4.2 and its rooted (i have the safestrap recovery). this has happened before but i didnt have the patience and reflashed the stock kitkat firmware through odin and re-rooted. I lost all my data and would like to avoid doing that again. any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you get into Safestrap atleast or not?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras

xXPINCARXx said:
Can you get into Safestrap atleast or not?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
Click to expand...
Click to collapse
I tried everything with no luck. Ended up just reflashing my firmware again. I'd like to know what that issue was however, in case it happens again.

Alright, did you install any xposed modules or anything of that sort?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras

xXPINCARXx said:
Alright, did you install any xposed modules or anything of that sort?
DK 4.1, GPE Orange, Xposed, xgel, and other great extras
Click to expand...
Click to collapse
i did not, it was 100% stock 4.4.2 firmware, rooted with towel root and safestrap 3.75
System tuner is an app i use, and i changed some build.prop info such as dalvik vm heap growth limit, start size, and wifi scan interval. but thats about it

Sorry for the late reply but these changes could simply be your problem. Though I am unsure of this it's really the only thing that would make sense besides a hardware issue
DK 4.1, GPE Orange, Xposed, xgel, and other great extras

Related

[Q] Stuck on Samsung logo + previous flickering problem

Hello.
About one month ago I rooted my Galaxy Note and flashed Phliz kernel, but kept the original ROM.
A couple days ago my phone started to have some screen flickering and battery drain issues. The screen started flickering and the battery drained till 15%, when the phone completely shuts down. This happened a couple of times. I always put the phone to charge after this, and was able to power it on.
But today this happened and when I tried to power the phone on, it stucked on the Samsung logo screen. And stays there forever. I tried to restart and even do a factory reset (I dont care about my data since its everything on the cloud). The problem persists.
When I put the phone to charge the battery charging icon appears and apparently it charges normally.
I am able to enter the Recovery mode (CWM Touch) and the Download too.
What should I do? Can the problem be the battery? Maybe I should unroot it? Flash a stock kernel?
allanpoppe said:
Hello.
About one month ago I rooted my Galaxy Note and flashed Phliz kernel, but kept the original ROM.
A couple days ago my phone started to have some screen flickering and battery drain issues. The screen started flickering and the battery drained till 15%, when the phone completely shuts down. This happened a couple of times. I always put the phone to charge after this, and was able to power it on.
But today this happened and when I tried to power the phone on, it stucked on the Samsung logo screen. And stays there forever. I tried to restart and even do a factory reset (I dont care about my data since its everything on the cloud). The problem persists.
When I put the phone to charge the battery charging icon appears and apparently it charges normally.
I am able to enter the Recovery mode (CWM Touch) and the Download too.
What should I do? Can the problem be the battery? Maybe I should unroot it? Flash a stock kernel?
Click to expand...
Click to collapse
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Mayank Chandwani said:
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Click to expand...
Click to collapse
Can I follow your video step-by-step even having a custom kernel (Philz) and CWM?
Mayank Chandwani said:
flashing the latest stock rom shuld do the work.. stay on stock kernel with 4.1.2 may be u wanna try 4.2.2..watch my video for that link is in siganture
Click to expand...
Click to collapse
I did it. I followed your step-by-step video. Everything seen to be ok. Unfortunately the same error is happening, the only difference is that it's stuck on the Nexus welcome screen (the X), not the old Samsung screen.
It kept this screen till the screen started flickering again and the phone shut down, as before.
So, I changed the recovery to the normal 6, the kernel to the CM and the ROM to the Nexus 4. None of these solve my problem. What to do now?
So... I tried to flash a stock ROM (JB XXLSZ) through Odin. I did everything according to this video ?v=nmLm2pTdxk0 from youtube.
I also changed my battery to another (non-original) that I arranged. Now the flickering stopped.
Now I'm on a bootloop (like he was at the first try), but I tried the second time and it continues on a bootloop. Also, when I go to the stock recovery, it says:
"e: Failed to mount /efs (Invalide argument)"
It appears I bricked my phone? I do not have an efs backup.
Can anyone help me?
No one? Common guys, I don't know what to do...

[Q] Custom Roms will not boot 1.44 unlocked with S-off

Ok I got a replacement HTC ONE today. Unlocked the bootloader, used revone for s-off. All good.
TWRP recovery opens and runs fine.
Backed Up stock rom.
Wiped and Flashed both ViperRom and Android Revolution HD 30.0. Neither boot.
tried flashing the corresponding boot.img files for both, CMD says pushed OK. But still neither will boot.
I am stumped. Restore from recovery to stock rom backup works fine.
Any ideas? Needs some advice
OK i tried restoring from twrp back up and now when it boots its goes to a black screen with a status bar at the top. Shows the little android symbol for debugging. then on the other side battery, clock, signal bars that have a X for no signal. Cant do anything. Sits there for a few minutes then reboots.
Please help. lol
OK i tried restoring from twrp back up and now when it boots its goes to a black screen with a status bar at the top. Shows the little android symbol for debugging. then on the other side battery, clock, signal bars that have a X for no signal. Cant do anything. Sits there for a few minutes then reboots.
Please help. lol

Stuck on flying dots

My phone died last night, and today when I through it on the charger it turned itself on and it's been stuck on the flying dots boot screen and will not fully boot. I've tried a factory reset and nothing. Rooted with Chainfire's CF-AutoRoot, maybe that has something to do with it?
Any help is appreciated. Going to flash the factory images via fastboot shortly.
CaptainSpazzz said:
My phone died last night, and today when I through it on the charger it turned itself on and it's been stuck on the flying dots boot screen and will not fully boot. I've tried a factory reset and nothing. Rooted with Chainfire's CF-AutoRoot, maybe that has something to do with it?
Any help is appreciated. Going to flash the factory images via fastboot shortly.
Click to expand...
Click to collapse
It takes a long time to boot after rooting. I think it has to do with the encryption
Sounds like you have a bootloop. Try to wipe from recovery
How long u let it sit? Mine take a few mins
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
CaptainSpazzz said:
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
Click to expand...
Click to collapse
Yeah that's too long
CaptainSpazzz said:
15 - 20 minutes. I just reflashed the factory images and all is well. I dunno if root had anything to do with it or not. Kinda weird it died then when turned back on stuck on a boot loop.
Click to expand...
Click to collapse
Mine did that once. I just held down the power button until it rebooted again and then everything was fine.
Just had this issue again. Shut the phone down, turned it back on, stuck on flying dots for 20 minutes. Maybe its root related. Reflashed stock images again. I won't root again to see if the problem persist.

[Q] I can't unbrick my S5

Last night I started messing with the S5, I used Odin to restore to stock, then took all the OTA updates all the way to the 4.4.4 one that came out recently and after that I debloated it and removed the att apps and such, everything was fine. I tried changing the boot animation but messed up somewhere along the way and it wouldn't show a boot animation at all but still booted and got to the main screen and functioned perfectly. I decided to start over and tried to use Odin to restore to stock 4.4.2 but after flashing the first screen comes on and says that it's custom and has the open lock symbol then shows a slow and laggy samsung boot animation before freezing at some point on the animation and the screen goes completely black but the blue LED light stays on and it does nothing after that. I have tried using Odin repeatedly and erasing everything through recovery and nothing works. Please, any help would be appreciated.
It has been fixed I believe, I flashed the G900A_OA1_Stock_Kernel.tar.md5 and it works again.
Where did you get the .tar.md5 file? I think I just bricked myself out of recovery mode

softbricked 6? stuck at boot animation

Was running stock 6.0.1 in unlocked mode, and applied the 7.0 OTA Tuesday AM. Phone booted fine, with the exception that the 6.0.1 boot animation displaying. Phone booted into 7.0, so whatever. worked great for 2 days, when i woke up yesterday screen wouldn't turn on, so hold the the power button and re-start. Phone got to boot animation and stayed there for an hour until i shut it off, never got to the pattern unlock screen. I've tried wiping it, factory resetting it, installing TWRP to wipe and install, nothing, still stuck at the boot animation, no matter how long i let it sit. I've tried flashing other roms, with the same results. I can get into bootloader and recovery without issue, and can flash without errors (that i'm aware of) but always have the same result. Any thoughts? Or am i going phone shopping today?

Categories

Resources