Having a strange issue with the phone , phone battery died so I left it overnight to charge . Now when I try to boot the phone , i get samsung logo and the phone doesn't boot up.
Is the phone bricked ??
smartguy10 said:
Having a strange issue with the phone , phone battery died so I left it overnight to charge . Now when I try to boot the phone , i get samsung logo and the phone doesn't boot up.
Is the phone bricked ??
Click to expand...
Click to collapse
No, you are not bricked . Are you sure it even charged? If so, go into recovery wipe cache partition and dalvik cache then reboot. See if that fixes it. As long as you get a boot screen the phone can be fixed almost 100% of the time.
Related
My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
soupmagnet said:
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
Click to expand...
Click to collapse
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
vertcam9 said:
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
Click to expand...
Click to collapse
I see.
There was a user a while back that ended up with the eMMC bug and had to repartition his device to skip over the bad blocks. In doing so, he didn't allocate enough space for a proper cache partition (something like 150MB, I believe) and his device would do the exact same thing.
I would suggest clearing your cache and see if that helps. You may have to do a true wipe though, because I don't think a wipe in custom recovery will cut it.
You might want to check the cache, system, and boot partitions for bad blocks while you're at it.
Try other ROM
vertcam9 said:
My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Click to expand...
Click to collapse
From my experinces with KF1 for two years, switch to stock ROM 4.3 AOSP from Hashcode and everything became wonderful. better battery life, no freezing
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !
I have this problem for quite a while now. I had Lineage OS installed in my phone for about 6 months and suddenly , one day when I tried booting into it , it failed. The HTC logo appeared but then the phone shut down , it would boot if I plug the charger in. I took it to HTC service center , to get it checked. They told that it might be caused by faulty battery. I took it to a shop nearby to get the battery replaced , but replacing the battery did not work. The shopman told me that the phone is rooted , and they told me that they will lock it. After they did , now I am unable to boot at all. I unlocked the bootloader again , and when I try to open recovery (TWRP) it just shutsdown again. I will get the battery charging screen. If I press the lock screen , I can see a bit of twrp but I'm unable to operate it. I then flashed CWM , it works , but I have no idea what to do next. I only had TWRP backups , which unfortunately do not work any longer.
I have a5_dwg.
parik27 said:
I have this problem for quite a while now. I had Lineage OS installed in my phone for about 6 months and suddenly , one day when I tried booting into it , it failed. The HTC logo appeared but then the phone shut down , it would boot if I plug the charger in. I took it to HTC service center , to get it checked. They told that it might be caused by faulty battery. I took it to a shop nearby to get the battery replaced , but replacing the battery did not work. The shopman told me that the phone is rooted , and they told me that they will lock it. After they did , now I am unable to boot at all. I unlocked the bootloader again , and when I try to open recovery (TWRP) it just shutsdown again. I will get the battery charging screen. If I press the lock screen , I can see a bit of twrp but I'm unable to operate it. I then flashed CWM , it works , but I have no idea what to do next. I only had TWRP backups , which unfortunately do not work any longer.
I have a5_dwg.
Click to expand...
Click to collapse
try to install twrp 3.0.0, probably from adb shell over the USB cable, in cwm recovery.
that should sort it out. hopefully. then you can try restoring a backup and see if switching the battery actually made any difference or not.
Unable to boot into phone
I have the same problem with me but i have twrp installed(3.0.0) and stock rom and bootloader unlocked. When i install lineage os in it it boots but only when charger is connected whereas when i restore my stock rom back up it couldn't boot into it reboots again and again...
I have a5_dwg.
Vibhor verma said:
I have the same problem with me but i have twrp installed(3.0.0) and stock rom and bootloader unlocked. When i install lineage os in it it boots but only when charger is connected whereas when i restore my stock rom back up it couldn't boot into it reboots again and again...
I have a5_dwg.
Click to expand...
Click to collapse
Try wiping data with the stock backup to see if it'll boot. I had an evo3d with some internal glitch that would from time to time bootloop stock until I wiped data then it would start up again.
Sounds like your battery might be weak, ROMs like to shut down if they think the battery is too low.
Having the same problem right now, confused whether I should replace the battery or not, right now plugged into a charger, phone is fully charged nd removing the charger phone turns off.
Hello,
My OnePlus 3 just stopped working today, wihtout any reason, apparently.
I am able to boot on the OnePlus logo, I see the red dots turning indicating that the system is booting, but after few seconds the dots stop moving and the phone instantly turns off (the screen become black and nothing appears).
I can :
- Boot on the recovery : I wiped everything, flashed a stock ROM from OnePlus using the adb sideload with success, but the booting problem remains.
- Boot in fastboot mode : but the phone is locked and I cannot flash anything here.
Other observations :
- My battery is fully charged
- Storage is encrypted
Can anyone help me ? I don't have the financial ressources to buy another phone, so any help will be greatly appreciated...
try these option ..
https://www.youtube.com/watch?v=UUdDUfe7yUY
or
https://www.youtube.com/watch?v=O2_x9SnJ1Ak
kingviking said:
try these option ..
https://www.youtube.com/watch?v=UUdDUfe7yUY
or
https://www.youtube.com/watch?v=O2_x9SnJ1Ak
Click to expand...
Click to collapse
I've done it, but it didn't solved the problem.
Now, the problem is fixed. This is what I did : I unplugged the phone and let it reboot constantly overnight. At the morning, the battery was very low and the phone was off. I turned on the phone and it worked...
How the hell can this be possible ? What kind of problem is this ?
Since not so long ago I've experienced the following:
If I leave the phone two have low battery like 10% when it dies it enters a boot loop I cannot stop and I just can only plug it in and wait while it bootloops without being able to stop it and a long time later (20/30 min) it will finally boot up, last time it had 30% battery when it finally booted up.
What could it be? It may have been the last update? Has anybody experienced this?
If you did a major firmware upgrade without a factory reset, do a factory reset now.
Otherwise clear the system cache.
It it persists, factory reset.
If it still continues it maybe hardware. It could be corrupted firmware but trying to reflash may end up causing it to brick if it acts up during the reflash. Consider your options carefully at this point especially if under warranty or insured.
I have the same thing. The phone just starts to vibrate indicating a startup, then after a few seconds it vibrates again, and continues in this loop. The screen doesn't display anything.
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Maybe on an unlocked bootloader it doesn't work? Something related to offline charging?
IronHulk27 said:
I'm having the same thing right now, I tried wiping the cache from bootloader and charging the phone to 100%, but it doesn't seem to be fixed
Click to expand...
Click to collapse
I have not had it happen lately the other day I had 5% battery and it worked fine.
I think it might be an unsupported charger?