Database Info

[Q] boot issue with cyanogenmod 11

Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated

Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.

Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM

Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.

Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know

Paranoids works fine, seems like a CM problem .-.

Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

MOTO G (simcard issues with latest CM13 nightly)

I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......

iHackIt said:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
Click to expand...
Click to collapse
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:

karanksj said:
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
Click to expand...
Click to collapse
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.

iHackIt said:
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
Click to expand...
Click to collapse
I quoted 5.0.1 not 5.1 brother It worked for me every time.

karanksj said:
I quoted 5.0.1 not 5.1 brother It worked for me every time.
Click to expand...
Click to collapse
Sorry for misreading...:silly:
I cant flash 5.0.1, 4.4.2,4.4.4
When i try to flash it gives errors and warnings (only 5.1 works )
i will share errors...
works in the sense it was flashed perfectly but it also boots to the recovery everytime like CM13
My bootloader version is 41.1A..

Bootloop with every Android N Roms

After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.

Dush4711 said:
After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.
Click to expand...
Click to collapse
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.

ethicalhacker365 said:
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.
Click to expand...
Click to collapse
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.

Dush4711 said:
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.
Click to expand...
Click to collapse
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.

ethicalhacker365 said:
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.
Click to expand...
Click to collapse
Thanks
Will try after 2 days as I am currently out of town.
Reply you later
Please don't mind.

U are not doing it correctly.
Goto-twrp-wipedata-advanced-check(dalvik/art,Data & Internal Storage) dont check system.
After it Flash with any Custom Rom
Then Wipe-dalvik/art,Data & Internal Storage) uncheck system
Flash Gapps
Again Wipe-dalvik/art,data & internal storage)
Reboot to System
Wait Aleast (10-15)-For me After Flashing 6.0.1 Cyanogenmod from Official Website.
Finish(You have no problem of bootloop)
Hits thanks if you solve this way.

None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.

dh.y said:
None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.
Click to expand...
Click to collapse
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....

ankitdhimancr said:
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....
Click to expand...
Click to collapse
Yap it boots but problem is battery discharged within 1 hour

Yeah..phantom kernel will work but on other hand this kernel eats up battery and take to much time on charging usually 3-4 hours

Try censium kernel

Please Help! Enters bootloop when I flash multirom recovery!

Please refer this development thread https://forum.xda-developers.com/xperia-l/orig-development/mod-multirom-xperia-l-t3397663 . Been trying long to check out multirom and everytime I end up with a Bricked device and have to do a flash..
SO the problem is I tried flashing multirom with stock and doesn't seem to work. That's when I got to know that it doesn't work with stock ROM . Hence I tried with CM 12.1. Used dd Install Method to flash latest TWRP 3.0.2 on CM 12.1 and installed the multirom-20160614-v33x-UNOFFICIAL-taoshan.zip. It goes into Bootloop and stuck at sony logo everytime i try. Also I tried with LineageOS 14.1. Help Appreciated.:angel:

darklord717 said:
Please refer this development thread https://forum.xda-developers.com/xperia-l/orig-development/mod-multirom-xperia-l-t3397663 . Been trying long to check out multirom and everytime I end up with a Bricked device and have to do a flash..
SO the problem is I tried flashing multirom with stock and doesn't seem to work. That's when I got to know that it doesn't work with stock ROM . Hence I tried with CM 12.1. Used dd Install Method to flash latest TWRP 3.0.2 on CM 12.1 and installed the multirom-20160614-v33x-UNOFFICIAL-taoshan.zip. It goes into Bootloop and stuck at sony logo everytime i try. Also I tried with LineageOS 14.1. Help Appreciated.:angel:
Click to expand...
Click to collapse
It's not working with latest MM versions and never with android N! Because it's development is not continued in Xperia L (unfortunately ). But I think it's working with Resurrection Remix MM with being installed as primary ROM, and some older versions like Lollipop as secondary ROM ( lol I'm using this method now with RRemix MM & Stryflex MM v1.0 ! )
After installing first ROM using some other TWRP recoveries, go to recovery again and install multiROM recovery, then reboot to recovery again and install v33x zip file. Now go to main menu in recovery and select advanced option on top and install the second ROM in external sd card!
Now both of ROMs should work without any problem!

Partially solved now
Kungfu73 said:
It's not working with latest MM versions and never with android N! Because it's development is not continued in Xperia L (unfortunately ). But I think it's working with Resurrection Remix MM with being installed as primary ROM, and some older versions like Lollipop as secondary ROM ( lol I'm using this method now with RRemix MM & Stryflex MM v1.0 ! )
After installing first ROM using some other TWRP recoveries, go to recovery again and install multiROM recovery, then reboot to recovery again and install v33x zip file. Now go to main menu in recovery and select advanced option on top and install the second ROM in external sd card!
Now both of ROMs should work without any problem!
Click to expand...
Click to collapse
First of all Thanks man for taking up time for responding
I did a full wipe and then put up lineageOS 14.1 which comes equipped with a TWRP 3.0.2 recovery(or the one that I flashed through adb lol) and tried it again this time being more careful.. flashed the multirom recovery and then rebooted.. FINALLY got it this time flashed the MULTIROM too.. VOILA! done!
Now I have a different issue though... When I add a new ROM (CM 12.1) the lollipop one to the sd card I go through a new phase of errors. It says the nightly can't be used for flashing other than multirom now and ended with some errors and failed ! P.S The nightly is nt corrupted cuz i used it few days back and it was working just fine..

darklord717 said:
First of all Thanks man for taking up time for responding
I did a full wipe and then put up lineageOS 14.1 which comes equipped with a TWRP 3.0.2 recovery(or the one that I flashed through adb lol) and tried it again this time being more careful.. flashed the multirom recovery and then rebooted.. FINALLY got it this time flashed the MULTIROM too.. VOILA! done!
Now I have a different issue though... When I add a new ROM (CM 12.1) the lollipop one to the sd card I go through a new phase of errors. It says the nightly can't be used for flashing other than multirom now and ended with some errors and failed ! P.S The nightly is nt corrupted cuz i used it few days back and it was working just fine..
Click to expand...
Click to collapse
Good to hear that! Ok, I think there is two ways to solve this issue.
First, you may simply test and use another ROM for secondary!
Second way is longer and you should have an external sd card with more space (like 8GB and up).
First, full backup this ROM, and then clean flash 12.1 ROM to be primary.
Next, backup this ROM too, and then recover the first backup and go to recovery again, and now, go to advanced tab and choose "add a rom" and select install from backups, and use that second backup to be installed as secondary ROM. It should work now!
And remember that: the chance of booting android N after installing second ROM, is very low. It may bootloop! because as I said, development of multiROM for our phone is not continued.

Kungfu73 said:
Good to hear that! Ok, I think there is two ways to solve this issue.
First, you may simply test and use another ROM for secondary!
Second way is longer and you should have an external sd card with more space (like 8GB and up).
First, full backup this ROM, and then clean flash 12.1 ROM to be primary.
Next, backup this ROM too, and then recover the first backup and go to recovery again, and now, go to advanced tab and choose "add a rom" and select install from backups, and use that second backup to be installed as secondary ROM. It should work now!
And remember that: the chance of booting android N after installing second ROM, is very low. It may bootloop! because as I said, development of multiROM for our phone is not continued.
Click to expand...
Click to collapse
Shall try that and get back to you.. thanks mate!!!