Thanks for you help the install went without issue. Will this safetynet-fix work on other devices as well? I'd like to root my GT 2 Pro and wanted to know if this same safetynet-fix module is fine to use on it as well?
Thanks for you help the install went without issue. Will this safetynet-fix work on other devices as well? I'd like to root my GT 2 Pro and wanted to know if this same safetynet-fix module is fine to use on it as well?
That modified USNF zip is the standard module with some specific changes for OPPO/OnePlus fingerprint readers as detailed here: https://github.com/kdrag0n/safetynet-fix/pull/164/commits/2df4a714544f4358d98a95e644dfa806216c0f2b (see the README.md file in the zip)
Okay. So I should be able to use the unchanged version from kdrag0n's github on other devices?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
I guess so.Okay. So I should be able to use the unchanged version from kdrag0n's github on other devices?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
tecknight
Inactive Recognized Contributor
Sandro,
You can use the second method to root your ROM.
The latest TWRP or OrangeFox (my personal favorite) have root privs by definition.
Running Magisk-24.3.zip under TWRP or OrangeFox will patch your boot image, giving you root.
Depending on the encryption state of your /userdata, you may have to run Magisk-24.3.zip
from TWRP using adb sideload
Last edited:
tecknight
Inactive Recognized Contributor
yesOkay. So I should be able to use the unchanged version from kdrag0n's github on other devices?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
Thank you! I really appreciate all your help with this.
Only issue I am having now is the TWRP app immediately crashes when I select the "Flash" option. It used to do this before rooting, however I could always clear storage/reinstall to fix it but that no longer seems to work since rooting.
tecknight
Inactive Recognized Contributor
Try the latest OrangeFox recovery for the 8T. It is also TWRP, just with a different cosmetic.
It could also have to do with your encryption state. If your /userdata is encrypted, TWRP or OrangeFox will not be able to decrypt it or to access the /userdata folder. OrangeFox seems to deal with encrypted /userdata better than TWRP.
Put OrangeFox into adb sideload mode, then try flashing a .zip with:
adb sideload <whatever>.zip
Last edited:
Hi, I'm sorry what second method?
Anyway I thought twrp wasn't working on Android 12?
In settings it shows the phone is encrypted but that wasn't anything I did. Besides rooting as shown here I haven't done anything else besides restoring apps. Looks like the 8T isn't supported with OrangeFox. Is there an unofficial version I should be looking for? The TWRP app will only work without root.
Also having another issue. Maybe it has been like this the whole time and I am only noticing it now but Netflix is very dim. After I turn all brightness settings to max I would say it's only around 50-60% of the brightness of other video apps and noticeably much dimmer than the Netflix app on my other phones. Anyone else seeing this on their 8T or know what is causing it?
tecknight
Inactive Recognized Contributor
Second method:
1. Complete steps 1-6 above.
2. Download twrp-3.6.1_11-0-kebab.img from https://dl.twrp.me/kebab/ and rename to twrp.img
3. Reboot phone to bootloader and connect to PC.
3. Hold shift+right click inside the folder containing twrp.zip and open PowerShell.
4. Type "fastboot devices" to confirm connection then type "fastboot flash recovery twrp.img" to flash TWRP.
5. Once finished disconnect from PC. Make sure you see "START" in green and press power button to reboot.
6. Download latest Magisk apk currently being v24.3 from https://github.com/topjohnwu/Magisk/
7. Change the .apk file name extension to .zip (Magisk-24.3.apk > Magisk-24.3.zip) then save to phone.
8. Reboot phone to TWRP recovery (it may take a few min to boot and ask for your lockscreen p/w. This is normal)
9. Select "INSTALL" > navigate to Magisk-24.3.zip > swipe to confirm. This will patch+flash the boot.img and load Magisk.
10. Once finished tap "REBOOT" then tap "system" to reboot phone. Current slot can be either A or B. Do not change this.
11. Open app drawer search bar and type Magisk. If it doesn't show up immediately it should appear after a few seconds.
12. Click on it to install and follow prompts to get the full version to complete process.
13. Phone is now rooted.
14. Complete steps 18-25 listed above to fix the fingerprint scanner, safety net and play protect.
TWRP cannot decompress an encrypted /userdata partition for Android 12 based ROMs. Everything else still works.
tecknight
Inactive Recognized Contributor
Release OrangeFox Recovery R11.1 V9 · Wishmasterflo/android_device_oneplus_kebab
OrangeFox Recovery R11.1 V9 Changelog: Synced with latest OrangeFox R11.1 changes
github.com
Yes, pretty much all Android 10+ ROMs attempt to force encryption. The only way to prevent encryption is by modifying the fstab.com file in multiple places, including the boot images RAM disk image, the /VENDOR partition, and possibly other partitions. So far, I have been unable to remove forced encryption on the
OnePlus 8T + 5G, but I have been able to on other phones.
Sorry, I haven't tried Netflix yet.
Last edited:
I have downloaded an update but have not installed it or restarted the phone yet but can't find the update file. Has the location changed for OTA updates? The thread mentions they are saved to /sdcard/.OTA but I don't seem to have that folder.
I rooted my 8t with this procedure. Worked very well. I am now getting a newer phone and I would like to take the 8t back to stock and relock the bootloader. Only mod is magisk. My question is, after uninstalling magisk, do I need to put the OOS that came installed on the phone when I got the phone, or can I continue with the bootloader relock with the OOS that is installed on the phone now, which is Android 12. I've read that the OS has to be stock so I would think that the Android 12 OOS would be fine. Thanks.
EVERYTHING must be stock. This includes OS, Kernel, Recovery, etc. Of course, Magisk and all mods must be gone too!
You just have to be on official OS, doesn't matter which version.
Has anyone else noticed the 'Software Update' app getting disabled after root and cannot be enabled?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23DISCLAIMER
I have only tested this on my OnePlus8T Indian model - KB2001
Huge thanks to @topjohnwu for his magic.
YOU NEED TO UNLOCK YOUR BOOTLOADER!
In case you brick your device, use this unbrick guide
If you get into a boot-loop by flashing problematic magisk modules, consider using the patched recoveries from my post HERE to remove the modules.
Manual ROOT procedureSkip to step #6 and then #10 if you do not want to use the payload dumper tool and want to directly patch and flash the stock images for your variant and Build version!
- If you haven't updated OxygenOS yet, download it via the system updater. It will be stored in /sdcard/.Ota folder in your internal storage ( /sdcard/.Ota/OnePlus8TOxygen_15.I.16_OTA_0160_all_2010150110_84be0c.zip )
The size should be >2GB. If it is not, it's probably an incremental OTA, not a full one. This guide will NOT work on incremental OTA Zips.
DO NOT Reboot or else you will lose the file
- Copy the ZIP file over to your PC
- Download the Payload Dumper
Alt dumper for windows only:Extract the zip in the folder where you downloaded the payload dumper.
- Follow the instructions in the readme of payload dumper, and extract the OTA images:
You will get a boot.img file in the output folder.Code:python payload_dumper.py payload.bin
- Proceed with installing the OxygenOS update and reboot the phone.
- Download and install the latest magisk canary release to your phone : https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
- Copy over the boot.img file created by payload_dumper to your internal storage
- Open Magisk Manager > Select Install > "Select and patch a file"
- Browse and select the boot.img file.
Magisk will create a patched boot.img file in /sdcard/Downloads/magisk_patched.img . Copy this file over to your PC. - Reboot to fastboot mode
Code:
adb reboot bootloader - Either flash the patched magisk_patched.img in the active slot or temporarily boot into it if you are skeptical.
I recommend to BOOT first and then perform a direct install via magisk as it is more reliable to patch the active slot.
To flash:
To Temporarily boot into a rooted system (RECOMMENDED!!):Code:fastboot flash boot magisk_patched.img
Code:fastboot boot magisk_patched.img
If you used the fastboot BOOT method, next you'll have to open magisk manager again, and this time, perform a "Direct Install".
This will install magisk on the active boot slot and the next reboot will give you root.
How to update OTA and KEEP ROOT
It is advised to disable all magisk modules to be safe!
For the curious / impatient, Here are the OTAs / boot images for the different 8T Versions
All patched images are removed to ensure users perform the steps 6 - 11 of the guide and also not trust images patched by others.
To find your model and build to download the right file:
KB2000 / KB05?? - Chinese VariantBash:adb shell getprop ro.product.model KB2001 adb shell getprop ro.build.version.ota OnePlus8TOxygen_15.I.16_GLO_0160_2010150110 adb shell getprop ro.build.display.id KB2001_15_201015
KB2001 / KB05DA - Indian Variant
KB2003 / KB05BA - EU Variant
KB2005 / KB05AA - International Variant
KB2007 / KB05CB - T-Mobile Variant
It's also a good practice to backup a few important partitions once you're rooted.
I used ADB shell, but you can use any terminal emulator from the play store (Termux)
Other Misc Stuff for my reference!
Repo of Oxygen OS Builds
OOS Unbrick tool
ADB Enabled OOS Recovery
Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS
Widevine discussions
4
Already patched 11.0.8.12 boot.img EU variant
discleamer;
Not my fault if your phone gets bricked
11.0.8.12 boot.img - Google Drive
drive.google.com
cheers!3I'm posting here to detail how I solved an OTA update issue with my OnePlus 8T. For disclosure, I purchased this phone used, like new from someone who themselves got it open-box from a reputable retailer. So I don't know the full history of the phone, only that when I first booted it, it had clearly been factory reset and has been running flawlessly.
After I got the phone, I started looking into options for rooting. I unlocked the bootloader, and then, seeing that there was an OTA update for 11.0.9.9.KB05AA, prepared to try to root. I ultimately downloaded a Magisk-pre-patched boot image, thanks to Xi Jing Pooh (whoever you are), linked in these forum.
So after updated to the 11.0.9.9 OTA, I flashed that image, gained root, and again, didn't have any issues.
However, when the 11.0.10.10.KB05AA rolled out, I ran into problems. The OTA update kept failing with the message "Couldn't update, Installation problem."
I had prepared to update by following instructions on the forum; going into Magisk and restoring the stock boot image (an option when you choose "Uninstall Magisk"). I think it turned out I may flashed the pre-rooted boot image before ever booting into 11.0.9.9, so that might have been a problem. So I then used fastboot to flash the stock 11.0.9.9 boot image. I even did this to both a and b slots (maybe not necessary, I'm not sure).
While I did successfully unroot, my attempts to OTA update still kept failing. I then tried to manually update using a local copy of the OTA zip and got the same error.
After discussing with and getting good advice from @BillGoss and @g96818, I decided I would need to use the MSM tool to fully restore my phone to a previous OOS version and then incrementally update. @BillGoss also pointedly recommended I should do a full, manual update to 11.0 8.13 before letting OTA updates install, to ensure my file system had no inconsistencies.
Before I did this, I decided to try to capture a logcat while once again trying to manually update using my local zip of the 11.0.10.10 OTA. I started the update then immediately issued the logcat command in adb shell. As soon as the OTA install failed, I stopped logcat, then scrolled back to find the source of the error. Turned out that my dsp partition had been modified at some point and its SHA did not match that expected by the update.
@BillGoss pointed out to me later that 1) it's likely that the 11.0.9.9 OTA didn't touch the dsp partition, and that's why I had no problem with that update, and 2) I could have tried to dump the dsp parition from the full OTA for 11.0.8.13 and fix the issue without reverting to using the MSM tool.
But, I went ahead and followed detailed instructions to restore the phone to 11.0.7.9 (the latest MSM tool version). Per Bill's advice, after getting the phone setup again, I ignored prompts to download the OTA for 11.0.10.10 and manually ran the full OTA for 11.0.8.13. Finally, I OTA upgraded to 11.0.10.10, this time with no issues at all.
I forgot to unlock my bootloader during this process, so ended up doing that and setting up the phone twice. Then I rooted again, this time using the alpha TWRP that can be found here and installing the Magisk zip, which itself patches and installs the rooted boot image. This seems to have worked fine, and I've tested that I can also easily restore the stock boot before attempting to install the next OTA that comes out. - If you haven't updated OxygenOS yet, download it via the system updater. It will be stored in /sdcard/.Ota folder in your internal storage ( /sdcard/.Ota/OnePlus8TOxygen_15.I.16_OTA_0160_all_2010150110_84be0c.zip )
New posts
-
How can I find 'Test Point' (tp) on Pixel 2?- Latest: rtyuakatsuki
-
