Develop Bugs

Is it bricked? UnSolved AGAIN!

A strange thing happened and now I can't escape the bootloader screen. I lost my phone for a two days and when I found it it wouldn't come on. I connected it to a power cable and it immediately brought up the bootloader. The charge light won't come on but now the phone will power on without the power cable. Problem is it just brings up the bottloader and tries to install the rom image on the sd card. I put a new image on the card reinserted it and then allowed it to reflash. But it still just brings up the bootloader. Any advice?

Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,

orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.

Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.

orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Lennyz1988 said:
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Click to expand...
Click to collapse
Reflashed from PC, reboot to bootloader behavior does not change.
ultramag69 said:
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
Click to expand...
Click to collapse
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?

cyberscribe said:
Reflashed from PC, reboot to bootloader behavior does not change.
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
Click to expand...
Click to collapse
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1

this is certainly strange, could it be something with the SPL, i would look into that next if this doesnt help

cyberscribe said:
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
Click to expand...
Click to collapse
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.

stevedebi said:
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
Click to expand...
Click to collapse
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.

cyberscribe said:
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
Click to expand...
Click to collapse
Fixed! Stable as a rock

cyberscribe said:
Fixed! Stable as a rock
Click to expand...
Click to collapse
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!

cyberscribe said:
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
Click to expand...
Click to collapse
task 29 got me to the rom splash screen

cyberscribe said:
task 29 got me to the rom splash screen
Click to expand...
Click to collapse
reflash ROM from PC not SD. Reflashing after that from SD works. Hope I don't have to do this every time I change a battery!

I think I may be having the same or a similar issue as you cyberscribe. All of a sudden, I am getting restarted into the bootloader too.
I was using an older NRG 2.1 ROM (April-ish) and had to pull the battery after it froze up. Nothing new, it happens. The new part is that it would only restart into the bootloader screen. I thought it might be the older ROM, so I Task 29'ed and flashed NRG's newest 2.1 June 2nd ROM.
Successful boot and ROM setup while connected to USB. Unplugged USB, restarted phone, BOOTLOADER.
Plugged in USB, successful boot.
Unplugged USB, BOOTLOADER.
Plugged in wall outlet, successful boot.
Unplugged wall outlet, BOOTLOADER.
Obviously, I can conclude that there is an issue with trying to boot on battery power, or at least while not connected to a power source.
Anyone ever have this happen? Or have any ideas why this would be happening? I really don't want to have to find a power source every time I need to restart my phone, haha. I am still trying to troubleshoot further and will update if I find anything else worthwhile.

Also last night I tried restarting while plugged into car adapter, which as expected booted fine every time.
However, this morning I just restarted on battery power and it booted fine also. Nothing changed from last night to this posting. Honestly, I am completely at a loss as to why I am getting restarted into the boot loader seemingly at random. I thought I had it nailed down with the power source, but now that apparently is not the issue.
cyberscribe, are you still having issues? Anyone else ever have this problem? Any thoughts on a cause or solution? Or anything to help troubleshoot?

After the bootloader first pops up, there is a very quick screen that flashes, "Loading.... No image file", then goes back to the bootloader screen.
I have to discount my earlier theory that it will always boot when connected to any power source. Now it will only boot when connected via USB to the PC.
Looks like I am going to have to re-flash the stock ROM and then stock SPL and see if this solves the issue. Then, if not, I guess a warranty claim is in my near future.
I really wish we could have gotten some replies from smarter people than myself in this thread. haha

Finally flashed back everything to stock (SPL, radio, ROM) and still having the bootloader issue, looks like it is going to be a warranty claim after all.

Sounds more like a memory issue if it can't find the image file. If you both got your Rhodiums from the same carrier it could be a bad batch of phones...

Same issue on my tilt 2 just cropped up today. If I am reading the above correctly it sounds like 2 tilts and a t-mob rhodium having the issue, so different carriers. =/
Soft reset the handset and set it down, picked it back up and it was in bootloader. All attempts to get it out of bootloader (reflashing from sd, pc etc.) seem to complete just fine, but upon reboot dump into bootloader. May be a different problem than OP as I havent had any success in getting a boot after reflash.

Not sure if I am having the same problem, when I try to turn on it just comes up with the Touch pro 2 screen with the red text in the bottom left hand corner, I am using an energy Rom again from about April, I have tried re flashing but pc wont recognise/find phone, Wha acn be done?

[Q] Please help!! My Pro 2 keeps rebooting ..!

Dear all,
I flashed the ROM for my HTC Touch Pro 2 and installed a new one. the new ROM worked well for 2 days, until the night I charged my HTC on the laptop. It keeps rebooting and cannot load the system.
It can enter the color screen by pressing VOL - and Power, and I can still flash new ROM via both microSD card and ActiveSync under the color screen.
However, it still reboots as it enters the "Windows Mobile" screen.
I have tried hard reset and Task29 to wipe it before flashing ROM but both of them did not work.
I have tried different ROMs and I even successfully made a gold card in order to repair it, but it still reboots when loading the system when entering the screen "Windows Mobile" .
Does anyone know what's wrong with my phone ? I am so confused and thinking it is a problem with the hardware.
THX..!

I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.

doublen1 said:
I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.
Click to expand...
Click to collapse
Thank you doublen1, I plugged it on the wall socket and see whether it works or not tomorrow...

It does not work for me, but thank you anyway, haha！

Sorry, I tried. Maybe someone else will know.

Did I just BRICK my G Nexus?

So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.

Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom

My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..

i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).

i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk

The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.

Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?

i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium

And that might fix this charging bootloop? Because the LCD doesn't even turn off..

i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium

+1 for the new battery thought.

Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.

GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.

[Q] Tried to restore to stock w/odin and now no longer comes on

So received a phone with cyanogen 10-20120926-NIGHTLY-epicmtd on it and tried to restore to stock by following the post at http://forum.xda-developers.com/showthread.php?p=24694921
Everything was looking good and the phone was downloading the image.. after about 5 minutes or so, the screen went black and nothing was responding.. i tried tapping the screen and nothing.. finally I unplugged the cable and tried to redo everything and the phone no longer shows to be alive.. no led no screen image of the battery .. nothing.. computer does not even ding when i plug in the usb cable.. I cannot figure out what went wrong so i might have a permanent bricked phone...
Is there any resolution here to restore the phone to life???

Deep Ellum Dan said:
So received a phone with cyanogen 10-20120926-NIGHTLY-epicmtd on it and tried to restore to stock by following the post at http://forum.xda-developers.com/showthread.php?p=24694921
Everything was looking good and the phone was downloading the image.. after about 5 minutes or so, the screen went black and nothing was responding.. i tried tapping the screen and nothing.. finally I unplugged the cable and tried to redo everything and the phone no longer shows to be alive.. no led no screen image of the battery .. nothing.. computer does not even ding when i plug in the usb cable.. I cannot figure out what went wrong so i might have a permanent bricked phone...
Is there any resolution here to restore the phone to life???
Click to expand...
Click to collapse
You probably didn't have repartition checked. CM10 is MTD based, whereas stock is BML based.
Pull out the battery, connect the usb cable and boot into download mode again. (This should work to get you into download mode)
If that works, start Odin and be sure to check repartition and auto reboot before flashing the stock image.

[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 !