I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
can anyone provide the the stock bootloader of the latest official update of the oreo? please
i got bootloop but there is no working twrp on latest oreo as of the moment, i will flash the bootloader thru fastboot
You can download the official image from here:
http://en.miui.com/thread-1598771-1-1.html
Just use winrar or something similar to browse the file and you will find a boot.img inside.
Daydreamaway said:
You can download the official image from here:
http://en.miui.com/thread-1598771-1-1.html
Just use winrar or something similar to browse the file and you will find a boot.img inside.
Click to expand...
Click to collapse
wow thanks
Does someone have the original recovery for OREO?
I have TWRP and Magisk Installed and cannot install OTA or FULL-OTA with twrp.
I need the stock recovery for OREO.
I would appreciate if someone can share it.
eRecovery doesn't work for me and I don't want to format the device again (I already bricked it once and don't want to play with HWOTA - testpoint method was needed to get it back to life)
I've extracted the recovery myself
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.365 firmware (for the C432) variant):
http://www.mediafire.com/file/dy4m97771qz6m7z/RECOVERY_RAMDISKB365.img
You can flash the .img file using TWRP (flash it over the recovery partition) - not tested with fastboot.
I was able to update to the last version using the FULL-OTA-PV file and my bootloader is still unlocked, then I flashed twrp, installed magisk and then again flashed the stock recovery for future updates.
USE AT YOUR OWN RISK!!!
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
http://www.mediafire.com/file/77hkxqtlu1f1r52/RECOVERY_RAMDISKB369.img/file
Stock recovery for VKY-L29 (ver c636)
mexusbg said:
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
Hi there. I have TWRP. I need stock recovery for VKY-L29 (ver C636). currently i am on 8.0.0.366 and want to get OTA update. Can i use your C432 variant? i have used Huawei Update extractor to extract the latest update.app but i am getting three recovery files, Recovery_Ramdis, Recovery_Vbmeta and Recovery_Vendor. i dont know which file to use or how to proceed. Any help will be much appreciated. Thank you
Click to expand...
Click to collapse
gucchh said:
mexusbg said:
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
Hi there. I have TWRP. I need stock recovery for VKY-L29 (ver C636). currently i am on 8.0.0.366 and want to get OTA update. Can i use your C432 variant? i have used Huawei Update extractor to extract the latest update.app but i am getting three recovery files, Recovery_Ramdis, Recovery_Vbmeta and Recovery_Vendor. i dont know which file to use or how to proceed. Any help will be much appreciated. Thank you
Click to expand...
Click to collapse
It should work.
Do not use firmware extractor without creating a map for your device.... or you may brick it. The correct partition is recovery_ramdisk
Click to expand...
Click to collapse
DISCLAIMER
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:
https://androidfilehost.com/?fid=818070582850510260
1.Put payload.bin to "payload_input" folder
2.Run payload_dumper.exe
3.Successfully extracted img files are in "payload_output" folder
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:
Code:
python payload_dumper.py payload.bin
You will get a boot.img file in the output folder.
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:
Code:
fastboot flash boot magisk_patched.img
To Temporarily boot into a rooted system (RECOMMENDED!!):
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!
epr said:
- 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.
Click to expand...
Click to collapse
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:
Bash:
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
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
11.0.6.8 - 11.0.10.10
KB05DA - India Folder on AFH
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
11.0.6.9 - 11.0.11.11
KB05BA - EU Folder on AFH
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
OOS 11.0.6.8 - 11.0.11.11 : https://androidfilehost.com/user/?w=settings-dev-files&flid=329462
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)
adb shell
[email protected]:/ $ su
[email protected]:/ #
Now run:
Bash:
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
Other Misc Stuff for my reference!
If after flashing a custom kernel, you see Sim cards not working:
FullOfHell said:
Be sure NOT to have a magisk patched image on both boot slots. That causes this behavior
Click to expand...
Click to collapse
Recovering lost app data after a failed boot:
Download and flash one of my adb-patched recoveries from my post here
Reboot to recovery, enter the password, open adb shell
Create a tar bundle of the app via tar -czvf MiXBackup.tgz data/data/com.mixplorer/silver and adb pull it to your system
*Or* the entire /data partition via tar --exclude /data/media/0 -czvf /data/media/0/data.tgz data/ (You CANNOT restore all of /data like this due to encryption stuff! but you can extract one app at a time and test)
Reinstall the app , reboot to recovery, adb push, and extract via tar xf MiXBackup.tar
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
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2000_Magisk_15.H.16_OTA_0160_all_2010150101_4101.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.1.2.KB05DA.img
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.3.4_BOOT_MAGISK.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.4.5_BOOT_MAGISK.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.5.6_BOOT_MAGISK.img
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
MAGISK patched boot.img which you can flash/boot directly - boot_magisk_patched_11.0.1.2_EU.img
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2003_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thanks @rage302) - magisk_patched_11.0.3.4_KB05BA.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thank @rage302) - magisk_patched_11.0.4.5_KB05BA.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - magisk_patched_11.0.5.6_KB05BA.img
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
JWhetstone02 said:
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
Click to expand...
Click to collapse
Yep, the procedure will stay the same. I would recommend waiting for someone to upload the OOS OTA zip or Oneplus to provide a direct download link.
However, if you are on the same build version, you try to patch the KB2001 boot.img and just use the fastboot boot method instead of flashing the patched image.
If it boots, you're in luck. If it doesn't, force reboot back into stock OOS.
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
5nickers said:
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
Click to expand...
Click to collapse
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
5nickers said:
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
Click to expand...
Click to collapse
Also share the OTA zip too, please
If anyone can provide the OTA or patched img for the KB2005 that would've great, I was too quick to update [emoji2363]
Oh well, I guess I'll need to wait a little longer
Sent from my KB2005 using Tapatalk
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
After rooting and making the safetynet pass, does the widevine remains L1 like OP8 and OP8Pro? Or it becomes L3 like older OP devices?
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
What model is this for? ... Or would it matter?
Yeah please clearly state which version all these OTAs are from.
5nickers said:
Yeah please clearly state which version all these OTAs are from.
Click to expand...
Click to collapse
Just wanted to give Wykillin a little help...
Payload.properties from his OTA says: ota_target_version=OnePlus8TOxygen_15.O.16_GLO_0160_2010150057
Hope this makes it a little bit clearer...
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
DroidFreak32 said:
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
Click to expand...
Click to collapse
Hi. Could you please answer my earlier question? Thank you
theincognito said:
Hi. Could you please answer my earlier question? Thank you
Click to expand...
Click to collapse
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
DroidFreak32 said:
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
Click to expand...
Click to collapse
Yeah. Both OP8 and OP8 Pro can retain L1
DroidFreak32 said:
PS: For the curious / impatient, I have uploaded the OTA ZIP here (md5sum d1a944205b91898a84b082c57ebac5a8 ):
https://drive.google.com/file/d/18kTOttFEfQN04JHt_7bkoHN3MWa4ZKo4/view
Click to expand...
Click to collapse
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
zellleonhart said:
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
Click to expand...
Click to collapse
It will. Though I suggest that you flash the EU variant over the Indian variant (cleanest OOS variant).
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
@DroidFreak32
Magisk patched boot image for OOS 11.0.1.2 EU variant (from the full OTA zip - OnePlus8TOxygen_15.E.17_OTA_0170_all_2010150108_77edc51b51680.zip)
https://androidfilehost.com/?fid=10763459528675567936