Senior Member
Nov 30, 2019

Orangefox-DualBoot-Guac-Unified - Android 10/11 version


- Zackptg5 - The father of this mod
- DrakePL (Orangefox Recovery)
- Ae3NerdGod, Neel P, Whismasterflo
- Muphetz, Varun Soma, Pranav - for testing

#include <std_disclaimer.h>
* We are 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 us for messing up your device, we will laugh at you.
Modified recovery and installer script for all OP7/Pro/5G variants that re-purposes userdata for true dual booting. You can still use this as a regular stock twrp zip - one stop shop for magisk, verity, and/or forced encryption modifications

  • I am not responsible for anything bad that happens to your device. Only experienced users should be using this mod
  • This is no walk in the park mod. Although I have extensively tested it, there is always the possibility of a brick with anything that involves repartitioning. Make sure you have a backup and know how to reparititon your phone back to stock (there's a guide at the end of this readme with the basics)

  • YOU'VE BEEN WARNED - Use at your own risk

If you set a password, regardless of encryption status, it'll corrupt the other slot if it's also password protected.
Note that some roms set one automatically Either don't use a password on one slot, or leave one slot (I'll use 'a' in this example) unencrypted and:
  • Setup rom, password, and everything on slot a
  • Boot back into twrp, choose common data as storage, and backup userdata (if not using a/b/c layout, backup TWRP folder to your computer)
  • Setup rom, password, and everything on the other slot (b)
  • Boot back into twrp, switch back to slot a (reboot back into twrp), and restore the twrp backup

If you messed this up and are unencrypted - delete these files in /data/system if present: locksettings.db gatekeeper.password.key password.key gatekeeper.pattern.key pattern.key gatekeeper.gesture.key gesture.key

If you messed this up and are encrypted - you lost the data on that slot:
  • Unmount metadata in twrp gui
  • Format metadata with this command:
    mke2fs -t ext4 -b 4096 /dev/block/sda$metadata_partnum
    where metadata_partnum is the partition number of the current metadata partition (you can find this with sgdisk /dev/block/sda --print). DO NOT FORGET THE PARTITION NUMBER. If you do, you'll format all of sda which results in a brick
  • Reboot into twrp and format data in gui
Storage settings only supports 128 and 256gb userdata partitions
  • Just a cosmetic issue as it'll say that system is taking up the difference

Some other features/notes

  • Can choose between stock layout, a/b userdata, or a/b/c userdata where 'c' is a common data partition that'll show up in both roms - it's quite handy
  • Option to choose between ext4 and f2fs
  • Disables verity - fstabs are modified for dual boot and so this is a must unless you choose stock layout in which case it's optional
  • Option to disable forced encryption
  • Option to install magisk
  • Quickmode for faster rom testing
  • Failsafe to keep from changing slots automatically when used in conjunction with rom install

