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?
Related
I have been tinkering around with Checkrom all day after moving away from LightningRom (haven't even updated my sig yet ). I came up with a really stupid idea of trying to flash a battery mod made for CrickeloRom so I could get a better looking icon than the ones already available in the kitchen app.
After recovery mode flashing, and then gave me an error message on the home screen view before continuing endless reboots. Managed to wipe and format everything (sdcard, system, data, cache, emmc) I could through recovery mode and reflashed Checkrom to get it to boot properly.
Only problem now is when the phone is hooked up to the charger, it displays 96% and then quickly goes 97, 98, 99, 100....96 and repeats. The number changing only happens when the battery icon flashes it little charging animation. I have tried to reflash the stock battery mod hoping whatever got screwed up would fix itself but it didn't work. Any suggestions?
Is there any place I can find a stock nandroid backup that will replace all system files, not just the ROM-related files, so it gets back to true factory state?
I am hoping that you mean that even if the battery dips below 96% it still shows what you are saying.
If not i am fairly sure that it is part of checkrom revo 2.0 as mine does the same thing while it charges so mine at this pont in time will sit at 56% the count up to 100% stop for a little wile and repeat.
kenshinzer0 said:
I am hoping that you mean that even if the battery dips below 96% it still shows what you are saying.
If not i am fairly sure that it is part of checkrom revo 2.0 as mine does the same thing while it charges so mine at this pont in time will sit at 56% the count up to 100% stop for a little wile and repeat.
Click to expand...
Click to collapse
The problem you have is exactly what I am experiencing. I was using the blue circle bat mod from the kitchen app and it was not doing this before I messed up, so something definitely seems to be wrong software wise. I'm just hoping someone knows a way to restore deeper problems like this one, because a factory wipe and reinstall rom through recovery mode wasn't enough to fix it. I've even tried switching back to lightningrom and different kernels to make sure it wasn't a bug.
Last resort for is to restore stock rom+kernel and play dumb with samsung tech support, and get it serviced. Hope it doesn't come to that.
So my wife's razr shut off on its own not even a week after her getting it. So I played around with different chargers till a little white light came on left till morning and nothing. Took it to vzw and they charged it for a few and turned it back on told her to use the cord that came with the razr. The whole time battery was a little more than half full. So today the razr decided to go blank or shut off if you will because it doesn't respond to button presses. Battery was a little less then 3/4 full and laying in bed. No apps installed today since this weekend. Wanted to know if anybody else is having this problem and how it was solved also factory state phone
Sent from my Galaxy Nexus
Soundsike you've got a duff one. Send it back for a replacement
I've never had those problems... If I were you, I would go into recovery, wipe everything, then fastboot the .173. (The data wipe isnt necessary before fastbooting but I would still do it anyway) Before doing that however, I would also take a look at running applications on boot and try to eliminate possibilities. Since you replaced the razr already I would assume the problem had to do with some data somewhere. It could also be worth it to not restore any data from previous backups (Verizon adds things on to backup data and such. When you get ur phone you enter a pin to restore this backup) If you're using a data backup from another phone that could be causing it too. I would also download a battery logging application to make sure somethings not causing terrible battery drains. The best thing I thing would be restoring to an absolutely clean backup with no data and trying that out for a while. Obviously you could have another bad Razr, but I'm more inclined to believe that its a problem with data.
Sent from my DROID RAZR using XDA
mine the day you received restarted every 5 minutes. take him to warranty, stayed 48 hours. they could not fix and I got a new
do "factory reset" and don't install any apps. if it happens again, you need to exchange the phone
Mine has the same problem. I just saw the last times when it happens.
The phone sends a sound of empty battery, and if you are quick enough, you may hit power button and the lock screen gonna show your batter complete empty, only the red border.
This happened to me:
- Just some minutes after I charged my phone;
- After a factory reset;
- After a fast boot room;
Have no idea when it happens or why. It just happens.
I will send my to warranty as soon as possible.
As far as I know, it is not related with any app or config you do, cause even factory default with no app installed I have got this error :/
olivete said:
Mine has the same problem. I just saw the last times when it happens.
The phone sends a sound of empty battery, and if you are quick enough, you may hit power button and the lock screen gonna show your batter complete empty, only the red border.
This happened to me:
- Just some minutes after I charged my phone;
- After a factory reset;
- After a fast boot room;
Have no idea when it happens or why. It just happens.
I will send my to warranty as soon as possible.
As far as I know, it is not related with any app or config you do, cause even factory default with no app installed I have got this error :/
Click to expand...
Click to collapse
I'm an MDM administrator for my company. We have had 4 razrs die with this issue and possibly a 5th today. It's a PITA but I just get them swapped out.
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
If it was bricked it wouldnt turn on even a bit. Just charge it or try changing the battery.
coolstorybro_123 said:
If it was bricked it wouldnt turn on even a bit. Just charge it or try changing the battery.
Click to expand...
Click to collapse
If I try to charge it it displays the SGS2 charging screen for a few seconds and then switcher straight off.
I just got into work and tried my colleagues 2000mah battery which had 32% in it. Exactly the same problem. WTF????
Thanks
Edit: FYI, it turns off before entering download mode or recovery. WTF????
Maybe you hit this ?
VAXXi said:
Maybe you hit this ?
Click to expand...
Click to collapse
That's just what I was thinking, actually
I couldn't find a description of what actually happens when this brick happens. The page doesn't really say... Does anywhere say?
Edit: I swear I didn't even flash the Siyah RC6 that was known to brick the phones either... -_-;;
Thanks!
It's not just a specific kernel, more are actually faulty. The whole story is here.
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
your phone is ok as far as it shows u the s2 logo
you have 2 things to do , try to go to recovery or download mode and formate data/factory reset then flash another rom , btw what kernel u used before your phone go to this situation ? if you were using stable kernel "cm,neak,fluxi,syah stable" so you are safe from hardbrick bug , and the hard brick bug is done only if you have faulty kernel and wibed your data through recovery , and this isn't your situation , so don't be afraid
evaworld said:
your phone is ok as far as it shows u the s2 logo
you have 2 things to do , try to go to recovery or download mode and formate data/factory reset then flash another rom , btw what kernel u used before your phone go to this situation ? if you were using stable kernel "cm,neak,fluxi,syah stable" so you are safe from hardbrick bug , and the hard brick bug is done only if you have faulty kernel and wibed your data through recovery , and this isn't your situation , so don't be afraid
Click to expand...
Click to collapse
Thanks for saying, but I can't get into recovery or download. The phone switches off before then!
That's what's so confusing! xD
Thanks
With a known good batter try hard resetting to download mode 2x in a row.. Hold the button config to get into download mode.. Hold it through two restarts.. Might work.
Sent from my GT-I9100 using xda premium
I've nuked mine a few times with buggy kernels, sounds like a similar situation. I got my device back by flashing CM9 resurrection, then flashing Siyah, and finally from CWM flashing an ICS-based stock ROM.
I'd suggest taking a backup of your efs unless you're selling it with stock.
Sent from my GT-I9100 using XDA
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
i am having exactly the same problem.i did a factory reset after flashing siyah kernel (SiyahKernel v3.3.1) on Resurrection remix v2.2.let me know if you guys find any solutions
JIG
try to use a download mode JIG.
I'm not sure if a link will violate xda-rules....
google it
dont worry
if you boot up and are getting the sg2 logo then you have not bricked you phone.
to fix simply download a .tar version of any rom and run odin to pda reinstall if you wanted to you could go the whole hog and reflash a fresh cf-kernal (rooted or stock) and then flash fresh firmware. just remember to get the kernal that originally matches the (ithink) your correct baseband ie xxki4
there should be no worries aslong as you dont pull the plug.
could have had a worse error saying installation incomplete please use kies then you would have to had taken battry out reinserted and hoped the three butn combo for rec. mode worked happened to me awhile back lol
hope i helped you
ps never read your post fully just skimmd the jist of it although the above should be applicable
also try resetting your battry stats in cwm
finally fixed
thanks for the help everyone.i have fixed it now.it seems like the problem was with the updated version of siyah kernel .i managed to put the phone in download mode.(kept the phone on the charger for a while. than, i don't know some how when i tried to go to download mode it did).and flashed siyah kanel v3.2.6.4 via odin
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.
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.