Database Develop

[ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off

Changelog:
V5.23 Fix for Android 6 (Freeze on boot logo)
Installation of kcal kernel module for supported kernels. Get the app from https://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
V5.22 Bug in the vendor overlay creation. Existing directories (like /vendor/bin) have not been replicated correctly
V5.21 Fix issue when running on Linux (some CR/LF)
Patch libsepol in bootimg for backwards compatibility with Android 6
V5.20 Support for superuser as an alternative to SuperSU (https://github.com/phhusson/Superuser)
Fix for the missing internal storage link in TWRP
V5.11 Support for Android 7.0
Fix in the overlay layout which could prevent some libraries from loading and cause battery drain
V5.1 Support for Android 7.0
Updated bootimg to deal with Android 7.0 policies
New tool inside bootimg for adding new contexts to binary file contexts
New system overlay layout due to a more restrictive linker in Android 7
V5.0 New system overlay method using the /vendor directory. As this directory is also in the library search path even libraries can be easily replaced without modifying the system partition
System-less SuperSU integration improved (Version 2.76 or higher recommended)
System-less xposed integration (using the standard distribution)
Support for 32.A.0.253
V4.51 Fix for awk script for Linux kernel version detection when running on Linux
V4.5 Fixed adb and mtp file access in TWRP for 32.2.A.0.224
V4.42 Added support for Z2 (Sirius) and TWRP fstab fix for leo and aries (thanks to waleedsq81)
V4.41 Fixed issue with Y/N choice on non-english Windows. Added support for Z3 (leo)
V4.4 Support for Z3+/Z4, Tablet Z2, Tablet Z3 and Tablet Z4 added (Z4 still has an issue with TWRP, but DRM fix works)
SuperSU integration reworked in order to need less SELinux exceptions and to be more secure
All tasks can now be individually selected. Therefore there is no separate DRM only script required
V4.31 Renabled Z5P (satsuki) and Z5C (suzuran) for TWRP and drmfix
V4.3 Support for older Lollipop added
Script execution for Linux fixed
V4.24 Fix for for a bug in SuperSU integration in V4.23
V4.23 Fix for repacking 3rd party kernel (Some permissions were on custom directories were lost)
V4.22 Bugfix for readta (flash_dk reported unit not)
V4.21 Fix for the Linux binary of bootimg
V4.2 Updated TWRP to 3.0.2
V4.1
Fix for WideWine (if you have your device key) Thanks a lot to goofnorf101 for testing
unpackinitfs and makeinitfs in my bootimg tool now maintain date/time of files correctly
Automatic SuperSU installation
V4.0
Fix for older kernels (Lollipop)
Binary for Linux (The older version had the ARM version packaged)
Device is not stored in the kernel image anymore
TWRP updated to version 3.0.1
FAQ - Please read
Is is possible to have root with locked bootloader?
Short answer: no
Long answer: The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking
So any change to the kernel (like this script) or system partition requires unlocked bootloader
What is dm-verity?
A hash checksum on all blocks of a filesystem in order to verify the integrity
What is Sony RIC?
A protection to avoid mounting the root filesystem or system read/write
What happens if I unlock my bootloader
The device key (TA unit 0x1046b) will be wiped, which deactives everything DRM related. In addition a full wipe of your phone will be perfomed.
So extract your TA partition before with this great tool http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597 from zxz0O0
If you already unlocked the bootloader before, then at least the credentials will be restored, which will reactivate stuff like x-reality and camera de-noise
Why do I need to flash my device key?
Without your device only some functions can be reactivated, like x-reality. Other functions like widevine do not work with out your device key.
How do I enter TWRP recovery?
Restart your phone and press the volume key up as soon as the LED switches to yellow
I want to use a custom kernel with the DRM fix
Just say "N" to all other options. Nevertheless be prepared for problems if the custom kernel does not match your Android version.
What should I do if there is an update to this script?
First check if you really need to run this update by checking the changelog. E.g. if it says binary for Linux fixed and you are using Windows then probably you don't care. If you did not change your Android version then all you have to do is to update the kernel package with fastboot flash boot. If you do not use the automatic SuperSU integration then you have to reinstall SuperSU in TWRP.
This tool repacks an existing kernel package (usually the stock kernel) in order to make it rootable and adds TWRP recovery as well. Version 4 has been succesfully tested with LP and MM.
In particular it adresses the following issues:
DM-Verity: Android is now using dm-verity to verfy the integrity of the system partition. Until you switch it off your phone won't boot after modifying /system
SONY RIC: RIC is blocking the write access to the system partition
DRM Keys: After unlocking the bootloader your device key is wiped, which deactivates some functionaliy. E.g. x-reality, denoise in camera aso.
Recompiling the kernel is not required as only the init ramdisk needs to be modified. You can run these scripts either in Windows or Linux.
Thanks to the excellent work of zxz0O0 you can now backup the TA partition before unlocking the bootloader with this tool http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
If you managed to backup your TA partition before you unlocked the bootloader then this version will fully reactivate your keys as well. (many thanks to addicted1900 for helping me with the testing)
As there has been some confusion I would like to point out one more time that you cannot run any kernel package which is not signed by Sony without unlocking the bootloader. So this works only with unlocked bootloader.
As it seems that it is not clear to everyone I also want to mention that <...> is a placeholder. E.g. <extracted kernel> means that you should replace it with then name of your extracted kernel, which could be kernel.elf
There was a report that having SuperSU in the system partition installed may lead to a bootloop. Therfore you shoud first install the bootimage created by this script and then install SuperSU afterwards, as it will then use the system-less strategy.
In order to use these scripts you need the kernel boot image of your current version. There two different ways to obtain it:
Method1:
If you have a .ftf image then open it with zip application (7Zip, WinZip, Windows Compressed Folder) and extract kernel.sin. Afterwards use Flashtool -> Tools -> SIN Editor to extract the kernel. You should end up with the boot image with extension .elf.
Method2:
Run your favourite recovery and connect via
Code:
adb -d shell
Now run
Code:
find /dev -name boot
dd if=<output of the find command before> of=/sdcard/kernel.img
Once you have the kernel image you are ready to use the script.
The newest version support superuser as an alternative to SuperSU. This is available open source and can be verified. In order to integrated you need the current superuser.zip from http://superuser.phh.me/superuser.zip and to be install the app afterwards from Google Play (look for superuser phh) or build it yourself from github.
To integrate the kernel part just place superuser.zip in the rootkernel directory.
You can also still use SuperSU, although it is causing a huge battery draining on my Z5 with Android 7.0 If you place SuperSU in the same directory (SuperSU*.zip, case sensitive) then it will be also installed automatically . It did all the tests with 2.76, but newer versions should work as well. Please be aware that you can not update SuperSU within the application. For a newer SuperSU version you need to rerun the script.
If you want to integrate xposed as well just place the distribution for you device and Android version in the same directory. (e.g. xposed-v86-sdk23-arm64.zip). Only support with Android 6.0 (sdk 23) and higher.
xPosed for Android 7.0+ is still not available.
Code:
rootkernel <extracted kernel> boot.img
You are prompted for several choices:
Sony RIC is enabled. Disable?
I prefer not to disable it in order to keep my phone more secure. Unfortunately there are a lot of bad guys in this world and SELinux and RIC still can save us if someone discovers a new kernel exploit.
Sony RIC basically prevents mounting the /system partition for write. You can still modify it in recovery of of course, but if you require write access to /system without entering recovery then you need to disable it.
Install TWRP recovery? Here you should say yes unless you are trying to patch a non-stock kernel, which comes already with a recovery
Install busybox? For security reasons I prefer not to install. In recovery you have it anyway. This choice is only available if you chose install TWRP
Found SuperSU-v....zip. Install? Integrates SuperSU. For this option to show up you have to place the SuperSU package into the same directory with the name SuperSU*.zip (case sensitive)
Found superuser.zip. Install? Integrates superuser. For this option to show up you have to place superuser.zip into the same directory (case sensitive)
# Make su permissive (Permits any action as su)? This only appears if you install superuser. Permissive means you can anything as root, without it is restricted mainly to file operations (sufficient for e.g. Titanium Backup)
Found xposed-v....zip. Install? Integrates xposed system-less. For this option to show up you have to place the xposed for your device and Android version into the same directory. (e.g. xposed-v86-sdk23-arm64.zip)
Install DRM fix? Installs the DRM fix. First it tries to use the device key which you flashed with flash_dk. If it does not exist it uses an alternative method which cannot fix everything (e.g. Widevine will not work, but X-reality, Camera denoise etc. will work)
Now put your phone into fastboot mode (Volume Up + connect USB) and then run:
To test it without actually flashing it:
Code:
fastboot boot boot.img
For flashing it:
Code:
fastboot flash boot boot.img
If you managed to backup for TA partition before then you can reactivate your original device key as follows:
Code:
flash_dk <ta backup image> DK.ftf
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade. The device key has a length of just 16 bytes, so it is correct that the resulting DK.ftf has a size of only aprox. 500 bytes.
If you like my work you can buy me a coffee
Some background information:
There are two main tools involved (for both Android and Windows)
- busybox
Probably everyone knows it
- bootimg
A multicall binary with several tools for unpacking and packing the boot image as well as adapting the SELinux policy. Part of the code is written by me from scratch, some other parts are cherry picked from other projects. I will also provide the source for it. As Windows doesn't have softlinks I modified the tools for unpacking and packing the init ramdisk to write text files with __lnk__ at the end instead.

Would be great if someone shared E6653 stock .200 kernel boot.img or flashable zip so we can try this out

Funkmasterchilla said:
Would be great if someone shared E6653 stock .200 kernel boot.img or flashable zip so we can try this out
Click to expand...
Click to collapse
Do you want the kernel.sin of stock . 200?

lordriguez said:
Do you want the kernel.sin of stock . 200?
Click to expand...
Click to collapse
I am downloading the whole firmware again from xperifirm. Thank you mate !
Edit: Working great! I'll stick to stock kernel now since Androplus' consumes more battery while asleep !
Edit2: I successfully flashed recoveries in command window from my PC but can't access TWRP at boot though, no LED flashing.
Edit3: Ok that's cuz there's no recovery boot script obviously, my bad. That's above my pay grade, if somebody is kind enough to create a stock. 200 with recoveries it'd be much appreciated PM me if so
Edit!: I flashed monx new stock based kernel
Thank you Tobias !

tobias.waldvogel said:
Hi everyone,
as most of you know, even after unlocking the bootloader there are a few more requirements before you can modify the system partition, i.e. install SuperSU, xposed etc.
- Android is now using dm-verity to verfy the integrity of the system partition. Until you switch it off your phone won't boot after modifying /system
- SONY RIC is blocking the write access to the system partition
The good news is, that it is not required to recompile the kernel. It is sufficent to modify the init scripts inside the init ram disk. So you can just stick to the stock kernel.
I created a package which precisely does this job for you. Just run it from TRWP after installing a new Android version
With this you don't have to wait anymore until someone creates the right kernel package for your phone
PS: It leaves a copy of the new boot image in the internal sdcard if you want to save it somewhere. (boot.img) It can be flashed with fastboot if required.
Click to expand...
Click to collapse
Hmm... I don't understand what this zip file do with phone.... Can you explain more primitive for me?!
Is that for recover stock kernel with stock drm keys?! I understand correct?!

zavpasha said:
Hmm... I don't understand what this zip file do with phone.... Can you explain more primitive for me?!
Is that for recover stock kernel with stock drm keys?! I understand correct?!
Click to expand...
Click to collapse
Before you can start to install thing like SuperSU and xposed you have to change the kernel, otherwise your phone won't boot anymore. In the past you had to wait for someone to come up with a compatible kernel for your phone, now this package just converts your existing kernel.
Regarding the DRM please install the package from the DRM restore thread.

Funkmasterchilla said:
I am downloading the whole firmware again from xperifirm. Thank you mate !
Edit: Working great! I'll stick to stock kernel now since Androplus' consumes more battery while asleep !
Edit2: I successfully flashed recoveries in command window from my PC but can't access TWRP at boot though, no LED flashing.
Edit3: Ok that's cuz there's no recovery boot script obviously, my bad. That's above my pay grade, if somebody is kind enough to create a stock. 200 with recoveries it'd be much appreciated PM me if so
Edit!: I flashed monx new stock based kernel
Thank you Tobias !
Click to expand...
Click to collapse
Thanks for the feedback. Future versions of this package will add TRWP as well. I am currently working on it.

tobias.waldvogel said:
Thanks for the feedback. Future versions of this package will add TRWP as well. I am currently working on it.
Click to expand...
Click to collapse
As promised the new package with TWRP is out

tobias.waldvogel said:
As promised the new package with TWRP is out
Click to expand...
Click to collapse
Great work thanks ,
How would I go about disabling the vibration for recovery?
Sent from my E6653 using Tapatalk

Well, the script which checks if recovery should be started is bin/init inside the zip. If you don't like the vibrate then just remove the line and run the package again
Gesendet von meinem E6683 mit Tapatalk

huh, so it is possible to have 2 recoveries at the same time? (and why would anyone want 2 recoveries? )

Three Recoveries are als possible
CWM, Phils Touch & TWRP
Sent from my E6653 @ XDA Portal

Sorry for being noob.
I miss my Oneplus one where things were so easy.
After unlocking BL what do i do with this zip.
Is it going to Root my phone and Install TWRP?
Thanks for help.

I flash the v2 and i got bootloop. 4 time red LED and the phone reboot and all over again. What's the problem?

Hi Tobias,
can you please build a v2 for the z5 compact too?
thx
stiffmeister

FakeSmile said:
I flash the v2 and i got bootloop. 4 time red LED and the phone reboot and all over again. What's the problem?
Click to expand...
Click to collapse
On which model did you use it and with which firmware version?
If you used flashtool before then you can just flash the kernel one more time (i.e. deselect everything else).

stiffmeister75 said:
Hi Tobias,
can you please build a v2 for the z5 compact too?
thx
stiffmeister
Click to expand...
Click to collapse
This should work on Z5 compact with stock kernel as well, without any change.
In case of any issues you can flash the kernel again via flashtool
If it did not work you can pass me the generated boot.img from your interal sdcard for further analysis

hi tobias,
i didn't try the v2, because i thought, that the twrp recovery wouldn't be compatible.
but when you say it's ok, than i'll try it
br
stiffmeister

stiffmeister75 said:
hi tobias,
i didn't try the v2, because i thought, that the twrp recovery wouldn't be compatible.
but when you say it's ok, than i'll try it
br
stiffmeister
Click to expand...
Click to collapse
I flashed zombie kernel without making backup of stock kernel, can you share it with me so I can try this method (I doubt it will work on zombie)
ps : I have .200 fw

tobias.waldvogel said:
On which model did you use it and with which firmware version?
If you used flashtool before then you can just flash the kernel one more time (i.e. deselect everything else).
Click to expand...
Click to collapse
E6653 on .200 firmware

Install OOS Open Beta 8 (N) / 7 (MM) without Breaking official TWRP

This guide allows you to install OOS Open Beta 8 (N) / 7 (MM) without having to switch to modified TWRP
All credits to the respective developers
Downloads : G-Drive | MEGA
Unified Links above contains the following.
[Added] OOS Leaked Open Beta 9 (Mirror only) will modify Once it is released
1- Modded OOS Open Beta 8 (No F2FS , Downgradable to any OOS version)
2- Modded OOS Open Beta 7
3 - Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Unified Flashable Zip)
4- Super SU 2.78-SR5
5- Official TWRP
6 - Modified TWRP Recovery 3.0.2-1.28 Credits @eng.stk
7- Latest Xposed Installer (Beta 7 Only) (It will give you the option to download / install the latest version of framework automatically)
8- Open Beta 8 Full flash able (F2FS support with Modified Recovery @Funk Wizard)
Instructions for Clean / Dirty Flash (Over any Open Beta after 3.5.1) :
1. Boot into TWRP (modified or official which ever you are on)
2. Wipe Dalvik / ART cache & cache OR Factory Reset ( If you are coming from another ROM)
3. Flash Modded OOS Open Beta 8 (Dont Switch /system and /data to F2FS if you want to root) or Beta 7
4. Wipe Dalvik and Cache
5 . Flash official twrp as image (even if you are already on it)
6. Reboot to into recovery directly (this will prevent recovery from being overwrite by the stock)
7. Flash SuperSu (Optional)
8. Flash Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Clear Google App Data after Booting) (Unified Flashable Zip) (Optional)
9. Reboot to System (It will reboot twice if you flashed SuperSU) - That is normal
You are good to go :good:
Regards ,
Muhammad A. Iftikhar

Is there any kernel for this build ???

Normas Interruptor said:
Is there any kernel for this build ???
Click to expand...
Click to collapse
Eng.stk yesterday teased us with an upcoming kernel for 3.5.4 Community Beta.
Whatch this thread: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970 .

Can I dirty flash it from FreedomOS based on 3.2.7?

xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Nope, they are two different ROMs on different channels: for instance you could have dirty flashed if you were on 3.5.2 or 3.5.3.

I need to wipe system too? Or only cache/dalvik + data?

xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Yes you can as you have firmware of 3.2.7

xGOGI said:
I need to wipe system too? Or only cache/dalvik + data?
Click to expand...
Click to collapse
System Wipe only if you are coming from another ROM , I.E CM or AOSP based / Nougut

How do i flash official twrp in modified twrp, do i have to extract the downloaded file?

puschkin said:
How do i flash official twrp in modified twrp, do i have to extract the downloaded file?
Click to expand...
Click to collapse
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.

ahmediftikhar said:
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.
Click to expand...
Click to collapse
Thanks for the quick reply!!

puschkin said:
Thanks for the quick reply!!
Click to expand...
Click to collapse
This will further help you out

Thanks for this great tutorial, worked like a charm

I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki

ralph78 said:
I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki
Click to expand...
Click to collapse
You can even dirty flash this over 3.2.7 (will take some time after 1st boot to optimize apps depending on the number of apps installed) , Nandroid can be restored with out hassle if you choose to clean flash 3.2.7 after testing CB

