Develop Bugs

[Q] Need some advice for a noobie

Hi first time posting so please take it easy on the noob. So i just rooted my nexus 7 2013. The main reason was because i wanted to be able to extend battery life and the main thing is that i bought a micro usb host otg cable with power and want to be able to charge as well as power my external hard drive. now i read that elementalx kernel allows you to do that. Would i flash the elementalx kernel first or do i flash a rom before a kernel. I'm pretty confused on where to go to download and which one i flash first.

Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.

Pandae said:
Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
Click to expand...
Click to collapse
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?

j0hnnyyyy said:
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?
Click to expand...
Click to collapse
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob

Protomartyr said:
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob
Click to expand...
Click to collapse
thanks this helped out a lot and completely understand about not trying to repost questions that have been answered. Just one question if i flash a rom and do a backup. then flash a completely different rom and do a backup for that as well I'm guessing ill have back up for both roms. my question is i use twrp and have the app online nandroid backup, would it be better to go into recovery and backup or is it safe to use the app? Also after flashing a rom is it the same process to flash the kernel?

Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

aarsyl said:
Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?

j0hnnyyyy said:
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?
Click to expand...
Click to collapse
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?

j0hnnyyyy said:
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?
Click to expand...
Click to collapse
Once you get to the reboot screen in recovery, go ahead and reboot. It's after you reboot that first time that you should wait some time.
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I didn't know that about Nexus devices. I always wipe caches for my phone, because I will enter a bootloop if I do not do so. This is my first Nexus device, and I'm learning a lot of new things myself.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?

j0hnnyyyy said:
I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?
Click to expand...
Click to collapse
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!

Protomartyr said:
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!
Click to expand...
Click to collapse
thanks very helpful so using the online nandroid backup app is the same thing as making a backup in twrp recovery mode

[Guide/Development/Info/Discussion][GEE] Multiboot for the Sprint Optimus G!

This was being discussed in the unofficial CM11 thread, So I thought I would give it a home.
Here is the thread for; Development, Discussion, Information, and Also A guide on how to Multiboot different ROMs on the LG optimus G.
Code:
I in no way made this MOD,
all the rights and credit go to the original creators.
I Just wanted to give an area and help other people learn how to do this.
I (Or the Creators of this mod) are NOT responsible for anything bad happening after flashing this MOD;
Bricks, Soft Bricks, Explosions, Implosions, Girlfriend leaving you after trying to boot too many roms.
YOU choose what YOU do to your 700$ Device. Now Lets get to the Guide. :)
Before you do ANYTHING, Be sure to read this over many, many times. If you do NOT know what you are doing, do NOT try this. Enjoy. :good:
This is how I multi boot, using a backup.
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Now Wipe as normal like if you installing another ROM. and Set whatever ROM you want as your primary ROM.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose backup as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
This is how to Multiboot with a .zip. (results may vary)
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Make sure you have primary ROM. You don't need to edit this if you want to keep it
To change primary ROM before adding new ones, wipe as normal and setup/backup etc.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose .zip file of ROM as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
Helpful Quotes:
dopy25 said:
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.
Click to expand...
Click to collapse
gearslam said:
You need to install the TWRP-2.7.0_MR_geehrc.zip Recovery and then flash the multirom-20140409-v22-UNOFFICIAL-geehrc.zip
In TWRP under Advanced There is a MultiROM option. You can use a TWRP Backup or a ROM ZIP.
I'm currently running both Stock and Unoffical CM11 without any problems on the Sprint LS970.
Click to expand...
Click to collapse
gearslam said:
I just wanted to point out for those that don't know. OTG is working good in this recovery. I've been using a 16Gig flash drive formated to exfat. All you need is an OTG-Y cable. You can easily backup/restore and flash ROM's from USB drive. Another alternative to sideloading if you accidently wipe everything out.
Click to expand...
Click to collapse
gearslam said:
I patched the recovery and multirom zips so geespr roms can be flashed and EFS backups can be made. I used Unoffical CM11 as my primary ROM and a TWRP backup of the stock based ROM as a boot option. You can flash different kernels on the primary ROM not sure about the secondary, etc. Anytime you flash a new Kernel, you have to go into advanced ->multirom and there is an option to inject multirom into boot.img
The secondary ROM's and there Data are stored in /data/media/0/multirom/...
The patched recovery and multirom are in my google drive: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
Click to expand...
Click to collapse
Download Links to MultiBoot Recovery & .Zip: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
*ALL* credit goes to Gearslam and anyone who helped.

