I'm running twrp 2.6.0.0 and cm10.2 nightlies. I have no issues with the rom, everything works perfect. But just about every boot or restart it gets hung on the Samsung unlocked boot screen and I have to pull the battery,then the next time it gets past it. Also when I boot into twrp, it does the same thing. I pull the battery and then it finally boots into recovery. Almost always it works the second time but sometimes it take 3 or 4.
Does anyone know what the cause of this could be? It's done it to me with touchwiz roms too. Could it be an issue with Loki or twrp?
Related
Anyone seen this? I just did a wipe and flash CM 10.2 and on the first boot it hangs at the Samsung Unlock screen. Battery pulled and restarted... works fine. Then when I reboot it it hangs again requiring another battery pull.. then works. Etc. Same with Pac-Rom. Anyone seen this?
Let it do its thing on first boot. Out can take 3 to 5 minutes
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 tried to update to cm13 and flashed the 35B modem and kernel. I then wiped and flashed cm. It didn't boot so i tried Resurrection Remix. I finally got it to boot by selecting safe mode. It didn't boot into to safe mode but booted normally. Now I only get passed the lg boot logo every 5 or 6 times I try to boot. I get a black screen and have to power+volume down and continue boot. Eventually it boots and everything seems to go as normal. I'm only using it as a WiFi device for my daughter to play with but as far as I can tell the radio is working fine and there aren't any other issues. I'm not sure if there was a partition I should have flashed with the other two maybe I missed something during the update... Coming from cm 12.1
Hello!
I own a Galaxy s3 GT-i9300, android 4.3 (currently).
I rooted it, and then installed cm12.1 on it. It worked great for some time, and then one day, it suddenly froze, and after some seconds it rebooted. After it successfully booted, it got stuck, and rebooted again. It kept doing that until I decided to shut it down.
I booted the recovery (TWRP), and the same thing happened over there.
when the device was shut down, it didn't boot up suddenly, which means it's not the power button problem. I think that its a hardware problem, because it looks like the CPU or whatever it is gets overloaded. Or could it also be a kernel problem?
Its twrp or the rom causing it.
Flash back to stock and start over. Here is my collection of useful stuff for the btu variant only https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
Sent from my HTC One M9 using Tapatalk
ghsucbyuc said:
Hello!
I own a Galaxy s3 GT-i9300, android 4.3 (currently).
I rooted it, and then installed cm12.1 on it. It worked great for some time, and then one day, it suddenly froze, and after some seconds it rebooted. After it successfully booted, it got stuck, and rebooted again. It kept doing that until I decided to shut it down.
I booted the recovery (TWRP), and the same thing happened over there.
when the device was shut down, it didn't boot up suddenly, which means it's not the power button problem. I think that its a hardware problem, because it looks like the CPU or whatever it is gets overloaded. Or could it also be a kernel problem?
Click to expand...
Click to collapse
Samething happened to my device I am flashing the fully Stock Firmware to see if all ok, I dont think its going to be a Hardware issue Because I can boot to download mode successfully.
I had installed CM13 on my Nexus 5. Everything was working fine. Today I woke up to see Nexus 5 won't even get passed to CM android logo when starting. I then tried to go to boot loader. Hopefully, it opened and I navigated to Recovery and opened. But phone also stuck at TWRP logo. I also noticed when phone starts Google logo takes a little more time to disappear than before. I waited a lot for this but it stuck forever. Actually phone was in charging but battery connector was removed when I saw it in the morning. So it kept rebooting at Google logo. I don't think that could be an issue as it already happened before.
Now all I care about is my data. If I flash TWRP using fastboot, will it work? Will my data be removed? Please reply as soon as possible. I am so concerned about this. Thank you
It might be a little Late but yes you should be able to flash a fresh recovery..without loosing your data