Hey all for some odd reason once I plug in the usb cable, the NT just reboots and starts bootlooping on cyanoboot screen while loading emmc. if i don't have the usb cable plugged in it will boot just fine with no bootloops whatsoever. have any of you encountered this problem? I had cm10 running on it and thought it was a bad flash, reflashing didn't help and restoring to a cm7 backup didn't do the trick either...
any ideas?
Can you charge with wall socket plug and usb?
demetris_I said:
Can you charge with wall socket plug and usb?
Click to expand...
Click to collapse
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
ShinnAsuka said:
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
Click to expand...
Click to collapse
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
demetris_I said:
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
Click to expand...
Click to collapse
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
ShinnAsuka said:
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
Click to expand...
Click to collapse
You are right, is a hardware problem. Go get a replacement.
so i got the replacement a week or so ago, and this replacement is now having the same problem... what in the world is going on. i am using your rom with the sgt7 enhancements. is it possible that the governor being on hotplug may be the problem?
EDIT: changed it back to the default ondemand governor... the problem is still there... how is this possible.
All this make me think is a bad flash.
Check your rom for any corruptions
demetris_I said:
All this make me think is a bad flash.
Check your rom for any corruptions
Click to expand...
Click to collapse
i restored to the 1.4.2 factory stock image that i made with cwm when i first got my replacement nook. same problem exists... i think it has something to do with the usb port getting bent or something...
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
demetris_I said:
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
Click to expand...
Click to collapse
thats the plan lol... the replacement nook was a pre-certified one. this time around they say they are going to send me a brand new one....
Same Problem on nook tablet cm 10.1 acclaim
I had the same problem with my tablet after I allowed the battery to drain completely while using it. I have to mention in my situation I had lost the original charger that came with my nook and I've been using a wall charger from my cell phone. When I had the stock barnes & noble nook tablet plugged in I noticed that the device would say that it's not charging even though it really was. It just took a longer time to charge. More than likely i had a voltage difference between the two devices. I too was stuck in that cyanoboot loop where there was not enough power to load the operating system and cyanboot wouldn't indicated if my battery was in fact charging. I had two solutions to this; I left my endless loop on overnight and in the morning low and behold i was booted into cyanogenmod. My other solution was to leave the device off for a long period of time and then try again. Hopefully this helps anyone else out in the future.
Related
When the Nook Tablet runs low on battery, it will turn off. Duh..
However, what happens when the battery gets too low? It goes into a "sleeping death" mode. I theorize this is caused by a lack of power management when the device is in sleeping condition.
Here is the related portion of my UART log.. Put in simple terms:wires hooked up internally to read what would be "BIOS" on a desktop or laptop.
Code:
fullcap0=0x2067 VFSOC=0x08f0 remcap=0x02e5
fullcap0=battery full capacity
VFSOC= Voltage for? System On a Chip- the value required for the device to operate
remcap= remaining capacity
These values are checked before the screen even turns on. So, if the Nook Tablet has a dead battery, the processor will initialize, then turn off before turning on the screen. The device appears to be totally dead.
I verified that a standard USB cable will charge the device even when it's completely off. I do not have a Barnes and Nobel cable currently, so I don't know if this applies.
The solution is to leave the device plugged in for 2 hours, then attempt to turn it on.
I hope this helps someone who would otherwise return a totally operational device.
I purposefully ran my nt down to see how low it would go and what happens when the battery runs out. I got it down to somewhere around 4% before it went black. I then plugged in the nt wall charger and tried turning it on. Nothing happened. I waited a few minutes and tried again. It was then flashing a message about critically low battery on the screen and to wait 15 minutes before trying again. It was probably 5-10 minutes later that it actually booted into android.
Just to clarify, it flashed red text on black screen when too low to power on fully.
nook tablet wont charge
I have the nook tablet and last night the battery died and brought up a screen that said "battery to low to power on, please connect your charger" so I connected the nook charger and the little "n" on the cable lit up, but the screen just keeps flashing (once a minute or so without me touching it) the battery to low message. Everytime the message pops up the "n" on the charger changes color from Orange to green. Left it to charge all night and this morning more of the same. Any thoughts? Thanks in advance.
16GB
8GB SD card
Rooted
Purchased at christmas
My friend's nook tablet had the same problem.
http://forum.xda-developers.com/showthread.php?p=23836518#post23836518
Even after leaving it plugged up with the nook charger over night, it would not boot. I guess I should have tried a standard micro usb plug.
I ran into the same problem a couple of daya earlier. I tried a standard mini usb charger but my tablet woulbnt boot. Then I tried b&n charger and cable. After around 20 minutes I found it booted and charging.
I noted that standerd mini-usb chargers outputs ampere are far lower than bn chargers. For example nokia charger : 1200mA, sony erricsson : 850 mA and b&n charger : 1.9 A. Does it have to do anything with this?
Sent from my Nook Tablet using XDA
Thanks for the responses. I contacted Barnes and noble last night and they seem to think that it is the cable. They are sending a new one. I will update when it comes in. Thanks again.
mamnun said:
I ran into the same problem a couple of daya earlier. I tried a standard mini usb charger but my tablet woulbnt boot. Then I tried b&n charger and cable. After around 20 minutes I found it booted and charging.
I noted that standerd mini-usb chargers outputs ampere are far lower than bn chargers. For example nokia charger : 1200mA, sony erricsson : 850 mA and b&n charger : 1.9 A. Does it have to do anything with this?
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
The B&N cables are known to stop working after a while. Guess its built a little on the cheap side and the end that plugs into the nook is the problem as it is to heavy and so it bends the plug and causing it to snap off on the inside which of course is a bad thing. Some of the pins snap and thus causes problems.
My nook is doing the same thing. Thing is that im on my second B&N cord and my phone cord which usually charges it wont charge it either. The screen just say battery too low.. wait 15 minutes.
I'm wondering if making a bootable sd card will solve the problem.
Ended up taking mine to the b&n store after the new cable didn't help. They ended up replacing my NT all together.
bustedukulele said:
My nook is doing the same thing. Thing is that im on my second B&N cord and my phone cord which usually charges it wont charge it either. The screen just say battery too low.. wait 15 minutes.
I'm wondering if making a bootable sd card will solve the problem.
Click to expand...
Click to collapse
A regular micro sd cable will not charge the nook. The receptacles for it are set in deeper than normal and thus the reason for the extended microsd pins on the nook tablet charger.
Cubanluke88 said:
A regular micro sd cable will not charge the nook. The receptacles for it are set in deeper than normal and thus the reason for the extended microsd pins on the nook tablet charger.
Click to expand...
Click to collapse
I guess my question is if I make a bootable SD card is there a way for me to force my nook to restart through the computer?
bustedukulele said:
is there a way for me to force my nook to restart through the computer?
Click to expand...
Click to collapse
sorry for asking a question about a question... is your adb running ?
old_fart said:
sorry for asking a question about a question... is your adb running ?
Click to expand...
Click to collapse
No, I have not set up ADB on my computer. If I do so, can I force my nook to reboot using ADB?
Code:
adb reboot
Should do the trick.
Just wanted to post an update.... i made a bootable SD card and inserted it in my nook... one push of the power button had clockwork recovery up.
Once i had a ROM installed the battery read that it was full.
Thanks for your replies. I'm glad i don't have to replace it
Sent from my ADR6400L using XDA
Rooted using Indirect's sd method, installed CM7 to internal using clockwork mod. I installed CM7 around tuesday, and nothing happened for a while. Then, I woke up this morning to try and do stuff with it and it booted up fine. My touchscreen was acting wonky (a hardware problem) so I turned it off to reboot, and when I went to turn it back on it got to the CM7 splash, and turned off and rebooted itself. It kept doing that for a while, and I let the battery run out. I then plugged it into my PC and it gets to the "N" screen (where it says powered by adobe reader technology or whatever) and it reboots. It has not gotten past that screen. It makes my computer spaz out by starting the "Found New Hardware" wizard for "OMAP4430". I have no idea what that is. My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in). Any help would be appreciated.
TL;DR My nook is in what I think is a bootloop, I can't access the internal storage from a computer, omfgwtfbbq.
EDIT: I have taken my SDcard out, that was suggested earlier. Could this possibly have something to do with the fact that I cleared all my SDcard contents from the CM7 options menu? I also cannot access my nook or SDcard by plugging it into my computer, I suspect that has something to do with the unplugging and plugging back in sound mentioned above.
off course will do this
My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in
Click to expand...
Click to collapse
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
lavero.burgos said:
off course will do this
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
Click to expand...
Click to collapse
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Maggot226 said:
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Click to expand...
Click to collapse
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
lavero.burgos said:
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
Click to expand...
Click to collapse
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
It's been charging, from a wall charger, with the sd card out, for around 4 hours now and it's still doing the loop thing.
Maggot226 said:
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
Click to expand...
Click to collapse
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
ckevinwelch said:
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
Click to expand...
Click to collapse
Leave it alone as in unplug it from the charger? Or keep it charging?
Maggot226 said:
Leave it alone as in unplug it from the charger? Or keep it charging?
Click to expand...
Click to collapse
Plugged in.
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Maggot226 said:
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Click to expand...
Click to collapse
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
ckevinwelch said:
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
Click to expand...
Click to collapse
It would turn on, but yes, it would not boot to the menu. It wouldn't get past the "N" screen as stated in the OP. I was plugged into the wall charger and using the cable I received with the Nook. I've had it plugged into the computer for around a half hour, and I have attempted to turn it on with no success. I'm really wondering what this "OMAP4430" thing is. My computer is wanting to find software for it, the "Found New Hardware" wizard starts up every time I plug my nook in.
It's fixed, I let the battery run completely out, booted from CWM and wiped everything. I reinstalled CM7 and it's working like a charm. Mods can lock this thread.
I bought three nook tablets, put NT-CWM-SD on a sd card then installed sgt7-10-20121209-meghd00t-acclaim on all three.
All three ran great installed many apps on each one. Once all three battery drained none of the tablets turn back on. The N on the usb charger is green and has been plugged in for 24 hours.
One known/reported issue with many recent CM10 builds is the NT while asleep will not detect USB cable insertion and kick into charging mode; one would have to wake it up with the power button or "N" button for it to go into charging mode (afterward one then put it back to sleep with power button and it will stay in charging mode).
I suspect your problem might have the same underlying root cause.
The only "shot in the dark" thing I can suggest trying is to stick in a bootable SD card (e.g., your CWM SDcard), then insert the powered USB cable -- hopefully with luck that would jolt the NT to boot up and go into charging mode. Please provide feedback on whether this works.
I would also suggest that you report this on the SGT7 development and CM10 support threads -- so that other CM10 users know not to ever let their NT battery completely drain.
If it's anything like mine you cannot plug it in to charge while it's in standby. The "n" turns green right away. I have to "wake it up" and then it starts to take charge. ("n" turns orange)
Edit: LOL! Digixmax posted while I was writing!
asawi said:
...
Edit: LOL! Digixmax posted while I was writing!
Click to expand...
Click to collapse
Great minds think alike
Joke aside, I am now really concerned -- previously it had not occurred to me that the problem the OP reported is a logical and fatal corollary of the problem you/I/others had seen/reported.
If the bootable cwm doesn't do it, try making a bootable cm7 (this rom didn't have the bug)
NT no longer charging or waking up
baberswallet said:
I bought three nook tablets, put NT-CWM-SD on a sd card then installed sgt7-10-20121209-meghd00t-acclaim on all three.
All three ran great installed many apps on each one. Once all three battery drained none of the tablets turn back on. The N on the usb charger is green and has been plugged in for 24 hours.
Click to expand...
Click to collapse
I experienced this type of problem a few days ago on my NT. I replaced my charging cable and it started working fine.
nigelshea said:
I experienced this type of problem a few days ago on my NT. I replaced my charging cable and it started working fine.
Click to expand...
Click to collapse
Could it maybe be that you need to force a reboot or reset or whatever by holding the PowerOn and N keys at the same time? For a 20 second count on my NT 16GB.
It would be great to hear back from the OP if any of the above suggestion works.
Hello everyone,
I have an SGP 5.0 that I've been using for sometime. Everyday I let it charge overnight and usually in the morning its warm but full. Today it was burning hot and the device keep on boot loading and failing. I've tried going into recovery mode but it fails completely, I just keep going into the boot looping. Download mode works but that's about it. The device was working yesterday with no problems with the rom/kernel listed in my signature.
If I disconnect the power cable and leave it disconnected it will NOT boot. Not even into download mode. Only when I plug in power and leave it for a minute will it try to boot.
I've tried writing the rom and kernel (http://forum.xda-developers.com/showthread.php?t=1863004) but it dies before it ever finishes (By die I mean the battery runs out). I've pushed only the kernel (Entropy's DailyDriver) and it does work but its still boot looping.
I've stopped the above and the device is getting hot. I presume if left without a kernel/rom that it will recharge and I can continue what I'm doing? (The download logo stays on for about a minute and disappears and appears a minute later repeatedly. )
Just so you know, when you flash CM10 (Paranoid, or just Cyan) that these flashes provide a new kernel, hence that you do not still use the daily driver from Gingerbread. You'll probably notice the different in CWM changes from five to version six.
With that said, it might be best if you tried adjusting your voltage, I've had the same issues with an over heated device with Gingerbread / CM10 modifications which a member of the community did offer some assistance ( Check Page 75 on Cyan Thread)
Wouldn't hurt starting from scratch, flashing the stock, and working your way back up. Only suggesting this because I'm unsure of other factors that could cause this.
I forgot about that since I went from PM 4 to PM 4.1. That's what my goal was by starting with galaxy_player_2.3.6.tar.md5 and working up but I got nothing since the device dies, from no power?, when I try to write a rom. I guess I have no choice but to charge the device and hope that after many boot loops, the battery have enough juice for one run? That being said I've just opened the device and figured out how to remove the battery.
Google isn't helping with batteries and a quick search of ebay shows that everyone is happy with their device. Is there any place you recommend to get a new or semi-new battery for the thing?
By Write your referring to flashing.
Have you been able to get into the download mode? What do you also mean by recovery fails?
Yes. Download mode works fine. As I've stated the device will stay on for just one minute before it dies, not enough time to flash on a new rom. If I pull the plug, regardless of if I'm flashing, it will die. By die I meant that the device shuts off. The screen is black and the backlighting on the buttons is off.
I've held the power + volume up button on boot and it kicks into download mode.
I've left the device plugged it and its generating a lot of heat, with battery inside.
UnsignedZero said:
Yes. Download mode works fine. As I've stated the device will stay on for just one minute before it dies, not enough time to flash on a new rom. If I pull the plug, regardless of if I'm flashing, it will die. By die I meant that the device shuts off. The screen is black and the backlighting on the buttons is off.
I've held the power + volume up button on boot and it kicks into download mode.
I've left the device plugged it and its generating a lot of heat, with battery inside.
Click to expand...
Click to collapse
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
bmxer4130 said:
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
Click to expand...
Click to collapse
Mine also shows the charging screen then bootloops. If I powerdown my GP5 then plug in the cable, everything works fine. So for me it only performs reboots if I powerdown the device while it is plugged in.
bmxer4130 said:
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
Click to expand...
Click to collapse
I haven't had any issues with any cables used. I've switched to stock cable + stock charger yesterday and nothing there but a boot loop. I wish there was a place to buy a new battery just to check.
The title says it all. My brothers Note 2 will only boot past the Galaxy Note 2 boot screen if it is connected to the charger. It doesn't matter if it is a USB or wall charge. If the phone is connected to a power source it boots into the system fine, however, once you remove it from the power source it turns off. I was wondering if it could be a bad battery but the charge is showing it at almost 80%. Has anyone ran into something like this before? If I try to boot the phone without it being connected, it sits at the Note 2 screen for about 15 seconds and then shuts itself off.
I'm not really sure but it sounds like the internals of the battery are closing up (shorting). Are you able to get another battery to test and see if it is the battery?
Note 2 - Boots , Loops, No SDS Detected as per eMMC checker on play store
chrisjm00 said:
The title says it all. My brothers Note 2 will only boot past the Galaxy Note 2 boot screen if it is connected to the charger. It doesn't matter if it is a USB or wall charge. If the phone is connected to a power source it boots into the system fine, however, once you remove it from the power source it turns off. I was wondering if it could be a bad battery but the charge is showing it at almost 80%. Has anyone ran into something like this before? If I try to boot the phone without it being connected, it sits at the Note 2 screen for about 15 seconds and then shuts itself off.
Click to expand...
Click to collapse
Having same issues
Seems it hardware plus software issue.
Running 4.1.1 Jelly Bean
Happened after installing few games .
Goes in constant boot loop
Can start by attaching power cord only to socket.
With USB attached to Laptop .. still goes in loop
Powerbank is workaround.
Seems to reboot when saving to sd card ..
Will keep posted
technoracy said:
Having same issues
Seems it hardware plus software issue.
Running 4.1.1 Jelly Bean
Happened after installing few games .
Goes in constant boot loop
Can start by attaching power cord only to socket.
With USB attached to Laptop .. still goes in loop
Powerbank is workaround.
Seems to reboot when saving to sd card ..
Will keep posted
Click to expand...
Click to collapse
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
chrisjm00 said:
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
Click to expand...
Click to collapse
I second this. My phone went down Saturday. Thought it was something with CyanogenMod 11, but flashing back to stock did nothing. Replaced the battery, haven't had any problems since.
chrisjm00 said:
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
Click to expand...
Click to collapse
Thats first thing i did .. checked different battery ..
Battery is fine .. its not battery issue .. atleast in my case ..
i checked for SDS .. my phone has no SDS insane bug either .. though symptoms were same .
I have backup phone, using it.
I showed for mobile repair.
Said he will solve it .
So plan to take tomorrow.
I can root and all..
But after this booting dont want to brick it ..
So plan to do it via the mobile repair shop
Had same issue. Solved after replace the battery.
I have the same issue right now as well. I was on stock for awhile and used casual one click method, switched between a few roms. Than it started happening after that. So I flashed back to stock on odin and still have that issue. Havent figured it out yet.
Sent from my SCH-I605 using XDA Free mobile app
Boot cycle loop
DX.Deception said:
I'm not really sure but it sounds like the internals of the battery are closing up (shorting). Are you able to get another battery to test and see if it is the battery?
Click to expand...
Click to collapse
I have had this issue and replacing the battery did the trick. I was having issues with the battery beforehand. once the battery showed as being at 17% the phone would start the reboot cycle and not fully boot until it was plugged in.
Have same problem here.....All these started when I replaced my bulge battery. New battery doesn't hold power below 20%. Phone goes off in boot cycle until plugged in a charger
Try to boot on USB/PC data connection
When connected t PC-system will boot to a point. PC indicates new connection then looses it and Note 2 returns to flash screen. Problem start when using corporate email and encrypted data. Works w/o error connected to wall charger. Disconnect crashes system. Flashes screen forever. No diagnostics. Did all SW reboots. Doubt battery, but will try.
suntreepops said:
When connected t PC-system will boot to a point. PC indicates new connection then looses it and Note 2 returns to flash screen. Problem start when using corporate email and encrypted data. Works w/o error connected to wall charger. Disconnect crashes system. Flashes screen forever. No diagnostics. Did all SW reboots. Doubt battery, but will try.
Click to expand...
Click to collapse
Did you ever test a new battery/figure it out?
Mine is doing the same thing I think. I only boots if connected to a wall charger. If connected to PC with USB it will boot to the [T-Mobile in my case] boot screen, connect to PC for a split second (long enough to make the connection sound in windows, then I can't find it) and it stays on that screen. Without being connected to either, or after pulling plug, it turns off.
Same problem here with mine
can't be just the battery because it will stay on w/o charger when in download/recovery mode or if it gets stuck on the Verizon screen.
___________________________
Verizon Galaxy Note II
model SCH-I605
android 4.4.2
kernel 3.0.31
build KOT49H.I605VRUFND7
hardware version I605.06
I'm having the same issue but i can boot into recovery without the charger.