yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] Dan3ll1:
I would be so free and link this thread if thats ok :)

https://xdaforums.com/t/can-t-install-flash-twrp.4370457/

Maybe someone can help me with that.

One question i do have. Why there are no .IMG files anymore? Only the .zip and the .zip.asc?

What does the .asc file do? Is it needed?

Or is the .zip file the normal file for flashing in ADB now?
[OnePlus 7 & 7 Pro Cross Device Development] christantoan:
.IMG files are there, scroll down a bit.

I believe the .asc file is used for verification to make sure the file is not tampered/corrupted.

.zip file AFAIK is for flashing through Magisk (like the old official version) though I haven't tested yet.
[OnePlus 7 & 7 Pro Cross Device Development] Dan3ll1:
Oh man....I am special :)

Dont know but i thought that when the last time i downloaded straight from twrp.me both files where next to each other.
[OnePlus 7 & 7 Pro Cross Device Development] christantoan:
Don't worry. I also didn't notice it the first time around :D
[OnePlus 7 & 7 Pro Cross Device Development] Qutayba Khader:
if i already installed magisk can i just flash the [twrp zip] as normal ?
[OnePlus 7 & 7 Pro Cross Device Development] reef2009:
Did anyone installed TWRP 3.6 with encrypted filesystem? How did you flash it?

One Running laatst OOS with everything stock except Magisk. last TWRP broke everything bouse the encrypted filesystem.
[OnePlus 7 & 7 Pro Cross Device Development] osm0sis:
It's only really necessary to update to these unofficial builds if you're on an Android 11 ROM, since the latest official can't decrypt those.
[OnePlus 7 & 7 Pro Cross Device Development] Volidon:
disregard
[OnePlus 7 & 7 Pro Cross Device Development] Etoo22:
Does this twrp support dual boot pls
[OnePlus 7 & 7 Pro Cross Device Development] 5star02707:
thanks finally unofficial TWRP for android 11 ;)
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
Hi guys.

So if I was to upgrade from OOS 10 to OOS 11 and retain TWRP with the ability to restore back to latest OOS 10 backup and retain root what procedure should I use...

EDIT...

Ok so I bit the bullet and installed the latest OOS11 and kept both root and this new TWRP.

1. Install OTA update but DON'T REBOOT.

2. Open Magisk and install to direct install DON'T REBOOT.

3. Open Magisk again and install to inactive slot NOW REBOOT.

4. After reboot you should still be rooted and have the latest OTA update with stock recovery.

5. Use adb to flash nebrassy 2 TWRP image in bootloader.

6. When in TWRP go to Advanced > Flash Current TWRP.

7. Flash latest Magisk again to keep root.

8. Reboot and enjoy latest OOS11 version with TWRP and rooted.

Thanks to the dev for making this possible.

Edit 2.

I tried to do a backup of the new OOS 11 and got the following 255 error.

It's probably my fault but a little help would be appreciated...

View attachment 5334261
[OnePlus 7 & 7 Pro Cross Device Development] lollyjay:
I have OOS Beta 4 installed. I would like to flash Beta 5 with TWRP. Has anyone tested this?
[OnePlus 7 & 7 Pro Cross Device Development] dipleg:
Sorry if this is a stupid question but will this work on op7pro oos 11.0.0.11 encrypted w/ latest magisk?
[OnePlus 7 & 7 Pro Cross Device Development] cr1cr1:
This build works as expected, with decryption for oos 11.

fastboot boot the img, flashed current TWRP as instructed. Another option is to copy the img on the phone and flash recovery img. Same outcome.

Also flashed Magisk 23 and blu_spark kernel.

View attachment 5334271

View attachment 5334275

View attachment 5334277

Great job to the author, sent him a beer. Thanks a lot!
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
Have you tried doing a backup?

I got the 255 error described above...
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
When trying to make a backup, it gives an error "createTarFork( ) process ended with ERROR: 255".

Can I beat this?
[OnePlus 7 & 7 Pro Cross Device Development] cr1cr1:
Just tried, confirm that fails with ERROR 255.

I actually never back up data this way, instead, I am using Titanium Backup Pro (one reason to need root).
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
Is there a version of Titanium Backup for Android 11??
[OnePlus 7 & 7 Pro Cross Device Development] cr1cr1:
Still on google play. Actually is "abandonware", but still works as expected in A11.

