Database Info

[Unofficial] [PATCHER] [APP] DualBoot Patcher APP for Exynos7870 and 7880

I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. 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
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. 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.
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.
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.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
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
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
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy J7 (2017)
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03

Thanks for this MOD

will definitely use this when/ if we get los for our phone thanks

How can I flash GApps ??

is this mod still alive ?

Magisk Dual Boot For Lg Stylo 2 Plus

Warning:This is an experimental find and i am not held liable if you brick your device (go into twrp and start over)
Installing Magisk in a Dual Boot Environment:
Things you need
(i advise to save all to your external card if you have one so it wont be erased):
Need to Create:
primary rom
secondary rom
gapps (unless you prefer one in link)
gapps in secondary (dual)
included in following link:http://www.mediafire.com/folder/95yswgomsz3d3/Magiskdualboot
gapps aroma(both normal and dual)
no verity zip(both normal and dual)
su remove(both normal and dual)
magisk 14.3 dualboot
dualbootutilities(just in case something goes wrong)
Dual boot patcher app
Step One:
Assuming your on the latest twrp for this rom (check official twrp app)
you will want to go to wipe in twrp and wipe data,
reboot to recovery,wipe advanced options and wipe everything except internal storaage and external storage then reboot into recovery again
Step 2:install primary rom,no verity,gapps,remove su addon,and magisk 14.3 dualboot zip.
(when everything loads set it up as you would normally making sure everythings up to date from play store,magisk manager update,etc
Step 3:install every magisk module you wish to have and reboot (once rebooted go into modules and unclick everything and reboot)
Step 4:get a root file manager and go into /data/adb in the root folder (make a copy of magisk.img and put on your sdcard)
step 5:install dual boot patcher app,run it,grant permission and when it asks to set kernal do so (everytime you change a rom it may ask you to set kernal)
step 6:use the patch zip file to patch your primary rom as an upgrade,then flash the patched primary rom then reboot to system (this allows nonconflict with other roms to avoid error and enables app sharing on the app)
step 7:assuming you downloaded the secondary rom,go to patch zip file section in the patcher app and add flash file and select your second rom zip and put it under secondary slot
step 8: patch as well in secondary:no verity zip,su remove zip and gapps.install the patched dual rom and files in twrp then reboot to system (it should start setting up your second rom)
step 9:update everything in second rom from play store plus do the setup
step 10:reboot back into recovery and install the dualboot magisk 14.3 zip again.reboot system and update that magisk manager and zip
step 11:install dual boot patcher app on the second rom now and itll ask you to set second kernal when you go to roms,do so
step 12:reboot back to recovery and then go advanced>file manager and then go /data/adb and select magisk.img copy file to data/multiboot/dual/data/adb/ then reboot to system.
step 13:now when you reboot into second rom you will notice in modules in magisk manager all the modules you had in primary are there
(be careful when enabling some as some will not work but its a small list)
(Warning:if theres any updates to any app you need to follow steps 12 and 13.
installing modules directly from the manager in second rom can cause bricks or crashes)
Step 14:have Fun
Tested Modules that work:
android mic fix,app systemizer,audio modification library,boot animation replacer,detach(doesnt really hide market links nomore but doesnt crash),google camera patch,google framework,init.d linker,iybp,mm recovery,max resolution for youtube,priviledged api booter,ram management by crok,secure if,single user mod,splatoon 2 font,sysconfig patcher,terminal app systemizer,terminal app debloater,teethering enabler,ts-bindsunified hosts adblock,universal dee buffer remover,busybox, universal safetynet fix beta v 5,volume steps increase,wifi bonding and xmlpak

Will give it a shot when I get the chance

could someone help me just install magisk with the either the stock rom, or even any of the custom ones?
Im unable to find a step by step guide similiar to this one, for installing magisk on lg k550 (without the dual boot option, as im a newbie and prefer not to add any extra possible complications )

takethe5th said:
could someone help me just install magisk with the either the stock rom, or even any of the custom ones?
Im unable to find a step by step guide similiar to this one, for installing magisk on lg k550 (without the dual boot option, as im a newbie and prefer not to add any extra possible complications )
Click to expand...
Click to collapse
All the ROMs on the 2 plus work for both models. Also do you have telegram. We are all there to give advice. I'm more the magisk expert though you can shoot a line thru there or follow guides we have posted. We welcome all new members
t.me/lgstylo2plus

Frosthaxx said:
All the ROMs on the 2 plus work for both models. Also do you have telegram. We are all there to give advice. I'm more the magisk expert though you can shoot a line thru there or follow guides we have posted. We welcome all new members
t.me/lgstylo2plus
Click to expand...
Click to collapse
I am looking for something similar but for LG Stylo 3 Plus.
Sent from my LGMS428 using XDA Labs

[GUIDE] [Q&A] [TREBLE] From Stock to Treble - everything you need to know!

Here I will share all the info you need to know about using Treble on the Mi A1. Everyone is more than welcome to ask questions and clarification here, I am happy to answer and will update this thread over time. Thanks!
Contents
0. Key Terms
1. Restoring to Stock
-- 1.1. Requirements
-- 1.2. Full-device backup
-- 1.3. Stock restore process
2. "Treblize" (repartition) the device
3. Your first Treble ROM install
4. Installing AIO's, GSI's, Vendors and More
-- 4.1. Install a Treble AIO
-- 4.2. Install a Treble GSI
-- 4.3. Install/update a Vendor Pack
-- 4.4. Install a non-Treble ROM
-- 4.5. Restore a TWRP backup
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
6. FAQ and Troubleshooting
----------------------------------------------
0. Key Terms
Throughout your Treble adventures, you may see lots of new terms. Here I will explain them all. This is essential reading!
Treble
Treble is the broad term of a new Android architecture model of splitting the system into two partitions:
System: where the Android OS goes, i.e. Oreo or later operating system;
Vendor, where the device-specific files go, such as drivers.
Before Treble, both the Android OS and device-specific files would live together on system. See below for a more detailed description of Vendor.
"Treblizing"
May also be called Treble-enable, Treble-conversion or some variation of that. This is the process of converting a non-Treble device to a Treble-capable one, unofficially, by changing the partition map of the device. This involves shrinking an existing partition - such as userdata or system in the case of the Mi A1 - in order to create a new vendor partition - or two vendor partition in the case for our Mi A1, one for each slot. Treblizing is just the preparation stage - you still need an AIO installation (see AIO below) before you are actually able to use a Treble ROM.
Vendor
Also known as Vendor Pack or Vendor Image. In the context of Treble, this is a standalone vendor image (either as a ZIP or usually as an IMG) that can be flashed to your Treble-enabled device for it to be compatible with a Treble system/ROM. These are similar to a kernel in the way that they are flashed to their own partition on your device and are compatible with many Treble ROM's. They are also similar to a kernel in that they are made specifically for one device to provide the low-level functionality of the system. It mostly includes drivers, but can also include apps and overlays that are automatically added at runtime to the Android OS that's living on System.
Treble developers for the Mi A1 may release standalone "vendor.img" for use on other ROM's - usually GSI's (see description of GSI below) but they are also part of an AIO (see description of AIO below).
GSI
Stands for "Generic System Image". This concept, introduced and developed by @phhusson is the creation of a System image that is device-agnostic - that is, it is a ROM that is designed to work with an existing Treble device, as long as the device has a GSI-compatible Vendor and kernel installation. For devices with official Treble support, phhusson makes the effort to try and adapt his GSI system for compatibility - but for unofficial Treble device like the Mi A1, it's our (tissot developers) responsibility to make a Vendor/Kernel that is as GSI-compatible as possible.
AIO
Stands for "All In One". This is a Treble firmware that includes a Kernel, System and Vendor image in the one ROM ZIP. This provides an all-in-one Treble experience through a device-specific Treble ROM. AIO's are designed to work well with their own ROM but should also strive to be compatible with a GSI.
An explanatory chart of Key Terms
{
"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"
}
Click here for full size image.
Ignore this spoiler (coded link to thumbnail because XDA thread edit breaks the IMG link)
Code:
https://img.xda-cdn.com/ic22y2zu5yi9EClrY11FS8FU5C0=/https%3A%2F%2Fimg.xda-cdn.com%2FU8u8IdA66PAFHOM4PsKNQbFHwSA%3D%2Fhttps%253A%252F%252Fimg.xda-cdn.com%252Fo1fMEJDyu5x7pv2B9KB323i8_IA%253D%252Fhttps%25253A%25252F%25252Fthumbs2.imgbox.com%25252Fd7%25252Fc2%25252FDxa93pOz_t.png
----------------------------------------------
1. Restoring to Stock
For the sake of consistency, I highly recommend everybody revert to a clean stock state. This ensures that as many of us are coming from the same place to eliminate inconsistency with reported bugs. If you're impatient or experienced though, feel free to skip this - but if you have issues, be sure to try again from here before asking for help.
Note that this will also restore you to the stock partition map, i.e. before "Treblizing".
1.1. Requirements
Unlocked bootloader and EDL access/drivers. See FAQ at bottom of this post for details on EDL.
Modern fastboot binary - it needs the "--set-active" option. Check with fastboot --help to see if it's listed in the usage.
Latest/recent official firmware package. Recommended "V.9.5.10.0.ODHMIFA" only because it's what I used, if you're not sure - but anything newer should be fine too.
Recent MiFlash version. I used 7.4.25 which can be downloaded from here.
1.2. Full-device backup
HIGHLY RECOMMENDED. While all this is relatively safe (as safe as device modding can be), I cannot be held responsible for any data loss or bricks. You can make a Low-Level backup with my tool here. You can use the "skip-systems-and-userdata" partition list to save time, since those can be backed up in TWRP anyway. This is here mostly as a failsafe.
Also backup your internal storage files. The Treblizing process may wipe your internal storage.
1.3. Stock restore process
Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Optional: If Wifi is broken (you can check by booting ROM), flash the "tissot_images_V.9.5.10.0.ODHMIFA___persist-only" in MiFlash under EDL, attached. Just extract the ZIP and browse to the folder in MiFlash. You can replace the persist.img from official V.9.5.10.0.ODHMIFA or another ROM if you want to be sure it's genuine. Credits to @AlexAiS for discovering this.
Remember - you backed up your original persist.img in step 1 anyway, so this is not risky.
I am not sure how this works exactly. It seems MiFlash in EDL is able to re-build a MAC address while flashing the persist. I don't know where this MAC comes from though.
----------------------------------------------
2. "Treblize" (repartition) the device
If you looked at the chart, you'll know that this is just the first step. You will need to actually install an AIO ROM after this part. This is a ONE TIME PROCESS for getting Treble capability on your device.
Repartitioning is relatively painless ever since I created TWRP with Treble Manager. Read on for a walkthrough.
Fastboot boot to TWRP with mohancm's recovery img (i.e. recovery-3.2.1-1) if you don't already have TWRP installed. Do not get the installer - we're using the one with Treble Manager instead.
Install the latest TWRP with Treble Manager (v1.2 at time of writing, but of course latest version is best) then Reboot Recovery to actually load it. Be sure to read about TWRP with Treble Manager in that thread to understand how it works. If you have any questions specifically about the TWRP and Treble Manager, please ask in that thread.
Format Data in Wipe menu (to remove Stock encryption), then Reboot Recovery again (maybe not necessary but it can't hurt).
In TWRP, go to Advanced > Treble Manager and repartition the device by following the wizard. Userdata shrink is recommended, as per the in-menu description explaining this. Just try the Treble Manager and see yourself - it will ask you one last time before repartitioning so don't worry about it wiping without warning. Alternatively, you can just check the screenshots.
After finished it will reboot TWRP. You are now ready for installing a Treble AIO (and then a GSI, if desired), but be sure to still read on, especially the next section below (there is a known issue that you need to work around - otherwise a bootloop will occur).
----------------------------------------------
3. Your first Treble ROM install
THERE IS AN IMPORTANT STEP THAT MUST BE FOLLOWED HERE WHEN INSTALLING YOUR FIRST TREBLE ROM. FAILURE TO FOLLOW THESE INSTRUCTIONS WILL RESULT IN A BOOTLOOP.
Make a note of the current slot (in Reboot menu). If you followed this guide from Section 1, you should be in Slot A. If you're not, just swap any mention of Slot A and B in these steps.
Download a Treble AIO ROM (such as RR Treble Experimental) and flash in TWRP. This is required even if you want to use a GSI, since it has the required Vendor Pack and Kernel.
Immediately install TWRP with Treble Manager again, as you usually do, to re-inject TWRP into the new ROM boot image.
Reboot Recovery, NOT SYSTEM.
Confirm in Reboot menu that the device has successfully switched to Slot B. If it is still stuck in Slot A, this is a one-time bug that must be solved now - if you do not fix this then you will just bootloop.
If it is still stuck in Slot A, you must reboot to fastboot (make sure you have a current version, as explained in Section 1.1. "Requirements") and manually run the command:
Code:
fastboot --set-active=b
...after doing this once, slot switching should work fine in TWRP again. You should never have to do this again (unless you go back to stock then re-Treblize again).
In case you didn't know, all ROMs for our Seamless device actually install into the *other* slot that isn't currently active - that's why you always need to Reboot Recovery first before installing Magisk or Gapps and such.
I advise users from now on to keep an eye on their Slot switching whenever you install an AIO ROM to make sure it worked. If it happens again after these steps, please report it to me with as much details as possible (we're still trying to figure out this bug).
After following these steps, you should be able to flash Treble ROM's just as you would a normal ROM from now on. Your Treble transformation is complete. But read on for more help and walkthroughs if you need it.
----------------------------------------------
4. Installing AIO's, GSI's, Vendors and More
Assuming you followed Section 3 above, you are now ready to install anything as usual. But some users have expressed confusion about what they can and can't do from this point, so I will give you some example choices here.
4.1. Install a Treble AIO
At the time of writing this guide, currently the only Treble AIO is the RR Experimental build. If or when others come along, you can just install them like normal ROMs. We already did this in Section 3 above, but here is a simplified summary of that process:
Flash the AIO ROM in TWRP with Treble Manager 1.2+ - do NOT reboot
Immediately reflash TWRP with Treble Manager 1.2+ so you get the Treble-compatible TWRP back
Factory Reset if it's a different ROM, as you usually would in this case.
Make a note of which slot you are on right now
Reboot recovery
Make sure your device has now swapped to the other slot by checking the reboot menu. If it has not, you will need to repeat the fastboot --set=active step as explained in Section 3. (I don't know if this is necessary again - but I just want to warn users to be aware of this known bug)
Now that the slot has changed, you can install Gapps, Magisk and/or whatever other compatible additional mods you want.
4.2. Install a Treble GSI
You may remember from earlier that the Treble GSI's are just System images that use your existing Vendor and Kernel. We already have a Treble kernel and Vendor from an AIO (Section 3 or Section 4.1. above), so this is quite simple:
Download any GSI/Phh-Treble ROM's from the Treble-Enabled Device Development section and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Flash the IMG to "System Image" in TWRP with Treble Manager 1.2+
Factory Reset if you're changing ROM's
Install any other mods (Gapps, GSI-compatible Magisk [i.e. 16.4 beta or later], etc.). You may need to boot the ROM once before installing any mods - this varies per GSI. Some existing mods may also be outright incompatible with the GSI.
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP or Reboot Recovery.
4.3. Install/update a Vendor Pack
While you're on a current and working AIO or GSI slot, you can flash a vendor.img to update the driver/device level stuff for that ROM. This could be done to e.g. fix the Camera. This is useful if you're running a GSI.
Download a vendor.img from your AIO or Vendor Pack provider (e.g. RR AIO Experimental) and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Optionally make a TWRP backup of Vendor (or more) if you want to be careful and it's your daily (I always do).
Flash the IMG to "Vendor Image" in TWRP with Treble Manager 1.2+
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP, Reboot Recovery or install any Mods (Gapps, Magisk, etc) UNLESS it's a Vendor mod (as of time of writing, no Vendor mods exist yet).
4.4. Install a non-Treble ROM
This is simple, same as you're used to before Treblizing. But do note that this is only possible if you chose to resize Userdata when repartitiong with Treble Manager.
Download the ROM to your device
Optional - make sure the active slot is one with a Treble AIO/GSI ROM already - remember that ROM ZIPs install to the OTHER slot, not the currently active one; so this way you can easily switch back to the Treble ROM just by doing a Factory Reset (or TWRP restore of Data) and slot switch.
Factory reset
Install the ROM as per usual procedure (Install ZIP, reflash TWRP with Treble Manager 1.2+, reboot recovery to allow slot switch, install Gapps + Magisk + Mods, etc., reboot).
4.5. Restore a TWRP backup
There is nothing special about restoring a backup. Even if your backup was from a non-Treble ROM, you can restore that backup on a Treblized device. Obviously, though, any Treble ROM backup can only be restored on a Treblized device.
----------------------------------------------
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
After you have confirmed that TWRP is booting in to the correct slot (see Section 3), you're ready to install other ROMs (see Section 4) followed by mods. I did briefly go over mods in Section 4, but I'll go into more detailed info about compatibility here.
Any usual Gapps should work fine, just as long as you flash after the slot is correctly set. Note that RR Camera (GCam) requires Gapps to be installed. I used Nano, they worked fine.
Also note that some GSI's will require you to boot the system first before installing Gapps.
Custom kernels must be marked Treble compatible for our device. Specifically (info for kernel developers) this means adding slotselect flag to vendor entry in DTB, and disabling dm-verity (so we can inject vendor changes to system).
It is reported that standard Magisk will work in RR Treble ROM, but it does NOT work on GSI. You need Magisk 16.4 beta or later for GSI's. Also see the FAQ section at the end for more info on the Magisk situation.
Some other ZIP's might need updating for Treble, really unsure. Experimentation is welcome. Just be sure you make TWRP backups before testing anything, of course!
--------------------------------
6. FAQ and Troubleshooting
Q) I get "cannot receive hello packet" in MiFlash
A) Just reboot EDL mode and try again. Usually only happens if you try to flash in EDL twice in a row. See the Low-level Backup/Restore/Unbrick toolkit thread for more info about EDL.
Q) How to Magisk with Treble? What is the TWRP and Magisk interaction?
A) Best to use Magisk 16.4 beta or later, it's reported as working on GSI's. Also note that Magisk is installed to the boot ramdisk (the same place as where TWRP goes) and this has the following implications:
Whenever you flash the TWRP installer, you will need to reinstall Magisk *after* you Reboot Recovery
TWRP installer will flash to BOTH slots, but Magisk will only flash to the CURRENT slot. So if you flash TWRP installer, it may erase any Magisk install on the inactive slot.
TWRP survival (in my recent TWRP builds) backs-up and restores the whole ramdisk. This will include Magisk, if it was already on the boot slot that it backs up.
Q) EDL mode? Eh?
A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
Code:
fastboot oem edl
EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
Other important notes:
You will need good QDLoader drivers. These drivers gave me the best results.
You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
Make sure you use a good USB-C cable.
Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?

