I read this to mean that he was on OOS, successfully flashed TWRP through FKM, and then flashed a kernel through TWRP. It's not completely clear, but I'm not sure that he was saying he actually flashed OOS through TWRP. Maybe 8m reading it wrong though
Ok so first off, I prob should have known what you meant regarding decryption... but its been a while since using TWRP I guess. All good on that so to answer your follow up questions:From my part, when I said "Can I mount the /data partition and decrypt the files?" I was referring to TWRP's ability to ask for a password and then use that password decrypt /data/data/*, /data/media/* etc. I would assume from the answers that this is possible.
I asked it because I thought I had read in another thread somewhere that Oneplus used a non-standard encryption scheme for 8T and there were other users speculating that because of this, there would never be a TWRP for this device. I think theincognito or the other devs and senior members would have to comment further. Regarding mounting Android system partitions, I think you can access these files in adb shell with su, I'm not sure if MTP exposes anything outside of Internal Storage although I doubt it.
You mentioned that "it would say there is NO OS installed". Do you see this message just when using TWRP or when the phone is booting?
Also, does this phone display a orange warning message when booting about how the device can't be checked for corruption due to the unlocked bootloader?
Thank you for taking the time to share your experience, this is welcome news. Having a full featured recovery option like TWRP really is a hig asset for a device.
So to sum it up:Hell I just booted it, encryption works, data backup works, I'm on OOS... The real test is to attempt to restore it... Actually I just flashed it to recovery from fastboot, it works! Although attempting to flash the incremental update fails; it doesn't appear to have the proper partition layout as it can't find system_root on slot B (I'm on slot A, TWRP attempts to flash to the inactive slot B, just where the update is supposed to go anyway)... But I found a Payload dumper https://github.com/vm03/payload_dumper that supports incremental updates so more to come there...
A "full" backup requires data, boot, dtbo, and super.So to sum it up:
With the current TWRP for 8T modell
1. DATA partition is - as stated - backupable, incl. fingerprint backup and restore.
2. A full nandroid (DATA and SUPER partitions like usually) is - as far as I experienced - possible. But restoring failed.
My device has latest OOS with working magisk (patched boot.img via fastboot) and installed twrp.
Elemental-X kernel works perfect (flashed within EXKM).
Has anyone a detailed instruction for successfully restoring everything (nandroid) coming from a factory resetted device ?
Have I overlooked/done wrong something ?
Everytime I want to restore DATA and SUPER partitions the phone gets stuck after boot animation.
Only solution was EDL tool (hardbrick tool) to get into life - which means the whole installing, BL-unlock and rooting process :-(
Maybe I mixed up something with Slot A/B ? Never had a phone with A/B so I would be thankful for any hint.
ah, I see, thanks a lot.
system_ext is a read only partition, this is intended on OxygenOS. So I'm not sure what you're getting at. Besides, TWRP does not mount logical partitions R/W as far as I know, even if the partition is writable.
The data backup/restore process is not something you could work out other than by testing. That's why it's documented.ah, I see, thanks a lot.
Yes, I saw that tutorial in the first posts of OP but it only concerns the data backup and another file includes instructions for the fingerprint backup and restore.
The attached file (unchanged from OP post) for fingerprint backup and restore is imho quite nice to fill in the missing steps.
May I ask if you can provide a step by step guide to make a full nandroid resp. the all-I-need-instructions to fully restore a former backup state?
Would you do that ?
I think because of the A/B slots it is not easy for those coming from former twrps not fully understanding what is going on with that A/B-slots and how to access them and how to check where to backup and where to copy the files - like me *confused*
alright, thanks for the heads up.The data backup/restore process is not something you could work out other than by testing. That's why it's documented.
Backing up the system side is far easier and can be worked out by understanding what gets flashed in a custom ROM and understanding how virtual A/B partitions in super work. So it doesn't really warrant a how-to other than what I told you:
- backup boot, dtbo, and super.
- restore them to the same slot you backed them up from (because the super content is slot-specific).
Haven't needed to restore whilst using 210726, but I've done it numerous times with the previous two versions.
If someone is intressted I created a black Themed TWRP Version (Themed by @acuicultor and @Morphine1) for the Oneplus 8t.
This TWRP is the same one as the one here in the OP just with the black Theme applied to it.
I put the IMG file for that here which can just be booted with fastboot boot twrp_black-3.5.2_11-0-kebab.img
As of now I only put the black themed .IMG file there but will provide a black themed installer.zip as well later on.
View attachment 5427341
Yes, I plan on installing Magisk. I know, this is not directly the topic of this thread but still related to my question:
Lets say I installed TWRP and Magisk and there is an OTA available and I want to stay rooted: Do I need to flash the original boot.img before flashing the OTA or not? (And after the OTA I would reinstall Magisk in the manager app)
Some guides do say to flash the original boot.img, some not. I don't understand in which cases this needs to be done?
An OOS OTA incremental update checks for the presence of stock versions of both boot and recovery before it runs.
This means that if you're using Magisk you have to restore the stock boot image before starting the update. And if you're using TWRP you have to restore the stock recovery image before starting the update.