Common Data

  • If you choose a/b/c layout - you'll have a/b userdata, but you'll also get a 3rd userdata partition I call 'Common Data'
  • The name 'Common Data' gives away its purpose - to store files that you'll access on both slots/roms. So stuff like zips, pictures, music, TWRP backups, etc.
  • In TWRP, this shows up as another storage option for backup/restore and on your pc as well - your phone will have 'Common Storage' and 'Internal Storage'
  • In order to be accessible when booted, some parts of the system are modified so that the it'll be accessible WITHOUT root by the following mechanisms:
  • The common data partition is mounted to /sdcard/CommonData
  • .nomedia file is placed in CommonData so files in it won't be picked up twice if you decide to mount over internal storage as outlined below
  • Furthermore, if your use case is like mine where my music files are in common data, you can make 'mounts.txt' file in /datacommon containing a list of every FOLDER to mount directly over top of sdcard. So for example:
  • /datacommon/Music -> /sdcard/Music
  • This of course mounts over anything there (overwrites it for as long as it's mounted) so make sure that you don't have the same folder in both datacommon and regular data
  • Note that there are 3 exceptions to this folder mounting rule:
  • All - if this is the FIRST line, ALL folders in datacommon will be mounted
  • Android
  • lost+found
  • The reasoning should be obvious - lost+found isn't something you should need to mess with and Android is for regular data partition only - that's OS specific and should be on separate slots
  • Note that you should have 1 folder listed on every line, for example:
Flashing Instructions (if Android 11, see second post)

  • You MUST be booted into TWRP already when flashing this zip (you can grab a bootable twrp image from here)
  • Since this modifies data - the zip CANNOT be on sdcard or data at all UNLESS you do not want to repartition/format
  • If you flash from data, the zip will copy itself to /tmp and instruct you to flash it from there OR you can just install twrp/magisk/disver-fec
  • You could do the above or copy it to a place like /dev or /tmp and flash it from there
  • Alternatively, you can adb sideload it
  • Read through ALL the prompts - there's lots of options :)

How to Flash Roms

  • Nothing changes here except ONLY FLASH IN TWRP
  • Roms always flash to the opposite slot. Keep that in mind and you'll be fine
  • So don't take an OTA while booted - boot into twrp, switch slots, reboot into twrp, flash rom
  • Normal flash procedure:
  • Boot into twrp
  • reboot into twrp selecting slot you do NOT want rom installed to
  • Flash rom
  • Flash this zip
  • Reboot into twrp
  • When using failsafe mode,
  • TWRP will boot into the slot you were in BEFORE you flashed the rom.
  • TWRP will almost certainly show the incorrect "current slot" at the reboot menu.
  • The slot selection buttons still work. If youve kept track in youre head, and the zip didnt fail; pick the correct slot now
  • or reboot to recovery, then switch into the slot which contains the new rom youve just installed
  • Flash everything else


Change the zip name to enable quickmode options (Case Sensitive!)
  • keeps current layout

  • add the words fast or quick in the zip file to enable quickmode with the following default options:

  • ForceEncryption disabled for both slot
  • Magisk installed to both slots

add any of the following options to the name of the zipfile to custimize quickmode to your liking, capitilizing the letter of the slot youd like to enable that option for:

  • fec.ab will ENABLE force encrytion for the capitalized slot letter
  • su.ab or magisk.ab will ENABLE the installation of magisk for the capitalized slot letter
  • Example: if the file is named Orangefox-DualBoot-fast-fec.AB-su.aB.zip then:
  • ForceEncryption will be ENABLED on both slot _a and slot _b
  • Magisk will be installed on slot _b, but NOT installed on slot _a


  • confirm.y will skip the final confirmation before any work is done, and run the options chosen or defaults if none specified

  • the word warp this can be used instead of fast or quick and confirm.y if you'd also like to use quickmode without confirmation

Failsafe usage / explaination
I've had a few instances where a rom doesnt agree with whats going on, and the dualboot zip gets stuck on a slot and never finishes. This results in forcing the phone off, and leaves the phone in a non bootable state, with an unprepared slot. Not to mention a stock, or worse, no recovery at all. Bootloop city.
Enter the failsafe option: just add ` nofail ` or ` failsafe ` (case sensitive) to the zip name like above, and the zip will revert the slot change caused by the rom install and keep you able to boot back into the current slot's TWRP so you can sort out the slot youre working on. Pair this with a usb drive or commondata, and youre (relatively) safe to flash on the go, or from your bed with the computer off.

  • After applying the failsafe, the reboot screen in TWRP will ALMOST CERTANLY show the incorrect slot until you either manually select a slot or reboot recovery.
  • This adds a step or two to the flashing process, make sure you've read that.

Help! I Can't Boot!
  • Usually this is because you switched roms without formatting data first. This should be flashing 101 but we all forget sometimes. Plus this slot stuff can get confusing
  • If it only happens with a/b/c and not any other layout, there's a good chance it's selinux related. Try setting selinux to permissive at kernel level with this mod (source here).
How to Manually Repartition Back to Stock

  • In the event any step in the repartioning fails, the entire installer aborts. The good news is that this prevents a potential brick. The bad is that you need to manually revert back
  • Boot into twrp. If sgdisk is not present in sbin, grab it from this zip (in tools) and adb push it to /sbin and chmod +x it
  • sgdisk /dev/block/sda --print Note that /dev/block/sda is the block that userdata and metadata are stored on - no other block is touched by this mod. This will show up the current partition scheme. Stock looks something like this (on OP7 Pro):
Number  Start (sector)    End (sector)  Size       Code  Name
   1               6               7   8.0 KiB     FFFF  ssd
   2               8            8199   32.0 MiB    FFFF  persist
   3            8200            8455   1024.0 KiB  FFFF  misc
   4            8456            8711   1024.0 KiB  FFFF  param
   5            8712            8839   512.0 KiB   FFFF  keystore
   6            8840            8967   512.0 KiB   FFFF  frp
   7            8968           74503   256.0 MiB   FFFF  op2
   8           74504           77063   10.0 MiB    FFFF  oem_dycnvbk
   9           77064           79623   10.0 MiB    FFFF  oem_stanvbk
  10           79624           79879   1024.0 KiB  FFFF  mdm_oem_dycnvbk
  11           79880           80135   1024.0 KiB  FFFF  mdm_oem_stanvbk
  12           80136           80263   512.0 KiB   FFFF  config
  13           80264          969095   3.4 GiB     FFFF  system_a
  14          969096         1857927   3.4 GiB     FFFF  system_b
  15         1857928         1883527   100.0 MiB   FFFF  odm_a
  16         1883528         1909127   100.0 MiB   FFFF  odm_b
  17         1909128         1913223   16.0 MiB    FFFF  metadata
  18         1913224         1945991   128.0 MiB   FFFF  rawdump
  19         1945992        61409274   226.8 GiB   FFFF  userdata
You may have different size userdata - mine is 256gb - depending on your device but that doesn't matter. You just need to see where they're located
Take note of the number (I'll call userdata_num for the sake of this tutorial) and start sector (userdata_start) for the first partition AFTER rawdump, and the end sector (userdata_end) of the last parititon on sda

  • sgdisk /dev/block/sda --change-name=17:metadata - renames metadata partition back to non-ab stock
  • sgdisk /dev/block/sda --delete=19 - this deletes the entire partition - use this command for each user/metadata partition after rawdump (ones generated by this zip)
  • sgdisk /dev/block/sda --new=$userdata_num:$userdata_start:$userdata_end --change-name=$userdata_num:userdata - this creates the new userdata partition
  • Final step is to format the new userdata partition: mke2fs -t ext4 -b 4096 /dev/block/sda$userdata_num $userdata_size - where userdata_size can be calculated with this shell command: sgdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}'
  • MAKE SURE YOU VERIFY ALL VARIABLES HERE ARE SET PROPERLY - if you mess this up, you could format all of sda resulting in a brick
  • Run sgdisk /dev/block/sda --print again to make sure everything is correct and then reboot back into twrp

13/02/2021- V1.5
  • Updated the dual boot companion app V1.7.2
  • Updated Orangefox recovery to latest git
06/02/2021- V1.3
  • Updated the dual boot companion app
  • Fixed the Orangefox full screen bug on OP7 pro
05/02/2021- V1.1
  • Added the dual boot companion app
  • Fixed the OOS11 flashing bug
20/01/2021- V1.0
  • It works with OxygenOS 11 ( WARNING: --- Stay unencrypted! --)
  • Magisk 21.4 updated
  • New version of Orangefox recovery (R11) - 20-01-2021 update
  • Know bug: Flashing from OOS11 slot can overwrite the same slot.
19/11/2020 - A11-0.4
  • Fixed root install for Android 11
  • Minor improvement
21/10/2020 - A11-0.4
  • Root not installed if Android 11 - Please do it manually.
  • CommonData mount fix in Android 11
  • Minor improvement
Android 11: please install Magisk 20422 and MagiskManager 297

16/10/2020 - A11-0.2
  • Changed to OrangeFox Recovery
  • Added check to get the right initrc (Android 11 compliant)

16/10/2020 - A11-0.1
  • Initial release


Telegram support chat: https://t.me/OrangeFoxDualBootRebornOnePlus7

XDA:DevDB Information
Orangefox-DualBoot-Unified, Tool/Utility for the OnePlus 7


if you like my work, send me a beer :)

