Dual Boot for SGSA
So many devices are getting Dual Boot capability nowadays.So i decided to do same for our beloved SGSA.
EDIT : Guide Updated. Using slow sdcard as /system and /data was bad idea. Now secondary ROM work at same speed as primary ROM since we aren't using external SD card anymore
Read first three posts carefully before doing anything
Highlights:
No lags, bugs.Both ROMs works almost same
Stable. Booting of ROM is based on kernel. So as long as you stay on a kernel it'll keep booting ROM for which it is designed without interference with another ROM.
ROM can be switched by changing Kernel.
Stock ROM fully supported. Now you can feel speed of CM ROM with stability of stock ROM
Click to expand...
Click to collapse
How to use this:
Well, steps are quite easy.Just follow them one by one and you won't get any troubles.But please follow steps one by one, don't take shortcuts.
On PC extract ROM which you want to install as secondary ROM.
You'll get following files/folders there : META-INF, system, boot.img
Delete META-INF and boot.img
Download appropriate META-INF_*.zip from downloads section.Extract it and move extracted META-INF folder to location from where we deleted META-INF.
Navigate to /system folder and move folder named app to parent folder (i.e. if app folder is located at C:\blah\system\app then move it to C:\blah\app)
Select three folders (META-INF, system, app) and compress them to zip format.Push this file to device.
All above steps are mentioned in below video
Download appropriate Kernel from Downloads sections.
Flash that kernel using Universal Kernel Flash Tool or by writing in terminal dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
Power off your device
Now reboot into recovery by holding VOL UP + HOME + POWER (don't take shortcut here )
Ignore any warnings recovery shows.
Install the zip file which you pushed before as you install normally (Do not use Wipe options)
Download appropriate GAPPS package from download section (Do not install normal gapps.To know reason, read third post)
Reboot it.That's all (Keep in mind, first boot always takes long time)
If WiFi don't work on secondary ROM then flash appropriate modules from Downloads section
Read "Things to keep in mind" in third post.
Click to expand...
Click to collapse
How to switch ROM:
Flash kernels provided here to boot secondary ROM.
Flash native kernel (which comes with ROM) to boot primary ROM. (If you're using CM based primary ROM then take backup of stock CM kernel before flashing another kernel.)
Click to expand...
Click to collapse
How to change ROM:
Boot up your primary ROM.
Navigate to /data
Delete folder : /data/secondary_data
Now flash secondary Kernel and flash secondary ROM as you would.
or you can use my App for doing this stuff...
Click to expand...
Click to collapse
Using DualBoot App:
After installing secondary ROM as mentioned above, you can use my Dual Boot app to switch easily between ROMs. Additionally you can also use it for other options like sharing installed apps, factory reset secondary ROM etc. It will automatically download required kernel (Read third post). App is easy to use, just install it as Normal apk. You can also share this app with secondary ROM as mentioned below.
Wipe data/factory Reset - Factory reset secondary ROM
Share Apps with Primary - Share all apps of primary ROM with secondary ROM. This will reduce space used by secondary ROM. Use this option with CAUTION because some apps like Play store can FC. So it is better to use custom share apps option.
Revert Share Apps with Primary - This will remove all installed apps of secondary ROM
Custom Share Apps - Best way to share installed apps on primary with secondary ROM. Share as much apps as possible to reduce storage usage by secondary ROM.
Clean UP - Removes all files used in DualBoot mode
And more to come...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
Technical info:
--> Mounted /dev/block/mmcblk0p4 as /system
--> Since it is smaller (300 MB) in size we're symlinking /system/app folder of secondary rom to /data/app
--> Using /data partition for both /data & /cache of secondary ROM
Click to expand...
Click to collapse
Future Plans:
An App so things become more easy (done)
Kexec support in kernel (WIP)
Click to expand...
Click to collapse
Sources:
Kernel Sources : Checkout TeamCanjica's repo
DualBoot App : Github
Click to expand...
Click to collapse
I'm writing an app for this.Once it is completed it would be much easier to do this thing
As usual, i don't take any responsibility of bricked devices, nuclear wars etc...
Downloads & Changelog
Downloads:
EDIT:
Since Dev-Host removed all my files i've re uploaded them to mediafire (Link to folder below). Since all files are removed from my account DualBoot app won't be able to download kernels. So manually download them and put them on sd card as instructed.
META-INF:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK) || Liquid Smooth 3.0
Click to expand...
Click to collapse
Kernel:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK)
Click to expand...
Click to collapse
Modules:
CM 11
Click to expand...
Click to collapse
GAPPS:
CM 10.1 || CM 10.2 || CM 11
Click to expand...
Click to collapse
Download META_INF, Kernels, GApps:
Mediafire Folder
Click to expand...
Click to collapse
DualBoot Application:
DualBoot v1.22
Click to expand...
Click to collapse
Changelog:
27/04/14 ---> Fixed FC problem on CM11, Kernel with OC support (same as TC's last release)
21/02/14 ---> Liquid Smooth 3.0 Support
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI v5 Support
21/01/14 ---> DualBoot App released, Updated META-INF folder for latest CM10.2 to fix errors
08/01/14 ---> Fixed bug with CM11 which was preventing it from booting second time
06/01/14 ---> CM11 support
04/01/14 ---> No need for external SD card.Both ROMs work at same speed, no more lagginess
11/11/13 ---> Initial Release
Click to expand...
Click to collapse
DualBoot App Changelog:
27/04/14 ---> Unsupported device problem fixed, Updated all kernel links
12/02/14 ---> Fixed AOSP, Removed app folder share (use custom app share instead)
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI support. Allows user to flash unknown kernel to use any ROM as Primary ROM
21/01/14 ---> Initial Release
Click to expand...
Click to collapse
Pros, cons, Tips, Future Plans
FAQs:
Q. How can i factory reset second ROM?
A. Boot into primary ROM and go to /data/secondary_data using any explorer and delete following folders : cache, data
Click to expand...
Click to collapse
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder.Now delete all contents of /cache folder.
Click to expand...
Click to collapse
Q. WiFi is not working on secondary ROM. What should i do?
A. Boot into secondary ROM's recovery and flash appropriate modules from downloads section
Click to expand...
Click to collapse
Things to keep in mind:
Wipe/data Factory reset from primary ROM will remove secondary ROM also.
Do not wipe cache partition after installing this mod (for both primary & secondary ROMs).
Don't touch anything other than install zip ( like wipe data/cache etc because they'll lead to unexpected results ) when using secondary ROM's recovery.
We're running out of space for /system partition in secondary ROM so please don't keep flashing random tweaks, mods which put files on /system partition.If it is emergency then use /preload partition and symlink them manually.
Do not install GAPPS for secondary ROM.Use only which i provided.
When CM based ROM is installed as secondary ROM then by default swap functionality is disabled on /preload (which TeamCanjica enabled).So stock ROM as primary ROM is compatible.
Ignore any warnings shown by secondary recovery.If you get any error then contact me.
Provided GAPPS are not full gapps it'll only install Play Store s that you can install other apps from market.
We have 2GB space in /data partition.I've been using this device for 9 months and it never took more than 1GB space on /data.But still if you're finding less storage then move some apps to sdcard.Still if you need more then contact me, we'll move some more files.
If you want to dual boot CM & stock ROM then it is necessary to install stock as primary because they're huge to be included on /cache partition.Although it is not impossible, if you're expert there, then you can create symlinks to make it work.But i won't support that way.So secondary ROM must be CM based.
Backup/Restore function won't work with secondary ROM
When wiping primary rom, it is impossible to save secondary rom unless you made backup.
Even though Dual Boot app downloads kernel automatically, it is advised that you download required kernels & manually and put them in proper folder ({internalsdcard}/DualBoot/) to avoid bad & corrupt downloads. In case if this happens & you phone don't boot up, don't worry, just flash stock kernel with odin & everything will be fine.
Click to expand...
Click to collapse
How to add Support for Unsupported ROM:
This tutorial will help you to add support for those ROMs which are based on already supported ROMs (like CM11, CM10.2 etc). This tutorial will teach you to create META-INF folder for particular ROM to avoid status 7 error. Please follow it carefully
Open META-INF\com\google\android\updater-script
Find and delete following code/ same code
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
Now find
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
& replace /dev/block/mmcblk0p3 with /dev/block/mmcblk0p4
Search for package_extract_dir("system", "/system"); & add this code after it
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/primary_data");
run_program("/sbin/busybox", "mkdir", "-p", "/primary_data/secondary_data/system");
delete_recursive("/primary_data/secondary_data/system");
package_extract_dir("app", "/primary_data/secondary_data/system");
symlink("/primary_data/secondary_data/system", "/system/app");
At the end of the script remove package_extract_file("boot.img", "/dev/block/mmcblk0p15"); or anything related to kernel flashing like write_raw_image etc.
Click to expand...
Click to collapse
Awesome...:good:
Wanted to try it but I have a 2gb memory card...
So I will have to Wait till my new memory card arrives:fingers-crossed:
i have a class 10 sd card..i ll try this as soon as i can..just a thing...AWESOME
Sent from my GT-I9070 using XDA Premium 4 mobile app
tried but not work. it just boot direct to recovery
wmfaiz said:
tried but not work. it just boot direct to recovery
Click to expand...
Click to collapse
Yep because you messed up with our param drivers.As i told before don't use any command like reboot recovery and don't use 4 way reboot (if your ROM supports) to enter recovery.This will keep you throwing into recovery.The solution is flash primary ROM's kernel then reboot normally.Use UKF to flash secondary kernel.Now power off your device and then use Hardware keys to enter recovery or if you've already installed secondary ROM then power on normally.
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
frapeti said:
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Thanks.I'm waiting for next build because last build has lzma compressed zImage.
dual boot?
cool...
I was used dual boot on my old device Galaxy Tab 2, very useful for testing a new rom before become it that rom as primary rom for daily use
great work
Update
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Many thanks for your hardwork man! For achieving dual boot on our device and keep on simplify the method of doing it. It is also happy to see that there is another app under developing to make things more easier, i will definitely try this out once i finished my exam!
Thanks a lot man :thumbup:
I will use it when you will add CM 11 compatibility.
BOOTMGR said:
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Click to expand...
Click to collapse
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
<O.T>
+1 to each thing in above post....
let me again tell u that you r really really AWESOME :angel: :laugh:
btw idea of debloating HJ is good ......personally i'm using heavily debloated HJ without any feature loss
BOOTMGR said:
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
I assume Primary ROM must be 4.0 or higher and not GB?
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
anantttt said:
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
Click to expand...
Click to collapse
Yeah it can be fitted as secondary ROM by debloating.But still some users will ask for some features.We can even use symlinks and can place it as secondary ROM without debloating it but it'll raise complexities.So it is better to use it as secondary ROM.
Odexing and placing them on /preload i also nice idead.But still i'll prefer to use it as primary ROM...
BTW,HarshJelly seems better than BOOTMGRjelly...:silly:
purplepizza said:
I assume Primary ROM must be 4.0 or higher and not GB?
Click to expand...
Click to collapse
Yeah.No support for GB (i'll think about it.If there won't be much difference (except baseband) between GB and JB we can also do it.)
darcik said:
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
Click to expand...
Click to collapse
Yesterday @Sami Kabir asked same question on FB group.Here is the answer.
Only apps can be shared between both ROMs not their data.The reason is that data of system apps and normal data apps both are stored under same folder (/data/data).So can't we share this folder? answer is no because namespace conflicts will arise there (Ex. package name for phone app is com.android.phone.It'll remain same for all android versions.It is possible that use have installed both ROMs of different API level.So if one phone app stores its data under /data/data then other won't be able to read it and you'll get FC)
Although it is possible to share apps between two apps.When i'll complete app, i'll provide an option for that....:good:
Cache partition
FAQs:
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder
Click to expand...
Click to collapse
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
CM11 Support
darcik said:
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
Click to expand...
Click to collapse
Yeah i forgot to write, you also need to delete contents of /cache folder or format cache partition.
That partition is like placebo.It is only used when upgrading android (that means generating dalvik cache (actually that partition was used to store dalvik cache but later on dalvik cache was also moved to /data partition so its useless now except time of generation of dalvik cache)
@all:
Added CM11 support.
Links are up.
Method remains same.
I've checked way to share apps between ROMs (and thus storage use will be much less).
I'll let user to choose whether to share apps or not which will be possible through DualBoot app.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INT2EXTV2+ Posted
If you like it please click thanks on this post and give it a rating
Thanks to all users and contributors
About:
CronMod INT2EXT was wrote for use in my rom with the goal to achive a stable and fast way of moving the data partition of your phone to the sd-ext partition, they are available for all users and developers to use in any rooted rom with init.d support.
CronMod INT2EXT scripts are the first universal INT2EXT method released
Developer Stuff Next Post
Features:
(All scripts are tested on Android 2.3.7 - 4.2.2)
INT2EXT
-Mounts /sd-ext to /data
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4
-Mounts /sd-ext to /data
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXTV2+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
-Supports SWAP2INT
-Completely universal (Testing is needed)
Prerequisites:
-Rooted Rom with init.d support
-SD-EXT partition
-100mb internal is needed for every 500mb sd-ext
SD Card Partitioning:
Partition 1 - Fat32
Partition 2 - Ext 2/3/4
Install:
(Instructions based on ClockWorkMod recovery)
-Download Chosen Script Below
-Place on root of your sdcard
-Reboot Recovery
-Select "install zip from sdcard"
-Select "choose zip from sdcard"
-Select "CronMod-****_signed"
-Select "mounts and storage" category
-Select "format /sd-ext"
-Reboot
(if you already use a A2SD/D2EXT/INT2EXT/M2SD script then you will need to remove it completely)
Downloads:
(Please leave feedback)
INT2EXT
INT2EXT+ (Recommended and featured in CronMod Roms)
INT2EXT4
INT2EXT4+
INT2EXTV2+ (This script is a new int2ext script that should fix all bugs, it cannot be flashed over previous versions, please test and leave feedback)
Dalvik-Cache Wipe Tool (This is for wiping /dalvik-cache when running a INT2EXT script)
Extra:
Bravo/Bravoc GB thread
Bravo/Bravoc JB thread
Dream thread
Sapphire thread
Bugs:
-Some phones can experience a low sound bug (fix: run fix-permissions or try INT2EXTV2+)
Credits
-Wes Garner - "Auto ZipAlign Script"
-CyanogenMod - "Bind Cache Script"
-Matermind1024 "Help with resolving IMEI and Baseband issues"
-vvFICKvv, DK75, and Dark Passenger "Help to fix compatibility issues with Android 4.2.x"
[email protected] "Code to check if mmcblk0p2 exists"
-BlazinReign (my girlfriend) "donating her old laptop to the cause, and putting up with my development work "
-XDA "hosting the fourms"
Donators
(if you make a donation and your name is not here send me a pm)
[URL="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RXYPT5A5ACJ7W"]
[/URL]
Developer Area
Developer area
Info
These scripts are for use in your roms if you like them and want to include them all i ask is that you give me proper credit in your thread.
Instructions
To include one of my scripts in your rom just add it to the init.d folder and rename it to 40a2sd/40d2ext/40int2ext depending on the chosen script, if you choose a d2ext/int2ext script then remove the "06mountdl" or "06BindCache" if they exist as the script will do this from now on.
CronMod A2SD/D2EXT/INT2EXT Scripts for Developers
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
rmg2 said:
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
Click to expand...
Click to collapse
They activate on boot and do not require a reboot after firstboot like most d2ext
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
jackson0829 said:
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
Click to expand...
Click to collapse
thanks for the feedback glad you like it
D2EXT or D2EXT+
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
gonzalocav said:
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
Click to expand...
Click to collapse
i prefer the d2ext+, the int2ext is like d2ext but uses no symlinks
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
siavash2death said:
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
Click to expand...
Click to collapse
i dont use mount2sd so i am unsure, i would recommend if you need stability to use d2ext+ because the int2ext scripts are not long term tested.
Works with the wildfire s, no need to reboot twice to get d2ext+ working, in first boot after rom install working flawlessly. Thanks
andreasf93 said:
I am unsure what to use. I have a Galaxy Mini with very low internal memory. I should install A2SD++ right?
Sent from SGM using CyanMobile
Click to expand...
Click to collapse
try a d2ext script first they give the most space, if you find it to slow use a a2sd script instead
Currently trying A2sd++ on Lg500h Cm7 nightly 7/01. Simple enough to setup, and works flawlessly, keep up the good work :thumbup:
Sent from my LG-P500 using xda app-developers app
is possible to use this script in a sense rom? thank you
katurras said:
is possible to use this script in a sense rom? thank you
Click to expand...
Click to collapse
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
andreasf93 said:
I tried both D2EXT and A2SD on cm7.2 official galaxy mini and none worked. Applications get installed in internal memory as usual.
Click to expand...
Click to collapse
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
croniccorey said:
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
Click to expand...
Click to collapse
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
katurras said:
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
Click to expand...
Click to collapse
thank you i will try to make 1 for sense roms
hi
getting Status (0) error.what am i doing wrong
Running df
croniccorey said:
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
Click to expand...
Click to collapse
I thought I installed D2EXT+ and it was working. But I see this image and I don't know now...
Is it working?
Features:
install zip from sdcard or sideload into system1 or system2
mount and format system1 or system2
fix permissions on system1 or system2
set bootmode to system1 or system2
automatically checks for install-recovery.sh on both systems and asks you if you want to delete them
TrueDualBoot
TrueDualBoot notes:
Enabling or disabling TDB will completely wipe your data-partition. Once enabled your data partition will be VIRTUALLY split which means that both systems together can use the full space of the data-partition.
There are some things which will break TDB:
everything which removes CWM(like Xiaomi Updater App's live install)
ROM's which don't support mount_ext4.sh (I did not see any ROM without support yet)
Changelog:
Code:
2014-07-08:
- update to 6.0.5.0
- fix CWM's recovery updater
2014-05-10:
- update to 6.0.4.8
- enable swipe
2014-03-23:
- kernel change to allow "adb reboot dload"
2014-03-15:
- fix restoring backups with TDB enabled
2014-03-13-2:
- fix error when installing zip's
- unmount data when switching system
2014-03-13:
- update to CWM 6.0.4.7
- use opensource(4.4) kernel
- USB-OTG support
- use global choice for system
- prepare for merge into CM(for official CWM)
2013-11-15
- support 4.4 roms
2013-05-24:
- update to CWM 6.0.3.2
2013-04-13:
- fix flashing modem1
2013-04-06:
- update kernel to fix boot on MIUI since 3.4.5
2013-03-24:
- update to CWM 6.0.3.0
- block access to recovery partition from android
look here for more information: [URL]https://github.com/M1cha/android_bootable_recovery/commit/333f6101e155ebe4e6eba577719fd13680e06c71[/URL]
2013-03-09:
- introduce TrueDualBoot feature
- backup/restore boot1 because it was missing in first release(CHECK YOUR OLD BACKUPS!!)
- show existing images in advanced restore menu only and provide system-selection
- merge upstream commits(from cyanogenmod)
2013-02-22:
first release
=========== IMPORTANT ===========
I removed all builds of CWM, Philz, etc prior 2014-07-08 because
this new version contains a important fix.
Also check the new point "4" in installation notes below.
if you want to make sure everything went well after you booted into your ROM,
open the file /system/bin/mount_ext4.sh and check if there is this line somewhere
at the bottom of the file:
NO_HIDE="$(getprop ro.keep.recovery.partition)"
================================
Download:
http://d-h.st/users/M1cha/?fld_id=11289#files
Sourcecode:
https://github.com/M1cha/android_bootable_recovery/tree/cm-10.1
Donate:
I do this just for fun but if you like my work it would be great if you want to spend me a beer
Installation:
Download latest recovery-signed-***.zip
if you are on stock recovery: Copy the file as “update.zip” in the root directory of your sdcard
Reboot into recovery and install the zip file
if you come from any other recovery or from CWM pre-2014-07-08, DIRECTLY reboot into recovery again before doing anything else so the dualboot(even without TDB) hook's will be updated.
Final notes:
Please be aware that your phone has only ONE data-partition. If you have TrueDualBoot disabled that means:
You can't install AOSP and MIUI on one phone
If you wipe your data, the settings in both systems will be deleted
Furthermore you shouldn't use the feature of MIUI-Updater app which lets you install during running system. Otherwise you'll have to reinstall CWM after every update.
Bootloader MiRecovery is now locked, installation with fastboot only.
Στάλθηκε από το TPC1057 μου χρησιμοποιώντας Tapatalk
NightHeron said:
Bootloader is now locked, installation with fastboot only.
Στάλθηκε από το TPC1057 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Small but important correction: RECOVERY is locked.
I think I have read somewhere that there is some kind of updater.
Is there any app to update or do I always have to flash the zip?
CM11 updates CWM with every nightly if u enable this in the Developer settings.
does it cwm touch recovery for Mi2* in plans?
Bucci said:
does it cwm touch recovery for Mi2* in plans?
Click to expand...
Click to collapse
no because it's closed source and CWM isn't maintained by koush anymore.
What do u think about Phil touch recovery?
TDB
About TDB, when System1 & 2 contains the same app, will they use the same folder in data partition to store things which means the app will share the same data in two systems?
Alting said:
What do u think about Phil touch recovery?
Click to expand...
Click to collapse
A old version of this exists already but I don't have time to maintain this.
riowong said:
About TDB, when System1 & 2 contains the same app, will they use the same folder in data partition to store things which means the app will share the same data in two systems?
Click to expand...
Click to collapse
no, I hope this explains it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
m11kkaa said:
no, I hope this explains it:
View attachment 2948994
Click to expand...
Click to collapse
Thanks for the partitions layout. I'm new to data_root. Since I will install many many apps in userdata originally, will the storage space be shrinked in using data_root? Or would you mind quote any websites for me to read more about the data_root please?
riowong said:
Thanks for the partitions layout. I'm new to data_root. Since I will install many many apps in userdata originally, will the storage space be shrinked in using data_root? Or would you mind quote any websites for me to read more about the data_root please?
Click to expand...
Click to collapse
data_root root is just a mountpoint.
mountpoints are any folders where you can access the files of a partition. (unlike windows, where u have driver letters like C or D, you bind partitions to folders).
so instead of mounting the data partition to /data TDB mounts it to /data_root.
Then a special linux feature called "bind mount" is used. that just means that instead of mounting a partition to a destination directory, you mount another directory(ANY) to the destination directory.
This way TDB can either bind /data_root/system0 or /data_root/system1 to /data.
if you would insert your NAND as a harddrive to your computer and open the data partition your would see these two folders then.
This means that all the space of the data partition is shared for both systems. there's no fixed line or anything, both together can use all available space.
So may I say when there is the same app called ABC installed in both systems, there will be two folders for this app located in /data partition?
Yep
And may I say the /data_root is mainly to store symbolic links to redirect to /data?
riowong said:
So may I say when there is the same app called ABC installed in both systems, there will be two folders for this app located in /data partition?
Click to expand...
Click to collapse
what i can say from my experience is, that same version apps share the same folder, Tapatalk for example...
Sent from my MI 2 using Tapatalk
riowong said:
And may I say the /data_root is mainly to store symbolic links to redirect to /data?
Click to expand...
Click to collapse
Kind of. It may appear to you as if these were symlinks, but it behaves differently:
when you delete a symlink, the target file still exists.
when you delete a file in a mount-bind, it gets deleted also in the original mount location - because it is the same file, which was just shown on two locations.
---------- Post added at 07:33 PM ---------- Previous post was at 07:26 PM ----------
CBpbxEcmecmBeH said:
what i can say from my experience is, that same version apps share the same folder, Tapatalk for example...
Sent from my MI 2 using Tapatalk
Click to expand...
Click to collapse
Here you talk about "storage" rather than "userdata".
In TDB, the former is shared and the latter is unique for each of the 2 systems.
In other words, the two systems are not completely separated and some apps may have problems (if they put their version dependent data in "storage").
@m11kkaa
We have advanced restore, can we have advanced back-up?
I'm confused about Active partition and Manage partition options. When I install ROM, will it be installed to Active partition?
riowong said:
I'm confused about Active partition and Manage partition options. When I install ROM, will it be installed to Active partition?
Click to expand...
Click to collapse
Nope.
When you boot cwm it asks u which partitions to manage (system1 and system2). Everything you do is on the partition you selected at the start. You can change managed system by choosing it from the first entry. To change boot system you have to go to advanced > boot system and choose the system
Hello, am new here so if I did something wrong please correct me OK
-presentation:
we all love running latest android versions and install big a** games like asphalt 8 and have all the Google apps that we love
But in Janice it's some kind of impossible to do all of that ( come on its only 4 years old!!)
As they say no impossible under the sun now you can easily increase system or data or what ever partition your want just by flashing a Lil file and without losing a single file
-Warning:
Me and XDA are not responsible for any soft hard leaks or what ever you are doing this by your self!!!
Make a full backup(system data boot) before starting..
DO NOT USE THIS FILE WITH ROMS THAT USE CACHE (CM10.2)
-Requirements:
1. Janice or Janice-p(not tested)
2. TWRP Recovery (Any Version)
3. The attached file
Instruction:
1. Download the repartition file
-rename the file with your favorite partition sizes like "lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip" which means 1gb system 2gb sdcard and the rest will go to data partition so you will be able to install more apps
2. Boot into TWRP and make a backup
3. Flash the repartition file of your desire
4. Take a nap or watch big bang theory just waste some time
5. When the script finish restore your backup and reboot
6. Enjoy your games or what ever
-Credit:
1. @Lanchon
2. @madkita
If you want a file with your own sizes just write or in comments and i'll do my best to offer it to you
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=0.0625+wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add '+wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Lanchon said:
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=0.0625 wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add ' wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Click to expand...
Click to collapse
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
madkita said:
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
Click to expand...
Click to collapse
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Lanchon said:
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Click to expand...
Click to collapse
Yeah thank you updated OP
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
TheSteve87 said:
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
Click to expand...
Click to collapse
In TWRP it will be around 500-600mb with compression
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip
Just rename the file to this and your will have 1gb system 2gb SD card and the rest well go to data if you want to edit a partition size for example the number 1 after system means the system will be 1gb and the number 2 in front of SD card means the SD card will be 2gb and max in front of data means the rest well go to data partition
Preload and fota are partition used in only stock ROMs and stock based ROMs so if you are running a custom ROM this will give you more space in the partition your set to max
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
TheSteve87 said:
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
Click to expand...
Click to collapse
Yup it works if your wanna check system download a small app called disk info
If you want 3gb on sdcard change the 2 number in front of it this will give you 2gb on data
DaksAnkit said:
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
Click to expand...
Click to collapse
Yup 100%
Make a backup first and when resizing all partitions will be formated to ext4 then restore your backup it will automatically format them to f2fs
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
DaksAnkit said:
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
Click to expand...
Click to collapse
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
madkita said:
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
Click to expand...
Click to collapse
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
also so i have to now restore my backup to get back to cm13 coz i am stuck at recovery ? any shortcut,like(flashing cm13 kernel) to go back to system as it was before or i have to restore the backup ?
DaksAnkit said:
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
Click to expand...
Click to collapse
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
madkita said:
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
Click to expand...
Click to collapse
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i just install my backup and that is it ? right !!
DaksAnkit said:
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i ust install my backup and that is it ? right !!
Click to expand...
Click to collapse
Yup just restore your backup and you're done ?
madkita said:
yup just restore your backup and you're done
Click to expand...
Click to collapse
alrighty then !!
:good:
I`ll post how did it go later in the thread .
you have a good day bro enjoy sunday .. cheers
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
TPD-21 said:
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
Click to expand...
Click to collapse
First make a backup with your cm11's kernel then flash cm12.1 kernel then flash the script and the kernel doesn't t care about your current rom so it should work every where
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. 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
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to 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/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.