[RECOVERY] [12] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)

[parag0n1986]

Guys, this discussion isn't about TWRP but about Magisk. You should be discussing this in a Q&A thread or some other Magisk-related thread, but not in this thread.

Very sorry Bill. Was just trying to rule out if it was TWRP or not. I will continue discussion in private message. Sorry again

 

[denisovich]

One of the prerequisites for posting something here is that it actually works ...

For me on my 8T, flashing to recovery and then booting to recovery, gives a whole lot of blank screen, and I have to use the power and volume buttons to get back to where adb recognises the device then reboot to bootloader from the duff recovery. Then I can flash the proper recovery.

I very nearly ended up with a bricked phone, and all because people think they can post things without ever testing them.

What an absolute crock. And completely typical of the amateur hour nonsense in the DIY TWRP world.

But I am grateful for your efforts, because it reminds me NEVER to trust garbage like this again.

 

[parag0n1986]

One of the prerequisites for posting something here is that it actually works ...

For me on my 8T, flashing to recovery and then booting to recovery, gives a whole lot of blank screen, and I have to use the power and volume buttons to get back to where adb recognises the device then reboot to bootloader from the duff recovery. Then I can flash the proper recovery.

I very nearly ended up with a bricked phone, and all because people think they can post things without ever testing them.

What an absolute crock. And completely typical of the amateur hour nonsense in the DIY TWRP world.

But I am grateful for your efforts, because it reminds me NEVER to trust garbage like this again.

Works just fine here... Are you on OOS12 firmware?

 

[jabe78]

One of the prerequisites for posting something here is that it actually works ...

For me on my 8T, flashing to recovery and then booting to recovery, gives a whole lot of blank screen, and I have to use the power and volume buttons to get back to where adb recognises the device then reboot to bootloader from the duff recovery. Then I can flash the proper recovery.

I very nearly ended up with a bricked phone, and all because people think they can post things without ever testing them.

What an absolute crock. And completely typical of the amateur hour nonsense in the DIY TWRP world.

But I am grateful for your efforts, because it reminds me NEVER to trust garbage like this again.

Works for me too. My issues stemmed from other sources.

 

[BillGoss]

Updated 220821 after testing V1_4 (see OP for download)
TWRP 12 is now fully functional from my perspective
** On OOS 12 C21 or later ONLY ** - It will not boot on earlier versions of OOS

Note: I have NOT tested, nor intend to test, TWRP 12 with any custom roms.

What works:

• Backup and restore of data (tested on KB2003 and KB2005)
• Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
• Rooting by flashing Magisk-*.apk
• Sideloading
• Fastbootd
• OTG

Known problems:

• Backups will fail if there are *.ttf files in /data/fonts/files/*/ or if /data/nandswap is present.
  I delete /data/nandswap and all the directories in /data/fonts/files (using my file manager - Solid Explorer) before booting recovery because I've had issues with deleting the directories in TWRP.

Things to be aware of:

• EU only: You MUST have Airplane mode turned ON before you take a data backup in TWRP to ensure that the system starts properly after restoring the data backup.
• You do not need to remove the lock screen password before taking a backup
• You MUST remove the lock screen password before restoring a backup (TWRP warns you to do this) otherwise the phone will boot up in an unusable state. And you'll have to format /data to get out of this.
• After a restore you will have to reboot the phone 2 (usual) or more (I've had to do 4) times before you can properly enter the system. Note that if your backup was taken with a password then your fingerprints will also restored.
• You do not need to remove the SIM card when rebooting after restoring a data backup (as was necessary with TWRP 11).
• You may need to clear the storage from some of your apps before they'll work properly after a restore.

Download: I've attached a flashable zip that installs it to both slots. It can be flashed in TWRP or Magisk (in Modules). Md5sum: 67fc2359908fbce21c23d79f651538bb

 

[parag0n1986]

TWRP 12 is still not fully functional but WIP builds are at the point where I am happy to use it for:
** On OOS 12 C31 or later ONLY ** - It will not boot on earlier versions of OOS

• Backup and restore of the data and other partitions (eg, super).
• Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
• Rooting by flashing Magisk-*.apk

Known problems:

• Fastbootd doesn't work. The phone will not connect to the PC. If you need to use fastbootd then install the OOS stock recovery.
• Backups will fail if there are *.ttf files in /data/fonts/files/*/
  I delete all the directories in /data/fonts/files (using my file manager - Solid Explorer) before booting recovery because I've had issues with deleting the directories in TWRP. Note that 9R backups will also fail if /data/nandswap is present.

Things to be aware of