Mine. Muhahahahaahahahaha :good::good::fingers-crossed::laugh:

Awesome.
I use this method and am rocking the dual boot with @gearslam 's mods. Thanks again for all the help.
EDIT: 4-29-2014
@gearslam Can you edit the script to allow installation of geespr roms? I tried to install an official rom and it said during installation that the process is for (insert multiple "GEE" type roms) and listed gee_spr but said the one I was trying to install was geespr. I think the underscore might make a difference. And since I have no idea how to update it to allow other roms, would you please?

Awesome! Thanks for this guide!
Sent from my Optimus G using XDA Free mobile app

Thanks for this, and thank you too gearslam! Rocking both cm11 and stocktimus ce. Love it, especially now that the stock Rom is using the 0 folder to load files so there aren't 2 separate areas to search through ( had to use twrps file manager to move some things up so I could view photos I took on stock lol)
Sent from my LG-LS970 using Tapatalk

So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Whiplashh said:
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.
Click to expand...
Click to collapse
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.

dopy25 said:
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.
Click to expand...
Click to collapse
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.

Whiplashh said:
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.
Click to expand...
Click to collapse
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
I uploaded another one using the "geehrc4g" id which seems to be what the latest version of the LS970-TWRP is using these days...
Click to expand...
Click to collapse
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.

dopy25 said:
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.
Click to expand...
Click to collapse
Okay. Thank you man

Whiplashh said:
Okay. Thank you man
Click to expand...
Click to collapse
Any time. Let me know how it goes if you do flash those other files.
If you try it out and it works for you maybe you could add it to the OP, that the ones to flash are the geehrc4g because anyone looking at them might not know that right off hand.

Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...

treezy26 said:
Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...
Click to expand...
Click to collapse
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.

Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem with the error saying no Kexec. Have you tried making a new backup and then adding as 2nd rom? That is now mine worked.

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.

dopy25 said:
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.
Click to expand...
Click to collapse
Not yet just tried again by making a back up of PAC and flashing a stock ROM but the stock ROM wouldn't boot kept kernel crashing immediately after the lg pop up so I'm going to download another stock ROM which one are you guys using? Says the same thing with trying with liquid though so I'm not sure what's going on tried to dual boot liquid and PAC had same exact results even tried making those two share the kernel as well as not buy of course didn't try that with the stock rom I kept it as is
Sent from my LG-LS970 using XDA Premium 4 mobile app

EDIT: I added some pics. 2 show the about this device. One is the boot menu the other is the list ROMs function under recovery.
The screenshots are the about info for my primary ROM.
Edit 2: Wow that was a weird double post. I use the stock zvc (from zip on the forum) but only as a secondary. PAC gee version from 4-4 is my primary.
@spleef ! I just thought of something, when I tried to use solid kernel on liquid smooth ls970 when it was a secondary ROM, my phone would also only boot the primary! I had to use f93 cpq to boot it and any other ROM other than primary. Maybe some kernels are not compatible if they override the primary. Try like I have with gee version of pac as primary and the kernel I'm using (might even be built in kernel) I'm hoping you know more than I do about it based on the about device info.

Nope still couldn't get it going...no matter how i try it get the kexec error doesn't matter which i use a primary stock or custom and same goes for secondary doesn't matter which one kexec error when trying to choose...I'm using geehrc4g version is very confusing
Sent from my LG-LS970 using XDA Premium 4 mobile app

Can I dual boot, with seperate Data partitions?

I was wondering if there was anyway I could dual boot my Nexus 7 and have both installs totally independent of each other?
I want to keep my device rooted, but I want to use Sky Go as well, and Sky Go doesn't play nice with root.
I would like to have one partition rooted with a custom rom, and another partition that is completely stock, stock ROM, kernel etc.
And I would also like to have the apps installed totally independent of each other so that my stock partition can't see any superuser stuff that I have installed in my custom partition.
I hope this makes sense? Is this possible?
Cheers
Stewart

Hypothetically you might be able to do like CM already does on the touchpad, they have virtual partitions to store all the android stuff since they dont want to remove/modify the underlying webos partitions.
At the very minimum you would need a rom that is modified to take advantage of running from a different location.
You would also need some way to select which one to boot at start.
Some dual boot solutions cheat by using recovery to boot the other rom, since there's no major differences beyond the fact it doesnt boot by default

You want MultiROM. The first ROM would have to be rooted, but the secondary can be completely stock and unrooted.

There is a module for the xposed framework which are able to hide root for selected apps.
Sent from my Desire HD