I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?

XS_31 said:
I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?
Click to expand...
Click to collapse
Try re-flashing Twrp by downloading a fresh copy , and manually mount system before flashing the ROM ,
You can also try downloading it directly to your gdrive and let it sync in your PC / phone by "make available offline" feature in drive app

how to back from 3.5.4 to stock again?

File corrupt from both links, also.

ritchiedrama said:
File corrupt from both links, also.
Click to expand...
Click to collapse
Yes... File is corrupted... So much of mobile data wasted..

[RECOVERY] [TREBLE] [RETIRED] TWRP with Tissot Manager (Treble & Dual boot support)

RETIRED! No longer supported or being developed. @Giovix92 is now the lead dev, please use his TWRP for full compatibility with modern kernels/ROM's - https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
Old thread below:
-----------------------------------
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing, Dual boot repartitioning and other power-user tools with integrated Aroma Installer-powered GUI screens that I call Tissot Manager.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know!. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready with dual-boot ROM patcher;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Option to install a payload ROM in the current slot, rather than the inactive one;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Adds a "Tissot Manager" Aroma GUI to TWRP Advanced Menu (bottom-right button), which is the tool used to repartition the device for Treble and Dual boot, as well as some other nifty stuff:
Has the option to shrink System OR Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink System, you will keep max size Userdata - however it will be incompatible with non-Treble ROM's (they will crash on installing with Error 28 due to System being too small). It will Erase system, requiring you to reinstall a ROM or restore a ROM backup.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Dual boot requires Userdata shrink and works by splitting into userdata_a and userdata_b. The partition split size is customizable during the repartition process.
Adds a "Patches" section with the following current options:
Patch the current Vendor for dual-boot capability (only required if automatic patching wasn't possible). See the 'About Dual-boot' section below for more information.
Enable an insecure ADBD on boot for the current slot (i.e. enable debugging and remove authentication requirement). Useful for ROM hackers/porters.
Patch the current slot to enable/disable forced userdata encryption
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-boot.img-3.2.1-with-Tissot-Manager-x.x.zip:
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches (Aroma Installer powered GUI - a fully guided and interactive process).
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack. Reminder - check out my full guide for learning and instructions on all things Treble.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
About Dual-boot
Dual-boot on this device is relatively simple. As you know we have Slots - boot_a and _b, system_a and _b and vendor_a and _b (for Treble). This repartition splits userdata into userdata_a and _b too. You can simply change your Slot in TWRP reboot menu to change which ROM to boot.
This is designed for developers and testers - NOT for daily use. There are some significant issues with dual boot systems:
Any kind of security lock (PIN, fingerprint, etc.) set on one ROM will cause the other ROM to believe it has security too, but constantly fail with unlocking. This is reportedly because security info is stored on persist, which is shared between each slot (and not compatible with differing ROM's).
Because Userdata is split, so is Internal Storage. In TWRP, when changing slots, the MTP will remain mounted to the old slot - it must be manually disabled and renabled (Mounts menu) to update to the new slot.
I will not fix these issues - dual-boot is not designed to be for general/daily use and there may be more minor issues that I don't know about. It's intended for developers only.
In order for a ROM to be dual-boot compatible, the fstab file (information given to Android about partitions to mount) needs a small modification. This TWRP can try to do this patching automatically when you install a ROM, or it can be done manually in Tissot Manager's Patches menu (as well as single-boot patch to e.g. revert a ROM backup from a dual-boot state).
You will see in the install log if a dual-boot patch attempt is successful in the flash text output.
Automatic dual-boot patch occurs only if necessary when:
Flashing an AIO Treble ROM ZIP with TWRP
Flashing a vendor.img in TWRP "Install Image" mode
Automatic dual-boot patch does NOT work when:
Flashing a vendor.img via fastboot
Restoring vendor in a TWRP backup
Any other way of flashing a vendor
In any of these cases, you can manually patch Vendor for Dual Boot in Tissot Manager's Patches menu. You can also remove dualboot support the same way. It will detect the dualboot state of the current Vendor slot and present the available option. If you find that it doesn't actually change after patching, the Vendor is incompatible (please report it to me). RR AIO Vendor is tested OK.
Download
All downloads (and source code) always at:
https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
...or via DevBB Downloads section.
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/CosmicDan-Android/android_system_update_engine_tissotmanager-mod
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk. The void kernel included in RR AIO does not have this problem and can therefore be safely used without Magisk (for e.g. GSI compatibility).
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work. It will definitely not work if you have shrunk system.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ROM ZIPs with a shrunk System (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Credits and Thanks
- @mohancm for the original TWRP port, I used some flags from his DT
- @ghpranav and @mountaserhalak for the RR device tree that this is built with (and random help)
XDA:DevDB Information
TWRP with Tissot Manager (Treble & Dual boot support), Tool/Utility for the Xiaomi Mi A1
Contributors
CosmicDan
Source Code: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot
Version Information
Status: Stable
Created 2018-05-29
Last Updated 2019-11-24

Reserved

Screenshots (click for slightly larger non-cropped version)
Screenshot of new TWRP button:
_______________
Main menu (stock partition map detected):
_______________
Repartition choice type when coming from stock:
_______________
Repartition wipe warning/disclaimer if chosing to shrink Userdata for Treble:
_______________
Main menu (Shrunk Userdata type Treble partition map detected):
_______________
Repartition wipe warning/disclaimer if chosing to restore Stock from Shrunk Userdata Treble mode:
_______________
Example of Repartition processing screen:

Good job! :good:

Nice work!
Did you tested treble roms with this? Aex now have treble support

Omg, you are the best man. @mohancm also huge thanks to u man, great devs in our XDA.

I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!

Chikoow1 said:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Click to expand...
Click to collapse
This is just the repartition part, one step of Treble. You still need a Vendor pack. But yes, this enables Treble ROMs and the ROMs require repartition.
ddaggebi said:
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Click to expand...
Click to collapse
1. If you do, it will wipe partition map back to stock. So you will need to repartition with Treble Manager TWRP again. But you can make a backup of stock ROM in TWRP and just restore it after the repartition. It should work.
2. Don't know. Needs testing.
3. Yes! I forgot to add this to the FAQ.

Has this tpwr f2fs support and working?
Since Los support It i would like ti have

@CosmicDan
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?

Filip013;76586434 [user=1844875 said:
@CosmicDan[/user]
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Click to expand...
Click to collapse
It's indeed not intended to be compatible with stock ROM, but your mileage may vary, and as @CosmicDan said, it might work good enough or it won't. You can only try to see the results yourself.
This whole Treble thing is meant mainly for custom ROMS, since stock will never be Treble compatible (still, anything could happen)

I've just updated the TWRP with Treble Manager to 1.1 which fixed a semi-important bug.
Also, I've released a guide for those who find the Treble conversion/install process confusing - check it out. If you can, keep TWRP and Treble Manager specific questions in this thread, but ask your general questions and help over there - I will update the guide as I get feedback

CosmicDan said:
FAQ
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) Untested. Please report your results. But Treble is really not about Stock, you will likely encounter more problems down the line or it may turn out to be completely incompatible.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest/only way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (untested - if you get bootloop when using stock, it means you do) or Magisk (also untested, may still get bootloop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ZIP's on ROM's with a shrunk Userdata (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Unable to mount '/vendor' (Invalid argument)" red error in this TWRP
A) You can safely ignore it. It just means you have not repartitioned your device for Treble yet, so it can't mount the /vendor image.
Click to expand...
Click to collapse
Ay!
Have just finished testing about OTA on stock after Treblizing!
Result?!?
OTA works perfectly on stock after shrinking data to Treblize! Hurrah! ???
Process I followed:
1) Treblize by shrinking data
2) This is important: flash stock ROM in fastboot using MiFlash! When flashing for the first time, select "clean all and lock"! No other standard options working! I couldn't even boot stock using other options!
I've tested by fastboot flashing April build and then updating it to May OTA!
*** On a note: clean all will erase everything on your phone including your personal data!
If you use "save user data" then stock can't even boot! This may caused by the encryption!
BTW, after everything I just restored my non-Treble RR backup and everything works perfect! Just Treble Check app can't check that it's Treblized!
But don't worry! Treble partition table still remains! Fastboot flash can't touch that and can't recognize that it actually exists! Which to me is a good thing!
@CosmicDan, give me a thanks buddy! I deserve this!

SomratMJX said:
-snip-
Click to expand...
Click to collapse
Don't quote the whole OP and please use a smaller font size.

Change slot doesn't work... Others are okay as far as i have seen

dback31 said:
Don't quote the whole OP and please use a smaller font size.
Click to expand...
Click to collapse
Just thought it's too important to highlight! Nothing else!

Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Reboot to fastboot and change the slots with
fastboot set_active b

Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Use the latest TWRP 1.1! Works fine for me!

SomratMJX said:
Just thought it's too important to highlight! Nothing else!
Click to expand...
Click to collapse
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this

dback31 said:
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
Click to expand...
Click to collapse
Ha ha ha! It's related to OP buddy!
Anyways, I am too lazy to quote a certain part of the OP!

no_verity_op5(t) _v3.zip for OOS OB13 with Project Treble

I made small changes based v2
Suitable with OOS OB13 with Project Treble.
No need to mount any specific partitions (in recovery) manuly such as /vendor
Click to expand...
Click to collapse
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Download Link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

daxiaamu said:
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Click to expand...
Click to collapse
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)

Awesome. Thank you very much @daxiaamu!
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
Same thing here. Thanks for the heads up.

fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

a63548 said:
Awesome. Thank you very much @daxiaamu!
Same thing here. Thanks for the heads up.
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

Need new link please

Aballamis said:
Need new link please
Click to expand...
Click to collapse
You can also use the one from xXx https://forum.xda-developers.com/on...1-1-speed-ram-optimized-t3627121/post72802213

Aballamis said:
Need new link please
Click to expand...
Click to collapse
Here's a mirror: http://www.mediafire.com/file/1psz6...ForceEncrypt_2.0_%28OP5-5T-Treble%29.zip/file

Recommendation
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**

Mohitash said:
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Click to expand...
Click to collapse
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie

amitporedi007 said:
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
Click to expand...
Click to collapse
Magisk must be flashed after dm...zip. But if you have already installed magisk then no worries. Flash DM Verity n force encrypr disabler and then again flash magisk. No need to format data in this case. Format data only needed when you are doing pure clean install of stock (based) rom. Check my signature, i am on OOS 9.0.2 that is android pie 9.0 and magisk v18. Decrypted (using that dm verity and force encrypr disabler).

[RECOVERY] [TREBLE] TWRP 3.3.1-0 with Tissot Manager

Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01

Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!

Reserved

Great work.
Sent from my Mi A1 using Tapatalk

Thanks ??

Nice. Bro you carried legacy ?

nice work waiting for shrp version of this ??

Noice :good:
Sent from my Mi A1 using XDA Labs

This is an update of TWRP Comic Dan?

manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op

Any way to flash it using cosmic dan's twrp? I don't have any pc now

Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.

Great job dude ?

Awesome work!
Thank you so much for this.

@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?

sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.

Where is the survival checkbox??

What is this "inject twrp" does ?

oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option

Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?