• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY] [11] [ALPHA] TeamWin Recovery Project (8T / Kebab) (2021-09-04)

Search This thread

mad4some

Senior Member
Dec 10, 2012
538
165
East TN
I'm currently running crDroid custom rom. Has anyone updated a custom rom using the instructions in the OP: "For updating a custom ROM - Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system"? Results successful? Thanks :)
 

theincognito

Senior Member
Feb 26, 2015
584
703
Redmi K20 Pro
Redmi Note 8
I'm currently running crDroid custom rom. Has anyone updated a custom rom using the instructions in the OP: "For updating a custom ROM - Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system"? Results successful? Thanks :)

I did it with Havoc, but I am the dev, so :p Just follow tyler's advice, since I don't use crdroid.
 

theincognito

Senior Member
Feb 26, 2015
584
703
Redmi K20 Pro
Redmi Note 8
New build released - 20210726 (Kebab only)

Changelog:

  1. Removed 9R support
  2. Fixed the TWRP screen overlapping with the notch
  3. Various mount errors while flashing ROMs should be gone now (atleast my testers think so)
  4. Latest upstream changes
  5. Removed AOSPA kernel, and updated to latest LOS kernel
Download links:

IMG: twrp-3.5.2_11-0-kebab-20210726-alpha
Installer: twrp-installer-3.5.2_11-0-kebab-20210726-alpha

As always, links are updated in the OP too.
 
Last edited:

lpdavidgc

Senior Member
Jan 9, 2011
278
57
Xiaomi Mi 10
OnePlus 8T
New build released - 20210726 (Kebab only)

Changelog:

  1. Removed 9R support
  2. Fixed the TWRP screen overlapping with the notch
  3. Various mount errors while flashing ROMs should be gone now (atleast my testers think so)
  4. Latest upstream changes
  5. Removed AOSPA kernel, and updated to latest LOS kernel
Download links:

IMG: twrp-3.5.2_11-0-kebab-20210726-alpha
Installer: twrp-installer-3.5.2_11-0-kebab-20210726-alpha

As always, links are updated in the OP too.
Thanks you so much!
 

pratyush28

Senior Member
Oct 4, 2016
464
181
OnePlus 8T
Has anyone tried to flash magisk on stock rom using this twrp?

It is mentioned that OOS flashing is broken so I was a bit confused whether it can flash zips over the already installed oos.

I am currently on latest OOS and locked bootloader so what I'm planning to do is -

1. Unlock Bootloader
2. Flash Recovery
3. Flash Magisk
4. Reboot System

Will this work?

Edit - This worked, I think this is by far the easiest way to root. There's no need to patch boot partition and use fastboot anymore.
 
Last edited:
  • Like
Reactions: Laapander

theincognito

Senior Member
Feb 26, 2015
584
703
Redmi K20 Pro
Redmi Note 8
Has anyone tried to flash magisk on stock rom using this twrp?

It is mentioned that OOS flashing is broken so I was a bit confused whether it can flash zips over the already installed oos.

I am currently on latest OOS and locked bootloader so what I'm planning to do is -

1. Unlock Bootloader
2. Flash Recovery
3. Flash Magisk
4. Reboot System

Will this work?

Yes.
 

ruszok

Senior Member
Jan 5, 2010
50
5
@theincognito - what do you mean here:
  • It's better to flash ROM + TWRP installer, if you want to keep your TWRP after flashing a ROM
I have stock OOS. So if I have update of OOS (full package), install it at OOS installer (not in TWRP). Then I should not click "Reboot" in the updater just flash TWRP installer zip in magisk manager. And then? Install magisk in inactive slot or reboot to TWRP and install magisk?
 
Last edited:

pratyush28

Senior Member
Oct 4, 2016
464
181
OnePlus 8T
@theincognito - what do you mean here:
  • It's better to flash ROM + TWRP installer, if you want to keep your TWRP after flashing a ROM
I have stock OOS. So if I have update of OOS (full package), install it at OOS installer (not in TWRP). Then I should not click "Reboot" in the updater just select "Reboot in recovery mode" and install the ZIP with TWRP there? Or should it look different with original OOS?

I don't think it is possible to update OOS in any way if you have twrp installed. Only way to update would be to get the stock recovery somehow and then use the ota update from settings.

Please correct me if I am wrong, I am writing this after reading the entire thread and I saw someone mention this before.
 

ruszok

Senior Member
Jan 5, 2010
50
5
As I think you can update OOS in recovery (for now is impossible) or you can update in OOS (not in recovery - should be possible?). But maybe I'm wrong?

I have in mind full package of OOS (not incremental OTA package).
 
