I have tried installing cm-10-20120822-NIGHTLY-grouper.zip and cm-10-20120821-NIGHTLY-grouper.zip which installs but now I just boot to the CM animation logo which looks like it is booting but never does. I am going straight from stock Jellybean and never had CM or any other mods installed. Any ideas on what is going on or what I should try?
phenixdragon said:
I have tried installing cm-10-20120822-NIGHTLY-grouper.zip and cm-10-20120821-NIGHTLY-grouper.zip which installs but now I just boot to the CM animation logo which looks like it is booting but never does. I am going straight from stock Jellybean and never had CM or any other mods installed. Any ideas on what is going on or what I should try?
Click to expand...
Click to collapse
Did you wipe data/factory restore and installed gapps also?
snapilica2003 said:
Did you wipe data/factory restore and installed gapps also?
Click to expand...
Click to collapse
I did.
Finally was able to get it to work. Had to do some messing around with installing, wiping, etc...and one of the combos of doing it booted up.
reset, wipe systems, cache, dalvik, install
Related
I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.
aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.
aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.
Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!
Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?
TheErk said:
Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?
Click to expand...
Click to collapse
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni
jerdog said:
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni
Click to expand...
Click to collapse
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?
TheErk said:
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?
Click to expand...
Click to collapse
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
That would be awesome, thanks
jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
Think I found the problem - a "default" wipe in twrp won't do it - I had to go in to advanced and choose "cache,dalvik,data and system" now it works like a charm! Good to know for the future..
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
matthewclso said:
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
Click to expand...
Click to collapse
you can...try this!
@halfdevil said:
you can...try this!
Click to expand...
Click to collapse
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
FIXED
Turns out that I just had to flash the boot image through fastboot, works great now! Thanks
matthewclso said:
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
Click to expand...
Click to collapse
well you can try AOSP too, just remember all these projects are discontinued, so any support in case you break anything support won't be there..so always backup.
for AOSP!