Related
i dont have any gapps even though i had flashed latest tiny gapps for my dream
i had check df -h and my system space is 99% free
when i boot on recovery and flashed gapps, im sure that it says installing google apps and its say installing complete
i had wiped and reflashed several times
any help?
tiny gapps are for cm 6.0
flash the right ones from here and it should work, and next time post in the cm 5.0.8 section
http://forum.xda-developers.com/showthread.php?t=688262
tried it
reflashed using the link u posted
still cant see market and other gapps
any recommendation?
aqulue said:
tried it
reflashed using the link u posted
still cant see market and other gapps
any recommendation?
Click to expand...
Click to collapse
wipe everything, reflash rom and gapps then boot and see what happens.
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!
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Try provide with a logcat, might be more useful in helping you.
No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.
Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz
Hey guys need a bit of advice!
Probably missing something blindingly obvious, So don't hold back with the stupid questions! !!
I have just been given a Samsung Galaxy Tab 2 10.1 (GT-P5110) and I'm trying to install another Rom on it. (either : CW/Slim/AOSP 4.# and 6.# images)
Roms install OK until I try and flash Google apps ( either using OpenGapps or Google apps) Then I either get stuck on a "Unfortunately Setup Wizard has stopped" at first reboot Or it gets stuck in a boot-loop.
I've tried flashing the Play apps directly after flashing the rom, as well as letting it reboot once then flashing the Play apps. Both have issues which basically gets me stuck in either a boot-loop or crashing setup wizard.
I'm using TWRP v2.8.5.0 for my recovery.
Just wondering if i'm stuck without the Play apps.
&
Anyone got a good email client to pick up my Gmail accounts if i can install the Play apps?
thanks!
s0litaire said:
Hey guys need a bit of advice!
Probably missing something blindingly obvious, So don't hold back with the stupid questions! !!
I have just been given a Samsung Galaxy Tab 2 10.1 (GT-P5110) and I'm trying to install another Rom on it. (either : CW/Slim/AOSP 4.# and 6.# images)
Roms install OK until I try and flash Google apps ( either using OpenGapps or Google apps) Then I either get stuck on a "Unfortunately Setup Wizard has stopped" at first reboot Or it gets stuck in a boot-loop.
I've tried flashing the Play apps directly after flashing the rom, as well as letting it reboot once then flashing the Play apps. Both have issues which basically gets me stuck in either a boot-loop or crashing setup wizard.
I'm using TWRP v2.8.5.0 for my recovery.
Just wondering if i'm stuck without the Play apps.
&
Anyone got a good email client to pick up my Gmail accounts if i can install the Play apps?
thanks!
Click to expand...
Click to collapse
update your twrp to latest version (3.0.2-4) from here https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
smart-t78 said:
update your twrp to latest version (3.0.2-4) from here https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
Click to expand...
Click to collapse
Updated to latest TWRP, still having problems with gapps.
Needing non gapps alternatives for the stock apps.
Failing that I'm stuck back to the stock Samsung ROM
Go here http://opengapps.org/ download the pico version of the gapps... if you are installing cm13 or any marshmallow get the AMR 6.0 Pico put it in your external sd card with the rom.. from the Recovery go to wipe advanced wipe everything except your external sd go to install flash the rom and the gapps restart... I garantee everything will be ok now..
zidane01 said:
Go here http://opengapps.org/ download the pico version of the gapps... if you are installing cm13 or any marshmallow get the AMR 6.0 Pico put it in your external sd card with the rom.. from the Recovery go to wipe advanced wipe everything except your external sd go to install flash the rom and the gapps restart... I garantee everything will be ok now..
Click to expand...
Click to collapse
That was one of the first things I tried!!
No matter which ones I try (ROM or opengapps version) as soon as I install the google play services app it crashes, or I get stuck in a boot loop!
I've tried kikkat lollipop marshmallow builds, all are the same!
Currently running Slim6 with no play services installed and its running fine!
Just something with the play services causes my tablet to flake out!!!
Will go back to stock ROM with no root and start from scratch, see If that makes any difference.
Sent from my espressowifi using XDA Labs
s0litaire said:
That was one of the first things I tried!!
No matter which ones I try (ROM or opengapps version) as soon as I install the google play services app it crashes, or I get stuck in a boot loop!
I've tried kikkat lollipop marshmallow builds, all are the same!
Currently running Slim6 with no play services installed and its running fine!
Just something with the play services causes my tablet to flake out!!!
Will go back to stock ROM with no root and start from scratch, see If that makes any difference.
Sent from my espressowifi using XDA Labs
Click to expand...
Click to collapse
I guarantee for you 8f you install the latest twrp https://www.androidfilehost.com/?fid=24591000424963475
Andi cm13 rom
https://www.androidfilehost.com/?fid=24591000424965117
GAPPS
https://github-cloud.s3.amazonaws.c...esponse-content-type=application/octet-stream
From here ( amr 6.0 pico)
http://opengapps.org/
You will get the perfect tab.. ..,
When you reboot in recovery 3.0,2.4 go to advanced wipe.. wipe everything except the external sd card then install cm13 Andi version (the newest and the best zero lag zero freezing.. Everything works great with this rom) install the gapps.. Reboot.. That's it all your problems are past now
zidane01 said:
I guarantee for you 8f you install the latest twrp https://www.androidfilehost.com/?fid=24591000424963475
Andi cm13 rom
https://www.androidfilehost.com/?fid=24591000424965117
GAPPS
https://github-cloud.s3.amazonaws.c...esponse-content-type=application/octet-stream
From here ( amr 6.0 pico)
http://opengapps.org/
You will get the perfect tab.. ..,
When you reboot in recovery 3.0,2.4 go to advanced wipe.. wipe everything except the external sd card then install cm13 Andi version (the newest and the best zero lag zero freezing.. Everything works great with this rom) install the gapps.. Reboot.. That's it all your problems are past now
Click to expand...
Click to collapse
Thanks
The latest cm13 (sept 11 build) was the only one not to bootloop after installing gapps !
Now got a working tablet again!
s0litaire said:
Thanks
The latest cm13 (sept 11 build) was the only one not to bootloop after installing gapps !
Now got a working tablet again!
Click to expand...
Click to collapse
Welcome! it's Andi latest and best ever rom the 3.0.2.4 recovery is his work too. You should thank him for this brilliant work
zidane01 said:
Welcome! it's Andi latest and best ever rom the 3.0.2.4 recovery is his work too. You should thank him for this brilliant work
Click to expand...
Click to collapse
**update**
Everything is 99.5% working.
The 0.5% is the WiFi! It tend to drop every so often,
WiFi frequency is set to automatic so might an issue jumping between 5Ghz and 2.4Ghz bands.
I've set it to only use the 5Ghz frequency band for now, I'll see if that makes difference...
I'm using a BT Home Hub 3. ( saving up for half decent WiFi router to replace this!)
zidane01 said:
I guarantee for you 8f you install the latest twrp https://www.androidfilehost.com/?fid=24591000424963475
Andi cm13 rom
https://www.androidfilehost.com/?fid=24591000424965117
GAPPS
https://github-cloud.s3.amazonaws.c...esponse-content-type=application/octet-stream
From here ( amr 6.0 pico)
http://opengapps.org/
You will get the perfect tab.. ..,
When you reboot in recovery 3.0,2.4 go to advanced wipe.. wipe everything except the external sd card then install cm13 Andi version (the newest and the best zero lag zero freezing.. Everything works great with this rom) install the gapps.. Reboot.. That's it all your problems are past now
Click to expand...
Click to collapse
Had the same problem with resurectionremix and slim6. This works perfectly
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!!!