First time using MultiRom. I currently have CM11S with AK kernel as my primary rom. I have a TWRP backup of CM12 5.0 also. I would like to use MultiRom with them so I can use each whenever I want without having to wipe/restore each time. I read on the MultiRom thread that CM12 has to be the primary rom for it to work. I don't want to mess anything up, any help would be appreciated.
You read right, lollipop ROMs only work with Multirom if they're the primary ROM.
Transmitted via Bacon
timmaaa said:
You read right, lollipop ROMs only work with Multirom if they're the primary ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
BlakeSm said:
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
Click to expand...
Click to collapse
I thought there were pretty comprehensive instructions in the Multirom thread? You can't make 5.0 a secondary ROM, full stop, so that won't work. Just flash 5.0 like you normally would then add CM11S as a secondary.
Transmitted via Bacon
BlakeSm said:
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
Click to expand...
Click to collapse
Make a backup of your primary ROM(cm11s) then in multirom recovery add a second rom and restore the backup of your cm11s ROM.
Next, wipe the primary ROM. (Data, system, dalvik & cache) then flash 5.0 with gapps and AK kernel for CM 12
Thanks guys!
Related
I want to flash Cyanogenmod 11, but I'm currently running DN4 ROM on my Galaxy S3 (Int.) with arter97 kernel. Do I have to return to stock ROM and kernel before switching to Cyanogenmod?
Sawake said:
I want to flash Cyanogenmod 11, but I'm currently running DN4 ROM on my Galaxy S3 (Int.) with arter97 kernel. Do I have to return to stock ROM and kernel before switching to Cyanogenmod?
Click to expand...
Click to collapse
Not sure what DN4 ROM is. If it's KitKat, then just wipe /system, /data, and dalvik cache then fish your ROM's zip file.
If you are on Jelly Bean, then you will need a KitKat compatible recovery like PhilZ CWM Touch or TWRP, and probably an updated modem. zip file to flash first to your S3.
Then format system and data partitions and wipe dalvik cache, then flash CM11.
If on an older Android version like Ice Cream Sandwich, you might need to install a newer KK/JB recovery and radio, format system, data and dalvik, and flash CM10 Jelly Bean first, then follow the steps to flash CM11 KitKat.
Hope this helps. Good luck!
NoSpamDan said:
Not sure what DN4 ROM is. If it's KitKat, then just wipe /system, /data, and dalvik cache then fish your ROM's zip file.
If you are on Jelly Bean, then you will need a KitKat compatible recovery like PhilZ CWM Touch or TWRP, and probably an updated modem. zip file to flash first to your S3.
Then format system and data partitions and wipe dalvik cache, then flash CM11.
If on an older Android version like Ice Cream Sandwich, you might need to install a newer KK/JB recovery and radio, format system, data and dalvik, and flash CM10 Jelly Bean first, then follow the steps to flash CM11 KitKat.
Hope this helps. Good luck!
Click to expand...
Click to collapse
DN4 is basically a port of the Note 4 ROM (which is KK) for the Galaxy S3. I really appreciate your help, but my my problem is the kernel, because now I have arter97's kernel, but I want to flash CM12 with JustArchi kernel in order to have better performance. On the latter kernel's thread I've read that it's strongly not recommended to flash it on another custom kernel (arter97 in this case), so I was thinking to go back to stock and then flash CM12 with JustArchi's kernel. Is this okay to go like this or there's a better way to do it? Thanks again for your help!
Sawake said:
DN4 is basically a port of the Note 4 ROM (which is KK) for the Galaxy S3. I really appreciate your help, but my my problem is the kernel, because now I have arter97's kernel, but I want to flash CM12 with JustArchi kernel in order to have better performance. On the latter kernel's thread I've read that it's strongly not recommended to flash it on another custom kernel (arter97 in this case), so I was thinking to go back to stock and then flash CM12 with JustArchi's kernel. Is this okay to go like this or there's a better way to do it? Thanks again for your help!
Click to expand...
Click to collapse
Just make a nandroid backup and try it. Make sure you format system and data partitions and wipe dalvik cache before flashing CM12.
You don't need to go stock first; if you have a custom recovery and the bootloader is unlocked, worst case is you restore your nandroid.
I suggest asking about this in the JustArchi thread too.
Sent from my OnePlus One BACON using Tapatalk
NoSpamDan said:
Just make a nandroid backup and try it. Make sure you format system and data partitions and wipe dalvik cache before flashing CM12.
You don't need to go stock first; if you have a custom recovery and the bootloader is unlocked, worst case is you restore your nandroid.
I suggest asking about this in the JustArchi thread too.
Sent from my OnePlus One BACON using Tapatalk
Click to expand...
Click to collapse
Okay! Thanks again for your help!
Sawake said:
Okay! Thanks again for your help!
Click to expand...
Click to collapse
You're welcome.
Sent from my OnePlus One BACON using Tapatalk
Hi all!
First off, I apologize in advance if this is a dumb question. But basically, I'm running a rooted One and I've been waiting for the official nightly builds for CM12, but now that they're finally here, I can't seem to flash them. I keep getting random errors when I try. I'm currently running on the latest 11s update that was OTA with TWRP, and I've unlocked my bootloader and everything. Anyone have any input? I've read in some places that you can't update to the CM12 nightly from 11s, and if that's the case, what's the best way to go from 11s to 11 without losing any data?
Thanks in advance!
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
timmaaa said:
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
Click to expand...
Click to collapse
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
CaptainBlackbeard said:
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
Click to expand...
Click to collapse
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
timmaaa said:
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
Click to expand...
Click to collapse
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
I'd wipe even going from CM11 to CM12.
Transmitted via Bacon
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
No, can't, unless you wait for CM12s. But I guess you can backup everything with Ti Backup then restore it back, No harm doing that though.
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
dirty flash
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
dd2 said:
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
Click to expand...
Click to collapse
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
timmaaa said:
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
dd2 said:
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
Click to expand...
Click to collapse
If you're just updating the same ROM (flashing a newer build of the exact same ROM) you can usually dirty flash. Any other time you must clean flash.
timmaaa said:
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
CaptainBlackbeard said:
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
Click to expand...
Click to collapse
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
timmaaa said:
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
CaptainBlackbeard said:
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
Click to expand...
Click to collapse
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
CaptainBlackbeard said:
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
Click to expand...
Click to collapse
Did you read the second part of my post??
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
The new version you linked worked!
Now I'm attempting a restore through TItanium. How long does it usually take? It's been sitting at 0% on the first app for a little while now.
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
Hi All,
I am using Samsung S2 GT-I9100 device with CM12.1. Earlier I was using KitKat and recently updated to Lollypop. While I was on KitKat got an update for CM12.1 Nightly and updated my phone to Lollypop. After that all my Gapps have stopped working and even I have tried to flash them through recently available Gapps packages, none of the Gapps are working.
Please suggest the fix.
Thanks!!
sbehera23 said:
Hi All,
I am using Samsung S2 GT-I9100 device with CM12.1. Earlier I was using KitKat and recently updated to Lollypop. While I was on KitKat got an update for CM12.1 Nightly and updated my phone to Lollypop. After that all my Gapps have stopped working and even I have tried to flash them through recently available Gapps packages, none of the Gapps are working.
Please suggest the fix.
Thanks!!
Click to expand...
Click to collapse
get the update from cm site, and a lollipop gapps. wipe cache, dalvic cache, and system only in advanced menu, then flash rom and gapps.
no data will be lost. make a backup first, in case there is a problem.
Thanks for your input. Just querying, if i will flash only the gapps will it work as my phone is already have lollipop os. Just trying to avoid to flash lollipop again.
Please let me know your thoughts.
sbehera23 said:
Thanks for your input. Just querying, if i will flash only the gapps will it work as my phone is already have lollipop os. Just trying to avoid to flash lollipop again.
Please let me know your thoughts.
Click to expand...
Click to collapse
really nothing will change by doing it the way i said, unless you made a bunch of system mods.
you can try it your way, it may work.
my way just gives you a clean system, so there is no chance of conflict with the old gapps that dont work properly.
bweN diorD said:
really nothing will change by doing it the way i said, unless you made a bunch of system mods.
you can try it your way, it may work.
my way just gives you a clean system, so there is no chance of conflict with the old gapps that dont work properly.
Click to expand...
Click to collapse
Can i flash using default cyanogen recovery? I have tried installing CWM but it is going by default to Cyanogen Recovery. Could you please help in providing the steps for easy reference if possible.
Thanks!!
sbehera23 said:
Can i flash using default cyanogen recovery? I have tried installing CWM but it is going by default to Cyanogen Recovery. Could you please help in providing the steps for easy reference if possible.
Thanks!!
Click to expand...
Click to collapse
i wasnt aware cyanogen had their own recovery. not knowing anything about it, i cant speculate if you can use it to flash with.
the procedure i described in post 2 are the proper steps, but if you dont have those options in the cyan recovery, im not sure what to tell you. sorry
Help! My phone is about to explode and only a true hero can fix it. Up for the challenge?
So I currently have multirom installed on my phone with a stock, kexec-able kernel. Everything seems to be running smoothly except for the fact that I have no multiboot menu. I have tried a stock kexec kernel and bouffla kernel with this however I have yet to find my hardboot menu.
Any help would be very appreciated!
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
andybfmv96 said:
Help! My phone is about to explode and only a true hero can fix it. Up for the challenge?
So I currently have multirom installed on my phone with a stock, kexec-able kernel. Everything seems to be running smoothly except for the fact that I have no multiboot menu. I have tried a stock kexec kernel and bouffla kernel with this however I have yet to find my hardboot menu.
Any help would be very appreciated!
Click to expand...
Click to collapse
Alternatively, you can try "Inject boot sector". The boot menu is a part of boot.img, so if it's wiped or if it's completely fresh then MultiRom will not show up.
SirSoviet said:
Alternatively, you can try "Inject boot sector". The boot menu is a part of boot.img, so if it's wiped or if it's completely fresh then MultiRom will not show up.
Click to expand...
Click to collapse
Tried that actually. I've flashed multirom multiple times. I am having trouble with Kali Nethunter installation as well. Something g weird is going on with my phone and I don't know what it is...
MZO said:
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
Click to expand...
Click to collapse
Just saw this. Trying now with a fresh install..
MZO said:
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
Click to expand...
Click to collapse
i cant find that force overlay option actually...