I have been using it for years. Helped me migrate all my apps and apps data as they are, and system settings from one phone to another. The main advantage is that it backs up each app, the backups are self contained, can be encrypted, and copied to cloud storage, like google drive. This is way better imho, because a full system image will not work on another phone, in case you lose/break the current one.

You will need also to install Magisk module busybox-ndk or any busybox.
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
Titanium Backup backuping only the data.TWRP serves to backup the entire system and makes it possible to restore normal in case of failures
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
I'd rather use TWRP but there appears to be an error 255 issue with backups...
[OnePlus 7 & 7 Pro Cross Device Development] osm0sis:
You guys need to upload the actual /tmp/recovery.log after the backup error. The dev doesn't have the device so will need your help ironing out any remaining issues.
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
Backups may be unreliable and might be working only in specific cases, currently even if you manage to get a backup, restoring might not work as you might get an unbootable system after, don't rely on them as your only backup, but yes I do need recovery.log
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
Here is the error log 255 https://dropmefiles.com/Y2N0q
[OnePlus 7 & 7 Pro Cross Device Development] dianoandr:
I'm sorry if I take this opportunity, my curiosity, but what repo package do you use in magisk manager?

To restore magisk after installing the new twrp recovery, have you changed the magisk.apk file to magisk.zip and installed it from recovery?

Thanks for the info.
[OnePlus 7 & 7 Pro Cross Device Development] stephanb1:
The error 255 shows up when parallel apps are activated as user 999 cannot be decrypted.

Even when trying to decrypt user 999 manually in TWRP, the password is not accepted.
[OnePlus 7 & 7 Pro Cross Device Development] khalisz:
I did it, from the previous version.

- Copy the TWRP 3.6 zip to your phone

- Reboot to TWRP

- Flash the new recovery TWRP 3.6 zip

- Flash Magisk

- Clear dalvik cache

- Reboot to recovery and check if you noticed the new login "pad" then you're running now the new TWRP 3.6

- Reboot to system and enjoy.
[OnePlus 7 & 7 Pro Cross Device Development] khalisz:
@reef2009 Let me know ;)

There is also a second option in case.
[OnePlus 7 & 7 Pro Cross Device Development] reef2009:
I'll try it next weekend. I can't allow any brick before this week.
[OnePlus 7 & 7 Pro Cross Device Development] Purplezigar:
I followed these steps exactly, except for the magisk zip. I forgot to copy over beforehand so i ended up doing an adb sideload via twrp.

I'm on regular OOS11 w/magisk.

I'm now stuck in a bootloop and can't get out of twrp. I'm unable to mount my /data filesystem. I had a simple pin passcode, but it won't take it and keeps saying failed to decrypt.

When I boot it doesn't prompt me for my pin to decrypt, but just shows 0mb for storage. I've also tried decrypting via adb shell with no luck.

How the heck do i get out of this bootloop?

Edit: I am also seeing init user 0 failed error now
[OnePlus 7 & 7 Pro Cross Device Development] khalisz:
Because the wrong TWRP has been installed for your phone.

- Flash this one : https://dl.twrp.me/guacamole/twrp-installer-3.6.0_11-0-guacamole.zip.html

- Reboot to Bootloader

- open cmd with admin rights

- open "CD" in the folder where the twrp is located

- connect your phone

- tape this command : fastboot flash recovery twrp-installer-3.6.0_11-0-guacamole.zip (file name)

- Reboot to recovery and check.
[OnePlus 7 & 7 Pro Cross Device Development] Purplezigar:
I have been using the FBEv1 TWRP image and getting the same result
[OnePlus 7 & 7 Pro Cross Device Development] khalisz:
There is something strange.

the v2 is only for custom rom.

Have you tried to flash this one now ? : https://dl.twrp.me/guacamole/twrp-installer-3.6.0_11-0-guacamole.zip.html
[OnePlus 7 & 7 Pro Cross Device Development] Purplezigar:
Yes I did try that one, I also tried booting from the older 3.5 as well with no luck. I ended up using MSM to reset to 10, and am updating back to 11 now.

I wish I didn't have to do this, but it's too late to go back now
[OnePlus 7 & 7 Pro Cross Device Development] khalisz:
Indeed no choice.

After the update to 11.

- Unlock the BL

- Reboot to fastboot