parasnarkhede said:
can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?
Click to expand...
Click to collapse
Yup. Just flash a stock persist.img in EDL mode. But backup your original in case, it could erase or change your BT MAC too.

@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.

Typhus_ said:
@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.
Click to expand...
Click to collapse
EDL mode is like fastboot mode, but even lower-level.
You enter into it with:
Code:
fastboot oem edl
It is needed by my backup tool yes, but it's also used to flash in MiFlash.
Will update the guide and FAQ with this info.

How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?

Ahmed Al-Sayed said:
How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?
Click to expand...
Click to collapse
Just browse to the folder with MiFlash....

CosmicDan said:
Just browse to the folder with MiFlash....
Click to expand...
Click to collapse
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?

Ahmed Al-Sayed said:
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?
Click to expand...
Click to collapse
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash

CosmicDan said:
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash
Click to expand...
Click to collapse
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?

Ahmed Al-Sayed said:
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?
Click to expand...
Click to collapse
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!

CosmicDan said:
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!
Click to expand...
Click to collapse
Thanks !

Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?

Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.

sudipta08sarkar said:
Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?
Click to expand...
Click to collapse
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
CosmicDan said:
2. Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Click to expand...
Click to collapse

Ritik99 said:
Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.
Click to expand...
Click to collapse
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.

CosmicDan said:
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
Click to expand...
Click to collapse
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?

Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.

CosmicDan said:
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.
Click to expand...
Click to collapse
Yup.. that what make people say "i do it the same as instruction and bricked my devices." It is because u just copy what other ppl do and dont know what exactly u do lol... Fir me, what in text is more worth.. because it explain everithing. And the video just a guidline of what u read.

sudipta08sarkar said:
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?
Click to expand...
Click to collapse
Yes. Well, depends.
RR Treble has Vendor included, because it needs it. GSI's are just a system image that use your existing vendor.
squallbayu said:
Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.
Click to expand...
Click to collapse
If you.can tell me exactly what "Play Certified" actually is, then I might be able to answer that question.
The TWRP with Treble Manager tells you the size change.

[Guide][Video/Text] Install Android 9.0 Pie GSI on Moto X4 (Windows/Mac/Linux)

Install Android 9.0 Pie GSI on Moto X4 (Windows/Mac/Linux)​​​Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4: You will loose all your data. Make sure to backup your data.
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.
*/
Not Working :
headphone jack
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video
Moto X4 A/B Slots Explained
Steps
1. Download all the files listed in downloads section and place them inside one folder.
2. Unzip A/B GSI zip file. Unzip fastboot and adb zip file. Rename treble image file to twrp-payton-treble.img. move twrp img file to platform-tools folder.
Create folder PieGSI in internal memory of phone.
Move below files to AndroidP folder on phone
* Android P GSI Image
* Gapps
* Trebelized Lineage OS
* trebelized twrp zip file
* partition copy zip file
Reboot device into bootloader mode.
3. Navigate to platform-tools folder. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-payton-treble.img
Mac/Linux
Code:
./fastboot boot twrp-payton-treble.img
4. Once booted into TWRP,
Go to install, Navigate to PieGsi folder.
Flash the partition copy zip file.
5. Next, go to home screen.
Wipe -> Swipe to factory reset.
Main menu, click on Install. select Lineage OS zip, add more zips and select TWRP zip. Swipe to flash. Once done, go to main menu. Reboot -> Recovery.
6. Once back in TWRP. Go to wipe, Advanced. Select system,data and cache. Swipe to wipe. Go back to TWRP main menu. Click on Install, select Image option on bottom right. Select AB GSI img. Select System. Swipe to flash. Once done, go to main menu. Reboot -> Recovery.
7. Once back in TWRP. Install -> Select gapps file. Swipe to flash. Reboot -> System.
8. If stuck in bootloop. Reboot to twrp. Go to wipe. Select format data. Enter yes. This will wipe your internal storage so make sure to backup. Reboot -> System.
9. Android 9.0 Pie. Profit!
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
Downloads
Partition Copy Zip File :- https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Lineage OS Moto X4(Treble) :- https://www.androidfilehost.com/?fid=5862345805528063250
TWRP Image File Moto X4(Treble) :- https://www.androidfilehost.com/?fid=5862345805528063210
TWRP Zip File Moto X4:- https://www.androidfilehost.com/?fid=5862345805528063564
Android 9.0 Pie GSI Download Links (Download arm64 AB):- https://github.com/phhusson/treble_experimentations/releases
Gapps for Android 9.0 Pie (Use Micro) :- https://builds.nezorfla.me/?dir=opengapps/pie/arm64
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/
ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Important Links
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...ice-development/aosp-9-0-phh-treble-t3831915/
Donations :
Donate to Phhuson
Buy me Coffee.
Contributors
munchy_cool, erfanoabdi
@phhusson

