Database Develop

[Kernel][Roms][TW/MIUI/CM9-10][Aroma][Menu][Dual Boot 5Roms GT-N7000 v2.3c [10-27-12]

Finally, I finished creating my scripts & kernel for booting a rom on SD Card. Dual boot kernels, preinstalled roms, setup scripts, instructions are available below.
How to make a rom on SD Card
Requirements: 3.1 GB of free space on your internal SD Card.
New method to set up the rom, fast and easy. You can now boot 5 different roms
Here is some new kernels you can try, but the setup in the Aroma v2.3c package below
PhilZ-cwm6-XXLS7-XJB-3.1-dualboot.zip (support only TW JB roms)
http://www.mediafire.com/?os6zi3u2mpe6yih
PhilZ-cwm6-XXLS2-XJB-2.7-dualboot - thanks to Phil3759 (support only TW JB roms)
http://www.mediafire.com/?k574667whh3c6qk
Hydracore v6.2 beta3 OC - dualboot kernel
http://www.mediafire.com/?0w852y7hl5yf8k8
Hydracore v5.4 - dualboot kernel
http://www.mediafire.com/?iawqi5picfcb9sm -STD
http://www.mediafire.com/?w18xigwkd9ya4no -OC
Download this current Aroma version
Version 2.3c http://www.mediafire.com/?5ym62wr7kta1u2o
- Added Timeout 15 seconds for the Boot Menu
- Fixed issue with the rom3 external in the Boot Menu
- Added Option to fix root in page 2 of the tools section.
Version 2.3b http://www.mediafire.com/?g3g8hdc2n0j3u9v
- Added Hydracore v4.3b kernels
- For some users, if you don't see the bootsdrom.cfg in the \sdcard\SDRoms folder, simply extract it from the Chuan_Dualboot_Aroma_v2.3b.zip (in the Default folder) and put the bootsdroms.cfig in the \sdcard\SDRoms to enable the dualboot roms.
- For some users, if you want to show the boot menu, you can put an empty file named "bootmenu_on" in the \sdcard\SDRoms folder.
Version 2.1b http://www.mediafire.com/?7aqibjh5nhgnh6m
- Added Hydracore v4.1b kernels
- Possible fix for the bootsdrom.cfg not being extracted for some users
Version 2.0 http://www.mediafire.com/?y0gsnzmwb7e8r6z
- Added Hydracore v3-5 kernels
- Fixed issue setting up the rom partition images on the external SDCard.
Version 1.9-1 http://www.mediafire.com/?foumtinhrhid2c6
- fixed the issue that the STD kernel always being flashed when select the OC one.
Version 1.9 http://www.mediafire.com/?ykvjahj8d32pcdv
- Added Hydracore v3-1 both OC and STD versions.
- Add boot menu options. This can be turned on and off in the "Set Default Booting Rom" section in the dualboot Aroma.
- More checking in the mount partitions tool to make sure we don't mess-up the phone rom. Again, if you see any error, don't flashing any rom/mod, otherwise it will mess up the main phone rom.
Version 1.8 http://www.mediafire.com/?lpxesvw31u3es6a
- Use a new method to mount the partitions for a rom on SDCard. Now you can directly flash new roms without messing up the phone rom.
- Clean up other versions, they seem to be obsolete now.
How to setup and flash a new rom for booting from SDCard
Please follow the instructions below, this is the most easiest ever!!! There is no need to modify the rom or mod before flashing with my tool.
1. Back up your data (just in case)
2. Reboot to recovery and flash Chuan_Dualboot_Aroma_v1.8.zip
- Select Tools section. Then select the rom slot you want. If this is the first time you use that rom slot you need to setup system, data, and cache images for the rom. In page 1 of the tool, check "Setup System" and "Setup data & cache" to setup the images. You need to do this only one time
- In page 2, select "Wipe system", "Wipe data", and "Wipe cache"
-And the most important one, select "Mount Partitions". Don't forget to select "Mount Partitions" otherwise it will overwrite the data and mess up your phone rom.
-Press Next until complete, and don't reboot the phone. (If you see any error, reboot in to recovery and try again)
3. Make sure you don't see any error in the step 2. then you can now flash any rom you like as normal. It will be flashed to the rom slot you just select in the step 2. Don't reboot after complete because you need to flash a dualboot kernel after.
4. Flash Chuan_Dualboot_Aroma_v1.8.zip again, then select "Set Default Booting Rom", then select the same rom slot in step 2.
- Then select "SDCard" as default, and select "Don't Share"
- Then click "Yes" for the popup "Flash a Dualboot Kernel?" to flash a dualboot kernel. You have to flash a dual-boot kernel because in step 3, the kernel has been changed after flashing a new rom.
- Next select "HydraCore v1-7" this can boot most roms, Or you can choose "Goku v1.5-11" only CM9 & TW.
- Click "Next" till the end, and reboot the phone.
5. Now the phone should boot in to a rom on your SDCard.
Tips: To switch the rom, flash Chuan_Dualboot_Aroma_v1.8.zip again, and then select "Phone" as default in the "Set Default Booting Rom" section.
Or you can keep pressing and un-pressing the HOME BUTTON at boot.
Enjoy flashing and new roms, and good luck to you!!!!!
Here is the tutorial how to flash mods/themes, just a little bit different from flashing the rom.
1. Back up your data (just in case), you may also backup the rom folder in the SDRoms folder you want to flash a mod.
2. Reboot to recovery and flash Chuan_Dualboot_Aroma_vXX.zip
- Select Tools section. Then select the rom slot you want. Skip Page 1, Then in page 2, select "Wipe dalvik-cache" only
-And the most important one, select "Mount Partitions". Don't forget to select "Mount Partitions" otherwise it will overwrite the data and mess up your phone rom.
-Press Next until complete, and don't reboot the phone. (If you see any error, reboot in to recovery and try again)
3. Make sure you don't see any error in the step 2. then you can now flash any mod you like as normal. It will be flashed to the rom slot you just select in the step 2.
- Click "Next" till the end, and reboot the phone.
4. Reboot the phone and boot the rom you want.
FAQ
1. I get an error, what should I do?
- Reboot into recovery, and start over
- If still get the error, Flash "HydraCore v1-7" kernel, and reboot into recovery, and start over
- If still get the error, save the recovery log and post it here.
2. How do I reset the rom on SDCard?
- Flash Chuan_Dualboot_Aroma_v1.8.zip, then select "Tools", select the rom slot you want to reset, skip page 1, then select "Wipe data", and "Wipe cache" in page 2. Then next until finish.
Credits and special thanks to:
- Hardcore for his SpeedMod N7000 ICS.
- superatmos for his TUTORIAL Building Kernel from source
- criskelo for some aroma scripts
- g.lewarne for HydraCore Universal kernel
- funky81 for first CM9 & TW kernel
- ashwin123 for Video Tutorial
- Samsung and developers for some wonderful roms.
WARNING: I've tested and used my scripts and modified kernels on my phone without any problem. There is always a risk when flashing a kernel or a new rom, so flash as your own risk. I have no responsible for any damage to your phone
Pre-install Roms
To make it easier, I have some pre-install roms on SD Card for you guys. Just extract it then it's ready to go.
1. flash pre-install rom
2. flash dualboot kernel
3. reboot
Now you should be able to boot your current rom (samsung ics only) and the pre-install rom on your sd card. Keep press/unpress the home button at boot until you see the boot animation to switch the rom. Check the log and the config file in the SDRoms for more details.
Pre-installed Cassies_XLR_ICS_V4_LQ3 rom - thanks to thering1975
https://docs.google.com/open?id=0BwDBny0G97K5SXZ0dzc3RHNSb2c
Pre-installed [ROM][TABLET/HYBRID]STAXXTANIUM-PARANOIDANDROID. V1.7 - Original Thread - thanks to Staxxthedan
How to Install
- Backup or rename /sdcard/SDRoms/rom1 folder if you have any previous rom on your SD Card.
- Flash sd_internal_preinstall-rom-PARANOIDANDROIDv1.7.zip or extract the SDRoms folder to root folder on your internal SD Card
download link https://docs.google.com/open?id=0BwDBny0G97K5Uy04S0I4eGtrV1k
- Flash cm9_stock_kernel_dualboot.zip to boot the CM9 rom on your sd card
download link http://www.mediafire.com/?gkgvl950d38ka9c
- Reboot, and wait for the phone to boot in to PARANOIDANDROID rom
Pre-installed Preinstalled-Liquid_Black_V 3.2 - Original Thread - thanks to firasusman
How to Install
- Backup or rename /sdcard/SDRoms/rom1 folder if you have any previous rom on your SD Card.
- Flash Preinstalled-Liquid_Black_V 3.2_rom1.zip or extract the SDRoms folder to root folder on your internal SD Card
download link https://docs.google.com/open?id=0BwDBny0G97K5Z1FuMnh0M2otVG8
- Flash any Samsung ICS dual boot support above (not CM9 kernel) to boot the rom on your sd card.
- Reboot, and wait for the phone to boot in to boot rom on SD Card.
Pre-installed [ROM][JB 4.1.1] PARANOIDANDROID v1.2 [TABLET/HYBRID][CM10] - Original Thread - thanks to imilka
How to Install
- Backup or rename /sdcard/SDRoms/rom1 folder if you have any previous rom on your SD Card.
- Flash PARANOIDANDROID v1.2 [TABLET/HYBRID][CM10]_rom1.zip or extract the SDRoms folder to root folder on your internal SD Card
download link https://docs.google.com/open?id=0BwDBny0G97K5TmR3RWZxbG4wQ2s
- Flash cm10_kernel_dual_new.zip to boot the rom on your sd card
download link http://www.mediafire.com/?da4cuozus6tdlv3
- Reboot, and wait for the phone to boot in to PARANOIDANDROID v1.2 rom
- Note: Flash any kernel that works with your phone rom to boot back your phone rom.
Pre-installed CM9 Stable Aroma can select 1 of the 5 rom slot via Aroma. Hope someone can help post more pre-installed roms by replacing the system.img.
You can dual boot this rom with any TW rom using the Goku v1.5-11 kernel.
https://docs.google.com/open?id=0BwDBny0G97K5Tjl5dWVqZnNzc2M
Pre-installed Roms by REVERSiN Sep-3-2012
CM10 - Preview5 UNOFFICIAL : https://docs.google.com/open?id=0B-FfdI4hUTJReFVocmdYMFJwcVE
PARANOiD - JB - v1.911 BugFIX : https://docs.google.com/open?id=0B-FfdI4hUTJRMjgzSEhrelJjbm8
Pre-installed Roms by yats86
ParanoidAndroid 1.3 [JB][TABLET/HYBRID]
Link to download rom: http://www.4shared.com/zip/BxEHxBRC/...l-rom-PAR.html
Mirror: http://www.MegaShare.com/4496353
TMT Midteam 2.2 ICS 4.0.4
Link to download rom http://www.4shared.com/zip/_8VkyH18/...l-rom-TMT.html
Mirror: http://www.MegaShare.com/4496423
CriskeloRomNOTE.vICS-V11.2
Link to download rom http://www.4shared.com/zip/6DPerI8k/...l-rom-Cri.html
Mirror: http://www.MegaShare.com/4496472
More roms will be added later.....
How to make a pre-installed rom
- After setup a rom and copy the system partition to SD Card. You can simply replace the system.img file in any of my pre-installed rom with your system.ing then upload the zip and share with your community. Thank you to anyone who can help with this.
---------------------------------------------------------------------------------------------
Intramfs Source
http://www.mediafire.com/?sk31d47jeh7q2sy - initramfs source for my dualboot1.0 feature.
http://www.mediafire.com/?oob18xxqit8cqmy - initramfs source for my dualboot3.1 feature.

Old Version
Code:
Version 1.7 [url]http://www.mediafire.com/?5w03c1q49wppbgb[/url]
-Added HydraCore v1 - big thanks to g.lewarne who makes this universal kernel working for all roms TW, MIUI, CM9, CM10. Now you can use this kernel to dual boot any rom you want.
-Added latest CM10 kernel.
[SIZE="3"][B][COLOR="blue"]How to modify rom and directly flash it using the Mount Partitions Tool[/COLOR][/B][/SIZE].
[COLOR="DarkOrange"]Most of MIUI,CM9,CM10 roms have the format command which is not safe for directly flashing a rom on SD Card. Follow this instruction to remove the format command.[/COLOR]
1. Extract the rom
2. Then edit the file META-INIF\com\google\android\updater-script using Notepad++
3. Take out the format command [B]format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0");[/B] if there is any
You may also take out all the mount, unmount, kernel flashing, and modem flashing or any command that is related to mmcblk.
4. Compress/Zip the rom back. Now you have the modified rom.
5. Now it ready to flash using the mount tools. Boot recovery, run my dualboot aroma, select tools.., select a rom to flash, in page 1 select wipe system, data, and cache, then in Page 2 select mount partitions for rom on SDCard. Don't reboot after run the script. If don't see any error or fail. Then go ahead flash the modified rom. It should directly flash it into the rom you just pick. Now flash a dualboot kernel you like and enjoy your new roms.
Note: Do the same for any mod, except you don't need to modify the mod, just run the mount tool and flash the mod.
[SIZE="3"][B][COLOR="blue"]How to Setup[/COLOR][/B][/SIZE]
1. Flash a rom you want, make sure follow the instructions of the rom you want to flash. Otherwise you will get a brick.
2. Run (flash) Chuan_Dualboot_Aroma_vXX.zip, then select Tools, then select rom slot (1 out of 5 slots) you want, then select "Copy system to SDCard" and "Wipe data & cache". This tool will copy your current rom to SD Card and setup the data.img and cache.img for the rom on SDCard. I takes about 5 to 10 minutes to process. [COLOR="red"](don't reboot after completion)[/COLOR]
3. Repeat the step 1 & 2 if for the second, third, fourth, or fifth rom except you need to pick a new rom slot. [COLOR="red"](don't reboot after completion)[/COLOR]
4. Run (flash) Chuan_Dualboot_Aroma_vXX.zip again. Select Default Booting Rom, then select the rom slot you want to boot, then select "SDCard" as default. Then Click Yes to flash a dualboot kernel, pick a kernel you want (make sure it's compatible with the rom you want to boot). [B]Now Reboot[/B], and the phone should boot into a rom on SDCard.
[SIZE="5"][COLOR="Blue"][URL="http://www.youtube.com/watch?v=B6JU08mONHY"][COLOR="Blue"]Video Tutorial[/COLOR][/URL][/COLOR][/SIZE] - thanks to ashwin123
[media=youtube]B6JU08mONHY[/media]
[url]http://www.youtube.com/watch?v=B6JU08mONHY[/url]
Version 1.6 - [url]http://www.mediafire.com/?d7bs7srsecwgm16[/url]
- Added Notecore 14.1 kernel
- Added Goku v1.5-11 kernel - thanks to funky81 for the kernel source. This is a very good kernel that supports both CM9 & TW. Now you can dual boot CM9 and TW with this kernel. Keep press/unpress the Home button at boot to switch the rom.
- Added Wipe Tools for the rom on SD Card
- Added Mount partition Tool for the rom on SD Card. This allows you to directly flash a rom or mod on the rom on SD Card. Now you can easily flash a new rom on SD Card, [COLOR="Red"]but be careful if you want to use this tool to flash CM9/CM10 roms. There's a format command there, you need to take out before flashing those roms.[/COLOR]
- Some fixes for the Tools sections.
Version 1.5 [url]http://www.mediafire.com/?1493p91bg7z56nk[/url]
-Fixed the CM10 kernel flashing issue.
-Added NoteCore v13-4
Version 1.3 [url]http://www.mediafire.com/?3c06hnon548hhh2[/url]
-Added NoteCore v13
Version 1.2 [url]http://www.mediafire.com/?9z0uzof8b532bzb[/url]
-Fixed flashing error in version 1.1
Version 1.1
- Added Kernel backup/restore options
- Added share data options too.
Version 1.0 [url]http://www.mediafire.com/?b2i954vve1gh1c4[/url]
-Initial Aroma version
-----------Old Method---------------------------------------------------------------------------------------------------------------
1. Backup your current rom and your data just in case something goes wrong and you can recover your data. You can skip this step if you don't need to save anything.
2. Flash any rom you want like you've been doing. This rom will be a rom on your internal SD Card. Just follow the guild from Dev's of the rom you want to flash. Be careful about EMMC brick, please don't wipe using an unsafe kernel. (Skip this step if you want your current rom to be the rom on your SD Card)
Some roms don't auto get root, so just to be sure you can flash this [URL="http://www.mediafire.com/?8adhwsporsdd61w"]CWM-SuperSU-v0.95.zip[/URL]
3. Copy rom partition to internal SD Card. You can do it partially or all by flashing the following scripts.
- [URL="http://www.mediafire.com/download.php?te8soummj0b9iqv"]copy_rom_to_sdcard_system.zip[/URL] - copy system partition to SD Card. ([COLOR="Blue"]recommend flashing this only[/COLOR])
- [URL="http://www.mediafire.com/download.php?4c6de3h1e8hx4po"]copy_rom_to_sdcard_data.zip[/URL] - copy data partition to SD Card. ([COLOR="Red"]not recommended[/COLOR] unless you want to copy your current apps & data to SD card and want to restore back from the rom on SD card later)
- [URL="http://www.mediafire.com/download.php?vb5l6nc8qr4qlno"]copy_rom_to_sdcard_cache.zip[/URL] - copy cache partition to SD Card. [COLOR="Red"](not recommended[/COLOR], another script will take care of this)
- [URL="http://www.mediafire.com/download.php?dvapmhow79pe1v0"]copy_rom_to_sdcard_all.zip[/URL] - copy all rom partitions to SD Card. ([COLOR="Red"]not recommended[/COLOR], take long time to do)
4. Flash [URL="http://www.mediafire.com/download.php?7q8ml0muqhh930m"]sd_internal_rom1_wipe_data_cache.zip[/URL] to setup a blank data.img and cache.img for the rom on SD card. (only flash this if you didn't flash the above copy_rom_to_sdcard_data.zip and copy_rom_to_sdcard_cache.zip, or copy_rom_to_sdcard_all.zip)
5. Setup the config file for your rom on SD card.
- Flash [URL="http://www.mediafire.com/download.php?x1jsiec6c7g78qk"]sd_rom_config_setup_3.2b_default_phoneRom.zip[/URL] to setup the config file for the SD Rom and boot your phone rom as default.
- Or Flash [URL="http://www.mediafire.com/download.php?318jat6mkpjjec5"]sd_rom_config_setup_3.2b_default_sdcardRom.zip[/URL] to setup the config file for the SD Rom and boot your rom on the SD Card as default.
[COLOR="Blue"] Remember: if the phoneRom and the sdcardRom are the same base, or same platform (CM9, or ICS, or GB). You can switch the rom by keep press/unpress the home button at boot. [/COLOR]
6. Flash dual boot support kernel to boot the rom on the sdcard. You can flash one of the flowing compatible kernels.
[COLOR="Red"]Remember: Do not flash the CM9 kernel to boot the Samsung ICS rom and versus [/COLOR]
- GL_NOTECORE_V11_dual.zip [URL="http://www.mediafire.com/?dxdaqig1d060nru"]Standard[/URL] / [URL="http://www.mediafire.com/?jbaado5xacmx7fw"]OC[/URL] - Thanks to g.lewarne
- [URL="http://www.mediafire.com/?wf1mfqb2q7wtfrb"]dualboot3.2b_speedmod-ics-k3-11.zip [/URL] - Speedmod K3-11 with dual boot support for Samsung ICS roms only, set ro.secure=0 for fully adb root - Thanks to Hardcore
- [URL="http://www.mediafire.com/download.php?60lt63qtvfqcs6b"]GL_NOTECORE_V8.1_dual.zip[/URL] - GL NOTECORE v8.1 with dual boot support for Samsung ICS roms only - Thanks to g.lewarne
- [URL="http://www.mediafire.com/?cdoj67xoqgk82j3"]dualboot3.2_speedmod-ics-k3-9.zip[/URL] - SpeedMod 3-9 with dual boot support for Samsung ICS roms only. - Thanks to Hardcore
- [URL="http://forum.xda-developers.com/showthread.php?t=1710937"]GoKu Kernel 1.4[/URL] - I have not tested this myself, but the change log says dual boot support. - Thanks to funky81.
- [URL="http://www.mediafire.com/?da4cuozus6tdlv3"]cm10_kernel_dual_new.zip[/URL] - CM10 kernel from PARANOIDANDROID v1.2 - thanks to imilka. Note: This kernel also works with the Samsung ICS rom except Wifi and Bluetooth issue. Hope someone can fix it.
- [URL="http://www.mediafire.com/?gkgvl950d38ka9c"]cm9_stock_kernel_dualboot.zip[/URL] - stock CM9 kernel with dual boot support for CM9 roms only. - Thanks to CM9 team
7. Reboot and test the rom on your SD Card. Make sure you test both roms on the SD Card and your phone to make sure they are working.
8. Once you are able to boot the rom on the SD Card, You can now restore your old rom, or flash any new rom you want.
Remember: If my dual boot kernel doesn't support your new rom, you need to flash my dual boot support kernel to boot the rom on SD card, and you need to flash a compatible kernel with your phone rom to boot your phone rom back.
Please note that my current kernels with dual boot support work with Samsung ICS or CM9 roms. I have not tested them with any GB rom yet, so be careful when you flash them on a GB rom or a different platform rom.
[SIZE="5"][COLOR="Blue"][URL="http://www.youtube.com/watch?v=c9UnqqaPdvo"][COLOR="Blue"]Video Tutorial[/COLOR][/URL][/COLOR][/SIZE] - thanks to ashwin123
[media=youtube]c9UnqqaPdvo[/media]
[url]http://www.youtube.com/watch?v=c9UnqqaPdvo[/url]
[SIZE="4"][COLOR="Blue"]Aug 09-12[/COLOR][/SIZE]
- First Aroma version support 2 roms on internal SDcard and 3 roms on external SDCard.
- Add GL NoteCore V12
- Add TMT MIUI kernel
Download link: [url]http://www.mediafire.com/?b2i954vve1gh1c4[/url]
July 30-12
- Add new SpeedMod K3-11 with dual boot support and fully adb root.
- Add Video tutorial - thanks to ashwin123
July-28-12
- Add new kernel GL NOTECORE V8.1 with dual boot support [url]http://www.mediafire.com/?60lt63qtvfqcs6b[/url]
- Preinstalled Liquid_Black_V 3.2 - [url]https://docs.google.com/open?id=0BwDBny0G97K5Z1FuMnh0M2otVG8[/url]
July-26-12
- Add new kernel GL NOTECORE V8 with dual boot support [URL="http://www.mediafire.com/?6p5wapyps7q5qe8"]download link[/URL]
- Re-word the instructions. Much simple and faster to set-up.
Version 3.2
- Updated to SpeedMod-K3-9 source
- Optimized booting time - (about 6 seconds faster than original SpeedMod-K3-9)
- Add feature to safely share data partition if the two roms are the same base but different mod/theme.
- Update SD Rom by extracting system and data folder to /sdcard/SDRoms/update/ - experiment (report if it works for you)
Version 3.1:
- Add feature to put the update.zip in the /sdcard/SDRoms/update/ folder for flashing a mod/theme on the SD Rom.
- Create a file "wipe_dalvik-cache" file in the /sdcard/SDRoms/update/ folder to wipe dalvik-cache on the SD Rom. (simple and fast)
or simply flash this [url]http://www.mediafire.com/?690wyv2zt5j7185[/url] ro wipe dalvik-cache on the SD Rom.
Version 3:
- Updated to SpeedMod-K3-7 source
- Add script to wipe data & cache for rom1 on SD Card. You can also save 1.1 GB space with this. This contains empty data and cache partition images and extract them on your SD Card. You can also save a lot of time & space by simply copy the system to sd card, and then flash sd_internal_rom1_wipe_data_cache.zip
Version 2:
- Updated to SpeedMod-K3-6 source
- Add default rom value in bootsdrom.cfg. Now you can set default rom (phone or sdrom) by changing the default value in the config file.
- Add CMW restore scripts to restore sdrom back to phone rom.
- Some minor tweaks.
Version 1:
- Initial release
- Fix the mounting bug (swaping external and internal sd card) - Kernel/CWM

Could you make an app?
It would be easy to make some $.

Not right now, this requires some kernel modification which is not easy to do in an application. The app may help to flash the rom on SD card faster and easier, but can't change the kernel itself.
hi1 said:
It would be easy to make some $.
Click to expand...
Click to collapse

Good luck for this project
Will try it out sometime...

Nice concept.. I always want to have dual boot for Samsung and AOSP/CM based ROM... But now, wait until we see a one-for-all kernel like siyah to be developed for our Notes..

Wow ! Waiting for such a thing !
Will install it and see ....

How can I delete the Rom on SD again, if I don´t want it anymore?
And to be sure the SD means the external SD.
thanks for answer
Edit: sorry to say, but ur links are 404 Error, can´t download anything

Just delete the SDRoms folder on your internal SD card. SD means internal SD. You can move it to external SD by changing the bootsdrom.cfg values.
hara74 said:
How can I delete the Rom on SD again, if I don´t want it anymore?
And to be sure the SD means the external SD.
thanks for answer
Edit: sorry to say, but ur links are 404 Error, can´t download anything
Click to expand...
Click to collapse
Sent from my GT-N7000 using Tapatalk 2

chuandinh said:
Just delete the SDRoms folder on your internal SD card. SD means internal SD. You can move it to external SD by changing the bootsdrom.cfg values.
Click to expand...
Click to collapse
With changing that value, is it possible to get triple boot?
I imagine to have:
- CM/AOKP in the main ROM
- custom ROM based on TW on internal SD
- official ROM on external SD.

Download link
http://www.mediafire.com/download.php?xc03yg1wjjzziys

I would give it a try if the download links would work
and thanks for the quick answer
I think it´s really cool to have two Roms on our Note to play with
Edit: too late, first Link is back again

CM/AOKP is not supported right now.
Here is an example of the values in the bootsdrom.cfg file
rom=/sdmnt/SDRoms/rom1
system=/sdmnt/SDRoms/rom1/system.img
data=/sdmnt/SDRoms/rom1/data.img
cache=/sdmnt/SDRoms/rom1/cache.img
After you are done copy rom to SD card, you can rename the rom1 to rom2 in the SDRoms folder. Then change the values in the config file like this
rom=/sdmnt/SDRoms/rom2
system=/sdmnt/SDRoms/rom2/system.img
data=/sdmnt/SDRoms/rom2/data.img
cache=/sdmnt/SDRoms/rom2/cache.img
If you want to use external SD instead.
Copy the SDRoms folder to your external SD
then change the config file values like this. sdmnt1 means external SD.
rom=/sdmnt1/SDRoms/rom1
system=/sdmnt1/SDRoms/rom1/system.img
data=/sdmnt1/SDRoms/rom1/data.img
cache=/sdmnt1/SDRoms/rom1/cache.img
mbudh said:
With changing that value, is it possible to get triple boot?
I imagine to have:
- CM/AOKP in the main ROM
- custom ROM based on TW on internal SD
- official ROM on external SD.
Click to expand...
Click to collapse

is there a way to change that it boot normally the phone Rom and press home button only if I want to boot the SD Rom?

Wait for my next update
Sent from my GT-N7000 using Tapatalk 2

I tried the setup.zip but the is no bootsdrom.cfg file in SD Rom folder
I tried it twice.
so I cannot boot the SD Rom
any suggestions?
no root! for phone Rom
for first problem I copied over the bootsdrom.cfg in the folder and it works,
booted the SD Rom and it has still root
but now I can´t boot Phone Rom with holding Homebutton
now I can switch between the Roms by rename bootsdrom.cfg to .bak
but it always been optimizing the apps when switch the Roms
I get root back for the Phone Rom :laugh:

I get it nearly all to work :laugh:
only things are that the homebutten at booting doesn´t work, have to rename the bootsdrom.cfg into .bak for booting phone rom
and
the optimizing all apps at switch between the roms
but therefor it´s REALLY cool and I THANK YOU again for your GREAT WORK :good:
I always searched for a thing like this

Really great work
Looking forward ti seeing you porting it to cm9 kernel
Sent from my GT-N7000 using xda premium

a few little things that I noticed:
- after each switch I have to decide which Home Launcher I want to use
- the widgets I place on Nova Launcher are the same on both Roms, so I guess if I use the same Launcher I can´t use different Widgets by default
- the Icon Quickpanel Settings is shown in one Rom but in the other Rom the Icon is shown as not installed, so I have to put it again from app drawer to the homescreen
- and I tried to copy the files from sd_rom_setup into the right folders so that the homebutton work, but it doesn´t work

realy great job mister...
will learn how to implement..
now i can put also switch my fav rom... albafinalstage n cassie 4.5 slim :thumbup:

[HOW TO] DUAL BOOT for P990 & SU660 on BOTH Bootloaders v5.0

Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.​
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread

Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.​
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!

Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....

This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post

This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job

Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate

Nice ! Trying soon... :fingers-crossed:

SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.

i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?

what about ics and gingerbread on dual boot!?

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)

Nice man" I ll try it soon!

jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.

I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!

Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:

And what about dual boot with linux?

tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.

sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).

tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...

How about flashing the second rom that have aroma installer??

[Solved] No sdcard after flash The_apes Flashable zip in clockwork

Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0

Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download

Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !

You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.

Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea

Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!

I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...

Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha

[MOD][KK+]MultiRom v22a && TWRP 2.6.3.x (20.02.14)

Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff​
Taken and modified from official thread at Flo
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Manual installation
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
​
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Updating/changing ROMs
Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)​
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.​
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM​
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni

Reserved
Great work
Sent from my LG-P880 using Tapatalk

Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system

Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD

Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice

Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..

Nice work, could I ask you to prepare multirom uninstaller also?

It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.

Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app

Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk

dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds

Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880

remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...

I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.

Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880

love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release

Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?

Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff

For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .

not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?

[HOWTO] Changing Filesystem to F2FS on the Sprint S4

This guide is for the Sprint Galaxy S4 only and as of now it is only compatible with two kernels: KToonsez S4 Kernel 4.4 AOSP (4/17 or later) and PoKernel 1.7 F2FS ONLY Build. This guide CANNOT be used on Touchwiz or Android 4.3 yet. I will update it when and if that becomes possible
*Disclaimer: You are doing this to your phone under your own consent. This is an experimental procedure and may not work on some hardware revisions or on devices where certain conditions are not met. You assume all the risk by flashing any of the software below or changing your filesystems. I am not responsible if your phone does not work based on the method I am describing below. Modify at your own risk.
This guide had to be updated in order to correct misinformation. The guide will follow KT's instructions explicitly until it gets to the formatting of the system partition
***If you want to format your /system partition to F2FS please read that section first as it requires steps to be taken from your currently working AOSP rom!***
First, go this link download the file:TWRP-KT.ALL-IN-1.zip
http://goo.gl/HLz4al
Formatting Data and Cache to F2FS
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and check the box to force F2FS for data and cache (you can also check the box to include /system partition if you want to convert your ROM's zip to use that too)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
Formatting System Partition with F2FS (Required: KT SGS4 Kernel 4/28 or later!)
Steps:
1.) Before doing any F2FS conversion with the above instructions, use your currently working AOSP ROM to grab the AOSP 4.4 Kernel from HERE (4/28 or later only!) and save it to your external memory card
2.) Once it is saved reboot to recovery and install it (Flashing a kernel in TWRP is Install -> Folder where kernel is -> Click KT 4/28 kernel -> Swipe to install -> Clear cache/dalvik -> Main menu -> click advanced -> Fix Permissions -> Reboot to system)
3.) After you are back in your working AOSP ROM with KT 4/28 kernel installed, download the AOSP rom you want to use and save it to your external sd card (You can leave the filename as it is, the program will rename it for you)
4.) Open KTweaker and click "Tools" and at the very bottom choose "F2FS: Convert ROM ZIP"
5.) It will ask you to locate the file, ask if you're sure, and then it will do the conversion; upon completion the zip file that was created will have "-F2FS.zip" at the end of it
6.) Now you can follow the steps above, but when you get to step 9A you will use the "-F2FS.zip" file instead of the standard ROM file
This procedure is necessary because KTweaker changes your favorite ROM to pass the command mkfs.f2fs so that your system partition is formatted to F2FS before the files are installed. I did this myself to verify and it works a treat. One crucial step to remember though is that after you install your F2FS converted ROM you absolutely must install KT's kernel so your phone will boot.
Returning to EXT4
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and uncheck the box to force F2FS for data and cache (If you checked the box to include /system partition uncheck it first)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
FAQ
Q: Why can't I use this on Touchwiz?
A: It has been developed for the most recent Linux kernel 3.8 and has been implemented in kernels built for 4.4.x OSP builds. This isn't to say it cannot be used on Touchwiz, it is a filesystem and as long as there is a kernel that offers support for reading it installed on your device it should theoretically work on your hardware. However, this can be proven/disproven by the devs here and I will update this answer if it cannot be implemented in a backwards fashion.
Q: Are there advantages to using F2FS?
A: It is built and intended for use on flash filesystems which our devices run exclusively. So since it was developed for flash memory there will be a benefit to using it as it matures. However, this does not imply that benchmarks will increase or your whole phone will become more responsive, its intent is to have files be accessed and written more efficiently. It is supposedly also built for the long-term user who does not constantly reformat their devices because it is supposed to handle large amounts of old files and cleaning more effectively that EXT4. Source: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
Q: Will this trip Knox?
A: No more than installing a custom recovery would. So if you already had a custom recovery (Read: TWRP, PhilZ, CWM) in place you are safe following this guide. For now of course; I do not know if there will be another iteration of Samsung software that locks down the device futher.
Q: Can I clear Cache and Dalvik to troubleshoot after changing my filesystem?
A: I tried this myself and the answer is yes. As long as you are using the F2FS custom recovery made by KToonsez you can wipe Cache and Dalvik from recovery and it will rebuild your system. Something I did notice is that first boot will stay on the splash screen longer with F2FS than with EXT4. I saw it hang on the splash screen of my Liquid rom for an extra minute before actually booting and showing cache rebuild. **Your Mileage May Vary**
Q: Why isn't the System Partition formatted into F2FS?
A: This can be done now with KTweaker. See section above.
Q: What ROMs can I use with this filesystem?
A: Any 4.4.x rom (most are 4.4.2 now) that is compatible with either KToonsez S4 AOSP kernel or Pokernel 1.7 F2FS Only.
Q: In Advanced Wipe, Preload has been added to the options of things to wipe. Should I?
A: Ktoonsez answer found HERE was that he has never wiped preload. So I suggest against it unless you know what you are doing.
Thanks
Linux, Google, and Samsung (all this neat stuff comes from those communities)
TWRP Team for their custom recovery and its updates
Ktoonsez for his awesome kernel and the modified recoveries
CPA Poke for his awesome kernel that has F2FS support baked in
LuigiBull23 for edits and reminding me to add content
XDA for giving us a place to host experimental phone procedures
The XDA Devs for all the work they do for us with their time
The XDA community for providing feedback and making this a great place to hang out
If I forgot anyone specifically please let me know and I will update this section or any section
Enjoy and let us know how it works on your device!

