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.
Related
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.
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.
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
blueintegral said:
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
Click to expand...
Click to collapse
Should be easy to fix. Common issue.
Try booting into recovery. If you can then clear cache and dalvik. Try rebooting then.
If that doesn't work try re flashing the rom,
If you can't reboot into recovery but can get into download mode then you can easily fix it at the cost of losing all your data.
Let me know how it turns out.
At this point, my phone is just one big tweak.
Wiping the caches didn't work, so I ended up having to reflash the rom. Everything seems to be back to normal now though, thanks!
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.
I have an acer a700 and it was stuck on the acer startup screen. I tried an official factory reset using the acer firmware and got the red exclamation android symbol. I managed to unlock the bootloader and install CWM . I decided to try a custom rom and snagged the nightly CM-11 that was in the the suggested Roms thread. It started up I got to the welcome screen and I thought everything was going well except the AOSP keyboard kept crashing. Because the AOSP keyboard kept crashing I decide to try an older version to see if it was a bug, so I went with CM 10.2. I did the standard factory reset in CWM, wiped the cache, and the dalvik cache. On the next reboot It goes through the CM boot screen, then it hangs and reboots. It does this repeatedly. I tried the AOSP rom, and I tried Pacman as well. They all do the same. I tried to go back with the original CM that at least let me boot but now it's doing the same thing as well. CWM works every time and everything else checks out on the tablet. Do you think that it's got a hardware problem?
I have tried dling the roms again to make sure that it's not a crc error. Clock work mod works fine, I can format everything without a hitch and the bootloader is unlocked. I'm beginning to think I have a brick.