Database Info

[EXPERIMENTAL] MultiROM v19 (discontinued)

This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now​
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.

OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:​1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.​- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.​
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:​Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:​(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0

Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App

so this means we can test roms without replace current ??

Yes. Is my english so bad or you just don't read what I wrote?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)

how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....

*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.

eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.

sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium

I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App

So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P

I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.

Flashable zips and guide added, see first and second post.

keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx

gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....

I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.

Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App

v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.

[MOD][Z3C] MultiROM v33x

{
"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 a one-of-a-kind multi-boot mod. 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.​
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
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 Advanced -> 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 Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)​
FAQs can be found here.
CREDITs
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
If you think I deserve a donation, I won't stop you
Thanks a lot to those who have donated!​
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the Z3C
​
XDA:DevDB Information
MultiROM for Sony Xperia Z3 Compact, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom
Version Information
Status: Testing
Created 2015-05-22
Last Updated 2016-06-06

CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5-Kernel-L (starting with V2)
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.

Reserved
General Informations about Kexec are coming here soon.

I have encountered problems with secondary rom flashing. First try your test carbon rom boot loop, second try restore back up of stock rom failed, third try fresh install of a stock rom failed, fourth try pac rom with your m5 kernel flashing ok but will not start
my primary is cm12.1 with your kernel

me too.
primary rom is stock LP 23.1.A.1.28 with androplusV55
i succeeded installing second rom being CM12.1 nightly build
first without gaaps cm12.1, as per selecting the rom from the romlist in twrp and choosing flash zip
then tried deleting it and added the rom again, this time i flashed gapps as per selecting the rom from the romlist in twrp and choosing flash zip
is gapps required to load cm successfully at all?
When selecting cm12.1 at the multirom boot menu it reboots and only shows the internal (stock) rom and boots just fine.
then i was thinking about doing the swap rom from twrp or perhaps flashing cm12.1 as primary and having stock as secondary.
or perhaps flashing cm12.1 from scratch and then add stock sony as secondary via an old backup
but then i stumbled into this thread http://forum.xda-developers.com/showpost.php?p=60906102&postcount=129
i used multirom twrp which is inbuilt in andrplusV55, not the one from myself5's dl site!
-androplus is stock only supporting
-m5 kernel is only cm12 supporting
and i coulnd't find the way to choose de-select kernel for secondary rom as found somewhere else
what a dilemma

New Version is online!
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation

Important
Just one question
now say i flashed CM 12 as a second ROM
when i boot to it , will apps which i already installed on the stock appear their ??
in other words , does the each ROM affect the other one ?? like if i put something on internal storage will appear on the other ROM ??

Myself5 said:
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation
Click to expand...
Click to collapse
nice one, indeed.
but i still had the same issue, couldn't load cm og pac as secondary rom
i had androplusV55, now i've updated to androplusV57, and it's working like a charm.
apperently it was a kernel issue
ps. noticed that gapps are required so it doesn't share apps i think?
not in my case though, hence im running stock rom as primary
probably M5 kernel can be flashed as well, as long as it is flashed through mulitrom twrp from listed roms, like update tutorial for secondary rom in OP
thanks very much

Hey freaks,
I think there is something to explain.
The first Thing you have to do and this is one of the most important thing:
Donate to Myself5 or even "Thankyou"
Because you must know, this Multirom MOD is very sensitive like a young good looking girl and it can feel a donation...and works even better after a Thank you
Remeber we are here in Z3 "Compact" Area you can NOT choose a Main Kernel for Z3 or other Xperia Models.
The Main Kernel must support kexec-hardboot (support for MultiROM), for Z3 Compact
The best way to get all to work is:
-Backup all you ROMs you have right now on your Device "Remeber Z3 "Compact"
-Save this to your SD Card
-clean your Phone
-Install CM12.1 latest Nighty
-boot one time and check if you have a Plain CM12.1 (LP 5.1.1) System. Now you have Cm12.1 and the Cyanogen Recovery on your Phone.
-Copy the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and "multirom-20150522-v31x-UNOFFICIAL-aries.zip.md5sum" to your SD Card
-Shutdown your Phone and boot on Bootloader Mode (Press and hold Volume Up Button and insert USB Cable) a Blue LED appear now.
-Go with a Terminal in Administrator Mode in your ADB Folder with fastboot. (Windows PC)
-Copy one of the M5 V6 Kernel in the fastboot directory and copy the File TWRP-Multirom-20150524-00-z3c.img in the same directory
-type "fastboot devices" now you see your device is connected
-Now type "fastboot flash boot boot.img" <-- Boot .img is the M5 V6 kernel, you find in the release Zip Files from Myself5
-Now type "fastboot flash recovery TWRP-Multirom-20150524-00-z3c.img"
-Now type "fastboot reboot"
-Your Phone boots now normally and you should press Volume Up or down to enter TWRP MultiRom Recovery...Allmost all is done now.
-In Recovery Mode go to the Normal "Install" Button and choose the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and flash this. Now reboot system.
Well done...Multiboot is installed.
Now you can go everytime you like in the recovery Mode and go to the Button Advanced -Multiboot and install other ROMs, like your Backups or CM12 builds.
All your Secondary Roms must be updated over the Advanced- Multiboot- List Roms feature. To update multiboot itself or the Main Cm12.1 Rom you have to flash over the Main install button.
If this is not working, delete Data and flash your Backup again and sell your Z3 Comapct and buy an IPhone. Apple take care of all your Data
Panic Brothers
-

@Myself5 some problems when restoring backup of stockrom with androplus kernel as secondary. file attached

edit :solved couldnt figure how to flash gapps , rooky mistake but figured it out ....u go to advanced tab in twrp/multirom/list rom/flash zip

First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]

