Unable to restore backup during configuration and cts check failed

[Gabriel1495]

Hi,
I have a Oneplus 6T A6013. Yesterday my phone had this state:
bootloader u

• nlocked
• root installed with magisk
• a couple of magisk module installed
• latest stable

stock rom (10.3.0)

Then an OTA update (10.3.1) arrived to me and I installed as usual:
OTA full download and

• installation, without reboot
• Magisk installation o

n other partition and reboot

Here begin problems. My phone reboot and get stucked on OnePlus animation.
I can force shut down, enter stock recovery, enter bootloader.
I can not rely on

fastboot boot twrp.img

because phone reboots and stucks on fastboot logo.

I decide to do factory reset phone, with Google backup it is not a big problem, during configuration I obviously login in with the same account and obviously backup is on cloud, but phone says "no backup found".
Moreover it seems that magisk root files were still present on the phone, and even "uninstalling" them from magisk manager doesn't remove sucessfully them.

At this point I have tried to make a completely fresh install of the OS:

• during configuration still no backup found, even if I have created more backup in the meanwhile, one of them jsut before fresh install and on Drive I can see all of them
• Google Pay sais that my system is not right, maybe cause root
• using Magisk Manager I have checked that this time root is no more installed, but I can see that "cts check" fails
• Play Store -> settings also says to me that "my phone is not certified"

Maybe I am not able to recover backup cause cts check fails. I have still bootloader unlocked.
So here are my questions.

Someone knows beacuse my phone doesn't recognize its own backups?
How can I pass cts check?
In case I should relock bootloader, how can I check that everything is truly stock and avoid a possible brick?

Thank you so much for your future answers, I have searched on internet and made tries for a whole day and contacted OnePlus chat assistence twice, but without any luck.

 

[Dr. Mario]

You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP, and you MUST use the latest one (always use up-to-date tools) which in that case is TWRP 3.3.1-31 - you have to use "Q" version of bootable TWRP image for OxygenOS 10.3.1 which is obviously Android 10 Queen Cake so be sure to use the right one.

Tethered Fastboot TWRP boot works just fine for me, in fact I installed crDroid 6.2 ROM atop OxygenOS 10.3.1 on my converted T-Mobile OnePlus 6T.

As for the bootloader, once it's unlocked, I strongly recommend leaving it alone unlocked unless you really like to use MSMTools more often. Use SafetyPatch in Magisk's module manager, it will fix the CTS SafetyNet issues. Locked bootloader actually causes more problems compared to unlocked one in my experience.

Sent from my ONEPLUS A6013 using Tapatalk

 

[Gabriel1495]

First of all thank you very much for your answer.

Is this type of twrp right?

I thank you really much for your suggestion about locking bootloader. I don't want to specifically remove root, the real problem Is that I am no more able to recover my old backup. I have just supposed that bootloader and root could be tha causes.

Before I fully reflashed OS I was able to Hide robot and pass all checks using Magisk, buy as I said I was not able to recover backup, neither a fresh and new just made backup.
I worry about the future. Now I could set again all the phone, but what will happens if tomorrow I will have to reset again?

 

[Gabriel1495]

You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP

I used latest version by fajita downloaded from my previous link. I have waited for 10 minutes stacked on oneplus fastboot mode logo and nothing happens. Now I have the problem that I am no more able to flash magisk...

 

[Dr. Mario]

That doesn't sound good - MSMTools may be necessary. Did you back up all the files?

If your T-Mobile OnePlus 6T is converted, install OxygenOS 9.0.11 and unlock the bootloader once again (MSMTools usually relock the bootloader, so unlock it again), then update to OxygenOS 10.3.0 or 10.3.1 via update zip file (I don't trust OTA updates at all, they tend to cause problems), then install the TWRP once you're at it, and then reboot back into the recovery and install Magisk if you want to.

Unless... You want to install custom Android 10 operating system which then you must do that; First reinstall OxygenOS 10.3.x ROM (in all slots, it is mandatory because you will install the same custom OS on both slots so it boots properly) then boot into TWRP, and do factory reset and data wipe in the Wipe menu, then reboot back into recovery and then plug in the USB flash drive or copy the TWRP, OS installation zip and whatever else you want installed onto the phone via the computer. Then install crDroid, LineageOS or any of OS of your choosing, and TWRP, and reboot back into recovery once again and install the OS and TWRP one final time in another slot. After doing the last reboot, install Gapps and Magisk. Finally, after you are done and reboot the phone after the installation, it will reboot by itself once - that's due to Magisk doing some configuration.

Android 10 apparently have made installation of custom ROM difficult. I have managed to brick my OnePlus 6T eight - ten times before deciding to find out how to do it successfully, thus the instruction for installation of custom OS above.

As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).

Sent from my ONEPLUS A6013 using Tapatalk

 

[Gabriel1495]

That doesn't sound good - MSMTools may be necessary. Did you back up all the files?

Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.

As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).

Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.

 

[Dr. Mario]

Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)

As for MSMTools, I really wonder. OnePlus didn't object before.

Sent from my ONEPLUS A6013 using Tapatalk

 

[Striatum_bdr]

Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.




Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.

Try this thread

https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746

 

[Gabriel1495]

Backup argumentation is now more clear, thank you

As for MSMTools, I really wonder. OnePlus didn't object before.

About MSMTools I have still some problem, fault of my really bad English...
I have not understood your answer, what does it means "OnePlus didn't object before"? Actually I am simply no able to download the tool.

Thank you again for your kindness

 

[Dr. Mario]

Striatum_bdr, that will do. The unbricking tool collection looks good.

Sent from my ONEPLUS A6013 using Tapatalk

 

[Gabriel1495]

Wonderful, I will read the "unbricking tool" thread in order to understand how to install it

 

[Dr. Mario]

Hopefully you get it to work once again.

Sent from my ONEPLUS A6013 using Tapatalk

 

[Gabriel1495]

Here I am with some good update
I have used MSMTools to truly factory reset my phone. Initially I had "sahara connection" error, but install again both Qualcomm and Oneplus drivers do the trick. After execution of MSMTools phone reboot with bootloader locked and as it was out of box.
At that point on Drive I had 3 backup (9 Feb, 10 Feb and 10 Feb) and magically last backup of 10 Feb was seen! Saddly even deleting last two backups I am not able to recover my true backup of 9 Feb (at this point it doesn't matter).
Now I have a virgin and working phone. I have no root and can use Google Pay and banking apps.

Really happy and satisfied, thank you thank you thank you very much!!!!

 

[jova33]

Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)

As for MSMTools, I really wonder. OnePlus didn't object before.

Sent from my ONEPLUS A6013 using Tapatalk

What is up with that? I booted into TWRP the other day, figured I would make a backup before upgrading, and everything was garbled.

 

[Dr. Mario]

That's because of the onboard encryption; all Nandroid backup being attempted on Android 10 only hold half of the overall encryption keys, others just stays on the phone, so when you attempt to put it back on, it is already invalidated because also Android 10 ROM on some phones (particularly the Pixels, and a few OnePlus phones like this one) changes keys upon reboots for security reasons.

Google do not want anyone including the US Government to have their hands on the data thereon as it could be very bad if it falls in the wrong hands so they went extra miles to make it difficult to hack.

Sent from my ONEPLUS A6013 using Tapatalk