TWRP Recovery
{
"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"
}
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 Recovery
* 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.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1440x2560 (Note 4).
Note 4 Canadian
Note 4 Indian N910G
Note 4 Sprint
Note 4 T-Mobile
Note 4 US Cellular
Note 4 Verizon
Note 4 International N910F
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
Note 4 Canadian (trltecan)
Note 4 Indian N910G (trltedt)
Note 4 Sprint (trltespr)
Note 4 T-Mobile (trltetmo)
Note 4 US Cellular (trlteusc)
Note 4 Verizon (trltevzw)
Note 4 International N910F (trltexx)
TWRP Themes & Splashes (Note 4)
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 2.8.7.0:
Initial ground work for software drawn keyboard (_that)
Fix handling of wiping internal storage on datamedia devices (xuefer)
Allow DataManager to set and read values from the system properties (xuefer)
Fix crash when taking screenshots on arm64 devices (xuefer)
Fix error message after an ORS script completes (Dees_Troy)
Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
Add system read only option – more details below (Dees_Troy)
Add resize2fs and GUI option to run resize2fs (Dees_Troy)
Fix crash loop caused by empty lines in AOSP recovery command file (_that)
Prevent duplicate page overlays such as multiple lock screens (mdmower)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.
reserved 2
Give us version for F model.
Ogy77 said:
Give us version for F model.
Click to expand...
Click to collapse
uploading
Update
ogy77 said:
give us version for f model.
Click to expand...
Click to collapse
all download link ready now
uzairabdulmajeed said:
all download link ready now
Click to expand...
Click to collapse
Thank you sir.
I have twrp 2.8.7.0 in my phone now just flash theme right?
Ogy77 said:
Thank you sir.
I have twrp 2.8.7.0 in my phone now just flash theme right?
Click to expand...
Click to collapse
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
all info in #2 post
created separate threads for
T-Mobile
Sprint
Verizon
Aroma is not working for me...giving error
Sent from my SM-N910G using Tapatalk
splash
Did everything as stated in post#2
I don't understand the splash instructions.
Once i have the desired splash.jpg what do i do?
Can i put the jpg on the sdcard and than flash the AIK-Mobile-Installer?
Does anyone have a copy of the AIK splash installer? Its been removed. I want to change the splash to go with my newly themed recovery. Thank u guys.
Or.......tell me how to change it manually. Thanks
Hello sir i am using galaxy note 4 n910g twrp v3.0.2.0 and m unable to use pleas help me
Related
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
aromafm_galaxy5.zip (v1.91)
http://www.mediafire.com/?p5pdelpib6w8px
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
XDA:DevDB Information
PhilZ Touch Recovery : galaxy5, Tool/Utility for the Samsung Galaxy 5 I5500
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-07
Created 2014-07-12
Last Updated 2014-07-12
Very good recovery. :good:
Everyone should check it out.
I haven't found any bugs as of now.
UPDATE:
Changelog:
-Updated PhilZ sources to 6.23.8 (26.03.2014).
-Updated androidarmv6 sources. So, you'll be able to flash cm-ota without any Signature Verification error.
Below is the recovery.img file, flash using Terminal Emulator method:
recovery.img
Need feedback. If everything is fine, I'll add it to first post.
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
jpeps said:
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't try it until the developer says so!
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
RobsX2 said:
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
Click to expand...
Click to collapse
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Bhargav97 said:
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Click to expand...
Click to collapse
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
EDIT: Recovery has flashed and does work. Thanks!
RobsX2 said:
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
Click to expand...
Click to collapse
Then there is another simple solution.
-Install any CWM recovery (through ODIN).
-Now download any zip file of cwm recovery (use madteam.co if you don't find at xda).
-Open the zip and replace the recovery.img inside with this (PhilZ Recovery) one.
-Now, flash this modified zip file with the current cwm recovery (which you installed using odin).
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
RobsX2 said:
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
Click to expand...
Click to collapse
Have you done all the wipes?
Vagelis1608 said:
Have you done all the wipes?
Click to expand...
Click to collapse
Yessir
RobsX2 said:
Yessir
Click to expand...
Click to collapse
Did you pulled the battery to turn the device off when it hunged (at the "Android" screen)?
Have you tried booting up again?
Also, contact me via PM so that I will help you fix the issue. Let's not spam this thread .
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
deleted
Bhargav97 said:
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
Click to expand...
Click to collapse
ALL HARDKEYS WOORK FINE!
I just have one doubt.
When i reset to "Koush default" it gave me a netted grey background..
Whereas :"Philz default" gave a complete black background..
Is this supposed to happen.
Maybe I am too stupid
But where is on goo.im the PhilzTouch for this little jewel called galaxy5?
wrong post
{
"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
{
"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 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!