[CLOSED] [No longer maintained] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (8T / Kebab) (2022-03-09)

[BillGoss]

Thank you. Can we please pin this in the first page too?
Then what happens if system is not booting at all? Per instructions, you need to do a factory reset and reboot to rebuild data. Then you can restore your full backup afterwards.

How do I push apk's in /sytem_root/ in this? I've been trying to push AuroraServices.apk into /system_root/system/priv-app/ and it won't let me because error shows that it's 'Read-only file system.'

edit. did mount -o rw,remount /system_root to have write permissions but now it showing me, no space left wut

You'll have to use Magisk.

 

[noddledizzy]

You'll have to use Magisk

You'll have to use Magisk.

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/

 

[BillGoss]

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.

 

[denisovich]

Just a small note to say the latest recovery 20210904 is working nicely for me.

Nice to see honest, diligent development.

 

[Fumetsu_Guritto]

Goal: Create a Nandroid backup and restore successfully onto a 2nd identical device.

My understanding of a Nandroid back up is that it creates a gold image of your entire setup. If I have two identical phones, I can create a Nandroid backup /gold image of Phone A, then take the Nandroid backup / gold image and use the restore option in TWRP on the Phone B, in this case both phones are OnePlus 8T.

In my testing, the backup/restore feature on just one phone, possibly failed. To test, I created a Nandroid backup, rebooted, uninstalled an app, rebooted into recovery, and used the restore feature - selecting the Nandroid backup I created. The phone rebooted on its own and began the process - 1 hour later (give or take) the phone was still on the display that reads, "Starting Android". I restarted the phone and attempted the process to restore again, this time giving the phone 2 hours - which I think is far too long, but whatever, either way the same message is displayed.

Installation instructions followed was from Case II: Devices with A/B partition scheme


Device: OnePlus 8T (KB2003)
Android Version: 11
OS: LineageOS for microG 18.1 (Kebab)
Magisk Version: f822ca5b (23001)
App: f822ca5b (23001) (21)
Package: com.topjohnwu.magisk
TWRP version: twrp-3.5.2_11-0-kebab-20210726-alpha

First issue to note:
The boot partitions - System and System Image do not exist in this version - or at least on my phone.

These are the the partitions listed in the Backup feature of my phone:
Data (excel. storage)
Boot
DTBO
EFS
Metadata
Modem
Persist
Recovery
VBMeta
Super (system, system_ext, vendor, product, odm)

The options I chose to back up and later restore were:
Data
Boot
EFS
Super

Under Options for Backup feature no boxes are checked
The list of items in Options:
Enable compression
Skip Digest generation during backup
Disable free space check before backup

So my question is:

What is the right Partitions to be selected and Options if applicable in order to create a Nandroid backup I can depend on and more importantly use the Nandroid back up from Phone A to restore / image Phone B?

Also - I assume I shouldn't be backing up EFS from Phone A and used on Phone B? I believe EFS is exclusive to the phone due to IMEI information amongst other unique information exclusive to each device?

 

[Qnorsten]

Goal: Create a Nandroid backup and restore successfully onto a 2nd identical device.

My understanding of a Nandroid back up is that it creates a gold image of your entire setup. If I have two identical phones, I can create a Nandroid backup /gold image of Phone A, then take the Nandroid backup / gold image and use the restore option in TWRP on the Phone B, in this case both phones are OnePlus 8T.

In my testing, the backup/restore feature on just one phone, possibly failed. To test, I created a Nandroid backup, rebooted, uninstalled an app, rebooted into recovery, and used the restore feature - selecting the Nandroid backup I created. The phone rebooted on its own and began the process - 1 hour later (give or take) the phone was still on the display that reads, "Starting Android". I restarted the phone and attempted the process to restore again, this time giving the phone 2 hours - which I think is far too long, but whatever, either way the same message is displayed.

Installation instructions followed was from Case II: Devices with A/B partition scheme


Device: OnePlus 8T (KB2003)
Android Version: 11
OS: LineageOS for microG 18.1 (Kebab)
Magisk Version: f822ca5b (23001)
App: f822ca5b (23001) (21)
Package: com.topjohnwu.magisk
TWRP version: twrp-3.5.2_11-0-kebab-20210726-alpha

