So I was playing Asphalt 7 for a few hours (maybe too long?) and without being hot or dead battery or anything, my phone just went black and started vibrating in like 2 second intervals. Pulling the battery, and trying to boot into recovery didn't fix it.
I thought for sure something had gone terribly wrong!
So I took it over to the PC to see if I could get it into Download mode, and in trying that I managed to get it into recovery by pressing both volume buttons at the same time and inserting the USB. Not what I expected, but better still. So I tried rebooting and ended up in the same loop of black screen.
Went back into recovery using the same method, and then tried to wipe the Dalvik cache.... However, I got an error saying that the file system was read only! Thought I would try the fix permissions option, and then reboot recovery. Worked like a charm, wiped cache for good measure, and rebooted back into AOKP.
I don't really know what happend, but would like to avoid this in the future! Anyone have any clue what went wrong?
-SGA- said:
So I was playing Asphalt 7 for a few hours (maybe too long?) and without being hot or dead battery or anything, my phone just went black and started vibrating in like 2 second intervals. Pulling the battery, and trying to boot into recovery didn't fix it.
I thought for sure something had gone terribly wrong!
So I took it over to the PC to see if I could get it into Download mode, and in trying that I managed to get it into recovery by pressing both volume buttons at the same time and inserting the USB. Not what I expected, but better still. So I tried rebooting and ended up in the same loop of black screen.
Went back into recovery using the same method, and then tried to wipe the Dalvik cache.... However, I got an error saying that the file system was read only! Thought I would try the fix permissions option, and then reboot recovery. Worked like a charm, wiped cache for good measure, and rebooted back into AOKP.
I don't really know what happend, but would like to avoid this in the future! Anyone have any clue what went wrong?
Click to expand...
Click to collapse
Maybe the ram got overloaded and shut it down or you didn't have your cpu set high enough for asphalt 7. some apps like gta 3, call of duty, etc. require 500 MHZ OR HIGHER AT ALL TIMES WHILE PLAYING THE GAME. MY BOYS PLAY MADDEN 12, MINECRAFT. ASPHALT, SPIDERMAN ALL THE HIGH POWERED GAMES AND I KEEP MY CPU AT 802 MIN. THEY ALWAYS RUN LIKE A CHAMP NO PROBLEMS.
Related
Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.
Ryjabo said:
So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.
Click to expand...
Click to collapse
try reflashing the rom.
the CPU does have a set limit for how hot it can get. My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Sent From My Sprint Galaxy Nexus
ÜBER™ said:
My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Click to expand...
Click to collapse
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.
Ryjabo said:
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.
Click to expand...
Click to collapse
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image
simms22 said:
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image
Click to expand...
Click to collapse
I just booted into recovery and flashed a completely different ROM (AOKP). Now it's not going past the "Google" logo (with the lock at the bottom).
I'll wipe and reflash CM9 to see if that helps.
I just noticed something I've never noticed before... after flashing the ROM it says this:
Finding update package...
Opening update package...
Installing update...
Fixing fs_size in crypto footer...
Install from sdcard complete.
Click to expand...
Click to collapse
What in the world does that mean?
I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.
Ryjabo said:
I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.
Click to expand...
Click to collapse
sweet
Happens to me once when my kid are playing where's my water. Phone get to bootloop and first i try to wipe caches but no luck, reflash rom without data wipe -> no luck, luckily i have 1 day old nandroid backup i restored it and it started to work.
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.
jnr21 said:
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.
Click to expand...
Click to collapse
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.
Ryjabo said:
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.
Click to expand...
Click to collapse
My phone has booted itself many times also, but only once it got data loss.
I think that disabling fsync in kernel increases risk of data loss...
So CM9 is running just fine. This time I didn't flash Franco, probably won't, don't necessarily need to. And holy dogballs... Titanium Backup is truly, truly amazing. I wish I could give the creator a hug.
Anyway, I have noticed that the bars (signal/3G/wifi) have yet to turn "blue" like they normally are. What does this mean?
The problem only happens when I reboot or turn on the phone. When it boots up, I get multiple results. A: It boots up normally (not a problem) B: When it gets to the samsung screen, it freaks out and reboots itself again and again. It's like it's struggling to boot up. One time it got to the gs 3, but then it looped back. C: This just happened today. I booted up and it went pass the samsung screen but when it got to the gs 3 screen, the screen turned a faint pink and it stayed on that screen.
This just happened right after version 8. I know 10 was messed up but on 9 and 11, this problem persisted. Also,I don't think the issue is the phone, since I don't have this problem on other Roms. If I'm wrong please let me know .
Any suggestions, advice, help, etc is welcomed.
Please... i really need help.
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Naddict said:
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Click to expand...
Click to collapse
I unrooted, went back to stock, it did a factory reset so no bugs should have been alive. I re-rooted, made a backup, did a factory reset and wiped dalvik, then I flashed the rom zip and rebooted. It gets stuck on the Gs III screen. I waited like 5 minutes and it didn't move. My battery was at 50% so I just put it on the charger and tried to boot up and it went through to the set up screen for gmail.Just to see if it was coincedental, I did another reboot but this time it got stuck again. It sounds like a system problem but i'm not sure.Like i said earlier, this only happens on Jellybomb.
Any other ideas?
Edit: I've tried switching recoveries but it doesn't fix it.
Sigh.
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
joskur98 said:
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Click to expand...
Click to collapse
Which rom? Do you use the right gapps? Flash the rom without gapps and look if it's booting
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
Click to expand...
Click to collapse
Holy ****, this worked! Had the same problem last night for the first time (I used it until the battery drained and this morning I got the loop). Smacked it on the back and now it's fully on!
Shame I got desperate and did a factory reset first
So I feel like this is different from a typical bootloop (certainly different from ones I've had in the past). Any ideas short of factory reset would be very much appreciated. I just need it to load once more to do a Titanium Backup (and I guess I should install TWRP and do a nandroid backup)!
I've been using my Tab Pro for years now, rooted, works perfectly, and I always leave it on. I thought yesterday, perhaps this is a bad idea, I should turn it off every once in a while. But I wanted to play a game before I did. I click the game icon and then everything froze and it restarted itself.
It gets stuck at the SAMSUNG logo page. Sounds like a typical bootloop. After 20 minutes of waiting, nothing changes, so I hold down the power button and it restarts and actually loads to my home screen! Great! I swipe the screen lock, click on my game -- it restarts, rinse, repeat. Each time it restarts itself it stops at the SAMSUNG page, forcing a second manual reboot that fully loads, but doesn't go 10 seconds before restarting. I try to load different things each time and finally give up.
So I look some stuff up online. There's a suggestion to go into recovery (I could've sworn I had custom, but apparently not?) and "Wipe Cache/Partition." I look up that this is safe and do it (Sidenote: Power+Home+Vol Up only works around every 5th try or so. It glitches out every other time, there's a quick flash and a horizontal line and it restarts again). Now I restart and it worked! It loads and no reboot!
But now, a third of my apps/games have the android guy as an icon and even more of the real icons are all grayed out. I figure one more restart and it would come back. Now I'm back into my weird bootloop. I try wiping cache/partition again and again and it no longer works as a solution...
TL;DR - Tablet keeps restarting to SAMSUNG logo, requires 2nd manual restart. Home screen loads, but then restarts 10 seconds later. Clearing cache/partition made things worse. HALP!
EDIT: My current build is KOT49H.T520XXUANAE. I can't even find the stock ROM for this! Does it exist?
EDIT 2: After letting it charge for an hour (it was already 93%) I went back to it and it had loaded! But the home screen was blank save for the Google search and the Apps icon (which found no apps....). I was able to get into settings and attempted to click Application Manager and then it froze again.
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
hamstrman said:
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
Click to expand...
Click to collapse
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
starbright_ said:
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
Click to expand...
Click to collapse
I appreciate the response, but as I said, I'm looking for anything shy of factory reset. If I lose all of my apps and data and configuration, I might as well throw out the tablet and buy a new one.
Still trying to figure out the pattern. I got another attempt of it not restarting for 10 full minutes. The keyboard failing is annoying because it doesn't stop, but I can live with it if it means being able to backup my tablet with Titanium Backup. I only got 6 apps backed up before it froze, but I'll get through all of them eventually (I hope). It's just going to be incredibly frustrating.