Hi there.
I've recently dug up my Nexus 5 and wanted to downgrade it to KitKat for nostalgia.
However I couldn't get it to work. Always stayed at the Google-Logo and then Restarted.
So in order to unbrick it I installed TWRP and flashed Lineage 17.1 which worked. (Lineage 17.1 is currently the only Rom I got to work actually)
Now my end goal would be to install a KitKat Version of CyanogenMod but when flashing that it doesn't boot again. (Same as with the Factory Image)
Long story short: What am I missing here/How can I downgrade to CM11? I feel like the answer is simple but I just can't figure it out.
Thanks in advance
Related
Hi guys,
After searching for a few days and doing stuff myself (perhaps not everything for the best), I finally get it over with and ask for advice.
I've got a GT-N8010, since long been running an unofficial CM11 build (since one of these CM11 builds, the device was known as a GT-N8013).
Last week I started looking at the unofficial CM12.0 and CM12.1 builds, those looked promising.
After some info, I flashed to the CM12.1 build. A few minutes later, Android 5.1 in all it glory... everything running fine. Saturday evening I noticed I didn't get root.
Without thinking straight, the next morning I started flashing superuser but as you might imaging, that totally f'ed the system.
Now logically, one could just reflash CM12.1 and be done with it .. somehow I skipped all logic and started tinkering in recovery (TWRP).
After some doing, I managed to even F-up TWRP, it wouldn't boot anymore. The TeamWin logo was visible, screen flashed, logo and back.
No worries, there's still the download mode .. yeah about that ... already in panic mode .. doing more harm than good.
So .. Now I'm at this curious state.
I've managed to get it booting to a stock ROM. TWRP is also running.
The weird stuff I'm encountering now:
The device is semi recognized as a GT-N8000, if it was just that, I really don't care.
I said semi, when I want to flash another ROM (even specifically the CM12.1 for GT-N8000) it always states (in ADB Sideload in TWRP) that the package is not for this device.
There's a whole lot of devices listed, then it states "this device is ." , as in blanco device?
Anyone got an idea how to fix it so I can enjoy the Android 5.1 build again? (and seriously, remove the stock rom would be the first priority)
Thanks.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
Hello guys,
I was using CM12 (Lollipop 5.0.2) but I had some issues — my phone would very often reboot, sometimes for no reason as I wasn't even doing anything — so I wanted to switch ROM but wasn't able to install DU 5.1. TeamWin wouldn't work properly so I gave up. I then decided to at least upgrade to a more recent version of CM12, so I installed another recovery to do that, but it didn't work as well, so I put Philz back on my phone and tried to flash the exact same ROM I had before and now it won't install anymore and I'm left with nothing. Do you have any idea how I can get something back (and maybe then get an upgrade?).
Thanks in advance!
Edit: Ok, I got it to work again by downgrading step by step. CM11 Snapshot works but I'd like to get back upwards now and it still won't work even though I'm doing the same thing I did to get 5.0.2. :/
Edit 2: Now I'm back on 5.0.2, figured it out all by myself.
Good morning guys, sorry about the english. So, a while back I installed the 12.1 cm in my GT I9515L (Galaxy S4 VE), the rom was running normally, but i had some problems in some applications that were not compatible with the version BOJ1 (Lollipop). I performed the downgrade of the same for AJN1 (KitKat) to reinstall the CyanogenMod above, the problem is that whenever I go into recovery mode, time to flash the GAPPS, one error appears saying that the version isn't compatible. I performed the test of reset the machine without installing any version of gapps, and the cell was automatically updated to version Lollipop. I would like to ask for your help because I am unable to keep KitKat version in Cyano. I think that it's a litte mine mistake on wipes or in version of cyano, but I googled a lot and found nothing. Thank you guys.
Besides my comments in the title, the only thing my K1 can do right now is go into the bootloader and nothing else.
The Story:
I was running Blisspop 4.0.3 (Lollipop 5.1.1) then flashed to Blisspop 6.0 (MM 6.0). After that, it wouldn't boot into the OS. I did a complete wipe of everything and tried to flash Blisspop 6.0 again, same outcome. I heard I needed to get my hands on TWRP 3.0.0.0 to get MM roms up and running. My dumb ass flashed it and now, I don't have a recovery either now because it gets stuck on the first slpash screen. I went digging around the forums here and I felt like I read something about doing a bootloader update. If that's true well then I done messed up now. At this moment in time, I am only able to launch the bootloader but for the life of me, I can't get ADB to detect it connected to my computer to fix these issues. So as of right now, it's a $200 brick. If anyone can point me to some awesome tools to hack my way around this conundrum, I'd love you forever. Thanks in advance for listening to my problems.