First issue to note:
The boot partitions - System and System Image do not exist in this version - or at least on my phone.

These are the the partitions listed in the Backup feature of my phone:
Data (excel. storage)
Boot
DTBO
EFS
Metadata
Modem
Persist
Recovery
VBMeta
Super (system, system_ext, vendor, product, odm)

The options I chose to back up and later restore were:
Data
Boot
EFS
Super

Under Options for Backup feature no boxes are checked
The list of items in Options:
Enable compression
Skip Digest generation during backup
Disable free space check before backup

So my question is:

What is the right Partitions to be selected and Options if applicable in order to create a Nandroid backup I can depend on and more importantly use the Nandroid back up from Phone A to restore / image Phone B?

Also - I assume I shouldn't be backing up EFS from Phone A and used on Phone B? I believe EFS is exclusive to the phone due to IMEI information amongst other unique information exclusive to each device?

I have not tested this but what I understand from reading this thread you need to backup and restore
boot
super
DBTO
data

For a complete backup. You also must make sure that you restore to the same slot ( a or b) that you backup them up from, as some stuff in super is slot specific.

You probably also need to follow the extra steps for restoring data listed in the begining of this thread.

 

[BillGoss]

Goal: Create a Nandroid backup and restore successfully onto a 2nd identical device.

My understanding of a Nandroid back up is that it creates a gold image of your entire setup. If I have two identical phones, I can create a Nandroid backup /gold image of Phone A, then take the Nandroid backup / gold image and use the restore option in TWRP on the Phone B, in this case both phones are OnePlus 8T.

In my testing, the backup/restore feature on just one phone, possibly failed. To test, I created a Nandroid backup, rebooted, uninstalled an app, rebooted into recovery, and used the restore feature - selecting the Nandroid backup I created. The phone rebooted on its own and began the process - 1 hour later (give or take) the phone was still on the display that reads, "Starting Android". I restarted the phone and attempted the process to restore again, this time giving the phone 2 hours - which I think is far too long, but whatever, either way the same message is displayed.

Installation instructions followed was from Case II: Devices with A/B partition scheme


Device: OnePlus 8T (KB2003)
Android Version: 11
OS: LineageOS for microG 18.1 (Kebab)
Magisk Version: f822ca5b (23001)
App: f822ca5b (23001) (21)
Package: com.topjohnwu.magisk
TWRP version: twrp-3.5.2_11-0-kebab-20210726-alpha

First issue to note:
The boot partitions - System and System Image do not exist in this version - or at least on my phone.

These are the the partitions listed in the Backup feature of my phone:
Data (excel. storage)
Boot
DTBO
EFS
Metadata
Modem
Persist
Recovery
VBMeta
Super (system, system_ext, vendor, product, odm)

The options I chose to back up and later restore were:
Data
Boot
EFS
Super

Under Options for Backup feature no boxes are checked
The list of items in Options:
Enable compression
Skip Digest generation during backup
Disable free space check before backup

So my question is:

What is the right Partitions to be selected and Options if applicable in order to create a Nandroid backup I can depend on and more importantly use the Nandroid back up from Phone A to restore / image Phone B?

Also - I assume I shouldn't be backing up EFS from Phone A and used on Phone B? I believe EFS is exclusive to the phone due to IMEI information amongst other unique information exclusive to each device?

If you had read just the previous page you would have had a partial answer to your question.
Forget about how things used to work. The new virtual A/B devices, like the 8T, make things a lot more complicated.
1. You are correct about efs. It's specific to a given phone and should absolutely NOT be restored on another device.
2. See https://xdaforums.com/t/recovery-11...ect-8t-kebab-2021-09-04.4302449/post-85422489 for what you need to backup/restore.
3. You can only (I'm guessing here as I've not tried this) restore a "full" backup (as defined in the previous point) to another device if it is running the same firmware in the slot that is being restored.
4. I recommend you use the latest TWRP version as this is still an alpha release.

 

[mslezak]