Last edited:


Senior Member
Nov 30, 2019

Related to Orangefox-DualBoot-Guac-Unified-A11.zip

WARNING: OOS11 --- Stay unencrypted! ---

Example (starting point)
Slot A A10 Rom
Slot B A10 Rom

1 - Flash from slot A A11/OOS11 rom
2 - Flash Orangefox-DualBoot-Guac-Unified-A11.zip
3 - Reboot to recovery (Now you are in slot B automatically)
4 - Format data
5 - Flash Orangefox-DualBoot-Guac-Unified-A11.zip
7 - Reboot to system

Install magisk manager attached

Ending point
Slot A A10 rom
Slot B A11/OOS11 rom

Now you should have a working A10 rom on slot A and a working A11/OOS11 rom on slot B.
Please report any problems.
Last edited:


Senior Member
May 27, 2020
It works great with A10 and A11. I had a little issue because I had A10 on A and B slot and when flashed this, then A11 ROM, rebooted to other slot flashed this again A11 was working great, but when tried to switch back to the slot with A10, after boot my pin wouldn't work anymore, so needed to delete locksettings.* an *.key files from /data/system.

Thanks for the great job!


Senior Member
Nov 21, 2018
It works great with A10 and A11. I had a little issue because I had A10 on A and B slot and when flashed this, then A11 ROM, rebooted to other slot flashed this again A11 was working great, but when tried to switch back to the slot with A10, after boot my pin wouldn't work anymore, so needed to delete locksettings.* an *.key files from /data/system.

