- Mar 8, 2021
It doesn't seem to matter which twrp I use, I've tried all official versions from the website and a few unofficial ones.
I also get the same error when trying to boot to system with fastboot continue.
Further to this:Boot in twrp
Reboot to twrp
Install magisk zip
Yes, but I don't think there is a need of uninstalling Magisk in the first step.Further to this:
1. Uninstall Magisk.
2. Install update.
3. Install TWRP
4. Reboot to TWRP.
4a. Make sure you have renamed Magisk to 'magisk,.zip' (as there is no seperate '.zip' file anymore)
5. Install Magisk.zip file
Is that correct?
Not sure if this helps but I get that error if I attempt to restore after formatting data partition. If I format data, I need to let the phone boot completely first before restoring data backup.
Try TWRP v3.5.2-9 or something close. And try backing up data, system and boot and restoring those three partitions. Worked for me the other day. Remember your recovery is in your boot partition now ever since A/B partitioning has been on the scene. Whatever you back up in your setup, whatever recovery you have installed at that time is then restored when restoring your boot partition. To save room and time I just backup data partition then if and when I restore I clean install OOS, and whatever rom, format data..flash magisk, reboot, set up my Gmail account then boot back to TWRP and restore data partition and reboot system.So I made a backup of my own build of LineageOS 17.1 using version 3.3.1-32. I backed up System Image, Vendor Image, Data (excl. storage) and Boot. I'm trying to restore it now, but when recovering the data, I get this lovely 255 error.
View attachment 5281331
I would like to lookup the restore log, but I can't find it anywhere. The restore.log included in my backup folder, only includes the log from when the backup was created. Am I looking in the right place?
When messing around trying a different recovery version, wiping some partitions, installing another ROM (as you can see I barely have a grasp of what I'm doing here), I magically got it to restore without errors once, but then when I tried to boot into the system it would just loop to the recovery.
Possibly important info: I've had Shelter installed (it uses the work profile), but I uninstalled it before making the backup (because last time it wouldn't let me backup with it installed). Since it was no longer installed during backup, I suppose it shouldn't matter when restoring, unless it leaves some traces that I don't know of.
Anyone that can maybe give me some pointers on how to get the system back in its original state?
Att: make sure which version of the 6T you have before proceeding. They are 2 versions, International 2 active SIM slots & the T-Mobile which is 1 Active SIM slot.It is the unlocked version with 2 sim slots
You can install either using a zip file OR install an .img file per the instructions. Either will install TWRP onto your device.In the install guide, it says to copy the .img file into phone memory and install it to recovery ramdisk. Do we no longer need the .zip file to have TWRP permanently installed as the recovery? Or should the .img file be the .zip file?
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
Please be aware that the IMG fle is the following version of TWRP: twrp-3.3.1-18-enchilada-Q-mauronofrio.img.
So once you have completed the IMG install from the above post, reboot into recovery to confirm the recovery is TWRP (3.3.1-18)
I believe this thread was started before we got an official build of TWRP. I would definitely go with the official version. But I agree that OP should be updated to link to the official version.Thank you jhedfors!
Ok, so if the files you're referring to are correct, then the files that are posted at the beginning of this thread are incorrect and should be updated to reflect that.
I thought that Mauronofrio was the only one that was updating TWRP for the 6T??
So to be very clear for myself, I can use the files from the link above for the 6T?
That API error is only cosmetic. If you try another safety net checker, it should pass. It should be fixed in next Magisk build.Hey guys. Was running magisk over years...github.com
I also just installed magisk v22.1 on my 6T and it fails safetynet check. Something about the API
I flashed the ROM, then Orangefox, reboot to recovery. Flashed Nikgapps, and Magisk 23.0
This may be of help and I believe these methods are the same as A10 or A11.Are there any updated instructions for backing up and restoring an A11 custom ROM?
#include <std_disclaimer.h> /* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
Has anyone tried the latest official build, 3.3.1-0? It was generated on the 19th.
@mauronofrio, any plans for an unofficial build based on 3.3.1? The A/B partition flash in the changelog sounds like what your 3.3.0 build was already doing.