- Flash recovery https://dl.twrp.me/guacamole/twrp-installer-3.6.0_11-0-guacamole.zip.html

- Reboot to recovery and flash magisk 23. (zip)

- Boot to system and you're done. :-) (install magisk 23, rename zip to apk)
[OnePlus 7 & 7 Pro Cross Device Development] kroupper:
Just install Custom ROM Android 12. When this TWRP will work on a12?
[OnePlus 7 & 7 Pro Cross Device Development] manan001:
Great work finally after long time we are official. Hope we get new stable roms now.
[OnePlus 7 & 7 Pro Cross Device Development] iamMG:
Can the new 3.6.0 version backup user 999? Or do I still need to remove user 999 before backup? Possible to decrypt user 999 with pin when entering TWRP?
[OnePlus 7 & 7 Pro Cross Device Development] flash713:
You can also adb sideload magisk23.apk (or zip, if you rename it) or flash magisk23.apk in TWRP recovery. I wasn't aware of being able to sideload magisk23.apk or flash the apk in TWRP until the other day I just did said wth and swiped it and it installed.

I've been renaming magisk apk to magisk zip for roughly a year prior. 🤣😂😁

Awesome work on TWRP op! I haven't used a device that had a fully functional recovery in a few years! 💯👍
[OnePlus 7 & 7 Pro Cross Device Development] cantenna:
Hi guys,

Is backup/restore working now on Android 11?

Compatible with decryption?
[OnePlus 7 & 7 Pro Cross Device Development] flash713:
I haven't had to restore but I have a few nandroid backups I made in TWRP that I transferred to thumb drive in case I need them some day. I'm not encrypted.. I'll restore in about one hour from now and edit my post here as to the results. It's currently 7:42am my time..

Edit added:

Got tied up doing things or would have done this already. When I boot FBEv1 or v2 I get what's in attached screenshot. View attachment 5492335
[OnePlus 7 & 7 Pro Cross Device Development] iamMG:
TWRP 3.6.0 still can't decrypt user 999. I don't understand why that is so. Isn't it supposed to have to have the same password/pin as user 0?
[OnePlus 7 & 7 Pro Cross Device Development] H4X0R46:
OP says backup and restore is unreliable. Is that still the case or has that just not been updated in the OP? I figure it's better to ask before trying it and soft bricking my phone lol
[OnePlus 7 & 7 Pro Cross Device Development] VampireHeart:
I made a nandroid backup and it worked, just need to try if i can restore it. With previous official twrp it will work only using dfe cause decryption can't work without it but i'm pretty sure the restore will work like before, now on A11 decryption work normally.
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Is there a default data decryption password to be used in TWRP 3.6 for a OnePlus 7Pro running OOS 10.3.8?

I accidentally hosed my device and I am trying to restore. I am running TWRP 3.6, and it comes up and asks for a data password, and I vaguely remember reading somewhere that there might be some sort of default password to use.

I tried setting the screen password in the OS and then trying that inside of TWRP when prompted for the data password, but that doesn't work. I also tried totally disabling the screen password ("swipe mode") and going back into TWRP, but I am still being asked for a data password.

I am currently unable to use MSM to reinitialize my device due to problems with the PC, and so I'm hoping there is indeed some default data password that I could use.

Thank you very much in advance.

PS: I tried TWRP 3.5.2_9.0, and I have the same problem.
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Follow-up: I tried the following:

fastboot erase userdata

... and then ...

fastboot format:ext4 userdata

Both stated that they succeeded.

But when I went into TWRP, the data partition was still inaccessible.
[OnePlus 7 & 7 Pro Cross Device Development] hammered58:
Could you just pick a rom , go into fastboot , do a fastboot flash boot boot.img, go into to recovery and then do a format erase, then flash the rom vis adb sideload do another format erase , reboot
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Thank you very much. I did that. The ROM is OOS 11.0.5-1. Then, I do fastboot boot twrp-3.6.0_11-0-guacamole.img, and it indeed gets me into TWRP. However, when I try to format data, I get these messages:

Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Unable to wipe data

Doing fastboot erase userdata and fastboot format:ext4 userdata both say that they succeed, but when returning to TWRP, I have the same problem with the /data partition.

PS: Perhaps I have to "decrypt data". However, I have no idea what password to give when asked inside of TWRP. And before doing all this, I never had a password on my device.