Hi, have you tried this version on the x4? What things do not work with that version of GSI on the X4 ?
thanks......

DarkLara said:
Hi, have you tried this version on the x4? What things do not work with that version of GSI on the X4 ?
thanks......
Click to expand...
Click to collapse
yes tried it. headphone jack is the only thing thats broken.

munchy_cool said:
yes tried it. headphone jack is the only thing thats broken.
Click to expand...
Click to collapse
Can't it be fixed with the flashable zip we used for first pie GSI?

igna.98 said:
Can't it be fixed with the flashable zip we used for first pie GSI?
Click to expand...
Click to collapse
dont know ..try and let us know :highfive:

munchy_cool said:
dont know ..try and let us know :highfive:
Click to expand...
Click to collapse
I tried and it did not work....
Edit: NFC and tethering dont work...

I do not know if it's well done but I tried to get the logcat..

Headphone jack doesn't work ,
also network hotspot doesn't work.

new version of Android 9.0 Pie GSI ...
It contains the same errors as the previous version.

I don't have a navigation bar, not that it has the new style, it's non existent.

QWZR II said:
I don't have a navigation bar, not that it has the new style, it's non existent.
Click to expand...
Click to collapse
I don't remember now which line you can edit to make it appear, but you can install a magisk module to make the nav bar appear.

