Do you have the full NA update?I was able to temporarily boot TWRP to backup the kernel from 220.127.116.11. Instead of a boot.img file it gave a boot.emmc.win but I flashed it back with "fastboot flash boot boot.emmc.win" and it worked fine. I also tested the Magisk patch and it booted with working root access. I have North American KB2005.
Stock 18.104.22.168.KB05AA boot.emmc.win (NA): https://drive.google.com/file/d/1LS7ZL9ib9PqszQL_KW_BASQox8nOAKJX/view?usp=sharing
Magisk patched 22.214.171.124.KB05AA boot.img (NA): https://drive.google.com/file/d/15OS1wx7u7P6yc9ggDguWtVm-9Y6s8H1d/view?usp=sharing
Silly question! I'm seeing that getting root for kb2005 got a few more steps so I just wanted to find out: COMING FROM SCRATCH, if I unlock my bootloader and then "fastboot boot boot.img" the correct boot.img followed by installing magisk, should I be able to get root?126.96.36.199.KB05AA International Boot image & ROOT
I do not know if are multiple OTA files for those still stuck on a previous versions before 188.8.131.52.KB05AA. I recommend just updating it through the system update or download the full rom. I updated through system update.
That's right. I wouldn't say there are more steps since it depends on the device.Silly question! I'm seeing that getting root for kb2005 got a few more steps so I just wanted to find out: COMING FROM SCRATCH, if I unlock my bootloader and then "fastboot boot boot.img" the correct boot.img followed by installing magisk, should I be able to get root?
The ONLY time this makes a difference is if you're on custom rom and updating firmware. NOT on OxygenOS and non of the other processes for root or unlocking bootloader, etc cares about the memory speed.
Sure thing, here you go
Well topjohnwu himself refers to this method as deprecated and recommends against it.
Even though it is much more convenient, I suppose this kinda makes you have second thoughts, coming from the creator of Magisk himself.This installation method is deprecated and is maintained with minimum effort. YOU HAVE BEEN WARNED!
It is very difficult to accurately detect the device’s information in custom recovery environments. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended.
Can confirm works just fine ;-)Well the method might be deprecated but it saves a lot of time and effort. It's not like the method is not functional, it's just that it doesn't work with every device. There's been several guinea pigs now and looks like it works perfectly with OOS on 8T.
Anyways, it's up to you whether you want to go around the puddle or leap over it, both work just fine.
You won't find a KB2003 boot image because the software is determined by build numbers, not phone models.
Okay i did it i'll attach the patched image for this version follow step 10 & 11 to do so
python payload_dumper.py payload.bin
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot boot magisk_patched.img
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished to install, reboot and you stay rooted with newest OTA.
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
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst1 of=/sdcard/modemst1.img dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst2 of=/sdcard/modemst2.img dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemdump of=/sdcard/modemdump.img dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist of=/sdcard/persist.img dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist_bkp of=/sdcard/persist_bkp.img
Recovering lost app data after a failed boot: