[STABLE] EFIDroid MultiBooting on Nokia X2 [PORTED by yoAeroA00]

[STABLE] EFIDroid MultiBooting on Nokia X2 [PORTED by yoAeroA00] - X2 Android Development

/include/disclaimer or warning.h
/*
* Your warranty is not void as I Think!!
*
* 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 Port
* 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 $ Lot
* But I will always be here to HELP! You...
*/
yO Guys..
To Support the Project PM me but if you are not a Developer than Press Thumps Up! :good: Button for Encouraging..:good::fingers-crossed:
I @yoAeroA00 and @m11kkaa has spended two Days to Successfully Port it to Nokia X2 so you better try it out...
If you wan't any feature to be added in EFIDroid than you are specially welcomed:good:
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, m11kkaa, Nokia X2 Users and Fan's...
Source Code: https://github.com/efidroid/device/tree/nokia/ara
Version Information
Status: Stable
Created 2017-01-14
Last Updated 2017-01-21

Let's Continue
Table of Contents
1> About EFIDroid
2> How to install EFIDroid on any Supported Device
3> Configuring new ROMs from the APP before Installation
4> Adding a System to the newly created ROM Slot
5> MultiBooting into your newly created ROM
6> FAQ
About EFIDroid
As @m11kkaa said EFIDroid is a easy to use, powerful 2ndstage-bootloader based on EDKII(UEFI).
It can be installed one-click with the EFIDroidManager App. You can Add/RemoveEdit Multiboot ROM's.
There's no special support needed by ROM's or RecoveryTools(no kexec etc).
And I think @yoAeroA00 EFIDroid is a relatively new Multiboot solution for Snapdragon SOC based mobile devices which is based on the EFI implementation by Intel (EDK2).
In last few month's 90% of the Developers has just drop out for no Reasons. Without these drop-out's it could gain a Huge Success.
For more information , please visit to the Github WIKI and for support, please visit EFIDroid Slack. @m11kkaa and I @yoAeroA00 will always be on Slack Community to Help you Porting it to your Devices or Help you a little bit.:silly:
How to install EFIDroid on any Supported Device
> You can Download EFIDroid Manager App from Google Play.
> After installing EFIDroid Manager App Go to Install/Update..
> Then Click Install:
{
"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"
}
> It should be Successfully Installed!
Configuring new ROMs from the APP before Installation
Note: You need to configure the system before installing any new ROM for Multibooting.
> Before you do any of this you should have a ROM .zip file Handy on your SD card (/storage/sdcard1/ and !!NOT!! /sdcard!).
> To Add a ROM Slot got to "Operating Systems" List and click on the FAB (Floating Action Button)..
> Choose an ICON for your new ROM Slot..:good:
> Choose in the screen /data/media/0/multiboot or any other on screen places as a location for your ROM Slot.
> Enter a name and description for your ROM.
> You can leave the partitions as they are (Schema LoopSystem + BindOther) or modify their names or sizes.
> If you need your own custom replacements than configure them as per your needs in the Replacement Tab.
> Press the tick in the top right corner if you have finished setting up things.
> Now you can see that your newly created ROM Slot is in the "Operating Systems" list.
> Then Reboot to See the EFIDroid's Magic!:silly:
Adding a System to the newly created ROM Slot
Note: Once you are in the UEFI, you can navigate around with Volume Down to go Down, Volume Up to go Up and the Power Button to confirm your Selection.
> To flash a ROM select the empty slot, select TWRP (Internal) and then press Power Button.
> Next select your newly created ROM Slot.
> You will be now landed in TWRP and be greeted with a warning about keeping the System Partition ReadOnly. Swipe the Slider at the bottom to Acknowledge it.
> I will highly Recommend you to format all the Partitions(System, Data, Cache) to EXT4 or any file System before you Continue to Install any ROM..
> Click Install, select the Micro SDcard at the Storage tab and then navigate to the directory where your ROM .zip is placed.
> Select your ROM .zip file ****!-ROM.zip.
> Disable the Zip file signature verification and slide the Confirmation Bar.
> If Everything is good then you can Reboot!
MultiBooting into your newly created ROM
> Select your new ROM and press the Power Button. Do not be put off because of the long “Booting <ROMName>” screen as your ROM will open & play the boot animation very late (Unfortunately for only the First time).
> Aaaand Finally we are in the New ROM!
FAQ
Note: If you have any questions, please ask in the This Forum thread or PM me
Q.1> This is a UEFI port, can we port Windows?
> Not, till Yet but with your support we can easily Port it.
Q.2> Can I still use fastboot after installing this?
> If you flash to the boot/recovery partitions, UEFI will be overwritten.(dd in Android/Recovery instead) all other partitions will work as usual.
Q.3> I FOUND A BUG, what should I do now?
>Report it on Github. If there already is an issue for your bug and you don't have anything useful to add, just hit the thumbs-up button. This way I know how many people are affected and can adjust my priority list. I will not keep track of all bugs reported in posts of this thread. If you want a bug to get fixed, report it on Github.
[email protected]