Great guide my friend!

delete

Thanx great guide
Sent from my SPH-L720 using XDA Premium 4 mobile app

Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk

Mistertac said:
Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Hello again.. Lol
The ramdisk mod is now obsolete as it's already included in the kernel zip, which will automatically determine whether you're still on EXT4 or F2FS and make the required changes to the ramdisk accordingly. So no need to flash anything but the kernel as usual after following the steps.

OK yea I figured it was either to do with what I said or to do with the kernel obviously. Just figured I'd ask anyways
Sent from my SCH-I545 using Tapatalk

I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!

I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!
Click to expand...
Click to collapse
I understand. A lot of people were and still are confused about these files..
In short, during the testing phases of F2FS, KT compiled a separate zip for changes to the ramdisk that in turn would reflect the EXT4/F2FS mount points as a means to avoid possible bootloops and such. It was indeed a success and as a result was included in his kernel.
Now, upon flashing the kernel it is able to determine which partitions are formatted as EXT4 or F2FS and mod the ramdisk accordingly. He only left the files on his server in case he ever needed them again. So they are most definitely OBSOLETE. You certainly wouldn't have gone wrong using the term in this case.

Updated the guide for KT's new all-in-one TWRP recovery that will allow you to switch back and forth between F2FS and EXT4. I used his exact instructions from his guide in all areas except for the system formatting section which I wrote. If you are using his custom TWRP recovery go ahead and grab the new one so you can use it in the future!

F2FS with CM11 Nightly
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?

mwilder817 said:
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?
Click to expand...
Click to collapse
I know it has been forever since you posted this and I apologize for the late answer, but I imagine that if you received that error you got a bad download of CM11. I've personally converted the snapshot and several nightlies of CM11 and they all passed nicely.
So for anyone getting this, if you get a similar error message: Re-download the ROM you are converting

to bad its still not possible with touchwiz, love to use f2fs on a stock rom for my sgs4-lte.
is it possible in the near future that we can use f2fs on those devices with a Samsung stock rom, using another kernel is no problem.
or is this hard to tell ?

Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.

RealMikeyTaylor said:
Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.
Click to expand...
Click to collapse
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!

mwilder817 said:
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!
Click to expand...
Click to collapse
But doesn't it have to be in EXT4 for it to work for a GPE ROM?

RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
You are probably right. I haven't tried the GPE ROM yet.
Sent from my SPH-L720 using XDA Free mobile app

RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
Yup gpe uses ext4 on all partitions because it uses tw framework