PPS: And if I try to boot into System, I just get into a boot loop, and System never comes up.

PPPS: "Repair filesystem" fails also, with this message:

/system/bin/e2fsck -fp process ended with ERROR: 16 Unable to repair Data.
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
DELETED: accidental double message posting
[OnePlus 7 & 7 Pro Cross Device Development] hammered58:
Whenever I came to a password screen in twrp I just hit ok without inputting a password and it always worked.

I was once stuck on the just the boot screen and the only thing that saved me was the msm tool,, but you said that was not an option, sorry I am not of more help.. Good luck
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Thank you anyway. I appreciate the help you gave me.

TWRP doesn't do the decryption on my device without my giving a password.

Happy New Year!
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Regarding the issue I reported above: now I luckily managed to get access to a PC that I used before for MSM unbrick flashes. It always worked fine with those unbrick flashes in the past, and this PC is still configured exactly as it was configured before, and I have confirmed that it has the same device drivers as before, and the driver is indeed the correct one.

However, now the MSM flash consistently fails a few seconds after the EDL connection is established. It gives the "Sahara Connection Failed" message. This repeatedly occurs.

With all that I have reported, I'm now thinking that my device might have some sort of basic problem with storage, firmware, or something else, and that it may very well be beyond repair.
[OnePlus 7 & 7 Pro Cross Device Development] hammered58:
I can say my msm did not work untill the port drive section in my device manager said Qualcomm qds 9008, and it only says this when the phone goes into the edl mode, after edl it switches back to regular adb android device
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Thank you. Yes, before doing what I described above, I confirmed that it does indeed say Qualcomm qds 9008 for me under that situation.

This is one of the reasons for why I am thinking that my device might be "broken" in some way.
[OnePlus 7 & 7 Pro Cross Device Development] hammered58:
I have also read to uncheck the sha256 box, I don't know what that does but I have done that and it still works
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Oh, I didn't know about that. Thank you! I tried unchecking, but I have the same problem.

Also, I tried running MSM both as Administrator and not as Administrator. Again, same problem in both cases.
[OnePlus 7 & 7 Pro Cross Device Development] hammered58:
Another idea I've tried is hitting the start on the msm tool then issuing the command from adb ,, adb reboot edl,,. See if that triggers a response , other idea would be to reconfig another PC, or install a virtual machine install 2 ND is and config that one
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
I am already borrowing a friend's PC for this, but I have more than one friend :) ... so I will keep trying with other machines. However, this MSM procedure worked fine many times in the past from that same PC, and that machine hasn't been changed in the least for at least a year or so.

And sadly, I already know that I can't get MSM to work at all under a Bootcamp-installed Windows 10 instance on my Mac, nor on a virtualbox-installed Windows 10 instance on my Linux machine.

But I didn't know about the adb reboot edl command, and I'll definitely try that.

Thank you again for all your help!
[OnePlus 7 & 7 Pro Cross Device Development] iamMG:
I was trying backup with v3.6.0 when it said 'Not all users are decrypted'. How do I decrypt user 999? I don't know the password and I really don't want to remove the user for the backup. Is there a default password? Simply pressing the 'tick' button does nothing.
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
With regard to my recent messages concerning issues accessing /data, I have now solved that problem.

I had forgotten that in the past, I was trying the OrangeFox dual-boot recovery on this device, and it had repartitioned /data.

I fixed this by flashing the appropriate *.img files for my OS (OOS 10.3.8) via fastboot, and then by booting into the standard OrangeFox recovery (the non-dual-boot version) via fastboot, and then by using its adb sideload facility to flash that same OrangeFox recovery. OrangeFox's adb sideload mechanism offers options to the user for repartitioning and rebuilding /data. I utilized those options and set /data back to "Stock", and after that, /data became accessible again, and I could format it and access it in recovery with no problem.

At this point, I flashed OOS 10.3.8, and I then flashed the appropriate TWRP and Magisk. Now, my device is back up and running in that OOS version, and TWRP is working fine.

The EDL problem continues, but given that my device is now usable again, I am not overly concerned about this MsmDownloadTool issue at the moment. In my spare time, I'll continue to look into that.

