so decided to update my N4 from 4.3.1 to 4.4? from 10.2.1 stable to 11 nightly.. booted into TWRP, and tried installing CM11, but FAILED. wiped Cache, Dalvik Cache, and Factory Reset. Still FAILED. Wiped System too. Still Failing. Any ideas?
The CM 10.2.1 zip doesnt work either. Originally i had updated to 10.2.1 and noticed it was still android 4.3.1 XD just.. updated? so decided to go CM 11 then this happened T_T
any ideas?
-----------------------
so i found out CM11 doesnt work with TWRP. had to use ADB to flash recovery to CWM then flash CM11....
Sounds like you need to update your recovery
Sent from my Nexus 4 using Tapatalk
Happened to me also, you need to update to the latest version. I have CWM but for TWRP is probably the same.
yeah o well. i flashed to CWM recovery (newest one prob) and it worked. running CM11 now.
Related
Verizon VS980, TWRP 2.6.3.3
Finally, upgraded to the above TWRP, and was able to flash a CM 11 nightly. and Gapps for 4.3.0, 20130813 and to have that finally flash successfully is great! BUT it's not, when I boot into it I get an android system error and the keyboard AOSP error every time, I can't make it past the screen where I enter in my account.
I have wiped and tried again, and again, I have installed the ROM and gapps and then wiped dalvik and cache and same result...
It seems so close.
I have installed ROM Manager as well and it says that CWM is installed yet I cannot seem to boot into it, I have flashed it from the ROM Manager many times and no love. I was able to flash a zip of twrp, is there a zip of CWM that is flashable from twrp, I have heard that cwm works better with CM 11
Please help, I have no idea why going to CM 11 should be such a pain in the..
Thanks!!!
SO i figured it out
I was following/using rootz wiki for my reference of which gapps to use and it is not updated right now
got the right gapps here, and all is good now
http://d-h.st/mDt
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'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
MrJodroid said:
I'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
Click to expand...
Click to collapse
Maybe bad download redownload
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
MrJodroid said:
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
raptorddd said:
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
Click to expand...
Click to collapse
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Hiiii
MrJodroid said:
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Click to expand...
Click to collapse
glad you got it back working.. youre welcomed.
So I run my Galaxy S4+ GT-I9506 on Cyanogen 13.0 and I downloaded the latest update cm13.0 20160113 Nightly today and everything went smooth until after the optimization of apps. And when it said cm settings storage it just frooze and rebooted. And now Im stuck...
I've tried to wipe data/factory reset it just blinked very quickly and nothing happends
wipe cache partition nothing
tried to install the update again nothing
So... Im stuck in Cyanogenmod Recovery and I dont know what to do
anyone?
Tried that with odin fails all the time. What recovery should I use?
TWRP. Bu you need Odin to flash it. Unless you can flash it with CM recovery.
Cant do that, cuz Cyanogenmod do not support sdcars :crying:
What about internal memory? You might also be able to push it through adb.
Can you flash this version of TWRP using Odin: https://twrp.me/devices/samsunggalaxys4ltea.html
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!