Phone reboots when changing - Galaxy Note II Q&A, Help & Troubleshooting

Hi my phone reboots when I charge it and then goes into boot loop until I remove charger. If I charge via computer it's OK. Could be a hardware issue but could it also be a custom rom issue? I would like to try to reflash to original rom.
Can I just use kies or do I need to do something before?
I'm on lollipop rom now.

Related

automatic reboot

Hi all
This whole saga of auto reboot started when I started flashing custom kernels. Here's the situation, irrespective of the rom when I flash a custom kernel and switch off the phone to charge it up...the phone automatically restarts after sometime...there's no specific time at which it restarts but my hunch is that as soon as the phone reaches 100% charge it just reboots itself...I simply have no clue why this is happening...
Thinking that this could be a custom kernel/ rom issue, I went back to stock via the RUU route...this means everything is stock except for the recovery which is CWM...Guess what, the phone restarted again after being switched off for a while...I'm absolutely clueless..pls let me know if anyone else has had the same issue...
amirage said:
Hi all
This whole saga of auto reboot started when I started flashing custom kernels. Here's the situation, irrespective of the rom when I flash a custom kernel and switch off the phone to charge it up...the phone automatically restarts after sometime...there's no specific time at which it restarts but my hunch is that as soon as the phone reaches 100% charge it just reboots itself...I simply have no clue why this is happening...
Thinking that this could be a custom kernel/ rom issue, I went back to stock via the RUU route...this means everything is stock except for the recovery which is CWM...Guess what, the phone restarted again after being switched off for a while...I'm absolutely clueless..pls let me know if anyone else has had the same issue...
Click to expand...
Click to collapse
If you have done the revert-to-stock-RUU thingy and still the problem persists, i think it is a hardware defect my friend. revert to stock then ask your provider for repair or replacement if it is under warranty:cyclops:

[Q] Samsung Note N7100 stuck boot loop when unplug,but when charging loads the KitKat

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 !

[Q] Powering on after plugging charger even with stock KK bootloader

This has been driving me nuts for the longest time now: My P600 automatically powers on and starts to boot whenever I plug in the AC charger, meaning I can't charge it while it's powered off. The battery icon shows up for a second and then goes away, followed by the boot animation.
I'm aware this is a known issue when making the jump from 4.3 to 4.4.2 (that's when it started to happen anyways) and the recommended fix is to flash a stock KitKat ROM to get the KitKat bootloader, but I've tried that at least three times by now and the problem persists, which is really frustrating.
The first stock ROM I tried was the Mexico CNF1 version after fully wiping. I also ticked the "Phone Bootloader Update" option in Odin. Then I tried the Cellular South CND2, but that was also to no avail.
I don't know what to do now. I might as well try downgrading if nothing pops up. Could somebody help me out?
EDIT: Additional info, I'm using TWRP 2.6.3.3 to wipe system/data/cache/dalvik and Odin v3.09 if that helps any.

Reboot when USB Cable / Power Removed

I just received a replacement I747M. It was running android 4.4.2 I747MVLUFNK2. I rooted and flashed recovery. Even before I installed custom rom the phone would not boot with the stock firmware unless the phone is plugged in. When plugged in the phone will boot and work fine. Whenever the cable is removed phone automatically reboots, and will start boot looping. Return the cable and the phone works fine. I tried flashing back to stock with a sammobile image of the same firmware. I also tried installing a custom rom and experience the same issue. When I flashed back to stock firmware phone took forever to load and didn't seem to get past the splash screen after waiting for over 10 min, however it was able to boot without the power cable plugged in. Any advice here would be appreciated.
Thanks
Update: I have re-flashed to stock successfully but still experiencing the boot loop problem when not connected to a USB power source. There is no reboot in recovery or download mode. Again plugging the USB cable into the phone resumes normal boot and operation. Only when the cable is removed does the phone restart.
Update #2: Turns out it was an issue with the battery. Trying another battery seems to have solved the problem.
Rooting the I747MVLUFNK2
Northerntouch said:
I just received a replacement I747M. It was running android 4.4.2 I747MVLUFNK2. I rooted and flashed recovery. Even before I installed custom rom the phone would not boot with the stock firmware unless the phone is plugged in. When plugged in the phone will boot and work fine. Whenever the cable is removed phone automatically reboots, and will start boot looping. Return the cable and the phone works fine. I tried flashing back to stock with a sammobile image of the same firmware. I also tried installing a custom rom and experience the same issue. When I flashed back to stock firmware phone took forever to load and didn't seem to get past the splash screen after waiting for over 10 min, however it was able to boot without the power cable plugged in. Any advice here would be appreciated.
Thanks
Update: I have re-flashed to stock successfully but still experiencing the boot loop problem when not connected to a USB power source. There is no reboot in recovery or download mode. Again plugging the USB cable into the phone resumes normal boot and operation. Only when the cable is removed does the phone restart.
Update #2: Turns out it was an issue with the battery. Trying another battery seems to have solved the problem.
Click to expand...
Click to collapse
Hi there,
I have the same phone as you (I747MVLUFNK2) and can't find any Xda post on how to root it... How did you did it?
Thanks
Is your phone still under warranty? If not, flash a custom recovery and install supersu from recovery.

