TeamWin / Team-Win-Recovery-Project

Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/
http://twrp.me
1.94k stars 740 forks source link

Had to use Nebrassy, took weeks to find that out #1612

Closed auwsom closed 2 years ago

auwsom commented 2 years ago

Was trying to use the fastboot boot twrp.img method to reinstall Magisk after an update, and it froze my phone. I had to download the stock image and extracter to get at the tiny stock boot.img file to restore, was a pain. Why is there no mention of the Nebrassy versions on the page below? And why are the newer versions of TWRP shown that dont work?? I had to bug the guys over at Magisk just to find this out, because none of the XDA forums had solutions. Many people are looking for a solution. Please post this information on the official TWRP pages!

https://dl.twrp.me/guacamole/

bigbiff commented 2 years ago

Is it an AOSP11 rom?

auwsom commented 2 years ago

@bigbiff Hi, yes it is. If there is some caveat about 11, I saw zero information about that anywhere on the site. It's a stock OnePlus 7 Pro as the version link above might imply.

bigbiff commented 2 years ago

We are working on aosp11 now. Closing this issue.

auwsom commented 2 years ago

@bigbiff Thank you for working on it. It has been this way for the better part of a year. I tried multiple times to fix it because I cant use SwiftBackup, my NFC for GPay is broken as well as other root functions like AppQuarantine and AppOpps. Shizuku helped the last two, but I have to send an adb command on every restart. Backup through adb is now disabled from Google. I tried even the depreciated full backup which supposedly still works with no luck. TWRP backup is the only other way available, so I dont lose all my device configuration on my device I use for work if I mess something up trying to get Magisk working again.

Can you at least put some information on the TWRP pages, so people don't try the new and old files over and over, expecting them to work if there is no warning message?!