[Q] CM10 Reboot leads to Stuck on Boot - AT&T, Rogers HTC One X, Telstra One XL

I've seen a few other threads from people with similar issues, however most of them this happened after flashing CM10 or similar.
My phones been running perfectly fine on the 1/7 CM10 nightly with Rohan's B7 kernel. Actually haven't flashed anything in a fair while. Tonight I was about to go to sleep so I plugged my phone in since it was around 15%, then went to reboot it like I usually do. However it got stuck on the CM10 spinning boot screen. Now I think I might've had this happen a few days ago, but I recall that I rebooted into TWRP (bootloader and recovery both load fine), wiped both caches and it booted normally. This time however I tried such and still got stuck. I tried a couple more times, as well as tried to reflash the CyanDelta CM10 file and kernel (no wiping except caches), all with the same result.
Any ideas? I figure a factory reset will probably fix things, but I would REALLY like to save data if at all possible (stupid me for not doing backups in a bit). Also what could be causing this? As far as I know my phone's been running great and I haven't even flashed in awhile. Any help is greatly appreciated, thanks.

Related

[Q] Crashes at Google Sing-in

Hello, I just flashed cm9 for my htc sensation. I booted it up and it goes as far as google sign-in. I choose what language id like and then press next. It starts loading and then crashes and starts booting up again and keeps doing the same thing over and over again. I've tried reflashing the ROM a couple of times. Also tried wiping cache, delvik cache, factory reset, pretty much everything i've seen people say on threads so far. Also, this same thing happened to me before I flashed CM9. I first flashed AOKP's Jellybean and this same thing happened. I scratched that ROM and tried CM9, hoping that I'd ditch the problem. Well here I am now with the same problem and without a phone. Any help would be much appreciated! thanks!
I attached a few images of the process, maybe itll help.

[Q] Can't install roms, booting recovery kernel error

I've been working on this for nearly three days. My pad has been having issues for a while. Really laggy and slow. Finally couldn't take it anymore. I've restored to factory a number of times and while it helped briefly the lag always returned within a few days. Since I rooted (with Motochopper) and unlocked my pad the improvement is very, very noticeable. Faster than it was out of the box. I've been trying to install Cyanogen, but from the start I've been getting stuck at "booting recovery kernel image" whenever I try and boot into recovery. CWM can't get into it either. I tried TWRP instead but apparently their website is down because I can't access it via CWM or a web browser. I rolled the rom back to the last 4.1 and thought I'd bricked it. Kept getting stuck at spinning wheel on every restart. Wiped data and it restarted fine.
I'm convinced that it's the kernel issue, but after extensive searches I can't find a way to overwrite it without having access to "recovery". Yes, I'm noobish. I haven't cracked anything since my original Razr many a moon ago.
Any help would be greatly appreciated cuz im about to lose my marbles
Thanks!

Major breakage: phone hangs at unlocked bootloader after first reboot of custom rom

Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.

[Q] Memory leak or something else?

So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.

Need serious help with a zte blade l2

I Had CM12.1 installed on it and everything went fine until it ran out of battery. Then So far it started by having random resets and freezing up until it basically started freezing and turning off and on without going further than the ZTE logo the weird freeze ups affected it even on recovery mode so it wasnt soemthing from the ROM only.
I've had a terrible pain with it, i tried flashing different roms, tried wiping data, chache, dalvik. etc. I've format flashed the stock rom with sp flash tools so many times and even managed to get my sd formatted (thank god i had all backed up) and still no use. Recovery mode isn't affected anymore by the wierd freeze ups, but i can't enter the OS at all. I have CWM on it right now.
It's still doing the same thing, tried using a backup i made before all of this happen and still no go.
Anyone can help me out with this? THanks in advance.

Categories

Resources