So, yesterday afternoon i plugged in my phone to charge (about 11 PM) and left it for the whole night. I also have to add that Ive been running a mobile AP on it for the whole time. Today morning, I wake up and its crazy hot. I quickly DC it from charging, remove the back cover and let it be for a sec. I unlock it, it runs for few seconds normally and BAM, background behind icons is black and it froze up. I remove the battery to perform a hard reset of sorts and then the worst thing happens... Phone is stuck on boot Samsung logo. I turn it off again, hoping for a quick fix but it accomplishes NOTHING. I plug it into the charger and battery icon is visible but the circle on it is stuck and nothing seems to be happening.
Now I go into recovery mode that's working - surprise! And delete cache and dalvik cache. Nothing. I go back delete those things again and battery stats too this time. Nothing. I go back and do a factory reset... Nothing. Yeah.
So, imo since recovery is working it can't be a burned CPU/RAM right? Most likely (or hopefully) it's just the software that died? Im in the process of downloading a ROM and I will put it on my ext. SD card along with super-wipe that I will run but I was wondering - are there any good ROMs (or something else that might save my ass) that can be installed using Odin?
Yeah, it seems it was the case. Just installed ROM from my ext. SD and it's booted up which is very nice. Seems that it overheated and somehow killed my everything. Which is weird and anyone cares to help me explain this?
I recently flashed CM10 onto my Nook Tablet - thanks to all those who helped!!
Everything was working perfectly for about 1 week, then the kids ran the battery all the way down. I plugged it in to charge it, and it started doing funny things. As soon as I plugged it in, it would turn on to the initial screen with the sliver N, then it would turn right back off (presumably because the battery was drained). It just kept repeating this. I didn't do anything because I figure that once it charged everything would be back to normal. However, I turned it on the next morning and it started walking me through B&N's initial setup. My CM10 is gone and I'm back to stock OS. What happened, and how do I prevent it from happening again?
(I was surprised that the stock OS was even still there.)
I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.
asawi said:
I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.
Click to expand...
Click to collapse
Is there a way to stop the table from automatically trying to boot when it's plugged it - maybe this will correct the problem when trying to charge a fully-drained battery. Is there any reason I shouldn't do this (assuming it's possible)?
So, I recently received my dad's old Galaxy S2. Stock JB, unrooted. My dad used to charge the phone in his car and during office time, whereas I've always been an "overnight" charger (keep this in mind as it's important). So, here's what happened -
1. I woke up really late the next day and realised that the alarm clock hadn't rung. checked out the phone beside me to see that it was really hot. The phone had shut down by itself. I turned it on and it functioned normally. That day I rooted the phone using PhilZ (mainly for the adfree app)
2. I didn't do an overnight charge for the next night cause my dad told me that "it ruins the battery". And the phone was fine the next morning. I changed to dorimanx's kernel for all the wonderful extra features.
3. That night, I decided to try overnight charging once again. Woke up the next day to a shock. It was 10am! No alarm, hot phone. I thought the phone had just shut down again, so i tried to switch it on. It showed the samsung boot screen and then the pretty "dorimanx" screen, but then.. stuck. the device wasn't starting, but recovery was working. I removed the battery, I wiped the cache, I installed another kernel (siyah)... nothing worked. FInally, I decided to try flashing a new rom. Downloaded SlimKat and flashed it through CWM. The device then booted up and has been working quite normally now. And I like SlimKat much more than stock! But that's not the point. The point is, I'm scared of charging overnight again.
None of my previous phones have faced this problem. I'm just a noob, but I have a theory. I noticed that the phone, once it reaches 100%, doesn't give any indication that it has stopped charging (like most phones do). The charging icon on the battery still shows. Does this mean that the phone is still trying to charge even after the full battery, which is causing the overheating and shutdown of the phone? I'm still confused regarding why it refused to boot up.
Is this a battery/device problem, or was this merely due to some fault in the stock rom?
You were actually stock in a boot loop (which has happened to me before(hated it). Be glad that it didntt freeze at the Samsung logo. Because then you couldn't get into the CWM.
I am not entirely sure what is wrong with your phones battery, because I have never had this problem myself, so I am sorry I can help you with that. Try going to settings/battery and see if you can turn sound on for the battery from there. :thumbup:
Sent from my SGH-T959V
Given the age of the battery it's likely to be the battery, so replace that first. Could also be the USB board, but cross that bridge when you come to it (try the easier option first).
Your old man is wrong about charging - constant charging/discharging like he did for however long is far more likely to reduce a battery's useful life than a simple use the phone during the day charge once overnight arrangement.
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
DentalAppointment said:
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
Click to expand...
Click to collapse
So, if you disconnect the USB cable, remove and reinsert the battery (also, try another battery), then press and hold POWER+VOL DN for a few seconds are you able to get into HBoot? If not, it is likely borked, but not because of flashing a ROM, it was probably just it's time to go...
got it working
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
DentalAppointment said:
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
Click to expand...
Click to collapse
I had some unfortunate nastiness happen to my Rezound a while back which prompted me to go out and get an M8, but I did eventually get the Rezound 99% functional again.
First off, cell phones in general rely on something called NAND memory for all mass storage. It's decently quick stuff, but not the most reliable storage medium in the known universe. Basically, it slowly dies with use. NAND only has so many read/erase/write cycles before it begins to degrade. This can lead to very quirky corruptions in the partitions, and that's kind of what it sounds like has happened to your Rezound. The fix that got mine back to working order was a complete stock RUU restoration followed by a "factory reset" through Hboot. That will wipe and rewrite all of your partitions. Then flash your custom recovery, ROM, and kernel.
As for flashing ROM's and kernels in the right order, you want to flash the ROM and then the kernel. A lot of devs recommend flashing the ROM, then booting it up, then flashing a custom kernel, however, if you know you've got a working combination of ROM and kernel, there is no reason you can't just flash the ROM and kernel (in that order) at the same time in recovery.
Alright, I've got a hum-dinger here. I've been running CM12 for some time now, I started noticing much more frequent blue screens due to modem crashes so I wiped and reinstalled the ROM. Now I'm getting a really strange problem where so long as the phone is plugged in to something (charger, or computer) I can use the phone completely normally. The moment I unplug I get 1 of 2 scenarios:
1: the screen immediately goes blank (no power down sequence, no blue screen) and I'm kicked back to LG splash screen which then proceeds to go to the power off state. Attempting to power on again gets as far as the CM12 boot animation and then screen goes blank again. I've tried powering on several times from the stage only to get part way through the boot animation and then kicked back to the black screen.
2: Screen does not immediately go blank, I can swim around the home screens scroll to an app, even start an app - but about 10 seconds into the app the screen suddenly goes blank and I'm back at scenario 1.
The only way to get the phone past the ROM boot animation is to plug it back into something....but then I can't unplug lest I end up back at scenario 1.
The shutdown sequence almost looks like I tanked the battery, but going into the recovery (TWRP) I can see that I actually have a good 98% left.
Thinking CM12 had some issues, I tried another Lollipop ROM (blisspop) and I got the exact same behavior. Thinking Lollipop was still half-baked for this LG I reverted back to a KitKat ROM (CM11) and I got....the exact same behavior.
I tried wiping all the data, system, cache, dalvik, partitions and reinstalling completely from scratch -- but I get the exact same problem. The only thing I haven't tried yet is LGNPST back to 100% stock, but I'm struggling to see what difference that would make as I'm wiping out everything except the recovery between tries.
Anybody have any ideas, thoughts, comments? I'm grasping at straws here.....
You could always try to load the stock rom back on the phone to see if that does anything. Another thing you can try is to power off the phone, plug it up to the charger and see if it charges overnight, however I have a sneaking suspicion that the battery is toast.
Kilogrm, I've left it charging overnight and and am able to carry it around all day without issue doing the occasional glance at the time, but if I try to do anything of significance I will end up at a black screen again, so I'm rather inclined to believe it isn't the battery. I do have a replacement battery that I bought a while back that I never got around to installing....so I could try that.
I'm guessing that if I'm going to install a stock ROM I might as well just LGNPST back to stock....thoughts?
Ok well I used LGNPST to go back to JellyBean Stock, and I got the exact same behavior. I'm thinking it might be a hardware problem, but not sure what.
Well, it was definitely a hardware problem. I opened up the phone and took a look at the rigid-flex board that LG used to connect to the micro-usb jack and I noticed that one of the footprints was missing a component. I quick look around showed that a small(looked like 0402 size) diode had somehow sheared off at the solder joint and was rolling around in the case. I soldered it back on, replaced the battery with the new one I had gotten and closed the phone up. Everything works like a charm again. Now I just have to go back through the root/freeg/rom process again because I flashed all the way back to at&t ROM.
Remove the back cover, remove tiny screws on bottom and pop the cover off. There are another two tiny screws holding the battery connector on the pcb. Unscrew the tiny screws and unplug the battery, then plug in to power. Then unplug, plug battery in and plug power in. Let it charge. This added 8 extra hours on my battery from 15 hours to 24 hours. It appears to be going up too if u drain it to 0 dead and charge to 100 and unplug. Do it over and over again forever and the battery will slowly repair the damage.