... and I especially thank @hammered58 for so much very helpful assistance!
[OnePlus 7 & 7 Pro Cross Device Development] MJPollard:
I've encountered a strange issue using 3.6.0_11-0. I flashed the .zip installer from within TWRP 3.5.2_9-0 and rebooted to recovery. So far, so good. But, when I attempted to re-flash Magisk, it kept spitting up "digest check failed" errors and would fail to flash Magisk. This also happens with any other zip I try to flash. The only way I can flash a zip now is if I turn off zip digest verification. This did not happen with 3.5.2_9-0. (I'm running unencrypted, FWIW.) Addendum: I tried both versions of 3.6.0_11-0 (both the original and v2) and they both produced the exact same results.

Any ideas? Flashing zips without digest verification makes me very nervous, and makes me wonder if doing a nandroid restore (data partition only, in my case) with digest verification would also fail (I haven't tried it because I screw around with my main phone as little as necessary).
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
I'm wondering if any of you think that I could use TWRP in the following manner in order to upgrade the OS on my device (OP 7Pro, GM1917) ...

I actually have two of these devices. One has a broken screen and I use it as my "test device". I already have successfully flashed an A11 version of the crDroid ROM onto it, and it is working fine. It is using twrp-3.6.0_11-0. It's not encrypted.

My other device is running stock OOS 10.3.8 (i.e., A10) with twrp-3.5.2_9-0. It also is not encrypted.

Do you folks think that it would be possible for me to do a nandroid backup of the A11 crDroid-enabled device (Boot, System, Vendor, and Data) and then nandroid restore that backup to the other A10 device via its TWRP and have it be able to boot into the new OS? If so, that could be a quick way to upgrade the OOS 10 device to the A11 crDroid system which is currently running on the other device.

Thank you in advance for your thoughts.
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
And a related question:

Is there any down-side to upgrading TWRP on my OOS 10 device (OP 7Pro, GM1917) to twrp-3.6.0_11-0?

I tried booting up with that version of TWRP using "fastboot boot" on that device, and it worked. And I used it to make a nandroid backup, and that worked, as well.

Do you folks think that I will be safe to flash this OOS 10 device to that version of TWRP? I don't want to perform that flash and then find out that my device is bricked because the OS is still OOS 10.

If indeed this is safe, then the nandroid backup and nandroid restore that I'm asking about above will at least be performed by the same version of TWRP on each device.

Thank you for any thoughts and suggestions.
[OnePlus 7 & 7 Pro Cross Device Development] chogau1:
Thank you, I upgraded to 11 and forgot about having twrp for 10 only, I fastboot your twrp file and got out of the bootloop. One question, If I go back to 10 flashing using twrp, do I need to change twrp later to the 10 twrp or I can stay on this version? Thank you.
[OnePlus 7 & 7 Pro Cross Device Development] MJPollard:
It's 22 days later, and I'm assuming that no one has encountered this problem, judging by the lack of response. :cry:
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
With the last TWRP 3.6.0_11.0 it is not possible to restore a previously created backup on the same twrp, after restoring and booting into the system only a black screen instead of a desktop. On the previous TWRP, it seemed normal. Or do I think it was?
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
It should work after another reboot
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
I tried, it doesn’t help. To boot I had to make a drop to the factory settings. Everything went well, so the backup is restored,does not boot only the interface, instead of it black screen.
[OnePlus 7 & 7 Pro Cross Device Development] Pfeffernuss:
Still on OOS9 and being completely happy with it was tempted to see how things were on the TWRP front.

Have read the first and last couple of pages but it seems backup/restore still isn't completely stable. Am only going to upgrade to 11 if it has at least the same options as now running 9.

Wait some more or is the upgrade totally safe? As in:

Flash 11, install apps, tinker around and customize a bit. Make backup.

Fool around some more. Oops, mistake, bootloop. No biggie, will restore backup and done.

Is this possible?
[OnePlus 7 & 7 Pro Cross Device Development] flash713:
I'm encrypted and using DerpFest 12 and I've attempted to make a backup and restore it quite a few times with no luck. I've done my backups backing up only data and tried to restore and no go and I've also backed up various partitions and also wasn't able to restore. Not sure if encryption is removed if restore is possible or not. I haven't messed with it anymore but this is my user experience.

I've been using TBU pro to backup my user apps+data and manually backing up using Google backup option in settings and together it works well. Still not like a restore but it's what I've been using. Maybe there is a way to restore a full backup but I haven't discovered it yet. Pretty sure if there isn't a way it's due to the whole structure of Android changing and all that ...