[OnePlus 8T Guides, News, & Discussion] Mrmcfeffers:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.

Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools

Unlock oem bootloader

Enable developer options (click build number several times)(make sure you’re connected to internet)

Enable oem unlocking, advanced reboot, usb debugging

Reboot to bootloader/fastboot

fastboot oem unlock

Unlock bootloader

Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while

booting)

Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)

fastboot flash boot (path to boot.img)

fastboot flash dtbo (path to dtbo.img)

fastboot flash recovery (path to recovery.img)

Download firmware (https://kremowka.xyz/files/8fw/)

Enter recovery mode, enter fastbootd

Advanced > enter fastboot

Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload

LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in

there somewhere

Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer

(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”

Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.

Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)

adb devices (to confirm phone is connected properly and device drivers are configured properly)

adb sideload (path to lineage 19.1 .zip)

Sideload will likely get stuck at 47%. This is normal. Just wait.

Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)

adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are

too large. Just download them all from google play store once booted.

Signature verification failed will pop up, just confirm “yes”

Reboot recovery?

adb sideload (path to copy partitions .zip)

Back > Reboot system now

It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have

data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done

that before this step (do it in fastboot, search up adb shell pull)

If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something

happened.

OPTIONAL (if you want magisk/root)

Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on

Search in settings for “advanced”, click “advanced restart” and enable

Hold power button, restart, recovery

Apply update > apply from adb

adb devices

adb sideload (path to magisk .apk)

Signature verification failed, install anyway

Volume up to go to back arrow, reboot system now

Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts

Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file

transfer is on

DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE

What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)

Install from storage

Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters

Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click

google play services, google play store, and carrier services (the square check box next to the name, make sure

every check below when you open it as a dropdown menu is checked

Reboot phone

Now you can download whatever you want

If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy

your recovery if you try to use it on android 12.

Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not

have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I

was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”

You need to install that on your own from https://www.microsoft.com/en-us/software

download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and

add it from there.

If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few

things i’ve tried to fix it. Make sure you have correct drivers

from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008

“The system cannot find the file specified”

Open command prompt as administrator

Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"

I put mine in C: drive folder but I'm not sure it matters

Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading

and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t

know.

If that doesn’t work, do sfc /scannow

Open windows update, make sure all updates are applied and restart windows (make sure you go to optional

updates and select qualcomm drivers)

Fastboot won’t connect

Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.

Google the difference if you don’t know what it is. Download usb drivers

from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it

shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,

and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device

won’t start” when installing bootloader interface, one possible solution is to disable driver signing.

Open command prompt as an administrator (doesn’t have to be in platform tools directory)

bcedit /set testsigning on

Reboot, try to install driver again.

If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\

modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through

options with volume down, because it may enter an option cycle and you won’t be able to do anything unless

you fastboot flash boot twrp.img.

It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want

that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard

vendor_image may be but it’d not as important as persist.

To backup persist.img, put phone in recovery, type in command prompt or powershell

adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img

adb pull /tmp/persist.img persist.img

This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t

give it out at random as it contains your imei number, not sure what the consequences of that could be but

nothing good is likely to come of it.

Important shortcuts:

Power + vol up – boot into system

Power + vol down – boot into fastboot

Power + vol up + vol down – boot into edl

IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +

VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO

GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE

IS PHYSICALLY UNDAMAGED.

If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google

dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and

closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,

and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.

Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard

translate and possibly slow down device.

You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix

any auto update bugs. Credit to vewu for showing me that

https://github.com/j-hc/mindetach-magisk

https://github.com/Pixel-Props/raven/releases

https://github.com/kdrag0n/safetynet-fix

Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.

Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.

Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and

send me a better version