QWZR II said:
I don't have a navigation bar, not that it has the new style, it's non existent.
Click to expand...
Click to collapse
I have a similar problem but on the contrary I wanted to make the navigation bar disappear, when I started I put a backup of the cloud and the navigation bar appeared and now I can not get it xD ....

abrfilho said:
I don't remember now which line you can edit to make it appear, but you can install a magisk module to make the nav bar appear.
Click to expand...
Click to collapse
qeum.hw.mainkeys=1 is off qeum.hw.mainkeys=0 is on. For me the recents button doesn't work though and when the navbar is on it (recent apps) doesn't even work with the fingerprint sensor gesture.

Do I update GSI just by flashing the new system img?
I would lost all user data that way right?

x1357246 said:
Do I update GSI just by flashing the new system img?
I would lost all user data that way right?
Click to expand...
Click to collapse
1. TWRP main menu. Click on Install, select Image option on bottom right. Select AB GSI img. Select System. Swipe to flash. Once done, go to main menu. Reboot -> Recovery.
2. Once back in TWRP. Install -> Select gapps file. Swipe to flash. Reboot -> System.
I followed those steps and it worked and you do not lose the data greetings..

DarkLara said:
1. TWRP main menu. Click on Install, select Image option on bottom right. Select AB GSI img. Select System. Swipe to flash. Once done, go to main menu. Reboot -> Recovery.
2. Once back in TWRP. Install -> Select gapps file. Swipe to flash. Reboot -> System.
I followed those steps and it worked and you do not lose the data greetings..
Click to expand...
Click to collapse
Awesome Thanks, man!
These treble, A/B partition devices are so complicated compared to old devices