Oh, totally forgot about the app. It's coming next ofc, just need to setup the z3c folder on my server.
Sent from my Xperia Z3 using Tapatalk

Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
AnGrY sCoTsMaN said:
First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]
Click to expand...
Click to collapse
Ey bro on candy5 do you have full connection when you connect your cel into pc?

chikrron said:
Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
Ey bro on candy5 do you have full connection when you connect your cel into pc?
Click to expand...
Click to collapse
you can have stock as primary with androplus kernel, I couldn't manage to have stock as secondary

Ok bro thanks for the tip I'll try later

Hi
So I installed your MultiROM together with the M5-Kernel and cyanogenmod. Afterwards I flashed the modified TWRP recovery. However TWRP has issues to mount my external sdcard (32 GB), its just shown as 0 MB and its not possible for me to re-partition or format it.
- It says "auto" as its file system
- Its formated as FAT32 (tried extFat too)
- This sdcard was taken over from my old i9300
Edit:
Seems I fixed it by booting into cyanogenmod and going under Settings/Storage and select "delete sdcard" down there. Strange.....
Anyways. Thanks for your work!

myself5.de is down
In Case someone noticed my server being down:
I am aware that my server is down, it got suspended by an Admin and I need to figure out why (I have not done anything forbidden, last thing I did was trying to setup an instance of Gerrit Code Review) that however is not that easy cause the server is sponsored and I only have access to the SolusVM Panel, I can't create Support tickets, so I now need to wait for my sponsor to answer me. Stupid as I am I don't have a mirror, cause I did not set up one yet... I hope someone can upload the latest Version and post a link here, would be greatly appreciated.
Regards
Myself5
EDIT: Server is meanwhile back. Thanks to everyone who provided a temporary link

Installing Roms on SD Card and External Memory
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards

Myself5 said:
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards
Click to expand...
Click to collapse
@Myself5 how about multirom app,can it work for aries?