• You do not need to remove the lock screen password before taking a backup
• You MUST remove the lock screen password before restoring a backup (TWRP warns you of this) otherwise the phone will boot up in an unusable state. And you'll have to format /data to get out of this.
• After a restore you will have to reboot the phone 2 (usual) or more (I've had to do 4) times before you can properly enter the system. Note that if your backup was taken with a password then your fingerprints will also restored.
• You do not need to remove the SIM card when rebooting after restoring a data backup (as was necessary with TWRP 11).

Download: I've attached a flashable zip that installs it to both slots. I can be flashed in TWRP or Magisk (in Modules). Md5sum: 76fda95314da60a1fe3f59d818d8a5af.
You can get the recovery.img file by unzipping the zip file.

Note: I have NOT tested TWRP 12 with any custom roms.

Has anyone you know of tested on any custom ROMs?

 

[BillGoss]

Has anyone you know of tested on any custom ROMs?

I'm not aware of any testing on custom ROMs. Doesn't mean it hasn't happened, just that I don't know.

 

[scottlam1]

I'm not aware of any testing on custom ROMs. Doesn't mean it hasn't happened, just that I don't know.

So data restore is a thing now I've been using tarb in the meantime that works good and I don't have to backup in recovery

 

[BillGoss]

PSA: restoring a backup on KB2003 C.33 doesn't work. The restore doesn't give any errors but the phone will not boot - it just sits on the OnePlus boot animation. A factory reset (no need to format data) will let the phone boot successfully and then you can restore your apps (I use Swift Backup).

 

[parag0n1986]

I'm not aware of any testing on custom ROMs. Doesn't mean it hasn't happened, just that I don't know.

I will test soon and report back. Running EvoX A12 build with OOS12 firmware

 

[parag0n1986]

I'm not aware of any testing on custom ROMs. Doesn't mean it hasn't happened, just that I don't know.

I tried the data restore and got error 255. Odd though. I have no 999 folders, or multiple users

 

[BillGoss]

I tried the data restore and got error 255. Odd though. I have no 999 folders, or multiple users

It helps if you attach the zipped recovery log.

 

[parag0n1986]

It helps if you attach the zipped recovery log.

I did another backup and restore, but it took me a few times to make it work but it finally did! On Evo X using c33 FW.

Here is the log from the failed restore as well @BillGoss https://1drv.ms/u/s!AmBrhbf7jsVMhIFufHErB370Rwo9oA

Also, the backup was done on c21 EU FW and the data actually restored over the c33 FW

EDIT: My phone is the global unlocked variant KB 2005 8T

 

[jabe78]

Will backup and restore work (theoretically) if you make a backup on one custom rom, then attempt to restore on a different Rom? Or does it have to stay within the Rom it was backed up in?

 

[parag0n1986]

Will backup and restore work (theoretically) if you make a backup on one custom rom, then attempt to restore on a different Rom? Or does it have to stay within the Rom it was backed up in?

I think it depends on the ROM how they have the data partition set up. If it's F2FS EXT4 FBEV2 or 1 EROFS etc, but then even you might have issues I haven't tried it yet. I have a successful backup and restore on evolution X OOS 12 based with C33 EU firmware. I took the backup with c21 firmware though, and it was able to restore it on c33 firmware the data partition. The way I got it to work, is advanced wipe everything besides the USB OTG, then I format data, and then boot to the ROM. I tried restoring the super partition, but that didn't seem to work very well... I just reflashed the ROM itself, but reflash TWRP before I reboot to recovery, then I do advanced wipe and tick everything except USB OTG and then format data as well. Boot to the ROM once to build the data partition skip setup and then back to TWRP and restore the data partition. You will have to reboot a couple times though for everything to set through and open a few of your apps. I opened magisk right away, that way when I rebooted again root would be there again and all the root settings I had and modules.

 

[BillGoss]

Will backup and restore work (theoretically) if you make a backup on one custom rom, then attempt to restore on a different Rom? Or does it have to stay within the Rom it was backed up in?

To be more precise, the question is about backing up and restoring the data partition.
It helps to think that there's two types of data in there: user apps and then a lot of system related stuff.
Restoring the user apps is not a problem, but it gets messy with the system stuff.
Roms store data that is specific to them and which won't work on a different rom.
This is why you should always do a factory reset after flashing a different rom. And it was often the case that an upgrade to a rom might also require a factory reset before booting.

So the general rule is that you can't restore a data backup on a different rom.

But you might get lucky if the two roms share a lot of the system stuff in common.

 

[BillGoss]

I've updated my post on the latest (v1_4) of TWRP 12. See https://forum.xda-developers.com/t/...roject-8t-9r-2022-07-27.4473983/post-87271673

 

[santi68]

Hello. Do you know if there is a possibility to decrypt phone memory from twrp. Thank you

 

[BillGoss]

Hello. Do you know if there is a possibility to decrypt phone memory from twrp. Thank you

Yes, that works. You just enter your password when prompted.

 

[santi68]

many thanks . It is not necessary to do a format data or there is that option in twrp. i am used to xiaomi and oneplus is driving me crazy. Is there a tutorial with the process? Thank you