yUP Two...
:fingers-crossed::good:

Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind

netradip said:
Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind
Click to expand...
Click to collapse
he's not ROM builder but kernel builder :laugh:

yoAeroA00 said:
yO Guys..
Currently Testing..
To Support the Project PM me but if you are not a Developer than Press Thanks! Button for Encouraging..:good::fingers-crossed:
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, yoAeroA00, Nokia X2 Users and Fan's...
Source Code: http://Coming Soon...
Version Information
Status: Testing
Created 2017-01-14
Last Updated 2017-01-14
Click to expand...
Click to collapse
Could you please fix bugs on the new Lineage OS ?

Multi rom on 2,2gb is bad idea

thinhx2 said:
Multi rom on 2,2gb is bad idea
Click to expand...
Click to collapse
It is not multi ROM Bro. It is Grub bootloader through which I can even boot from a system image file stored in a folder on sdcard... And even boot Linux on the Mobile(Need's to be Ported First!)....
If anyone wan't to help me than PM me so that we can give it a start...

KenX2 said:
Could you please fix bugs on the new Lineage OS ?
Click to expand...
Click to collapse
Yes, but only those bugs related to kernel...

How to you add config of X2 to EFIDroid?

i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file

thinhx2 said:
i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file
Click to expand...
Click to collapse
No need Bro I have successfully made EFIDroid for Nokia X2...

after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.

frnsl3 said:
after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.
Click to expand...
Click to collapse
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
My SD card could be detected in TWRP and CM12, but it's mounted Read-Only, I can not add any file or remove any file.
I tried to connect it to my PC and format it or use the " Check " inside tool then It's had worked correctly but the problem happens again when I reboot my phone
How can I fix this ?

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
all i need is just repartition my sdcard bro :silly::silly:, just install efidroid its get partition error. now working as usual :victory:

@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
Click to expand...
Click to collapse
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?

symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?
Click to expand...
Click to collapse
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3

yoAeroA00 said:
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3
Click to expand...
Click to collapse
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?

symbuzzer said:
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?
Click to expand...
Click to collapse
Ohh... You should flash uefi_boot.img not lk.img and currently EFIDroid is in development so you can only add ROMs by using it's app and soon I will write a tutorial on how to install ROMs on EFIDroid...using app[emoji6]
Sent from my ara using XDA-Developers Legacy app

Related

Droid Dual Boot Tool - The Ultimate Dual Boot Wizard by ACRD Team

Droid Dual Boot Tool - The Ultimate Dual Boot Wizard by ACRD Team
{
"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"
}
Android Core Research & Development Team (ACRDT)
Proudly Presents You The
Droid Dual Boot Tool
Introduction
We from the Android Core Research & Development Team (ACRDT) are glad to present you this “Droid Dual Boot Tool”, which does all the necessary steps to make your device dual boot. All you have to do is flash the zips as mentioned below. The main focus of this tool to help all Android Users to understand and have dual boot OS in their smartphone in a user friendly manner. This tool takes all the coding, so with a single click of mouse you can have dual boot. Awesome Right!! Keep Reading...
This Whole Concept was a Big Gigantic Hack by ACRD Team.
**Neither Device Manufacturer’s nor Android . Let It Like this.**
How it works?
Normally when you boot your phone, the kernel (or boot.img) file loads all the files from all partitions like /system, /data, /cache, /firmware…etc. So to have Dual Boot you need to edit the boot.img of the CustomROM such that it loads all the files from the /system2, /data2
To Achieve that We Partition the Device using Parted Commands in Zips ..We Uses Intelligent OpenRecoveryScript Commands To Flash them Automatically..In a Order Wise..
In a Short way I'm Explaining How this Stuff works.. our current rom which was in /system /data .we back up that rom .Our Script flash this Boot-To-Secondary_BackUp_Rom.zip this contains a modified recovery.& boot when we restores the rom it'll sent to /system2 & /data2 . Now what happens is our current rom is moved to secondary partitions.. Now /system /data are empty right so we can install our custom roms there ..
Check Out this Video & Zips If you want to know about how our Intelligent code Executes..
Dual Boot Mechanism (youtube)
Why Dual Boot?
We Say If You Are A Custom Rom Lover..And An Enthusiast One to Try Out Roms..!!
To Try Out Every Rom..You Have To BackUp Your Current Rom And Flash It And Again Restore Your Old Rom..Seems Headache Process RIght..No Worries We Are Here For You..You Are In The Right Place With This 99% You Will Dual Boot Your Device..You Can Keep One Rom As Permanent And Try Out Other Roms With Out Touching First Rom.
Warning….!
Your warranty will be void, but for Xiaomi device you can get it back when you flash the ROM via EDL (Downlaod) Mode.
We Are Not Responsible For Damaged Ext-Cards,Corrupted emmc Chips, & Loss Of Data.
However, We'll Help You If you find any problem
Please Make a Full Nandroid Backup Of your Rom in External SD Card & Have a Full Copy Of Your Internal Data to your Ext-Card / Laptop.
Don’t try if BOOTLOADER is Locked. (You need to unlock it first)
Your System Performance Wont get Degraded..We Are Not using Both Roms Simultaneously ..We Are Just Switching From One Rom To Other Rom by Flashing Modified Boot.img Every Time..
Requirements
Our ultimate Tool & App..
MIUI /Current Rom “boot.img”.or it's Flashable Rom Zip
Custom ROM Marshmallow(CM,Mokee,etc) “boot.img”.or it's Flashable Rom Zip
TWRP Recovery Must Be Flashed To recovery Partition
An External Micro Sd Card.. With Minimum Free Space 8-10GB.
A Cup Of Hot Coffee / Ramen
Our Ultimate Tool Looks Like This
Our Ultimate App Looks Like This
DroidDual Boot Tool Majorly Contains Four Parts.
1. Wizard -: Used To Dual Boot Your Device
2. Tool -: Used To unpack/repack boot & recovery image files (For Advanced Users)
3. Donations - : Your Efforts Are Most Appreciable For us To Continue Our Work For All Android Devices. For Further Details Regarding Donation Kindly Contact Us. See You In Donation Page
4. AboutUs -: It’s Your Courtesy To Know About Us
How To Use This Ultimate Tool
Step 1 -: Select The Custom rom zip which you are going to install. Either Select The zip or it's boot.img
Step 2 -: Now Select your Custom TWRP Recovery.img in the Second Browse
Step 3 -: Here’s the Main Part. Now What You Have to do is .
- You need to pick up the boot.img from your current ROM i.e.
- Either you select the current rom zip . (“Which Is Flashed Already In your Device”) or select the boot.img from Your current rom zip
- OR If You Don't Have Your Current rom zip.. you can use these app From PlayStore To backup your Current bootpartition. (boot.img)
Rashr Open the app>Click On backup>Kernel backup>filename.img BackUpFile.img is Located In
Step 4 -: Once All the above *.img's / *.zips was selected . Select your device Then click start wizard It'll automatically does the necessary patches for your device & opens the folder.
Keywords:
1. Boot-To-Secondary_BackUp_Rom.zip = This Zip Is used to boot into Your Rom WHICH IS RESTORED VIA RECOVERY.This Zip Contains the patched recovery & patched boot.
2. Boot-To-Primary_Custom_Rom.zip = This Zip Is used to boot into cutom rom.This zip contains normal TWRP recovery & your Selected Custom rom Boot.img file.
3. /sdcard1 = Ext-card / Micro sd card
The Opened Folder Usually look Like This.
Flashing Process
Step 1 -: Paste that Folder Into Your Ext-Card Root Folder.. Like This
Note:: Always The path of DualBoot Folder & Sub Folders In Ext-card Root Folder (/sdcard1/DualBoot/AboveFolders/**.zip)has to Be Maintained..Otherwise No Flashing Will Work..
Step 2 -: Copy the Custom Rom Which you want to install And paste It in Install This Rom Folder..Check the Above picture..
I Assume you have done all Backup Of Internal & Cust EFS,Persist,Firmware Partitions
Step 3 -: Install Our DualBootManagerApp..You Can Find it in DualBoot Foder .Click On Wizard-->Click Create Partitions…Like Below..Now The Magic Starts..It Took Around 20 Min. Don’t Interrupt the process… Now Enjoy Your Coffee / Ramen
That’s it Guys..With In Three Steps..you Are in DualBoot.. Once the Above Process Done Perfectly You’ll Be Again Boot back to Your Current Rom..Again Use Our App..To Switch between Os’s..
Check Out These Videos..If you want .For How to Flash..
Dual Boot Flashing (youtube)
Switch Os'sIt's Dead Easy..Use our App go to SwitchOs’s..Select Your Desired OS..
Flashing Part Revert back to Normal1. Take A BackUp of your Internal..and Rom use Switch os To boot into particular Os And take a Copy & backup Of Respective os’s..Like Which os Backup you want..
2. Use Our App Wizard--> Remove Partitions.. Once All Done You’ll Rebooted Into Recovery..
3. There restore Your Rom. Or install new zips What Ever You Want….
Check Out this video If you Want. For Revert back to Normal.
Revert Back To Normal (youtube)
Check Out the FAQ (MUST)
Make Sure To Check Out The Help & About Us Tabs In our Tool.. Where You Can Find The More In a Crystal Clear way About The Procedures..1. What I have to do.If I want to change (Flashing New) custom roms?
A) Simply Follow Step 1 & Step 2 In How to use Dual boot wizard. Then Click Start Wizard..Then You’ll Get New Boot-To-Primary_Custom_Rom.zip In /DualBoot/2-SwitchOS..Copy That Zip And paste It In Your Micro-Sdcard..The Path Should Be Like /sdcard1/DualBoot/2-SwitchOS/ Paste The New File In here …Use our App to Switch to Primary os..Then Reboot to recovery..There flash Your new Custom Rom zip..
NOTE If you Are Changing(Flashing New) Custom Roms .Then You have to do the above process. Then Only Your Device Will boot into that particular Custom rom.You have to do this every time When Ever You Are Changing Custom Rom. The Main Purpose Of This Zips is to Switch between Custom rom to secondary (backUp) Rom. If You Didn’t change the boot.img while installing new rom.you cannot switch between roms.
2. If you Face Any Error Which Cant Be resolved..
A) Flash A full rom via edl mode. (Download Mode)
3) How to change(Flashing new) secondary(backup) rom.if i get any new update..
A) Changing the backup rom which was in /system2 /data2 was lenthy..it is like a permanent rom..I mean it's not easily changable ..if u want to change it no matter what..Here's one way.Use the wizard tool again from the beginning by browsing your new update rom in secondary os.then copy the new files in ext-card "DualBoot" folder..Then Start Remove partition process then Install Your updated rom.. there in that rom do what ever changes you want.Install Our App.Then Start the flashing process like from the beggining...
4) What Do i have to do if i want to flash any xposed or dolby or super su or any zips in any rom..
A) No Worries just Flash Them Normally as usual in recovery.. If it didn't work then report us.we'll look in that
5) When Will We Get This Awesome Tool & App For Our Other Xiaomi Devices...
A) As For now, It is For All Redmi 3S Varients..Soon..In the Next Release..We'll Include 2 More Devices..But We Need Your Support ..If You think We Are Affordable .You Can Show Us Your Support via Donations..Until Then .Stay Tuned With Our Forum...
Credits
Android Core Research & Development Team.
Justify Born Shadap (@justzzshadz),
Sai Tyson (Tyson),
Yuventius Hadinata Irgianto (Silfox),
Are The Developers of Droid Dual BootTool
Specific Device Testers
Thanks To m4mohit For Banner Editing
Humble Thanks to Our Donators. (Help Us to Serve You Better)
XDA:DevDB Information
Droid Dual Boot Tool, Tool/Utility for the Xiaomi Redmi 3S
Contributors
SILF0X, Tyson12
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2017-02-28
Created 2017-02-22
Last Updated 2017-02-28

DOWNLOAD LINK :
DROID DUAL BOOT TOOL V.1.1
Change log :
V.1
- Initial Released
V.1.1
- Added Dual Boot Manager.apk
- Added MobiKwik
- Added "Open Folder"
- Change some documentation
- Change some filename (due android limitation)
"More devices will add soon on next update. Stay tuned with us"

RESERVED

Thank you So much for Developing this tool. I will test this tool to install 2 ROMs

m4mohit said:
Thank you So much for Developing this tool. I will test this tool to install 2 ROMs
Click to expand...
Click to collapse
Thanks you mohit for the banners.

Not gonna using MIUI and LineageOS same time but thanks you for this developing for our device !

hiimpig1 said:
Not gonna using MIUI and LineageOS same time but thanks you for this developing for our device !
Click to expand...
Click to collapse
Thanks bro

SILF0X said:
Thanks you mohit for the banners.
Click to expand...
Click to collapse
My Pleasure

Updated : Dual Boot Switcher

SILF0X said:
Updated : Dual Boot Switcher
Click to expand...
Click to collapse
anyone tried its working or has bugs?

This isn't easy job. Good job bro..

Any one try. And working ???

Download is there in .exe format where is the .apk file
Is it system based or android.

Gud job there.
But if we had a menu while boot up to select any ROM to start that will be osm.

bhim768 said:
Download is there in .exe format where is the .apk file
Is it system based or android.
Click to expand...
Click to collapse
Dear user the apk was in the tool.. Once the tool extracts the zips.. In the output folder you Can See Apk..
you can Try It With Out Any Worries..it was tested & Working Fine.. Please follow the instructions as mentioned
Thanks
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
adityaon said:
Gud job there.
But if we had a menu while boot up to select any ROM to start that will be osm.
Click to expand...
Click to collapse
Sure We'll try our best to Implement It.. Thanks For the feedback..
---------- Post added at 06:54 PM ---------- Previous post was at 06:53 PM ----------
immy28 said:
Any one try. And working ???
Click to expand...
Click to collapse
you can Try It With Out Any Worries..it was tested & Working Fine.. Please follow the instructions as mentioned
You Can Check out the videos for your conformation..
Thanks
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
cc6691 said:
anyone tried its working or has bugs?
Click to expand...
Click to collapse
Dear User ..
you can Try It With Out Any Worries..it was tested & Working Fine.. Please follow the instructions as mentioned
you Can Check out the videos for your conformation
Thanks
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
javhusin2 said:
This isn't easy job. Good job bro..
Click to expand...
Click to collapse
Dear User
Thanks For the Feedback..Feel Free To Try it & Ask Any Queries Regarding This...
Thanks

Please add support for zenfone 2 laser
Or make a guide on how to add support for other devices

dont try this if your /data is encrypted
it wont work

Jure_aleksic said:
dont try this if your /data is encrypted
it wont work
Click to expand...
Click to collapse
can i use this on another device?

cc6691 said:
can i use this on another device?
Click to expand...
Click to collapse
Jure_aleksic said:
dont try this if your /data is encrypted
it wont work
Click to expand...
Click to collapse
Dear user
It's not like that, your whole /data will be repartitioned
So it's independent of data encryption.
You can try this with out worries
Thanks
Regards
SaiTyson
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
cc6691 said:
can i use this on another device?
Click to expand...
Click to collapse
Sorry the initial stage was meant fit for Redmi3S Variants
Soon it'll be released for other devices
Thanks
Regards
SaiTyson

Hi,I have some problems. When I added a new ROM ,then my screen lock was in error. Even if I draw the correct pattern, it will still show a pattern error.How can I fix it ？

[EXPERIMENTAL][TESTING][29-3-17] MultiRom Latest For mido

Download Links:
MultiRom Manager App 2.4-rishabhrao

1. Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Guys please test this in your mido and Please tell me how it works

How about the recovery? witch one we can use?

Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?

XMoDuLeSx said:
How about the recovery? witch one we can use?
Click to expand...
Click to collapse
It has it's own modified TWRP recovery
Sent from my LeEco Le 2 using XDA Labs

dragneelfps said:
Question 1: what is to difference between multirom and dual boot?
Question 2: can I use miui as secondary ROM with aospe as first Rom?
Question 3: when will dual boot be available for rn4?
Click to expand...
Click to collapse
1. MultiRom is a complete Multi Booting tool which has it's own Recovery, boot ui, etc.
2. Yeah i think so... You can.
3. Mido is rn4 only r8!
Also note that this is still in testing so please forgive me if you face any bugs. But it will be stable soon...
Sent from my LeEco Le 2 using XDA Labs

flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).

dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe

leo_pard2331 said:
I did the same thing and I'm having the same problem...
Only that I tried xenon HD instead of aospe
Click to expand...
Click to collapse
Let's see . op will fix the bug probably.

dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
I wiped everything and restored the backup and now I'm unable to install the multi rom

dragneelfps said:
flashed miui 7.2.23 as second rom ..(aospe as first rom).
I open the app and try to boot into miui..it says No-Kexec kernel found and reboots to recovery.
---------- Post added at 01:50 PM ---------- Previous post was at 01:18 PM ----------
Now tried LOS as second rom. Couldnt even boot in my first rom. So deleted the second rom. Still couldnt boot in the first rom. (screen goes off after mi boot logo). Now restored the first rom nandroid backup. Working now.(first rom only).
Click to expand...
Click to collapse
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs

leo_pard2331 said:
I wiped everything and restored the backup and now I'm unable to install the multi rom
Click to expand...
Click to collapse
What is happening when you try to install it?
Sent from my LeEco Le 2 using XDA Labs

dragneelfps said:
Let's see . op will fix the bug probably.
Click to expand...
Click to collapse
Definitely i will
Sent from my LeEco Le 2 using XDA Labs

Rishabh Rao said:
Hey u mentioned the screen goes off after mi boot logo
How much time did you wait after that happens?
Sent from my LeEco Le 2 using XDA Labs
Click to expand...
Click to collapse
actually 10-20 sec

Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol

Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
+1

Sarthak Narang said:
Hey sir, Did u test this before posting in here? Do u own a mido? Just curious lol
Click to expand...
Click to collapse
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now

Rishabh Rao said:
Hello Sarthak Sir
No i do not own a mido.
I approached in some TG, WhatsApp groups after i made this to get someone to test. But everyone got me to post it here
So i just posted it with the BIG Heading "TESTING".
Also just because I don't have this device, please don't think i will not fix this MultiRom.
I will work day and night to fix this lol:silly::fingers-crossed:
Now some guys at some TG group confirmed to me the following points:
1. MultiRom works through the app to dual boot.
2. Boot UI is messed up and needs fix. (Trying out different Pixel Formats now)
3. The Lockscreen and FP Bug exists just like some other devices like kenzo, s2, x2, etc. (Temporary fix: Disable your FP and Pattern before Installing any new Rom)
Now looking out for more testing and propably this thing will be ready to rock in a few days.
Sent from my LeEco Le 2 using XDA Labs
Edit: Just also added EXPERIMENTAL in the Title to show that this is just in the Alpha Stage till now
Click to expand...
Click to collapse
Looking forward to it.

[APP][Unofficial]Dual Boot Patcher for Cagabi one & MT6580

{
"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 first Dualboot project For Cagabi one. 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 (like /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 support for Cagabi one and other MT6580 devices to the DualBootPatcher App, I am not the developer, I am just the maintainer.
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.
What does the app do ?:
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 correctly and under Partition configuration select secondary (will install 2nd ROM in /system) or data or external SDCard 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 LO13-20170807-cagabi-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:
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
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
Source:
Source
All Releases:
Releases
Downloads:
07-Aug-2017 First Release
12-Aug-2017 Second Release
15-Aug-2017 Third Release
19-Aug-2017 Fouth Release
25-Aug-2017 Fifth Release
13-Sep-2017 Sixth Release
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@RendyAK for inspiration, help and tips
@yshalsager I copied his thread because I am too lazy
Enjoy

Changelog
Changelog
07-08-2017
Code:
[U]Added support for:[/U]
- Cagabi one
- Doogee X5 max
- Doogee X6
- GiONEE P5W
- GiONEE Marathon Mini
- Leagoo Z5
- Infinix Hot 3
- Symphony P7
12-08-2017
Code:
Downgraded the source to a previous stable release (Reseted the commits)
[U]Added support for:[/U]
- Alcatel Pixi 4-4
15-08-2017
Code:
[U]Added support for:[/U]
- Cherry Mobile Flare S5 Max
- Micromax Q354
19-08-2017
Code:
[U]Added support for:[/U]
- Walton Primo GH6
- Cherry Mobile Touch XL
- Cherry Mobile Flare J3
- Wiko Lenny 2
25-08-2017
Code:
[U]Added support for:[/U]
-Alcatel Pixi 4(5)
- Alcatel Pixi 4(7)
- Symphony i10
- Tecno l8 Lite
- Walton Primo GF4
- Walton Primo N2
13-09-2017
Code:
- Updated source (Now it is stable)
[U]Added support for:[/U]
- Tecno W4
- Lava Iris821
- Archos Helium 55 Plus
- Mororola Moto C

Screenshots
Some screenshots of the supported devices
Note for all: If you are using a custom rom, make sure your build.prop has your device name correctly! Otherwise you will face issues. (same goes for the default.prop in the recovery.img)

Well-done buddy !
keep it rocking

Thanks for adding Gionee P5W
Great work sir. :good:

Download link for 07-08-2017 release have been updated

Hello all, I started Dual Boot Patcher project for MT6580 devices, and I already built for 9 devices, but it seems that the source of the app is unstable for now.
I have opened an issue on github for the original developer to fix, and I also found users who are having the same problems with DBP and opened an issue before. (Check on github)
So please wait for fixes, in meantime I will continue to maintain more MT6580 phones.
Regards,
Ahmed Rahmy

New release is up
- Updated download links
- Updated change log
Enjoy

Does this work with recoveries other than twrp?

Please Made This For Micromax Q354
Mine Device name: Micromax Q354 MT6580 3.18.19+
I can't Sent the link in your post....they said error

Hello Mr. Mysteryagr, I am making my request to build dualboot patcher for my device
---------- Post added at 07:25 AM ---------- Previous post was at 07:01 AM ----------
Can you make one for me?

liccolailo said:
Does this work with recoveries other than twrp?
Click to expand...
Click to collapse
Yes
EsTaHaD_MrIdUl said:
Mine Device name: Micromax Q354 MT6580 3.18.19+
I can't Sent the link in your post....they said error
Click to expand...
Click to collapse
Send a pm to me

liccolailo said:
Hello Mr. Mysteryagr, I am making my request to build dualboot patcher for my device
Can you make one for me?
Click to expand...
Click to collapse
Added Support already

New build is up
Added support for:
- Cherry Mobile Flare S5 Max
- Micromax Q354

Make one for Walton Primo GH6
Stock Build.prop: https://pastebin.com/x9D5VfRF
Mountpoints:
System- /dev/block/mmcblk0p18
Data- /dev/block/mmcblk0p20
Boot - /dev/block/mmcblk0p7

abid.nnt said:
Make one for Walton Primo GH6
Stock Build.prop: https://pastebin.com/x9D5VfRF
Mountpoints:
System- /dev/block/mmcblk0p18
Data- /dev/block/mmcblk0p20
Boot - /dev/block/mmcblk0p7
Click to expand...
Click to collapse
Added support, will be available in the next release

*Maybe it is off topic*
@Mysteryagr,
can you tell me why i am getting this error?
-
make[2]: *** [data/devices/devices.json] Error 1
make[1]: *** [data/devices/CMakeFiles/run_devicesgen.dir/all] Error 2
make: *** [all] Error 2
The command "make" exited with 2.
-
i tryed to compile the dualboot patcher (downgrade branch) using travis.
but it is ending with this error
i froked the repo from your git.
froked git : https://github.com/Parthib24/DualBootPatcher
EDIT:i think i found the problem....it is problem in walton.yml ....i am so foolish

Parthib said:
*Maybe it is off topic*
@Mysteryagr,
can you tell me why i am getting this error?
-
make[2]: *** [data/devices/devices.json] Error 1
make[1]: *** [data/devices/CMakeFiles/run_devicesgen.dir/all] Error 2
make: *** [all] Error 2
The command "make" exited with 2.
-
i tryed to compile the dualboot patcher (downgrade branch) using travis.
but it is ending with this error
i froked the repo from your git.
froked git : https://github.com/Parthib24/DualBootPatcher
EDIT:i think i found the problem....it is problem in walton.yml ....i am so foolish
Click to expand...
Click to collapse
Yes, it was your device.yml
-
Good news for Walton Primo GH6 users, chenxiaolong has merged my pull request and now your device is supported officially, and you can enjoy automated builds
Rest of the devices are still pending, I hope he accepts them all

Mysteryagr said:
Yes, it was your device.yml
Click to expand...
Click to collapse
and why latest patches not working in my phone?
only that downgrad branch is working ..

Parthib said:
and why latest patches not working in my phone?
only that downgrad branch is working ..
Click to expand...
Click to collapse
You should ask in the original thread, anyway they were unstable updates.. I guess it is fixed now, cherry-pick new commits

[PATCHER][APP][OFFICIAL] DualBootPatcher For Lenovo Vibe K6 (karate)

{
"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 first dual boot project for Lenovo Vibe K6 (karate). 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 support for Lenovo Vibe K6 (karate) to the DualBootPatcher App, I am not the creator, 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 and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
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!
- 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 "karate" 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 lineage-13.0-20170307-UNOFFICIAL-karate.zip_dual).
- 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.
Click to expand...
Click to collapse
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
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
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:
All Downloads HereCheers ! we are officially supported
Note: You can download any version since "9.3.0.r6.g553fe6d3"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Lenovo Vibe K6 (karate) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/791
Known issues:
- You tell me !
Credits:
yshalsager For Adding the device !
@chenxiaolong for the awesome DualBootPatcher.

Notes:
1- If flashing Custom ROM Fail:
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Lenovo K6 Power not supported ?
When I open the app it displays an error message stating : " Cant determine boot partition .... device's codename K33a42 not recognized. "
As far as I know K6 Power's kernel is the same as vibe k6. Both of them have same codename - karate. Hence both devices should be supported.

Please support k6 power k33a42 also

nishadnmanish said:
Please support k6 power k33a42 also
Click to expand...
Click to collapse
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it

yshalsager said:
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it
Click to expand...
Click to collapse
Here is a log file
https://drive.google.com/file/d/0BzcRd6olCOzsT0ZwQ2RWRE52Q2s/view?usp=drivesdk

Magisk is not working with dual boot patcher.. so I edited..
Look into this post..
https://forum.xda-developers.com/showpost.php?p=74467090&postcount=12820
This edited magisk will eork with dual boot patcher..

yshalsager said:
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it
Click to expand...
Click to collapse
Please support k6 note

Finally, I found out the way.. to use magisk perfectly in non-primary ROMs of Dual boot patcher..
Guide is here.
https://forum.xda-developers.com/apps/magisk/guide-t3703596
Hopefully it will work with all ROMs!
Tested in my Lenovo k6 power in data ROM.

It does not work with Android 8.1. I cannot even set a kernel. Is there any fix for it?

Thomas_xxxxx said:
It does not work with Android 8.1. I cannot even set a kernel. Is there any fix for it?
Click to expand...
Click to collapse
Oreo isn't supported till now

yshalsager said:
Oreo isn't supported till now
Click to expand...
Click to collapse
Also the karatep or k6 note not supported till now.

yshalsager said:
Oreo isn't supported till now
Click to expand...
Click to collapse
You mean Oreo cannot be primary or secondary ROM? Or both? Because here is shown that there is 8.1 and 7.1.2 dual booted and you say Oreo is not supported -> https://i.imgur.com/4FIt9ga.png

firemax13 said:
Also the karatep or k6 note not supported till now.
Click to expand...
Click to collapse
Give me the logs, I'll add it

Thomas_xxxxx said:
You mean Oreo cannot be primary or secondary ROM? Or both? Because here is shown that there is 8.1 and 7.1.2 dual booted and you say Oreo is not supported -> https://i.imgur.com/4FIt9ga.png
Click to expand...
Click to collapse
It works on few devices as secondary. But for me, It's not working.

yshalsager said:
Give me the logs, I'll add it
Click to expand...
Click to collapse
What logs?

firemax13 said:
What logs?
Click to expand...
Click to collapse
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
Flash the GetLogs zip. The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.

Hello,
I tried this DualBootPatcher on AOSPExtended but when I want to set kernel, it states: "Could not determine the boot partition because this device codename "K33a48" is not recognized." Every solution is appreciated. Here are logs: https://drive.google.com/open?id=1EJuA1Up-5q9ImFhzPVSzfao9pSlAkOar
Thank you.

yshalsager said:
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
Flash the GetLogs zip. The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.
Click to expand...
Click to collapse
Here's the log.

Thomas_xxxxx said:
I tried this DualBootPatcher on AOSPExtended but when I want to set kernel, it states: "Could not determine the boot partition because this device codename "K33a48" is not recognized." Every solution is appreciated. Here are logs: https://drive.google.com/open?id=1EJuA1Up-5q9ImFhzPVSzfao9pSlAkOar
Click to expand...
Click to collapse
Change it to "karate" It'll work

[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 DualBootPatcherAnd 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.

Database Info

welcome