Thanks for the great job!
Only set a PIN on one of the slots. Otherwise you will have that issue that your PIN does not work anymore on the other slot if you set it on both!!


Senior Member
May 27, 2020
Take a look at the recovery.log in /tmp then to check while it is getting stuck.
Ok, just give me a minute, already installed another ROM, will try to give info u asked in a few minutes. Someone told me when i tried to do same with twrp dual boot that twrp can't yet decrypt OOS Beta 17 and 18

IDK what happened but now my touchscrren is not working...

After stuck at patching I rebooted into fastboot changed active slot to other slot, rebooted into recovery, it enter in OrangeFox Recovery but no touch...

Got a bit scared there... Rebooted to system then back to recovery and touch is working now...

But there is no /tmp folder...
Last edited:


Senior Member
May 9, 2013
Could you please also provide the postition of init.rc. look at /init.rc and check if the file exists.
Dualboot still no work with oos beta 17 and 18,,its always stuck when patching fstab ( decrypt).
There's init process called High Assurance Boot (HAB) that verify your system's integrity. Check the script "/vendor/etc/init/hw/init.mmi.hab.rc".


Senior Member
Mar 8, 2015
This command show many values, which one to pick.

gdisk /dev/block/sda --print | grep "^ *$userdata_num" | awk '{print $3-$2+1}'

edit: typo, worked fine now...
Last edited:


Senior Member
Mar 8, 2015
Works great, tested with multiple ROMs...
Having below issues
1. Even if pin not setup in secondary ROM, need to delete files otherwise pin in primary is not accepted
2. After every flash of this recovery, all my magisk settings, modules are all lost
3. Images and videos in common data not visible in gallery
Last edited: