{
"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 managed to support Samsung Galaxy Prime ( G530x )
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.
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.
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. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
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] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
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
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
Dualboot Patcher G530x, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
faizauthar12
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Created 2017-03-26
Last Updated 2017-03-26
Reserved
Reserved
Here we go, the screenshots!
Can i use the stock rom as primary and other rom as secondary? Need help to this, haha
DexIdiotGT said:
Can i use the stock rom as primary and other rom as secondary? Need help to this, haha
Click to expand...
Click to collapse
Yes, that's the main reason why i port this tools
It means 2 different roms???
Dehieu2003 said:
It means 2 different roms???
Click to expand...
Click to collapse
Yes it is...
3, 4 or even 10 roms at once installed
Just like a dualboot or triple boot at desktop
faizauthar12 said:
Yes it is...
3, 4 or even 10 roms at once installed
Just like a dualboot or triple boot at desktop
Click to expand...
Click to collapse
Did you have a tutorial about this? I don't understand
Dehieu2003 said:
Did you have a tutorial about this? I don't understand
Click to expand...
Click to collapse
go to ROMs tabs to patch your current kernel with mbtool
then:
prepare your ROM that will be patched
open DualBoot Patcher app
go to Path Zips File
press the "+" icon
and press "Add flashable zip"
allow the permission...
choose the zip file ( rom )
now choose the partition configuration
Code:
Primary rom is the current rom..., use this option to update the rom..
Secondary till multi slot 3 will use system partition
Data slot will eat the internal storage..
Extsd slot will eat the external storage, Sdcard
after that give an ID for your rom
( this will give a dedicated folder for it)
if you give pacman rom with ID "1" , slot 1 will be reserved for pacman, if you want to upgrade it
go back to partition configuration then give the same ID..
patched?
flash it via recovery
faizauthar12 said:
Here we go, the screenshots!
Click to expand...
Click to collapse
Hey there,
I have tried this on my fortunave3g. My primary rom is stock 5.0 TouchWiz and I am trying to install AEX 4.6. But I am facing issues installing it. I followed the instructions given on the apps GitHub page.
Patched the ROM using the app and flashing it from the app, everything okay but stuck at "Patching system image unconditionally". I sat there for 1 hrs but nothing happen. So I closed that and tried installing it with TWRP. From there, it was able to create system.img and other images but it fails to run updater-script.
Have any idea why this happens?
Sent from my fortunave3g using XDA Labs
Related
Hey guys the much awaited DualBootPatcher is here for our otus don't believe me test out yourself
It can patch:
Custom kernels for multi support
ROMs so that they can be installed as secondary :victory:
Google Apps packages :silly:
SuperSU so that it can be used in other ROMs :cyclops:
xposed :laugh:
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.
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:
1.Install the app you want to share
2.Open DualBootPatcher and go to "App Sharing" in the navigation drawer
3. Enable individual app sharing
4. 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.
FAQ's
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
Downloading: Here
CREDITS
@chenxiaolong For the app
Me for porting it for you guys
@princetrishi for the video
@Darkaidz for compiling app
ORIGINAL THREAD
XDA:DevDB Information
Multiboot for otus, Device Specific App for the Moto E 2015
Contributors
Carlos Arriaga
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Testing
Created 2015-11-21
Last Updated 2016-06-27
Reserved
How To Report Issues ?
Getlogs.zip: getlogs.zip
If a multi-booted ROM is unable to boot, logs will be needed for debugging the issue. Please reboot into recovery without shutting down the device (ie. no removing the battery u cant remove battery in moto e ) and flash the GetLogs zip. This must be done immediately following the boot failure because some logs will be lost after a reboot 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.
Also, state whether the ROM reboots or hangs at the moto logo or the ROM's boot animation. If the ROM reboots, please state whether it reboots into recovery or not.
NOTE- now is supported CM13!!!!
Reserved
Installation Video
Thanks to YouTuber Starkdroid (@princetrishi) for making this awesome installation video!
Link For Video: here
Screenshots
{
"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"
}
Can i use stock rom as secondary one
halfpsycho said:
Can i use stock rom as secondary one
Click to expand...
Click to collapse
I have not tried it, you can have stock as primary and custom as secondary.
Carlos Arriaga said:
I have not tried it, you can have stock as primary and custom as secondary.
Click to expand...
Click to collapse
--Edit--
I remind you that we must have 3-4 GB free.
Carlos Arriaga said:
--Edit--
I remind you that we must have 3-4 GB free.
Click to expand...
Click to collapse
In internal or external
I have only 1 gb free in internal
halfpsycho said:
In internal or external
I have only 1 gb free in internal
Click to expand...
Click to collapse
External, after watching the video, I use a 4GB and 2GB ultimately left him free.
Carlos Arriaga said:
External, after watching the video, I use a 4GB and 2GB ultimately left him free.
Click to expand...
Click to collapse
Ok i will test it soon
Tested and worked very well don't have any problem except app sharing
Please reply i have a problem with app sharing
halfpsycho said:
Please reply i have a problem with app sharing
Click to expand...
Click to collapse
if you do not give logs or details of your problem not wait to get help
magdeoz said:
if you do not give logs or details of your problem not wait to get help
Click to expand...
Click to collapse
I am a new here so dont know how to take log
I'm using the version created by chenxiaolong, download here:https://snapshots.noobdev.io The same functions as i see here..what's the difference, what are added features?
I mean, anyone with rooted+ custom recovery on any device can send logs to him and ask to get their device supported in just few days without someone porting the app, why do all this if no new/different features are added?
The best app to port to other devices with this functionality will MULTIROM officially for nexus devices, capable of running other non android OS like Firefox OS!
New World Order (NWO)
Any chances to do this with marshmallow ROMS.?
hey guys! now is official with support marshmallow.
Downloads: https://snapshots.noobdev.io
:'(
Sent from my XT1514 using XDA-Developers mobile app
Keep It Up!
No working for me XOSP rom surnia XT1526 Sprint
I keep getting a notification saying my sdcard is corrupted after updating ramdisk and rebooting. Then I have to reinstall the primary ROM.
Edit: seems to only happen with Chrizsuma kernel.
{
"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 Dualboot For Samsung Galaxy Win & Core. 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 Samsung Galaxy Win & Core 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 (delos3geur) in case of [GT-I8552] and (arubaslim) if you are using [GT-I8262] 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-14.1-20170702-UNOFFICIAL-delos3geur.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.2.0.r221.g4661ff8e"
Screenshots:
In screenshots tab
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Samsung Galaxy Win & Core Support: https://github.com/chenxiaolong/DualBootPatcher/pull/642
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@JulianoXDA for testing and screenshots [GT-I8552]
@Gautam Maini for testing and screenshots [GT-I8262]
XDA:DevDB Information
[PATCHER][APP][OFFICIAL][GT-I8552][GT-I8262] Dualboot For Samsung Galaxy Win & Core, Tool/Utility for the Samsung Galaxy Grand Quattro
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r221.g4661ff8e
Stable Release Date: 2017-07-08
Created 2017-07-07
Last Updated 2017-07-08
Notes:
1- If flashing Custom ROM Fail :
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "delos3geur" || getprop("ro.build.product") == "delos3geur" || getprop("ro.product.device") == "GT-I8552" || getprop("ro.build.product") == "GT-I8552" || abort("This package is for device: delos3geur,GT-I8552; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- If in-app flashing fail (delos3geur):
- Flash patched Zip Form TWRP
Changelogs:
07/07/2017
- Initial Release
08/07/2017
- We are Officially Supported, Pull Request Here
Awesome work bro ???
We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/642
Any video to help installation process?????
link for apk for samsung glaxy gt i8262
I have downloaded too many files but no one is getting installed to my glaxy core gt i8262 .
Please help me providing the link of apk supporting glaxy core gt i8262.
gautamajay52 said:
I have downloaded too many files but no one is getting installed to my glaxy core gt i8262 .
Please help me providing the link of apk supporting glaxy core gt i8262.
Click to expand...
Click to collapse
https://dbp.noobdev.io/downloads/
yshalsager said:
https://dbp.noobdev.io/downloads/
Click to expand...
Click to collapse
Sir i have downloaded the apk from this site.
But neither is installing saying praising error.
I am on cosmic rom of samsung gt i8262.
Plzz help.
gautamajay52 said:
Sir i have downloaded the apk from this site.
But neither is installing saying praising error.
I am on cosmic rom of samsung gt i8262.
Plzz help.
Click to expand...
Click to collapse
U have to be on CyanogenMod 11
Gautam Maini said:
U have to be on CyanogenMod 11
Click to expand...
Click to collapse
Thanks sir.
{
"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 Samsung Galaxy S8 / S8+ [Exynos & Snapdragon]. 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 Samsung Galaxy S8 / S8+ [Exynos & Snapdragon] 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 (dreamlte) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-dreamlte-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
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.2.0.r295.g3b684238"
Screenshots:
In screenshots tabNo Screenshots available i need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Samsung Galaxy S8/S8+ Support: https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@bighand01691 for testing
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot For Samsung Galaxy S8/S8+ [Exynos & Snapdragon], Tool/Utility for the Samsung Galaxy S8
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-07-10
Last Updated 2017-10-03
Notes
If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" || abort("E3004: This package is for device: cheeseburger; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP
Changelogs
- 10/07/2017
Initial Release
- 11/07/2017
Featured on XDA Portal Here
- 18/07/2017
Add support for S8+ Here
- 15/08/2017
Add support for S8/S8+ [Snapdragon]
Thank you very much !
I used this app on my S7 edge to use both AOSP and TW-based ROM in dual-boot, and it works perfectly !
Now I can't wait to see AOSP-based ROMs for the S8
Does AROMA installer work here ?
BigBen60 said:
Thank you very much !
I used this app on my S7 edge to use both AOSP and TW-based ROM in dual-boot, and it works perfectly !
Now I can't wait to see AOSP-based ROMs for the S8
Does AROMA installer work here ?
Click to expand...
Click to collapse
+1, as most custom roms are build with Aroma currently, will it work with Dual Patcher?
`SBR` said:
+1, as most custom roms are build with Aroma currently, will it work with Dual Patcher?
Click to expand...
Click to collapse
You can test and report
yshalsager said:
You can test and report
Click to expand...
Click to collapse
i will test tonight, now in office.. but as you might have tested did you flashed any Aroma based rom?
`SBR` said:
i will test tonight, now in office.. but as you might have tested did you flashed any Aroma based rom?
Click to expand...
Click to collapse
Nope, i don't have the device
and my tester didn't test aroma
I tried this but with all aroma installers it doesnt work. Can somebody get it to work???
[email protected] said:
I tried this but with all aroma installers it doesnt work. Can somebody get it to work???
Click to expand...
Click to collapse
I'm afraid this app is not made to work with AROMA Installer
BigBen60 said:
I'm afraid this app is not made to work with AROMA Installer
Click to expand...
Click to collapse
What can we multiboot then?
I haven't seen any ROM here that doesn't require AROMA installer.
I'm afraid that the developer just didn't consider that at the moment for the S8, all the ROMs are using AROMA
But at least, we will be ready for dual boot once AOSP ROMs will come to us !
Or maybe now ROM developers will develop some ROMs that doesn't require AROMA to let us use Dual Boot Patcher
[email protected] said:
I tried this but with all aroma installers it doesnt work. Can somebody get it to work???
Click to expand...
Click to collapse
BigBen60 said:
I'm afraid this app is not made to work with AROMA Installer
Click to expand...
Click to collapse
What about flashing patched zip from recovery?
yshalsager said:
What about flashing patched zip from recovery?
Click to expand...
Click to collapse
I used this on my S7 and AROMA Roms should be installed via recovery after the patch.
S8+?!
@yshalsager
Thank you for this, great work.
Any plan for GS8+ anytime soon?
demster said:
I used this on my S7 and AROMA Roms should be installed via recovery after the patch.
Click to expand...
Click to collapse
How did u do that ??
[email protected] said:
How did u do that ??
Click to expand...
Click to collapse
I patched the zip containing the Rom with DualBootPatcher, went to recovery and flashed the patched zip.
You can not have permissions / root at the second rom?
demster said:
I patched the zip containing the Rom with DualBootPatcher, went to recovery and flashed the patched zip.
Click to expand...
Click to collapse
Will it automatic be as secondary rom when flash patched rom???
[email protected] said:
Will it automatic be as secondary rom when flash patched rom???
Click to expand...
Click to collapse
If you perform the steps in the tutorial/manual correctly, yes.
{
"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 Samsung Galaxy Note 8 (Exynos). 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 250+ supported devices and their variations.
Information:
I have managed to support for Samsung Galaxy Note 8 (Exynos) 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 (greatlte) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20171004-greatlte-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
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"
Screenshots:
No Screenshots, I need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Samsung Galaxy Note 8 (Exynos) Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/791
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@geiti94 for twrp sources
@yshalsager for adding the device !
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Samsung Galaxy Note 8 (Exynos), Tool/Utility for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher/pull/791
Version Information
Status: Stable
Current Stable Version: 9.3.0.r6.g553fe6d3
Created 2017-10-03
Last Updated 2017-10-03
Notes:
1- If flashing Custom ROM Fail:
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "greatlte" || getprop("ro.build.product") == "greatlte" || abort("E3004: This package is for device: greatlte; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP
Great
hell yeah
thanks
Awesome! I used this on my Note 4 too!
Now I can try a new rom without deleting my stock rom... Cheers!
Nice job, OP. One issue is support for the Korean Note 8. You need to add the "greatlteks" codename to support the Korean Exynos variant. I see in your commit that you've already added the greatltexx codename but not greatlteks. I just checked my phone and the partitions are the same as the ones you've listed in your commit.
Oke so I followed the steps. But when switching to a new rom a giet the message switching roms failed. Any help?
Verstuurd vanaf mijn SM-N950F met Tapatalk
Featured on XDA Portal !
https://www.xda-developers.com/dual-boot-dualbootpatcher-note-8/
Enjoy !
peacey8 said:
Nice job, OP. One issue is support for the Korean Note 8. You need to add the "greatlteks" codename to support the Korean Exynos variant. I see in your commit that you've already added the greatltexx codename but not greatlteks. I just checked my phone and the partitions are the same as the ones you've listed in your commit.
Click to expand...
Click to collapse
I'll add it. but shouldn't it work with just "greatlte" codename?
did not work, the system was hanged after install and reboot.
yshalsager said:
I'll add it. but shouldn't it work with just "greatlte" codename?
Click to expand...
Click to collapse
Korea model has different hardware identifier so it's basically a different phone for the app, greatlte won't boot on that phone.
How can I change the OS ? What to do if i want to boot stock and the other time the rom ?
I get some errors on Xiaomi RN3 PRO and does not boot
galiatsosgio said:
I get some errors on Xiaomi RN3 PRO and does not boot
Click to expand...
Click to collapse
I tried this on a Note 8 N950N and it worked great (after adding the greatlteks codename and recompiling). I was able to install more than one ROM and switch easily through the app. Can't wait for AOSP ROMs!
Will this work for the snapdragon variation?
peacey8 said:
I tried this on a Note 8 N950N and it worked great (after adding the greatlteks codename and recompiling). I was able to install more than one ROM and switch easily through the app. Can't wait for AOSP ROMs!
Click to expand...
Click to collapse
Great, i added the codename, can you tell me what's the other codenames for different variants? so i can add it officially
mason2smart said:
Will this work for the snapdragon variation?
Click to expand...
Click to collapse
No, but if you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it
What do these sentences in red color mean. I have tried many roms but I get the same result. It seems like the app can't flash the zip.
galiatsosgio said:
What do these sentences in red color mean. I have tried many roms but I get the same result. It seems like the app can't flash the zip.
Click to expand...
Click to collapse
After you patch the zip file for your preferred ROM location, you can flash the zip in TWRP recovery. The in-app flashing works for some ROMs and zips but not all.
[PATCHER][APP][OFFICIAL] Dualboot For Samsung Galaxy for Tab S3
{
"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 Samsung Galaxy Tab S3. 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:
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 ?
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 (dreamlte) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-dreamlte-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
Downloads:
All Downloads HereCheers ! we are officially supported
Note: You can download any version since "9.3.0.r293.g94c5fb6e"
Screenshots:
In screenshots tabNo Screenshots available i need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Samsung Galaxy Tab S3 Support: Commit
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@yshalsager for his Thread i copied I hope its ok [/CENTER]
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot For Samsung Galaxy for Tab S3, ROM for the Samsung Galaxy Tab S3
Contributors
schwabe93
Source Code: https://github.com/chenxiaolong/DualBootPatcher
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2018-01-01
Last Updated 2018-01-01
Reserved
Reserved
Thank you! I'm getting the tablet this week in the mail!
Sent from my SM-G935F using XDA Labs
Wow! Things are really picking up for tab s3 finally!