Ok, to clear the air, I am not the original Dev for this particular project. I had been working on a very similar project until I found this. It just needed for me to add support for our device. So I did just that. I made a prominent build and after extreme testing it is ready to be shared with you.
See Continuous Integration Builds at the end of this post for a link to download latest releases. All releases starting from November 5, 2015 and onward will support the Huawei Ascend Mate 2.
It can patch:
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 other ROMs
NOTE: If you want to dualboot a stock EMUI ROM, I highly recommend installing it as your primary ROM first. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
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.
Secondary: 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 partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher got support for sharing apps (deprecated) 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:
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 becomes 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.
How do I...?
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
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".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
WATCH THESE HOW-TO VIDEOS:
Credits to @superbass311 for making these videos.
It will demonstrate how to use this app effectively. If you read the instructions and still can't figure it out then this will be very helpful to you!
How to install Multi Boot Patcher:
How to flash another ROM with Multi Boot Patcher:
How to flash Xposed with Multi Boot Patcher:
How to share apps with Multi Boot Patcher:
Original Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Contributors
chenxiaolong, SHM
Version Information
Status: Testing
Continuous Integration Builds: https://snapshots.noobdev.io/
Created 2015-10-11
Last Updated 2015-11-07
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
MT2-User said:
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
Click to expand...
Click to collapse
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
{
"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"
}
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Edit: please try not to quote the entire first post. Can be a pain scrolling through if using an app.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Click to expand...
Click to collapse
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
MT2-User said:
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
Click to expand...
Click to collapse
If CyanDelta targets the patched ROM then yes, buy pointless to jump back to the cyandelta app. While using the Dual Boot Patcher app you can install from there. After the patch is made you go to, Roms, then click on the icon at the bottom right. It will have a phone with an arrow pointing down. In the same location press another icon with an add sign. Select the patch ROM. Then flash it through the app. Don't even need to go to TWRP at all unless its the primary ROM. This is explained in the OP already
Sent from my Ascend Mate 2 using Tapatalk
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
MT2-User said:
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
Click to expand...
Click to collapse
No worries, maybe @superbass311 will make a video for others to help them out. He likes making them videos lol.
Sent from my Ascend Mate 2 using Tapatalk
Oh sh+t! @SHM I did not see these post! He'll ya this will be my reading for tonight and I will try it all out then I'll make a video. Sweet!
Sent from my Ascend Mate 2 using Tapatalk
Interested in App Sharing.
From @chenxiaolong (http://forum.xda-developers.com/attachment.php?attachmentid=3318276&d=1431909206), space would be saved from keeping two/more APKs; however, if I have to install the same App in each ROM, how would that happen? Or actually the 2nd, and other subsequent ROM(s) just redirect the same App other than do real installation OR delete the same App after permission of the same shared App?
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
MT2-User said:
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
Click to expand...
Click to collapse
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
SHM said:
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
Click to expand...
Click to collapse
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 700 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
SHM said:
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
Click to expand...
Click to collapse
DId you install each App 3X? Or just backup/restore using TB?
MT2-User said:
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 500 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
Click to expand...
Click to collapse
For your first question, yes, but the primary ROM needs to be patched first in order for it to work. My recommendation with that is to grab the latest ROM zip for your primary and patch that zip using the app. Then install the patched zip to your primary. It will add needed files and binaries to make things more effective. This also makes sure not to mess with other ROMs as well. As for your second question about gapps, if you wish to install the gapps to a ROM, let's say PAC rom, and PAC rom is installed on your external SD, then you must patch the gapps zip using the configuration for PAC. When the patch is done, simply flash. Doing this insures the gapps is properly installed to that specific ROM. Otherwise it will just install to your primary ROM by default and if your primary ROM already has gapps then this isn't what you want it to do lol. You must patch the gapps zip for each ROM configuration to insure that it installs to that specific ROM. It takes no time to do this. Its easy, and quick. Give it a try
MT2-User said:
DId you install each App 3X? Or just backup/restore using TB?
Click to expand...
Click to collapse
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
SHM said:
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
Click to expand...
Click to collapse
Actually I got confused from the quoted content in OP saying in each ROM to install the App first.
MT2-User said:
Actually I got confused from OP saying in each ROM to install the App first.
Click to expand...
Click to collapse
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
SHM said:
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
Click to expand...
Click to collapse
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish between system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
MT2-User said:
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
Click to expand...
Click to collapse
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
How much space are you using running three ROMs?
SHM said:
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
Click to expand...
Click to collapse
:good::good::good:
Related
Hello I have made a very detailed video showing how to get Stock Samsung Lollipop (5.0.1) and CyanogenMod 12.1 (5.1.1) on the same phone [n910w8] dual booting.
THIS IS DONE AT YOUR OWN DESCRETION and I am not responsible if something goes wrong or you do something wrong. I have repeated the process at least 10 times to see how it works. Even did it on a Samsung Galaxy S4 with no issues.
This video is demonstrating the installation process for the Galaxy Note 4 n910w8 (Canadian snapdragon version used in video)
PLEASE TAKE YOUR TIME even watch the video a few times before you give it a try. In the end you can always flash stock Samsung Rom and do a factory reset.
I really enjoy using this feature and having the choice between two different roms on the same phone.
You can share apps from your stock Samsung Rom to your Cyanogenmod Rom without having to reinstall most of your apps. Saving lots of space.
I hope you enjoy.
Like.
Subscribe.
Click an add or two.
Thanks and a wonderful day.
Happy dual booting.
VIDEO LINK:
Samsung Galaxy Note 4 Dual Boot/multi Rom support:
https://youtu.be/CpegzNc4ZH0
Download Link Dual Boot Patcher:
https://snapshots.noobdev.io/
Download Link CM 12.1 (trltetmo) WORKING ON N910w8:
https://download.cyanogenmod.org/?device=trltetmo
Download Link Cyanogenmod Google Apps:
http://wiki.cyanogenmod.org/w/Google_Apps
Thanks:
chenxiaolong
Working on getting support brought to the Samsung Galaxy Tab S 8.4 also. Awaiting conformation, working with the developer. No garinties but fingers crossed that another top device gets dual boot compatibility.
Does anyone have a link to this build????
cm-12-20150413-NIGHTLY-trltetmo.zip
i keep trying on cyanogenmod website but the link is down.
If anyone could help it would be greatly appreciated.
It would really help with Google cardboar/vr testing. Native sbs is reported working on the rom I am looking for and it would be worth a try.
Nice mate
So by using FolderMount I am able to save so far 3gb of space on my data folder. I transfer app data to external SD card. Link the app data on external SD card with FolderMount which tricks the app into thinking it is installed on internal data.
Then I created a backup in FolderMount. Switch roms load FolderMount. Restore backup for FolderMount. Restore link app data locations because cm and touchwiz see external SD card different and FolderMount corrects this thankfully.
Click the green linking tab a few times and FolderMount will recognize the data.
As I said I have saved 3gb of room on my internal data having app data on external SD card.
If something like this was built into our dualboot patcher it would make things easier. Maybe if we spoke to the developer of FolderMount. If not using both FolderMount and Dual boot patcher I now have 3 roms on my Note 4 and almost 4gb free space on internal data between all 3 roms. Look at the pics of before in my previous comment and this one to see.
Just finding ways of maybe booting 4 roms on one phone.
Will report back.
Think I am on to something, let me know what you think. Give it a try possibly. I will be making a youtube video to help better demonstrate.
Before and after of data saved
My current Tri Boot state on my Note 4
Currently running Touchwiz stock lollipop 5.0.1 (primary partition), cm12.1(secondary partition) and cm12(data partition) all on the same phone.
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
samurai_vara said:
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
Click to expand...
Click to collapse
Try reinstalling cm12 and sharing again once you boot up.
Leonidas87 said:
Try reinstalling cm12 and sharing again once you boot up.
Click to expand...
Click to collapse
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
samurai_vara said:
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
Click to expand...
Click to collapse
Once you do those 3 steps all apps should share between both the primary and secondary Rom once you do a quick reboot after enabling the app sharing. Whenever you install a new app on one or the other Rom and then boot in to one of the roms you will usually see android upgrading or upgrading apps something like that during boot up. But yea you only need to enable app sharing in the second Rom not primary. Everything from the secondary Rom seems to share with the primary Rom. Overall it is a great system. Complicated in thought but it works. Once you get a feel for it you will be impressed.
Nice. I will try this when I get home. Been wanting to run CM but gear vr has me stuck on touch jizz. Will report how it works.
Sent from my SM-N910T using Tapatalk
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
chrisa887 said:
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
Click to expand...
Click to collapse
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Leonidas87 said:
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Click to expand...
Click to collapse
I see, I want the cm12 as my secondary rom so I patch it first then install it then I patch the gapps then install them then I can reboot to secondary rom and set everything up right?
Sent from my SM-N910T using Tapatalk
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Leonidas87 said:
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Click to expand...
Click to collapse
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Great job, thank you dev.
I have question about App Sharing. Should I install Gapps on both roms or only on Primary and share them?
chrisa887 said:
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yes patch then install. No need to reinstall Google apps all that will still be there.
Joshndroid's UNOFFICIAL CM13.0 BUILDS
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.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"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"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
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 or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App 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:
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.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Bug reports without logs from flashing the GetLogs ZIP will be ignored and the post deleted.
Please make sure you read the entire first post properly, everything important is given here!
Reserved
hey, i'm using a stock mm 288 for primary rom.
but, when i flash anyting to data slot for secondary rom, i cant get root to work.
i've already try flash patched BETA-SuperSU-v2.72-20160510112018 but didn't work.
can you help me?
sorry for my bad english
@MSF Jarvis
hi thnx for great job.it's run perfect.
Error installation
We got found error when try installation dual boot
arfans said:
We got found error when try installation dual boot
Click to expand...
Click to collapse
Which ROM were you trying to install?
danthecoolboy said:
Which ROM were you trying to install?
Click to expand...
Click to collapse
Originally stock rom P1a42_S288_160721_ROW_RAW and i'm trying install custom rom DotOS
Thanks a ton for the update @MSF Jarvis
MSF Jarvis said:
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
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 or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App 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:
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.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Click to expand...
Click to collapse
Followed the guide in my Lenovo Vibe p1a42 rooted running custom AOSP Extended 5.6 . I tried installing Custom Carbon 5.1 Rom. The installation/flashing process is completed successfully, But after choosing the second Rom and rebooting the device, the boot open TWRP Recovery. And further boots also open recovery. I had to reinstall the AOSP Extended Rom using TWRP to boot into Android. Can you please suggest what would have gone wrong on my end which resulted the reboot to boot into recovery rather then the second ROM.
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the App from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App 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:
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.
(Hope my analogy didn't suck too much )
How do I?
Switch the ROM if something doesn't work properly ?
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Downloads
App - Here
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Lenovo Vibe K5 & K5 Plus , Tool/Utility for the Android General
Contributors
Dreamstar, chenxiaolong
Version Information
Status: Beta
Created 2016-12-19
Last Updated 2016-12-25
Reserved
Thanks for this!
Can anyone confirm this working?
Can confirm this is working in Lenovo Vibe K5 a6020a40 device thanx for this you are awesome
This is truly awesome!!
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
netship said:
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
Click to expand...
Click to collapse
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Wow man just wow!
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Thank you Very much!!
Recieved error message while installing secondary rom.
Guys any solution?
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
You may try this.
netship said:
You may try this.
Click to expand...
Click to collapse
I tried bro still same problem...
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Upload that log file here
Error log
App sharing not working.. or I'm doing something wrong.. don't know but not working for me.
What about efidroid manager
Can anybody try to port it to lenovo k5??
Last I checked with 10/4 aicp nightly, it's not working. Needs some fixes.
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Same here tried changing name no success
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Usage with my Proton Kernel is recommended to get the most out of your phone. The ROM does not include Proton Kernel, so you will need to flash it yourself. The ROM will still work with other kernels, but you will not get the benefits of Proton Kernel.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Thank you very much for posting this. I'll definitely be checking it out. Your Proton kernel is quite good already. Interested to see how the ROM functions too.
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
GoldElocks said:
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
Click to expand...
Click to collapse
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
letrain02 said:
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
Click to expand...
Click to collapse
microG is supported on the non-gapps build, not included. The gapps build includes full gapps.
Thank you for awesome rom, big plus for microg support. Will flash as soon as my Bramble arrives.
did flash all. now google logo, then a fire with beaker on screen.
edit: nevermind...guess that was the loading screen. took a few minutes. didn't seem like a "loading screen"
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Estebanium said:
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Click to expand...
Click to collapse
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
kdrag0n said:
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
Click to expand...
Click to collapse
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Estebanium said:
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Click to expand...
Click to collapse
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
kdrag0n said:
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
Click to expand...
Click to collapse
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
GoldElocks said:
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
Click to expand...
Click to collapse
Ocwa said:
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Click to expand...
Click to collapse
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Estebanium said:
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
Click to expand...
Click to collapse
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
OptoChip said:
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Click to expand...
Click to collapse
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
kdrag0n said:
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Dynamically sized partitions explains the "no free space" (and it makes total sense to layout the system partition this way). I was trying to use Magisk Systemize, took me revisiting it to realize that I didn't have Busybox installed. Installing the Magisk BusyBox module enabled me to Systemize the Phone app. Many thanks!
kdrag0n said:
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
wilspeak said:
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
Click to expand...
Click to collapse
Yes. The hotspot option comes with it from what I have tried.
J-I-N-X said:
Yes. The hotspot option comes with it from what I have tried.
Click to expand...
Click to collapse
Thank You for your time
I cant manage to root this rom with proton kernel even on stock cant root pixel4a 5g any guide or help apriciated....