[Addison]MultiROM v33 [No Kexec Workaround]

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for MotoZ Play. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting.
* Boot from USB drive attached via OTG cable
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.ays.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app (wait until I compile it) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual 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.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-addison.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (MULTIROM-TWRP-3.1.1-Addison-unnoficial.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
[*]Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.[/INDENT]
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
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 Advanced -> 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 Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - add ROM to boot
List ROMs - list installed ROMs and manage them
Inject boot.img file - When you download for example kernel, which is distributed as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - we'll, settings.
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
Code:
[HIDE]<!--Multirom-->
<remote name="multirom"
fetch="https://github.com/Tasssadar" />
<project name="multirom-dev/multirom" path="system/extras/multirom" remote="github" revision="master" />
<project name="multirom-dev/Team-Win-Recovery-Project" path="bootable/recovery" remote="github" revision="android-7.1-mrom" />
<project name="multirom-dev/libbootimg" path="system/extras/libbootimg" remote="github" revision="master" />
[/HIDE]
Kernel: https://github.com/Alberto97/android_kernel_motorola_msm8953/commits/twrp-7.1
Device: https://github.com/XPerience-AOSP-Lollipop/android_device_motorola_addison/tree/android-7.1-MROM
XDA:DevDB Information
[Addison]MultiROM v33 [No Kexec Workaround], Tool/Utility for the Moto Z Play
Contributors
TeamMex
Version Information
Status: Stable
Created 2017-05-20
Last Updated 2017-05-20

Reserved
Downloads:
TWRP_Multirom.img
multirom-20170520-v33-UNOFFICIAL-addison.zip
multirom_uninstaller.zip
MultiROMMGR Adapted for Addison

Reserved
FAQ and other notes
Device encryption
Encryption Fully working
SD CARD
Fully working
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 potentially make it easier for such software to attack that system.
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'd like to support more devices, but it is also very satisfying to work on code for device I don't have - I invested hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
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

CREDITS:
 @nkk71 (For kexec workaround) 
 @Tasssadar for MultiROM 
 @Alberto97 For TWRP kernel and Encrypt fixes taked from his TWRP repo.
Screenshots

Try to test but, mod twrp stuck on initial logo ( flashed via , twrp , flashify and fastboot )
Download it three time.
Please you can upload to another host?
Thanks sorry for my bad English.
Inviato dal mio XT1635-02 utilizzando Tapatalk

lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen....
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption

Alx31 said:
lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen..
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption
Click to expand...
Click to collapse
For me it's working fine
Sent from my Moto Z Play using XDA Labs

TeamMex said:
For me it's working fine
Sent from my Moto Z Play using XDA Labs
Click to expand...
Click to collapse
I mean is a upload problem..try to change host
Inviato dal mio XT1635-02 utilizzando Tapatalk

I'm getting, "Failed to create system.img" error for both SD card and internal storage.

Great work!
Waiting for Android O for the device.?
Can you tell if development of Android O for the device(Z Play) is started or not?
Thanks!

VR25 said:
I'm getting, "Failed to create system.img" error for both SD card and internal storage.
Click to expand...
Click to collapse
Me as well

Mrawesome13 said:
Me as well
Click to expand...
Click to collapse
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.

TeamMex said:
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.
Click to expand...
Click to collapse
I've decrypted my data, now recovery gets stuck at the splash screen. The standard TWRP works though. Tried MULTIROM TWRP 3 times -- Auto installation from the MultiROM app and manual from flashify & standard TWRP. I forgot to get a log. Will do it if I have time to try that again.

I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!

Hey, i did that. But it isnt working.. still same message

Anybody who can confirm that MultiROM v33 is working on moto z play under 7.1.1 stock rom with stock kernel?
Thanks!

wokawoka said:
I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!
Click to expand...
Click to collapse
yes but him was reverted the encription support.
I will try to update multirom in some day's.

Thank you for your reply @TeamMex!
I'm actually using in this right moment your TWRP 3.1.1 multirom and these are my findings:
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
I'm running a rooted stock moto z play 7.1.1 rom as my primary rom and I've installed MultiROMMGR and reinstalled TWRP from there as well.
Do you by chance have any suggestion about these issues?
Any new version that corrects bugs is of course very welcome. Thank you very much again for your work!

wokawoka said:
Thank you for your reply @TeamMex!
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
Click to expand...
Click to collapse
- Alright, so I was able to resolve the encryption password problem, as iit was my fault and not twrp multirom's: I just had to change again the security settings of the phone to enable the ask for pin code on boot.
- I circumvented the 64GB SDXC problem by using a 32GB SD card (still, it would be great to use a bigger sd card)
- Unfortunately, I'm still not able to use the multirom function: I'm running a moto z play stock 7.1.1 encrypted and rooted system, and as no alternative kernels exits for 7.1.1 at the moment. Is there a possibility in this conditions to get multirom working? I still receive the "E:Failed to create system.img" error when I try to install a secondary rom.
I'm not sure, but it feels like this moto z play multirom port is not actively mantained, which is a real pity because the phone is great and has all the characteristics to be the center of an active community of enthusiasts (in the same way some nexus or Samsung phones do) since it has quite unique features like good specs and an incredible battery life, the mod expandibility and an hardware qwerty keyboard that is going to be released very soon, and it also recently became very affordable.
Having a working multirom would help immensely and push the development of custom roms and alternative OSs (like for example sailfish https://talk.maemo.org/showthread.php?p=1538755#post1538755 ).
I would try to help or to take care of it myself but unfortunately I don't have the specific skills needed. I would be eventually up to give my contribution with some money (actually I'm thinking about creating a bountysource for it).
Is there by chance someone else that could bring on the port and release a stable working version?
If not, do you guys think that the it would be possible to adapt the twrp multirom released for the Moto Z (non-play version): https://forum.xda-developers.com/moto-z/development/mod-multirom-v33b-moto-z-t3513868 ? I can imagine that they have to be very similar.
Thanks again

any update on this?

[FIXED][OFFICIAL][APP]Dualboot Patcher For Lenovo A6000/+

{
"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"
}
I am proud to present the official dual boot project for Lenovo A6000. 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
What is DualBootPatcher?​DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:​I have managed to get Lenovo A6000 to the DualBootPatchers Official list, I am not the creator of the Dualboot patcher, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:​
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:​1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app from the download section below.
4. A rare thing you find now-a-days on XDA known by the codename: B.R.A.I.N
What does the app do ?:​It patches...
Custom kernels for dual boot support
ROMs to make them boot as secondary
Gapps
Any other mod you would like to install on your secondary ROM
What's supported ?​
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
-Grant Root Permission
-Go to settings and select install bootui
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later, and if you weren't asked to set kernel then select set kernel also.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to "a6000-Lenovo-A6000" and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip.
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Using Bootui:
- After installing (update) bootui, and flashing the secondary ROM then go to "ROMS" section again and open secondary ROM Settings) and select Update Ramdisk, Now when you will reboot a TWRP like Screen will appear, in that select whichever ROM u wanna boot.
Note-
Clean Flashing any simple ROM from TWRP will wipe both the ROMs, so if you clean flash and want to dual boot, follow the instructions again.
Partitions Configurations:
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.
How to boot to another ROM ?​This is simple ... . So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Instead you can use the bootUI to switch ROMs as stated above
Apps and Data sharing:​
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
FAQs​
How do I uninstall the secondary ROM
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".
OK, Now i Want to change my Primary ROM but want to keep the Secondary 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
I wanna change the secondary ROM
Wipe it using the 3 dot menu and 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
Ok but the Update Ramdisk failed
Dont worry simply follow the further steps, i have got it thoroughly tested on the telegram group and by myself
But I have the 8GB Variant so wont flashing secondary ROM eat my Storage space?
The Answer is NO, you may not be able to flash Gapps in some cases for secondary ROM, but as long as you flash the secondary ROM in /system, your storage space wont be used
Downloads:
https://dbp.noobdev.io/downloads/​Cheers ! we are officially supported
Note: You can download any version since "9.3.0.r97.g737d9dd5"
Sources:​DualBootPatcher:https://github.com/chenxiaolong/DualBootPatcher
Lenovo A6000 Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/922
Known Issues:
Comment here if you face any.
Credits:
@chenxiaolong for the awesome DualBootPatcher.​Other people behind the DualBootPatcher​And Me :V​
XDA:DevDB Information
[OFFICIAL][APP]Dualboot Patcher, Device Specific App for the Lenovo A6000/Plus
Contributors
[email protected]_, chenxiaolong
Source Code: https://github.com/varunhardgamer/DualBootPatcher
Version Information
Status: Stable
Created 2017-11-04
Last Updated 2017-11-04