I'm sorry if I missed it, but why does the lineage os zip have to be flashed and then the system image specifically flashed? I thought the whole point of treble was to only need to flash the system image?

retro486 said:
I'm sorry if I missed it, but why does the lineage os zip have to be flashed and then the system image specifically flashed? I thought the whole point of treble was to only need to flash the system image?
Click to expand...
Click to collapse
It's because Moto X4 don't have project Treble, but the Lineage build is treblelized, and when you flash it, will flash the vendor partition too, with that we can install and boot GSIs.

abrfilho said:
It's because Moto X4 don't have project Treble, but the Lineage build is treblelized, and when you flash it, will flash the vendor partition too, with that we can install and boot GSIs.
Click to expand...
Click to collapse
Oh dang. The Treble guide has a link that said the X4 was on treble. Got it. Thanks!

retro486 said:
Oh dang. The Treble guide has a link that said the X4 was on treble. Got it. Thanks!
Click to expand...
Click to collapse
Yes, it's a custom Treble, not native.

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP for Poco X3 Pro Global/Indian (vayu/bhima)
touch and adb work
SD card and USB OTG are working
Decryption is working
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_vayu
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocox3pro.html
Unofficial 12 builds: https://www.pling.com/p/1833617/

Nebrassy said:
Hello, this is an alpha build of TWRP, for Redmi note 10 Pro Global/Indian/Indian Pro Max (sweet/sweetin)
Click to expand...
Click to collapse
Are you sure you posted in the right subforum?