If you had read just the previous page you would have had a partial answer to your question.
Forget about how things used to work. The new virtual A/B devices, like the 8T, make things a lot more complicated.
1. You are correct about efs. It's specific to a given phone and should absolutely NOT be restored on another device.
2. See https://xdaforums.com/t/recovery-11...ect-8t-kebab-2021-09-04.4302449/post-85422489 for what you need to backup/restore.
3. You can only (I'm guessing here as I've not tried this) restore a "full" backup (as defined in the previous point) to another device if it is running the same firmware in the slot that is being restored.
4. I recommend you use the latest TWRP version as this is still an alpha release.

I just installed the new version - I was using the one from July - that one I noticed:

Super / Boot / etc. all would backup and restore just fine. Data would not. I suggest backing them up SEPARATELY.

Seems even on the new one, Data has some issues backing up. Same with multiple partitions. I'd suggest if you're trying to make a backup, just backup Data and nothing with it. Now I have no idea if a restore will work - it did not work with OOS 11.0.10.10.KB05AA on the prior version of TWRP (would not boot). And when I tried the new version, it didn't seem to finish a full data backup before exiting TWRP (it just... quit). I realize this is alpha, just a heads up you may want to use other alternatives for the time being for your data partition. But super and boot and such are all working fine. That's just my experience with it; I know somewhere in the thread it said OOS backups don't work. But Super does. Boot does. Recovery does... Now on an SD card it's kind of iffy. Sometimes it fails, sometimes it doesn't. You probably want to backup to the device and copy it over to the SD card later.

Still thanks much to the dev! The "core" parts work as they should. Have saved my a$$ several times (especially with the Super backup)...

 

[BillGoss]

I just installed the new version - I was using the one from July - that one I noticed:

Super / Boot / etc. all would backup and restore just fine. Data would not. I suggest backing them up SEPARATELY.

Seems even on the new one, Data has some issues backing up. Same with multiple partitions. I'd suggest if you're trying to make a backup, just backup Data and nothing with it. Now I have no idea if a restore will work - it did not work with OOS 11.0.10.10.KB05AA on the prior version of TWRP (would not boot). And when I tried the new version, it didn't seem to finish a full data backup before exiting TWRP (it just... quit). I realize this is alpha, just a heads up you may want to use other alternatives for the time being for your data partition. But super and boot and such are all working fine. That's just my experience with it; I know somewhere in the thread it said OOS backups don't work. But Super does. Boot does. Recovery does... Now on an SD card it's kind of iffy. Sometimes it fails, sometimes it doesn't. You probably want to backup to the device and copy it over to the SD card later.

Still thanks much to the dev! The "core" parts work as they should. Have saved my a$$ several times (especially with the Super backup)...

I've also had data backups that start but then TWRP exits so I've never managed to grab logs.

I tend to backup system partitions separate to the data partition simply because the systems partitions only change on a system update, whereas I backup the data partition on a weekly basis.

Backup and restore works fine for OOS (my daily driver) and I've also tested Los and Havoc successfully. This has been the case since the very first version of this TWRP.

What doesn't work is flashing OOS, as indicated in the OP.

 

[Fumetsu_Guritto]

I have not tested this but what I understand from reading this thread you need to backup and restore
boot
super
DBTO
data

For a complete backup. You also must make sure that you restore to the same slot ( a or b) that you backup them up from, as some stuff in super is slot specific.

You probably also need to follow the extra steps for restoring data listed in the begining of this thread.

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

^

 

[ArletPDR]

Can i flash this using some recovery flashing app or something?

 

[BillGoss]

Can i flash this using some recovery flashing app or something?

You can flash the zip using the Magisk modules "Install from storage" option.

 

[ArletPDR]

Does formating /data wipes internal storage? Meaning that i lose custom rom, magisk, and twrp installer i currently have stored in my internal storage?

I currently don't have pc near me so i cannot MTP zip files over to device

 

[tyler19820201]

Does formating /data wipes internal storage? Meaning that i lose custom rom, magisk, and twrp installer i currently have stored in my internal storage?

I currently don't have pc near me so i cannot MTP zip files over to device

Format data wipes internal storage. Factory reset does not.

 

[ArletPDR]

I cannot have access to data partition on B slot.
I do factory reset on A partition and then switch to B and reboot to recovery, just like OP post tells