[MultiBoot][unofficial]MultiROM V32 [DISCONTINUED]

Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.​
Special Thanks:​ @Tasssadar: For The MultiROM Source.​
Sources:​MultiROM
Modified TWRP​
Download is one post below.​

Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.​
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.​
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands

and another one...

Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app

Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app

Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk

Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.

I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app

lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.

Great! I do not have important data in the internal storage, so I can test it.

@Thunder07 I want to test it too

The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.

Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.

ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/

Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk

humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok

Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat

cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why

So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.

humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.

Take advantage of MultiBoot!!

As far as I know, not near enough Galaxy s3 owners are taking advantage of this amazing utility. It allows you to install multiple ROMs on your device without having to wipe the one you already have. I currently have 5 ROMs on my phone ranging from touchwiz to Cyanogenmod, Lollipop to Jelly Bean. It's very versatile and guess what!
It was recently updated to work with Lollipop ROMs! You can install any ROM you want as a secondary ROM and test to see if it works as a daily driver! No more getting scared about a brick or bootloop because a simple REBOOT switches you to your primary ROM!!
I constantly switch between CM ROMs for fluidity, Lollipop ROMs for cutting edge features, and TouchWiz ROMs to unleash the full potential of the camera, as well as get all those TouchWiz features like WiFi calling! You can flash any ROM, test experimental builds and flash any kind of ROM you want all without wiping the ones you already have! Unlimited ROMs!(space permitting)
Now, it may not be as simple as ROM manager for Nexus devices but it's pretty darn easy. here's the steps:
Flash MultiBoot Recovery(based on twrp 2.8.3.0)
Go to Advanced>
MultiBoot>
Create ROM>
Set ROM(to what you created)>
"Flash the ROM and gapps just like any other">
Set ROM>
Boot ROM(Click on one you just created)>
A menu will pop up saying Boot ROM!
There. You are done. I can boot into recovery and boot a ROM in a matter of seconds. Slimkat, SlimLP, CM11, CM12, TouchWiz 4.1.2, 4.3, 4.4.2, PAC ROM, any of them!
I just want more people to take advantage of this wonderful feat of developer genius!!! I feel like only have of the phones potential is had without this amazing recovery. Now that it is updated to allow Lollipop ROMs, it is too hard to keep it in.
Head over to development, it should be on the first page and try it! Alternately search for "Multiboot" and look for the thread.
All credits go to @Phil_Suz for being an amazing god.

but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?

YPG70 said:
but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?
Click to expand...
Click to collapse
You don't have to wipe your main ROM at all! It is just a recovery, and each secondary ROM is like a whole different device on your sdcard, you just have to switch to it it's amazing let me tell you. Your primary ROM, kernel, modem etc will not be affected at all until you decide to change it, which you just do like any other ROM (just be careful formatting because that will delete the multiboot folder on root of phone). If you flash another ROM and it doesn't boot, just reboot the phone to your main ROM and or go to recovery and try again you can create and delete ROM's as much as you please and even set up how much space you want to make the different parts of the ROM take on your sdcard (data, system, cache). Flash the multi boot recovery, read how to use it and you're golden there's also a video someone made of how to use it. If you don't like multiboot just flash another recovery and reboot the recovery. You won't lose anything unless you created an additional ROM or ROMs.

Can you give me instructions on how to do this properly? The video is a bit confusing. I understand how to create a new rom. I am just a bit lost, on how to switch to my current ROM, or set it up.

This is true its useful... for those who could figure out what to do at right times.
not only that but other carriers have it baked into the kernels for simply a reboot option.
we have more complicated version yet out phones are not bootlocked. if more people got tmobile phones I am sure they would have worked these issues out by now.

I certainly have taken advantage of this. Alternate between your favorite roms with ease.

reminds me of safestrap, which i used on my droid4, and appears to be available for some flavors of the SGS4 and some galaxy Notes. it also uses twrp. think of it as creating partitions on your PC - you make a partition for each Rom - they were called ROM Slots in safestrap - make a given slot active, then flash the rom and whatever else you want as you normaly would right there in twrp. if something breaks or you find a showstopper bug or just need to switch roms, simply reboot into recovery, change which rom is "active" and then exit - it loads the rom you just selected. it was great on my droid4 since gps and camera were both kinda buggy in almost any custom rom, and i was nervous not having it on my galaxy relay, but it worked out. it'll be nice to have on the sgs3, especially since I want to try out some L roms.
here's the thread for the multiboot recovery, so nobody else has to search for it:
http://forum.xda-developers.com/showthread.php?t=2646528