Related
Stock Android 10 Fastboot Rom Project
How i made is using payload dumper to unpack payload.bin file inside recovery rom and editing flashing scripts to be usable for this unpacked files.
Requirements
ADB must be installed on PC (Click to ADB to download if you dont have it)
Unlocked Bootloader( fastboot flashing unlock + fastboot flashing unlock_critical )
Steps to install
> Unzip zip file into desktop and open the folder.
> Then run flash_all.bat file and it will install the new update and reboot to system automatically.
(Your files will not be erased if you already unlocked bootloader.)
Latest - v11.0.11.0 - Global - April Security Patch
Recommended Server : Quebec, Canada
DO NOT MIRROR THE DOWNLOAD LINKS BEFORE ASKING ME !
AndroidFileHost - v11.0.11.0 April Security Patch
AndroidFileHost - All Versions
If you want to lock your bootloader after installing it , you can use flash_all_lock.bat OR i prefer to lock it manually by doing this;
Run flash_all.bat and make sure phone boots after installing then open fastboot mode and type
fastboot flashing lock_critical
Then phone will restart automatically into recovery and wipe data.
After screen goes black hold power + volume down button (to open fastboot again) then type
fastboot flashing lock
And after booting you can disable OEM unlock from developer options if you want to.
XDA:DevDB Information
[Fastboot ROM] Android 10 Update , ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-03-19
Last Updated 2020-04-07
XDA:DevDB Information
[Fastboot ROM] Stock Android 10, ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-04-07
Last Updated 2020-04-07
@TechGenius
thanks man
i updated my phone via ota rom
would you please put boot.img of this rom , it does not exist in ota file !
really good job bro thanks again
Is this possible on build with Magisk without twrp
Thanks dude!
Would your script flash on both slots A & B?
i does not go further than sending modem_b.
what can i do?
C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0>fastboot flash modem_b "C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0\images\modem.img" ||
Sending 'modem_b' (114084 KB)
Click to expand...
Click to collapse
Hi! Does it would update 11.0.7.0 with root and TWRP, without losing the data?
Thank you!!
any one that downloaded this rom please upload boot.img
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
https://forum.xda-developers.com/sho...&postcount=340
PS
@TechGenius thanks for making Fastboot ROM for April build. You are truly a genius.
moyses said:
Is this possible on build with Magisk without twrp
Click to expand...
Click to collapse
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
Have a look at THIS POST, you'll find the original boot and the pre-rooted one
HERE is the how-to guide and a list of original boots.
fuqi said:
i does not go further than sending modem_b.
what can i do?
Click to expand...
Click to collapse
did you solved?
Just installed using a notebook with windows 10 64Bit (i had issue with 32bit laptop)
Everything is fine but still receive the notification of android 10 update to install
i used a .bit file from a different release and it worked.
no update nag for me.
hi , at first thanks for your work!
2nd question: anibody have issues installing twrp? i' m stuck on fastboot everytime i try to install it.
Same issue here.
phillow said:
Same issue here.
Click to expand...
Click to collapse
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Is this the one that got pulled off?
Therion8594 said:
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Click to expand...
Click to collapse
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Masleyko said:
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Click to expand...
Click to collapse
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Therion8594 said:
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Click to expand...
Click to collapse
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
garylawwd said:
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
Click to expand...
Click to collapse
Yes, i've already flashed but i come back to MIUI for the battery, thanks anyway :good:
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
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Shahaf said:
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Click to expand...
Click to collapse
OMG
You should first of all know your phone model
"Redmi 9T" reads as different name than "Mi 9T", isn't it?
Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
oh damn, I can fix that somehow?
Shahaf said:
oh damn, I can fix that somehow?
Click to expand...
Click to collapse
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
zgfg said:
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
Click to expand...
Click to collapse
Thank you, I will check with them!
Shahaf said:
Thank you, I will check with them!
Click to expand...
Click to collapse
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
zgfg said:
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
Click to expand...
Click to collapse
It worked!!! now my device is working, now in order to root, which twrp should I use?
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
zgfg said:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
Click to expand...
Click to collapse
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
Shahaf said:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Click to expand...
Click to collapse
fastboot boot xxx.img boots one time to the xxx.img
For flashing (permanently) to boot you need to use:
fastboot flash boot xxx.img
Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from
Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot
You can use this app (now when your phone boots) to download and look for the proper firmware:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
zgfg said:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
Click to expand...
Click to collapse
it worked! thank you
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
x51 said:
TLDR: I need boot.img (stock or patched) for C.21
I made a huge mistake. I thought the _11 in the new version was OOS11. The upgrade window didn't indicate it was a significant upgrade.
Anyway, I was also on an old version of Magisk because I need Magisk Hide to hide root from applications required for work.
I did the usual OTA by restoring binaries in Magisk, then installing to inactive slot before reboot, but I guess due to the old MAgisk and New OOS12, it failed.
I'm now on the terrible IN2025_11_C.21 and I lost root.
I need a copy of the boot.img from C.21
I cant seem to boot into the latest TWRP (fastboot boot twrp.img) to access adb shell and extract this myself. (Should I be able to? Does TWRP still work?)
I tried downloading the OTA from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87101587 so I can extract boot.bin myself but payload dumper just throws an error.
I tried downloading the images from here: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87129235 but it seems I have to pay for them. Doesnt seem legit.
I was able to extract the c.21 image from the IN2021 (India) model, but I'm not sure if that's safe for my IN2025 model.
Advice? Help?
Click to expand...
Click to collapse
There are boot images.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
AFAIK, there isn't twrp for Android 12 yet
bacon612 said:
There are boot images.
https://forum.xda-developers.com/t/guide-how-to-avoid-killing-your-oneplus-8-pr
Click to expand...
Click to collapse
http://
bacon612 said:
There are boot images.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
AFAIK, there isn't twrp for Android 12 yet
Click to expand...
Click to collapse
Thanks.
I ended up using the Indian boot.img. it worked.
x51 said:
http://
Thanks.
I ended up using the Indian boot.img. it worked.
Click to expand...
Click to collapse
I have the same problem with IN2025_ 11_C.35 no version of twrp worked for me either. Wondering if c.21 boot.ing will work
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Orig-pinetree said:
Downloaded IN2025_11_C.21 last stable in full zip from oxygen update. Payload dumpered it and fastboot booted the stock boot.img and screwed it up good, restarted thinking it'd go back to original image but no, takes a while to fire up lock screen image comes up, home screen is black. Strangely google assistant works to voice open file manager and oxygen update, downloaded IN2025_11_c.35 incremental zip but "op12 local update" doesn't see it. Twrp doesn't work so can't side load the c.35 zip to restore the boot.img. if anyone's got a IN2025_11_C.35 boot.img or any advice I'd appreciate
Click to expand...
Click to collapse
I think boot.img corrupted the system launcher, making the settings, home screen and app drawer black or blank. Had Google assistant open a file manager and uninstalled the launcher and it came back
Hello everyone, I've been rooting phones for many years and this is my first post asking for help.
The phone was on Android 12 and rooted. I think it was C.16
I tried to do a local update with oxygen updater and then use magisk to install to inactive slot. It updated and booted up however I lost root.
I flashed a patched boot image and now the phone is stuck in fastboot.
My computer recognizes fastboot and I can flash etc. however ADB does not work and the device is not recognized.
I had a spare phone that I tried to replicate the process with and it updated locally, I patched the boot image from magisk and now it is on Android 12 and fully rooted. IN2025_11_C.21
The problem phone currently says the boot image is corrupted but I am able to get it back into fastboot.
I flashed C .11, C.16 and C .21 boot.img.
I used the spare phone to create a patched boot.img and tried flashing with that.
I have tried other patched boot.imgs with various versions from the forum.
I flashed both A and B slots with stock boot.img
When I set to slot B it boots up to a strange state but it blinks a lot and then restarts after a minute or two. I was able to look at the version number and it shows C21 regardless of boot.img. See attached image. I don’t have a keyboard or any other navigation bar. Only icons. No screen lock code at boot.
I'm wondering if maybe it did a system OTA update that I missed and the phone is not on the version I suspected for example C.33 and I don't believe there is a zip file to extract a boot.img from.
If the device is in Fastboot I should be able to reboot if I find the correct boot.img, correct?
If I can update the other phone to C.33 is there a way to extract the boot.img from the device without the full OTA file?
Any help is greatly appreciated. Thank you.
There is a c.33 zip for IN2023 which is the EU version.
At least its worth a try.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
If nothing works use MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Please watch out what you flash in fastboot mode.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
xtcislove said:
There is a c.33 zip for IN2023 which is the EU version.
At least its worth a try.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
If nothing works use MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Please watch out what you flash in fastboot mode.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. I tried everything except msm, still no luck. I am still working on it and asked about it in another subforum.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
It is really hard to find a boot image for a rom you think you have installed. Your best bet is MSM back to stock and start over.