I am currently on EuphoriaOS May 3 with TWRP 2.8.6.0 and want to revert back to Final Mahdi 4.4.4. What is the procedure to do this?
Your going to need to flash the KitKat firmware before flashing the ROM. You can flash the last cyanogenmod snapshot CM11 build. It has the firmware built in. Then wipe again and flash mahdi/4.4.4 gapps. You can find those on android file host.
Related
My dad's phone has a custom recovery and has a ROM of the version of KitKat before the OTA. Have ROMs been updated to support the official release yet? How do I know which ones are on the new or old drivers? Would it simply be to flash the ROM through the recovery, or do I have to go back and install the OTA, then flash a new recovery and ROM?
Thanks.
I'm rooting and running Dirty Unicorn 4.4.4 ROM.
If I flash a ROM that's using Android 5.0 and use it for a while can I then just flash a ROM using 4.4.4 and not have any issues? I guess i'm asking if it's possible to just flash any working ROM running on either 4.4.4 or 5.0 (swapping between them) and it work?
You'll need to wipe going between 4.4 and 5.0 custom ROM. Once you've set up new ROM once, and have Nandroid backups of both, you can go back and forth
can i flash cm12 nightly directly over cm11 without wiping data?
i ve previously flashed like this on earlier nightly of cm 11 it has gone crazzy all apkz gone forced stop
Yes, just flash.
experience7 said:
Yes, just flash.
Click to expand...
Click to collapse
Is that wise? Going from a KK based rom (CM11), to a L based rom (CM12)?
I'd advise user to wipe data, maybe even update to stock LRX22C and from there, flash twrp and cm12.
If he has a clean CM11 installation he can easily flash CM12 without wiping anything.
If you're on stock ROM and apply the OTA update you're also going from KitKat to Lollipop without wiping anything.
Official statement:
You can flash CM12 nightlies directly from CM11 M12 or CM 11 nightlies (no need to wipe), provided you read and followed items 1 and 2
Click to expand...
Click to collapse
http://www.cyanogenmod.org/blog/the-l-is-for-lollipop
beekay201 said:
Is that wise? Going from a KK based rom (CM11), to a L based rom (CM12)?
I'd advise user to wipe data, maybe even update to stock LRX22C and from there, flash twrp and cm12.
Click to expand...
Click to collapse
The OP's question was whether you could flash CM12 over CM11, not whether or not it would boot up
@Lethargy: That answer made my day :'D
Hi guys,
I flashed my bootloader and TWRP in order to install CM 12.1 NIGHTLY HammerheadCAF ROMs. It's working fine, but now I want to try the Android M preview. Do I just have to flash the original bootloader and non-caf TWRP and be back to normal?
Flashed stock images via fastboot and back to normal.
I want to install MM roms on my phone,stock or CM based. But the problem is that I installed Hurtsky Stable Kernel for 5.1. Do I need to flash a stock kernel of 5.1 to be able to flash 6.0 roms or do I need to flash any kernel for 6.0 roms. And if I do flash a stock kernel for MM rom while running CM12, will my phone boot?
You have only to make a full wipe via twrp recovery (Wipe system, data, cache, art-cache) and install zip of CM13 and gapps.
Download the main system zip from: https://download.cyanogenmod.org/?device=falcon
And the gapps from: http://opengapps.org/ (choose the 6.0 one).
There aren't stock based, because Moto G 1st gen (2013) does NOT HAVE 6.0 official!
There is also an Identiti crisis rom, a porting from moto g 2014, but CM13 is more stable!
All right.Thank you for replying! My concern is about the kernel. The kernel I flashed is meant for LP CM Roms and not MM. So when I flash CM13 with gapps,won't it create a problem? Will I have to flash stock 6.0 kernel or a kernel for MM CM Roms?
No, the kernel is replaced when you install a ROM. The kernel is a part of system, the heart of ROM, contains all the driver (called modules) and also set the CPU and GPU frequences. So you don't have problem if you install the zip because in the zip there is the default 6.0 kernel (if you see in the zip there is a file called boot.img).
Ohh! Thanks a lot! I shall try CM13 now!