kamild_ said:
Are you sure you posted in the right subforum?
Click to expand...
Click to collapse
Yeah, I just copied it from my other thread and forgot to edit a part of it

Wow finally Decryption twrp for x3 pro..

anyone try in Poco X3 PRO ?
Thanks.

Can it be installed from the current Recovery on a Poco X3 PRO? Or is it not permanent?

can I flash this if I have arrow recovery?

Nice, thanks to the dev. Is there a site/tutorial which explains the differences of the current recovery systems including why for example Arrow OS has its own?
I guess device memory setup,encryption and OTG plays a big role but since I used TWRP the first time years ago I did not keep up with Android/Recovery development much.

Well, I guess that escalated quickly
This is awesome news when it comes to custom recovery.

Can flash this recovery if im on orangefox with xiaomi.eu?
No problem when boot after flash new recovery? Thanks

Can't wait for version with adb sideload working

finally internal storage working.. great job

Can I install it like a image through my present Orangefox recovery ?

Luko69 said:
Can I install it like a image through my present Orangefox recovery ?
Click to expand...
Click to collapse
yep, just done that, decryption works so I can finally access the DATA partition.

Installed via previous Orangefox, working OK, decryption OK.

Using TWRP to install OTA Updates

I have tested it flashing Arrow vanilla version.
1) Able to read and write from Pc to internal storage and sd card.
2) Able to flash rom and Gapp separately.
3) Able to backup and restore.
It is almost like a perfect twrp to me. Thank you.

Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.

pl1992aw said:
Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.
Click to expand...
Click to collapse
After formatting data, you need to reboot twrp, I believe it tells you that while formatting

Nebrassy said:
After formatting data, you need to reboot twrp, I believe it tells you that while formatting
Click to expand...
Click to collapse
I did reboot again into twrp, even entering fastboot and boot twrp img, but same results if I never let the miui initialize once after formatting.