This is more than awesome dude.

Reserved

Fine...
Something new for A6k/+

[email protected]_ said:
Reserved
Click to expand...
Click to collapse
Oops!!! Seems I posted before OP. Sorry for that.

Jitheshwar said:
Oops!!! Seems I posted before OP. Sorry for that.
Click to expand...
Click to collapse
No problem dude, you reserved for me :good:

is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4

garvit girotra said:
is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4
Click to expand...
Click to collapse
I know that and we are checking it again, looks like something got derped

EDIT-> The issues are fixed grab the latest snapshot

The fix has been added, download fhe latest snapshot and enjoy

Astala vistala baby
Varun you are the man

Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work

garrygarvit said:
Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work
Click to expand...
Click to collapse
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants

[email protected]_ said:
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants
Click to expand...
Click to collapse
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Well i find the solution i revert to the stock rom of lenovo and try dual boot patcher work in that ramdisk kernel boot ui all work i think the problem is in the .aex rom by the thanks for all help varun
---------- Post added at 09:08 AM ---------- Previous post was at 08:46 AM ----------
Well a new problem arises now after all success that now when i am not able to download any things from chrome or other browser in the internal storage it shows no sd card detected download failed by the then i checked into storage there both my internal storage and external storage dont know why this happen now i fed up of all this. Now i will be only to stock rom for some while no rooting no flashing

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Right now i am on aex 4.4 dual booting aicp

[email protected]_ said:
Right now i am on aex 4.4 dual booting aicp
Click to expand...
Click to collapse
Updating ramdisk on work for in lenovo stock rom not on aex even after the clean flash

Dual Boot
Hello Varun
Can i Dual Boot Stock Kitkat and Viper
as Both has different Android version. so difference is only of one flaashable file that is: kk to lp firmware patch .
so how to do that.

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Huawei Y3 2017 (CRO-U00)

DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. 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.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM (Supported Y3 2017 CRO-U00. Such as MIUI 8.3 or Galaxy S8)
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What Can Be Done:
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
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (greatlte) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20171004-greatlte-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple . There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
Quote:
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Other How to ?
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".
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:
dbp.noobdev.io/downloads
Sources:
DualBootPatcher: github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: github.com/chenxiaolong/DualBootZips
Huawei Y3 2017 (CRO-U00) Source:
github.com/chenxiaolong/DualBootPatcher/pull/919
Known issues:
- You have to tell me !!!
Contributors
yshalsager, chenxiaolong, docs007
Version Information
Status: Stable