[Q] Boot loop only when plugged in to AC, and TWRP cannot wipe Data without crashing

I'm not sure how else to describe these two problems I have.
Just for reference, I am using Cyanide L RC 7.1 from here: http://forum.xda-developers.com/galaxy-s3-att/development/rom-cyanide-l-v1-android-5-0-2-t2980174,
and I am using TWRP 2.8.5.0 for d2att. I have a i747M on Rogers.
Problem #1: boot loop only when plugged into AC charging
In the past week, I found that my phone gets stuck in a boot loop only when the phone is plugged into the AC charger. It will boot up, show the Samsung logo, then the Cyanogenmod logo with Cid, then show the Cyanide L boot animation. Once the animation is over, the phone just reboots. This happens endlessly (I didn't let it go on for more than 20 minutes, I didn't have time to wait). However, if I let the phone boot while it's not plugged in, then it boots up just fine. It also boots up just fine if I am plugged in via USB as a data connection to a computer. This only happens when I am plugged in via AC.
I have tried different combinations of USB cable and USB AC adapters. Doesn't seem to make a difference. I thought maybe it's a battery thing and borrowed a colleague's battery (also i747M), no dice.
Thoughts on what's causing it to boot loop like this?
Problem #2: Cannot wipe Data in TWRP
I discovered this problem when I was trying to update to the latest version of Cyanide L RC 8. I booted into recovery (TWRP 2.8.5.0) and proceeded to dirty flash the ROM. First boot had terrible com.android.phone FCs every 5 seconds. So I booted back into recovery a couple more times to reflash, same problem. I decided to do a clean flash and do a factory wipe. That's when the problem began. Once it reads "wiping Data without erasing /data/media" (or words to that effect) TWRP would freeze (the animated progress bar at hte bottom stops moving) and the phone would just reboot. The phone then gets stuck in an endless boot loop. I tried this numerous times, same problem. Couldn't restore a NANdroid either because it wipes Data before restoring.
I had to boot up into Download mode to use Odin to flash a custom ROM back and work my way back to a NANdroid I had. Took me the better part of 2 days without a working phone to get back to my latest NANdroid backup.
Any ideas what causes this freeze + crash in TWRP? I have reflashed TWRP, but I'm too afraid to test it out, only to lose another 2 days like that.
Thanks
Maybe you'll have better luck with Philz Touch recovery for the d2lte?
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
daver68 said:
No luck with Philz Touch recovery. Tried that one, and also the latest TWRP. Seems to be the exact same behaviour with trying to wipe the Data partition.
I'm currently half way through using Odin to flash a stock TW 4.3 ROM to the phone. Hoping that this might solve my problems - perhaps something went awry during a recent ROM flashing, and I'm hoping that using Odin to nuke and pave my phone will fix it.
Fingers crossed...
Click to expand...
Click to collapse
If Odin doesn't get it try a wipe in the stock Samsung recovery.
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
audit13 said:
What bootloader is on your phone? Hopefully, it is 4.3 or newer and you are using the stock ROM from sammobile.com.
Click to expand...
Click to collapse
I'm on NF2, so definitely not an issue with the bootloops and bricking that might happen by being on 4.2 or earlier.
Flashing with Odin worked perfectly, and yes I used a ROM from sammobile.com. After that, I flashed SuperSU and TWRP 2.8.6.0 through Odin as well, before downloading another ROM to test wiping, flashing, more wiping, and more flashing. So far no crashes in TWRP when wiping data.
I haven't been able to re-produce the boot loop when plugged into AC, it's only been a day, but we'll see if that rears its head again.
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
daver68 said:
Well, it was a good 2 weeks, but now I'm back to having the same issues. This time I'm on a different ROM, but the two issues are the same.
I'm currently on S3Rx, 4.4 Touchwiz.
If plugged into AC (wall adapter), I get bootloops. If plugged into USB into a computer, it's fine.
Going into TWRP and doing anything with the /data partition causes the device to freeze up and then restart itself.
Is it possible that my storage hardware (the memory itself) might be failing?
Click to expand...
Click to collapse
The problem 1: you mentioned that the you are suffering with the problem of rebooting in the loop that occurs only when you use the AC wall outlet for charging. You must see in its rectifying circuitry detail. The problem may be there.
I eventually found a solution, though I don't know if it was a solution to the root problem.
My problem was that I was getting bootloops when plugged into AC charger. My solution, how ever random it seems, was simply to flash back to stock (via ODIN) to 4.4.2. Since then, my Problem 1 and Problem 2 were solved. This completely wiped everything on my phone (luckily I did a complete backup to my computer), but it also solved both of my problems.
It seemed the problem #1 was not caused by a bad charger or cable, as one might have thought.

Categories

Resources