Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
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.
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
you cant get into to recovery either? or fastboot mode?
k786 said:
you cant get into to recovery either? or fastboot mode?
Click to expand...
Click to collapse
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
Then I am afraid you're hard bricked pal
Sent from my GNexus
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
what about fastboot mode?
Same
AdmiralAqbar said:
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
Click to expand...
Click to collapse
I'm having a similar issue. I wanted to flash the memory so i relocked the phone using the wugkit, then unlocked and rooted. For some reason, it wouldn't load a new rom. I kept getting the triangle exclamation point android graphic. I pulled the battery and that was it. Black screen. Won't turn on. A cpl of times, it was almost recognized by the computer via USB, but just kept failing. This sucks.
cyberelli said:
just a thought: are you sure it's charged up enough to boot? i know i've mistakenly thought my phone was messed up when the battery was just dead
Click to expand...
Click to collapse
Yes the battery is charged. Occassionally, when I plug it into the computer, it makes the new device notification and then fails over and over again. I keep trying to get a glimpse of a lock so i can adb it.
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.
OK all I am sincerely reaching out as I am out of ideas. Here is the situation...
Issue : Last evening, running most recent Liquid Smooth 4.4 (Superb ROM, I don't feel this is really at fault just relevant and thorough), I had been doing some heavy tethering when I picked up my beast and stepped out for a smoke. As I am reading up on moto360's 2 1/2 hour sellout I get a random reboot. Eh, no biggy ... it does happen. (Not often, or at all to speak of in my case just stating.) Right after reboot I hit the power button to make a forced boot cycle and it rebooted again before I pressed anything on screen!
Now SOMETIMES I will boot past the initial "NOTE II" splash (NOT often at all ... usually get reboots, splash hangs, or the phone simply turns off on its own from here) If it does make it past Note II splash it will reboot, hang, or simply turn off from here as well.
Steps Taken: I firstly, attempted a restore... no dice. I attempted a fresh install (TW, SlimRom, and DU) ... no dice dos. OK hmmmm
Now to all mighty ODIN (L900VPUCNE2_L900SPTCNE2_1561791_REV04) .... NO FREAKING DICE!!! WTF?!?!? I additionally attempted MC2_STOCK_with_COUNT_RESET-20130511 ... no bueno!
I still have access to Recovery and Download soooooooo ... I lay down at the mercy of you the community!!!
Thanks in advance and if you need more info PLEASE don't be shy!
Same issue here!!!
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Exact same thing
I've been running the latest nightlies of OmniRom. And yesterday, out of the blue, random reset then bootloop. No luck with anything, recovery, odin, etc.
Did Sprint deliberately brick our phones?
I'll try the odin to stock to see if I get any luck there. But if anyone else figures it out, it'd be nice to know the fix. Thanks!
No luck going back to stock. It's dead Jim.
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
If my case, my phone would boot loop around the splash screen. on the battery power only. I could go into recovery and download mode with no issues and stay on for hours. If I connected it to, say a PC, it would boot, but would random shut off within five minutes. But if I plugged into the wall charger, it would boot with no problems. Stay on for hours. If I plugged it from the charger, it would immediately shut off and try rebooting which it would just boot loop.
Luckily, the batteries are pretty cheap at $10 to $20 on Amazon. I went with the Anker for $15 to get me by till I get my next phone, which will probably be October; I'm heavily learning towards the Note 4
Replace the battery
I had the exact same issues. I ended up buying a $10 battery on amazon and it solved the problem. I did go through all the flashing, odin to stock, etc. All was pretty good when plugged in to a good power source. It took me about 4 hours of trial, error, reflashing, etc before I realized it was probably a battery issue. The new battery has solved the problem.
lovekeiiy said:
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
Click to expand...
Click to collapse
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
crackrock360 said:
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Click to expand...
Click to collapse
I couldn't flash any of counter reset rom through anything but TWP so i have to boot into download and update away from Philz. AFTER the recovery update I started making headway. but couldn't ever seem to make it past boot no matter how much batter is charged. I was beginning to think it was something that died on the inside (heh...heh)
After reading through some of these greatly appreciated replies I am going to plug her up to the wall and try the ne2 counter reset again(12:58 am). ... AND I may go throw some cash at a battery juuuuuust in case. (I do tether 100gigs daily sooooooo it does make sense that it could have burnted up lmao!)
UPDATE 1:25AM : I did as advised and it does seem battery has taken a dive! hmmm so weird! It still shows having power and charging. But after being plugged into wall I made it booted into a fresh ODIN install!!! (keep in mind that AS SOON AS odin gave me a pass I switched to Wall outlet!) I have even performed a power cycle to confirm it wasn't a fluke! I will indeed be out first thing in the morn to get a new battery!
AGAIN I can not thank you all enough ... I would have never thought of that. (you would think it would be one of the first things but eh you live and learn.)
I will update with any new progress!
cheers!
crackrock360 said:
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
Click to expand...
Click to collapse
'When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.' EXACT CIRCUMSTANCES AS I SIR!!!
Mine does the same and hangs .... right? HIt the power button and as soon as it lights up to start to boot then plug in the power cable. (the freezing while off and charging is a known bug in at least two roms i believe)
Congrats Rubledub!
As for me, I'm still screwed. Invested $40 in a battery (had to have it today, couldn't wait on shipping)
With the new battery fully charged I still have the same result!
crackrock360 said:
,,, Do the batteries go bad instantly?
Click to expand...
Click to collapse
There were probably signs of the battery going bad, but misread. But in my experience, it went to total crap instantly.
The signs of going bad were shorter battery life, getting stuck/freezing when trying to charge the phone when off (there's that battery graphic that shows up). Unfortunately, I did all kids of other stuff before I really figured it out, and looks like a messed up my modem and now cannot connect to 3G. Kind of irritating, but luckily, I spend 75% of my time in LTE areas. Just got to ride this out till the Note 4 is released.
Here is thread of when I was having trouble: linky/URL]. It's a lot of me trying slightly different things with no changes in results. Plus, I was a buddy's house who was in a 3G only area. The worse part, my phone did this the day before I left to spend the weekend five hundred miles away from home at a friend's house to visit.
sloanmeister said:
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Click to expand...
Click to collapse
Just chiming in to say this worked for me! Thanks!
Joelski144 said:
Just chiming in to say this worked for me! Thanks!
Click to expand...
Click to collapse
Oh i agree! Thats is what had me so baffled ... Not even the odin installs were breathing life, and Odin ALWAYS works for me. If Odin isnt getting it done and neither is a battery then your problem may be far more serious???
Weird Recovery Lag and bootlooping after CM12 update
Hey guys,
I came across this thread and the issues I'm having sound so what similar, so I thought you might be able to help.
I have two Samsung Note 2(l900) and running on cm12 as of yesterday morning. I installed the new nightly manually on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
I'm back on stock rom and the device is working great but takes forever to get into manual recovery which I believe is why it is having issues booting Cm 12