Last edited:

pratyush28

Senior Member
Oct 4, 2016
464
181
OnePlus 8T
OOS supports flashing OOS..
So local upgrade would work when stock recovery is absent? Sorry for asking noob questions. Since I am coming from an OP3T, I am really not sure about what's normal on newer devices and A/B partitions.

From what little knowledge I have about A/B partitions, and from what you are saying that OOS is capable of flashing upgrades,

1. There's no need of a stock recovery anymore and OOS will flash the update on the other slot?

2. Will I lose root and my modules in the process?

3. Also will twrp be overwritten?
 

ruszok

Senior Member
Jan 5, 2010
50
5
It's also little bit confusing for me.

If I will try to flash stock OOS FULL PACKAGE I can do it by OOS local update installer, yes?

So:
1. Flash full OOS package by OOS system updater (without reboot).
2. Flash TWRP installer zip in magisk (or FKM).
3. Reboot to recovery (TWRP).
4. Flash magisk.
5. Reboot to system.

It is correct way?

Or:
3. Click "install" in magisk and then "install in inactive slot (after OTA)".
4. Reboot system.
 
Last edited:

BillGoss

Senior Member
Sep 2, 2010
4,725
4,143
Sydney
OnePlus 3T
OnePlus 8T

mslezak

Senior Member
Dec 12, 2016
393
358
Houston
Google Pixel 2
OnePlus 8T
Works great thanks for all the work I updated using old method worked. I've flashed the twrp. zip with fkm no issues boot then went to twrp flashed radioactive kernel it worked too. I was stock everything when I tried this way too
Then what's this??? This guy said he was stock and flashed TWRP via Franco Kernel Manager. I take it "stock" means OOS... Now that's how I interpreted it anyhow.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    New build released - 20210904

    Changelog:
    1. Removed repack tools
    2. Allowed OpenAES encrypted backups (to conform with the TWRP source change)
    3. Added logical flag for relevant partitions (to conform with the TWRP source change)
    4. Latest upstream changes
    Download links:

    IMG: twrp-3.5.2_11-0-kebab-20210904-alpha
    Installer: twrp-installer-3.5.2_11-0-kebab-20210904-alpha


    NOTE for 9R users: This build SHOULD work with 9R - you SHOULD be able to do everything except flashing OOS. This is experimental. Use it at your own risk.

    As always, links are updated in the OP too.
    6
    Magisk flashes to /system/
    but my priv-app is in /system_root/system/priv-app
    In return, it breaks my system when I flash using magisk. Not sure why, hence I'm manually pushing aurorastore to /system_root/
    Sorry, I should have been clearer. When you use Magisk to do systemless installs, eg systemless hosts, it doesn't physically write to the system directories but uses overlays that make it seem that it's been written to system directories.
    Typically you do this using a Magisk module.
    How to do this is not something that belongs in the TWRP thread. If you don't know how to do what I'm suggesting then you need to read up on Magisk and its modules and look through the Magisk forum.
    5
    Speaking of which, I recently was forced to test backup & restore.
    My OP8T (KB05AA international/US) failed to boot and was going straight into recovery. Looking at the op2 logs, all it was saying with a very long stack trace was that Android couldn't find PermissionManager. That definitely was strange since I hadn't been mucking with the system.
    The only thing I could do to get back the 8T to boot was to do a factory reset from the (stock) recovery. That worked, but I lost everything.

    I had a two day old TWRP backup performed with twrp-3.5.2_11-0-kebab-20210726-alpha on an encrypted device. I didn't bother with removing the PIN as it also removes fingerprints, disables VPNs, etc.
    I let the device do its first boot after the factory reset. I copied that back the TWRP backup to the device and booted TWRP with fastboot (I never install TWRP on the device, always boot it with cable and fastboot). At that point the device was encrypted but without a password. And then I started a lengthy restore.

    After the restore completed successfully:
    On the first reboot, everything was messed up, I got a black screen, the power menu was the only thing that was responsive, and it was a nonstandard/simple power menu.
    Upon the second reboot, I was back in business, but I had lost:
    • The LSP SELinux policies. Xposed was not functional. The LSP app detected that, and a quick LSP reflash with Magisk took care of the problem.
    • Most of my system settings were gone, but not all (WiFi access point list, Bluetooth connecions were all there for example). It looks like the settings storage settings.db was lost.
    • My widgets on the home screen were blank and needed to be reconfigured.
    • All apps using the system keystore had lost their data stored there. That was expected.

    So overall a positive experience, but some glitches. Better then reinstalling from apk backups, but not perfect.
    3
    Thank you for bringing TWRP to op8t. As far as installing recovery, magisk and rooting, is there a device specific version of magisk or is it one size fits all? I noticed in one of the rooting guides they recommended using the canary magisk but the guide was released before the first official release of TWRP.
    I use the last stable Magisk version (23.0) and I've never had a problem with it. Google Pay also works perfectly without making any changes other than enabling MagiskHide.
    2
    I use latest Canary and it's all good.
  • 73



    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 Oneplus 8T

    Installation:
    # To temporarily boot it
    fastboot boot <twrp_file_name>.img

    # Since 8T/9R has a separate recovery partition, you can flash the recovery with
    fastboot flash recovery <twrp_file_name>.img

    Updating to a newer build:
    Simply flash the latest TWRP installer zip from TWRP

    OR

    Flash the img from TWRP/fastboot


    FAQ/Know Bugs are given in post #2

    Send me a beer, if you think I deserve it: PayPal


    Huge thanks to:
    @bigbiff (For everything :D 🥰 )
    @Lossyx
    @osm0sis
    @Nebrassy

    for helping in making this recovery. Without these people, TWRP for this device would not have been possible. :D

    Special mention to a friend @apophis9283 :)

    Trees:
    Device: https://github.com/theincognito-inc/android_device_oneplus_kebab
    Kernel: https://github.com/AOSPA/android_kernel_oneplus_sm8250

    Download:
    2021-09-04

    IMG: https://www.androidfilehost.com/?fid=7161016148664800911
    Installer: https://www.androidfilehost.com/?fid=7161016148664801008
    26
    FAQ and Known bugs of TWRP:

    • OOS/H2OS flashing is broken.
    • If you are planning to switch to a custom ROM, and are currently on OOS/H2OS, format /data, switch slot, reboot to TWRP and then sideload/flash the ROM + installer.
    • It's better to flash ROM + TWRP installer, if you want to keep your TWRP after flashing a ROM.
    • Don't format /data, after a flashing a ROM, before the first reboot.
    • It takes around 50s to actually boot into TWRP.

    Ideal way to flash:
    • For OOS to Custom ROM - Format /data, switch slot, reboot to TWRP, sideload/flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
    • For Custom to Custom ROM - Format /data. Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
    • For updating a custom ROM - Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system

    PS: After formatting /data, until the first time the device is booted to system, the files you send to phone via MTP (USB) will be at /data/media, not at /sdcard

    PS2: If, for some reason, you cannot send files to phone after formatting /data and rebooting to TWRP, press vol +, vol - and power button simultaneously.

    PS3: Factory reset WILL NOT wipe internal storage.
    24
    New build released - 20210726 (Kebab only)

    Changelog:

    1. Removed 9R support
    2. Fixed the TWRP screen overlapping with the notch
    3. Various mount errors while flashing ROMs should be gone now (atleast my testers think so)
    4. Latest upstream changes
    5. Removed AOSPA kernel, and updated to latest LOS kernel
    Download links:

    IMG: twrp-3.5.2_11-0-kebab-20210726-alpha
    Installer: twrp-installer-3.5.2_11-0-kebab-20210726-alpha

    As always, links are updated in the OP too.
    16
    New build released - 20210904

    Changelog:
    1. Removed repack tools
    2. Allowed OpenAES encrypted backups (to conform with the TWRP source change)
    3. Added logical flag for relevant partitions (to conform with the TWRP source change)
    4. Latest upstream changes
    Download links:

    IMG: twrp-3.5.2_11-0-kebab-20210904-alpha
    Installer: twrp-installer-3.5.2_11-0-kebab-20210904-alpha


    NOTE for 9R users: This build SHOULD work with 9R - you SHOULD be able to do everything except flashing OOS. This is experimental. Use it at your own risk.

    As always, links are updated in the OP too.
    14
    Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )

    Remove any password/pin/pattern before doing this

    Backup

    In TWRP
    1. Backup: Select only the Data partition.
    2. Reboot System

    Restore
    In TWRP
    If you skip this step you will not be able to successfully start the system after restoring data
    1. Wipe>Factory Reset
    2. Reboot System (this will rebuild the data partition)

      Back in TWRP
      1. Restore: Select the backup you want to restore
      2. Reboot system

      Note:
      1. At this point the phone will take longer than usual to boot - that's normal
      2. You will be presented with a blank screen or a toast message saying "com.android.phone keeps stopping."
        Tap "Close app", hold the Power button down to be presented with the option to (Lockdown), Power off, or Restart. Select Restart
      3. It may take a couple of restarts

    If you want to backup and restore fingerprints too, follow the guide in the attached file