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)?
Hello everyone.
After several hours of googling and going through tons of pages here on xda I decided to make this post.
First, let me explain when the problem started:
The issue
Yestarday I was playing candy crush when suddenly the game started to get "laggy". I didn't think of it, exit the game and left my phone on the table. A few hours later I wanted to use it again only to find the small hard drive icon on the top saying something about Memory almost full. I clicked it and it took me to "All installed programs". I saw that it had used 1.9 gb of the total 2gb and only 20-40 mb were free. I started immediately to uninstall apps that I no longer use to see if this could help. It did for a few seconds but the memory got filled fast again.
This is when I started to search the net for solutions. The first post I read was to delete some log files so i did that. But it didn't change a thing. I thought to myself that I should make a backup of my stuff so it wouldn't go lost if I had to wipe the phone. But before I got to it my phone shut down. Now, when I turned it back on it would just start Media Scan and shortly after shut down. This is where I am now.
I am running stock ROM (have never rooted before).
What I have tried
I found the stock ROM (4.1.2 I think) and I flashed it with Odin thinking this would stop my phone from restarting. It did not.
I have tried to clear cache from Recovery Mode several times with no effect.
I have tried to wipe the phone from Recovery Mode but when I am half way through the setup process of setting up the phone for first use, it shuts down.
My battery also drops in power after the shutdown happens, so in this very moment I am waiting for the battery to charge fully so I can try to calibrate.
Please let me know if you need some additional information and I will happily provide what I can.
Thanks in advance!
You have flash stock and it still shuts down? Hardware problem. Battery old? Try with charger plugged in. Flashing stock makes it like new so there should be no faults. Id say battery is about had it. What firmware did you flash and were from?
My phone (and battery) is almost 1 year old so im still under warrenty if something fails. I just don't want to hand it in and wait weeks to get it back if I can handle it myself
Yes I flashed with stock ROM from samsung-updates.com/device/?id=GT-I9100 so it should be good.
It makes no difference if the charger is plugged or not (which I find odd cause shouldn't it be able to keep awake while on alternating current?).
At the time typing this my phone is online and I am currently backing up photos (yay!!!). What I did was to not type in PIN code so maybe the sim card is the trouble (also 1 year old). I will report back when everything is backed up.
Update:
4 seconds after entering the PIN code the phone shuts down. Also it plays about 10 silent "clicks". Can't hear if its from the phone or from the speaker.
Update2:
Alright so I tried inserting another sim card that I have which has no pin code. The phone boots (but only when plugged) but shuts down after statup, exactly the same place/ after the same time as when I use the other SIM and enter the code.
I have had it online for 5 minutes now without typing the pin so my guess is that it's some setting it loads with the sim that makes it crash (but its a wild guess).
It's also worth noting that it doesen't drop in battery capacity when it shuts down ATM.
Id still say battery problem but could be wrong.
I see some sort of flicker on the screen just before it shuts down. I don't know if this could help someone to address the problem.
For the full memory issue i solved wiping log files in the "/data/log" dir, i had almost 1000 log files, 1 MB each.
Hope this is your problem too.
There is hardly anything left in the /data folder. I have tried to delete the logs (65 mb) from Phone/log but that didn't change a thing. Im going to send the phone to the company i bought it from next week.
Ive recieved a battery that I ordered from china and the phone works now. So the problem was the battery just to let everyone know.
Glad you sorted it.
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.
Hello,
if my phone is in deep sleep and I press the power button it takes up to 5 seconds until the lock screen is showing.
I have already done some research, but it seems so that i am the only one with that problem.
Does anybody do have a fix for me?
Regards,
Chris
I also experience this so you are not alone. Standard OTA update. I've factory reset twice with no improvement. The issue extends to the FP scanner where I assume it detects the correct FP and yet doesn't bring the phone out of deep sleep for 5sec or so. Frustrating as everything else is very snappy.
It started happening for me after the latest update (June) - used the twrp zip version though (not ota).
At least I didn't notice it before that, but maybe it did as I've gone back to eragon 2.8 & I've noticed it on this too now.
It's as if the phone wakes straight away, just not the screen - if the lag is long enough, when the screen finally comes on you can see it's already dimmed ready to go off, in which case it only stays on for a further couple of seconds.
Anyway we can change this?
I'm not sure what happened but mine went away after the last update. The only thing I changed was remove an SD card that was faulty and reset... FP scanner issues went away and phone locks immediately
DavidGMC said:
I'm not sure what happened but mine went away after the last update. The only thing I changed was remove an SD card that was faulty and reset... FP scanner issues went away and phone locks immediately
Click to expand...
Click to collapse
What you said jogged my memory - my SD card became faulty after the latest update (June), the same time i got the screen on lag. Anyway I removed said SD card this morning & no lag ever since.
If you're wondering why I keep a faulty SD card in my phone, well it has worked again once - i kept getting a message saying SD card ready but after pressing OK nothing changed. Then one day I saw a message saying checking SD card, I clicked on it & it was working again, all my data as it was. But then an hour or 2 later it was as if there wasn't any SD card again, just like before. I have no idea what's going on with that as it isn't even visible on a PC. I think it was something to do with the update though...