• Format /data (I do factory reset, because otherwise I would lose all my rom flashing files and stuff)
• Switch slot (from A to B)
• Reboot to TWRP
• Sideload/flash the ROM + installer. (This is where I cannot have access to my files anymore, they are not gone, but I cannot see them)

What I'm doing wrong?

 

[Fumetsu_Guritto]

I just installed the new version - I was using the one from July - that one I noticed:

Super / Boot / etc. all would backup and restore just fine. Data would not. I suggest backing them up SEPARATELY.

Seems even on the new one, Data has some issues backing up. Same with multiple partitions. I'd suggest if you're trying to make a backup, just backup Data and nothing with it. Now I have no idea if a restore will work - it did not work with OOS 11.0.10.10.KB05AA on the prior version of TWRP (would not boot). And when I tried the new version, it didn't seem to finish a full data backup before exiting TWRP (it just... quit). I realize this is alpha, just a heads up you may want to use other alternatives for the time being for your data partition. But super and boot and such are all working fine. That's just my experience with it; I know somewhere in the thread it said OOS backups don't work. But Super does. Boot does. Recovery does... Now on an SD card it's kind of iffy. Sometimes it fails, sometimes it doesn't. You probably want to backup to the device and copy it over to the SD card later.

Still thanks much to the dev! The "core" parts work as they should. Have saved my a$$ several times (especially with the Super backup)...

To confirm

Select Partitions to back up: Super, Boot and DTBO
Then go back and select the Data partition to back up

When restoring do Super, Boot and DTBO first then go back and restore Data - or does it matter which one is restored first (Data vs Super, Boot, and DTBO)?

 

[Fumetsu_Guritto]

I have not tested this but what I understand from reading this thread you need to backup and restore
boot
super
DBTO
data

For a complete backup. You also must make sure that you restore to the same slot ( a or b) that you backup them up from, as some stuff in super is slot specific.

You probably also need to follow the extra steps for restoring data listed in the begining of this thread.

So I'm currently active on Slot B.
If I run a back up, it backs up Slot B. When I restore, so long as Slot B is still active, I can just restore without issue?

Or if I run the back up, will it be a back up of Slot A? So I'd have to switch to Slot A before beginning the restore process?

 

[mslezak]

To confirm

Select Partitions to back up: Super, Boot and DTBO
Then go back and select the Data partition to back up

When restoring do Super, Boot and DTBO first then go back and restore Data - or does it matter which one is restored first (Data vs Super, Boot, and DTBO)?

Depends on what you're doing - like if your system gets all messed up after an update you'd likely restore super first. Then boot and dtbo. Then data (only if needed; after a failed system update you probably don't need to - I didn't at least on the July version). If your data backup works. I haven't tested on the new version if restore of a data backup works on OOS 11.0.10.10.KB05AA - maybe if you post what you're running others can advise you better. I know the thread says "not for OOS installs." But backing up / restoring it's great on the core things.

Remember, I haven't tried to restore a data backup yet on my OOS version (maybe someone here has). I just suggest restoring separately to avoid issues, just reboot back to recovery between restores, I think in the Advanced Menu but can't recall off the top of my head.

 

[Fumetsu_Guritto]

Depends on what you're doing - like if your system gets all messed up after an update you'd likely restore super first. Then boot and dtbo. Then data (only if needed; after a failed system update you probably don't need to - I didn't at least on the July version). If your data backup works. I haven't tested on the new version if restore of a data backup works on OOS 11.0.10.10.KB05AA - maybe if you post what you're running others can advise you better. I know the thread says "not for OOS installs." But backing up / restoring it's great on the core things.

Remember, I haven't tried to restore a data backup yet on my OOS version (maybe someone here has). I just suggest restoring separately to avoid issues, just reboot back to recovery between restores, I think in the Advanced Menu but can't recall off the top of my head.

Thank you!!!

Followed your instructions and it restored perfectly. BTW I'm on Lineage 18.1 for microG.

 

[mslezak]

Thank you!!!

Followed your instructions and it restored perfectly. BTW I'm on Lineage 18.1 for microG.

Great! Glad it helped.