Hi, I am running the rom Liquid Gingersense and the tb was doing fine until it rebooted once, and so it turned back on and within 3 minutes of turning on again it rebooted again, it turns on and starts up everything and then reboots. Someone called me before it rebooted however, and it worked until the call ended and then rebooted. When I try to reboot into recovery it just reboots normally, and so I tried to download rom manager (because i hadn't done so yet) to get it into recovery and when the app was installing it rebooted. what should i do?
EDIT: LOL nvm, I figured out why, I had accidentally set it to overclock to 1.9 which messed it up, after setting back it is fine
Related
A couple of nights ago, I accidentally let my phone die. It must have been doing something important, because I kept getting force closes on all stock apps and also apps that required root including superuser. I rebooted to see if that fixed the problem but it didn't boot up after, I figured it wouldn't be a problem and deleted my cache and dalvik and rebooted. The phone booted to the lockscreen saying "Upgrading android, Optimizing x of x applications" but I noticed that when it got to the 33rd app, it would suddenly go very fast and the phone would crash to the boot animation (not the boot logo) on "starting applications". It wouldn't boot back up until I did a hard reboot. After a while, I realized it wasn't going to fix itself and just wiped and re flashed everything. I did restore some user apps in tb and everything was fine. On the next day, i made sure that the battery didn't die but i woke up to the same force closes and bootloop when i rebooted. Tried to delete cache and dalvik again to see if i could reproduce the problem but now it wont boot past the animation at all.
Im using siyah 3.2.7.2 and my second rom (which boots fine) is Pure ics
EDIT: On 3.3.1 now, doesn't make a difference
My note has been acting strangely lately. I had let the battery run fully down after a couple months of use and did a full charge cycle, but when I tried to start it up, I'd get 'SAMSUNG' and then it'd shut off. This repeated a good dozen times until it finally woke up and did a normal boot. Then today I tried to get into recovery mode so I could do a backup prior to trying CM10, VolUp+Home+Power at boot and it sits there and does 'buzz...... buzz....... buzz.....' endlessly until I let go and then it boots normally.
What happened to my phone? All I've ever done is root it to clear the bloat from AT&T. Did my recovery get corrupted somehow?
tigerknight said:
My note has been acting strangely lately. I had let the battery run fully down after a couple months of use and did a full charge cycle, but when I tried to start it up, I'd get 'SAMSUNG' and then it'd shut off. This repeated a good dozen times until it finally woke up and did a normal boot. Then today I tried to get into recovery mode so I could do a backup prior to trying CM10, VolUp+Home+Power at boot and it sits there and does 'buzz...... buzz....... buzz.....' endlessly until I let go and then it boots normally.
What happened to my phone? All I've ever done is root it to clear the bloat from AT&T. Did my recovery get corrupted somehow?
Click to expand...
Click to collapse
What Rom are you running right now? if your phone boots normally, try downloading Quickboot from the play store instead of using the 3 buttons to recovery. GL
Ltilt2 said:
What Rom are you running right now? if your phone boots normally, try downloading Quickboot from the play store instead of using the 3 buttons to recovery. GL
Click to expand...
Click to collapse
Running stock + root.
Quick boot helped a lot, thanks. Apparently it was my superuser setup that got mangled somehow. had to uninstall/wipe it from memory and reinstall. After that the quick boot (and TiBackup) worked. running a backup now.
tigerknight said:
Running stock + root.
Quick boot helped a lot, thanks. Apparently it was my superuser setup that got mangled somehow. had to uninstall/wipe it from memory and reinstall. After that the quick boot (and TiBackup) worked. running a backup now.
Click to expand...
Click to collapse
Nice! glad you got it working.
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?
I'm using Moto C plus since past 2.5 years. Last week it suddently restarted. I thought it may be an issue of main memory full. So, let it to restart. But it went on a bootloop. I had more than 2GB free in internal storage. Then I wiped cache and tried booting. It booted successfully and then after 5-10 seconds it froze again and restarted and the bootloop continues. I tried wiping all data but no luck. I tried system root integrity check which failed. I flashed stock ROM again and started phone but the same issue continued. It boots successfully, I get home screen and then after 5-10 seconds reboots.
I thought of flashing custom ROM then. I flashed TWRP. While I was flashing zips using TWRP, TWRP itself restarted randomly. I somehow flashed DotOS and Ressurection Remix with GAPPS but same issue existed.
Now I'm back on stock ROM. Sometimes it boots successfully and then after using for 5-10 minutes it randomly reboots and get stuck in a bootloop freezing on Moto logo or Lenovo logo and then restarting.
What could be the issue here? Is there a hardware problem?