First of all, I have the straight talk version of this phone. Second, here is everything I can do and what the phone does:
What I CAN do:
Enter CWM recovery (Though, sometimes it will crash instantly, the Power button will not work)
Enter download mode (Thanks to USB jig)
Use the phone (Max of 5 mins before the phone crashes.)
Fun information about the phone:
The Power button is a gamble. Sometimes it will work, sometimes it wont.
If I turn the phone on (Have to take battery out then put back in), and let it go to sleep. 9 times out of 10 the phone will crash.
CWM crashes...very often. Very often in this case can be defined as 'always'.
Here is what I HAVE done:
Attempted to flash the stock ROM
Factory reset
Wipe data and cache (Though, CWM crashed both times on these, don't know if it fully cleared them)
Here is what I attempted to do:
Perform a ROM wipe using a script from here: http://forum.xda-developers.com/showthread.php?p=38199542 (This was unsuccessful because everytime I try and do this, CWM crashes before I can start the process)
That ends that. I just want this boot loop to end...and restore functionality back to the power button (I'm thinking flashing back to the stock ROM will solve this). I have done nothing to cause this. The only thing that happened before the boot loop is the battery was low and when I turned the phone on (it was in sleep mode), I accidentally pressed the power button twice, which first froze the phone. Then, crashed the phone. Ever since then it was in a boot loop.
Related
Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!
About 3-4 months ago I flashed stock ICS into my Galaxy S2 (I did not wipe the cache, which I discover today was a mistake). I noticed a few weeks later that it was a bit unstable, crashing, restarting, etc. I did not care much and just kept using it.
Today it just would not boot, so after 1 hour trying, I managed to keep it alive (using safe mode) long enough to go to setting and have a factory reset.
Then it would not boot again.
From there, I tried several times the factory reset and wipe cache (using volume up + home + power menu). It would sometimes hang on the "installing applications" until several restarts it would eventually go. Then it would hang randomly on startup "s" video, until I managed to get to the welcome screen - which freezes pretty much on the first or second screen (choosing language and date/time).
I flashed I9100GXXLPY_I9100GDBTLP3_DBT and got the same result.
The phone is not rooted, there is no clockwork and I can't even access the phone to put it into debug mode.
Anyone has any more idea of what can be done besides throwing it on the trash? :/
Hey guys,
I just upgraded to Revolution HD 32.0 (coming from 31.0).
Here's what i did.
Boot into recovery.
Clear cache+dalvic-cache.
Install zip from sd-card (select revolution hd 32.0)
Started Aroma installer, left everything pretty much default, just removed some of the samsung junk.
After the install was finished i cleared the cache again and rebooted the device.
It started with the start up logo and after a minute or so "Android upgrading..." with the applications counting.
After that it shows "Finishing boot"
Then nothing, it stays at that for like 5 minutes, then reboots and stays stuck at the samsung logo.
So i decided to boot into recovery, whipe caches and fix permissions and reboot again.
Same thing happened as before.
So i wanted to do a full clean install of the rom, wiping all userdata.
Surprise! Can't get into recovery or download mode anymore.
Took out battery for a few minutes and put it back in.
Still can't access download mode or recovery with vol+menu+pwr...
Does anyone know what's going on, or better, how i can possibly fix this?
I have no idea how to access my device now to make changes...
Thanks a lot!
If you can't get into bootloader with vol down, home and power button then you have a brick, service centre repair required.
Worth trying a USB repair jig to get download before paying for a repair .
jje
Ok, so something seems to have gone very wrong with flashing my phone :S
I managed to get recovery working yesterday, and followed the steps in this thread, http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155 , to create a pre-rooted 5.0.2 image. I put it on the external SD card, booted into recovery and installed the flashable zip, then used flashtool to flash with the instructions (though I also cleared Appslog, Cache and Data to get a fresh install). This went fine and everything appeared to be ok. I then tried to get the Xposed Alpha installed, but after that whenever the phone was rebooting it just hung if trying to boot to Android. I tried re-flashing with Flashtool, but still got the same issue. Would boot fine the first time, but then any restart it would just hang and crash out. Tried clearing the cache from recovery, but no difference.
So today, I went into recovery, re-installed the flashable.zip, then powered off the phone and flashed using flashtool, just as I had yesterday. Now though, my phone wont boot. It shows the Sony logo, then a blank screen, then restarts. Even worse, it will no longer boot into recovery. I hold the volume down button when the LED shows, nothing. I try holding the volume down button all the way through several bootloops, nothing.
I've tried to re-flash using flashtool which goes through the process ok, I can hold the volume down button and connect the cable once its in the process of rebooting, and it goes through all the process fine. It then powers off as expected and I can just disconnect and power on the phone. But it's still stuck in the bootloop and I don't have TWRP recovery.
Is there anything I can do to get my Z2 working?
Update - Re ran flashtool, this time not excluding system, only Partition. It now gets a little further, going to "Powered by Android" and giving the purple wavy lines, but after a minute or so it just hangs and restarts again. And still no recovery sadly....
I think I've got it sorted...
Used Flashboot again to do a flash, excluding System and Partition. This time the phone does boot up normally. The downside being that my root was gone. Despite my flashing a pre-rooted image, it seemed to just put a stock image on. And my recovery is still mysteriously gone.
In the end, just to get things completely back to a stable/stock starting point for later on, I ran a repair from PC Companion. Seems I was in the none rooted position anyway so figured I'd get myself to a more certain position. At least this way I can wait for someone to come up with a root for 5.0.2 so I can root and get recovery back.
The phone is rooted and has a few Xposed modules installed; stock ROM.
I shut the phone down every night. When I wake up and turn it on, every now and again it gets into an infinite boot - not a bootloop (at least not in my understanding). It either stays on the LG logo or the Tmobile logo. Sometimes it boots just fine and quick, sometimes takes a minute longer. Other times I have to hold the Power + Volume Down for a few seconds to reboot it, and it boots fine after that. Yet other times, I have to get into the Factory Reset mode and rebuild the Dalvik cache form within TWRP, after which it boots fine.
The weird thing is that when nothing is changed from the moment it loops to the moment it boots fine; it may only be a reboot away. Granted, I do have (quite) a few things frozen and/or removed in Titanium Backup, but should it affect the boot?
Has anyone experienced anything like that?
Attached are the warnings and errors captured while LiveBoot was running. The lines go really fast, and Nexus 5 shutter isn't capable of going that quick (that's why you can see double lines in certain places). The phone booted after I switched to my swap battery.
Just an update, I restored the earliest Nandroid backup and instead of uninstalling these apps, I froze them in TB. No boot issues so far.
Another update. This morning the problem seems to be back, it was stuck on the T-Mobile logo. Although I can rebuild the cache, it's worse now, because I haven't disabled any LG or system apps since the last restore.
Update to this update: after the T-Mobile logo reboot, it now stuck again on the LG logo and took two 5-minute waits before reboots; it booted fine on the third (essentially, the fourth) reboot upon swapping the battery.
Does anyone else experience this?