Database Info

[How-To][Guide] Root Pixel 3 XL with Magisk 18.1 [pre-patched boot.img] - Feb

Updates
Updated to March (.002) based on Magisk 18.1. Please update to the latest adb/fastboot files provided by Google (found in "Useful Links") the latest is "platform-tools_r28.0.2-windows.zip"
As a little plus, I've but putting the stock boots up also since we started. Below in "Useful Links" is a link to my Android File Host where you can find the stock and patched boot images.
Preface
Magisk has been updated include support for Pixel XL 3 (crosshatch) and Pixel 3 (blueline) but I figured I would patch the boot.img and upload it to here for those who want to save a small amount of time or who are lazy like myself. Mishaal Rahman has put out a guide on the XDA Portal that directly inspired this guide and I give full credit to him and topjohnwu
HOWEVER, If you are new the the root/dev/command-line scene I HIGHLY recommend that you follow Mishaal's post on the XDA Portal. He goes into a lot of further detail than I will, tells you how to unlock your bootloader if you haven't already, walks you through the installation of Magisk and has suggestions of what to do with root.
I'm going to try to make this as clean and straight to the point as possible for those of us who know the ropes but also clear and concise enough for any newcomers. All credit is being given, if I overlooked where someone deserves credit, please let me know! Well, let us get to it ya'll!
Pre-Recs IMPORTANT
Unlocked Bootloader (this means no root for Verizon Pixel 3/XL owners) If you do not know how to unlock the bootloader, follow Mishaal's "Part 1" of his post and I recommend following his entire guide for those new to this
Correctly installed and up-to-date adb/fastboot and device drivers (see below for links)
This How-To is written for Windows 10
How-To
Rooting March update (.002) Links to patched_boot.March.002img AndroidFileHost | Google Drive
Make sure you are already on the March update (ending in .002)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date (latest are platform-tools_r28.0.2 for windows)
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting February update
Links to patched_boot.001.feb.img AndroidFileHost | Google Drive
Make sure you are already on the February update (ending in .001)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting January Update
[Links to Patched_boot.img Jan.004 AndroidFileHost | Google Drive
Make sure you are already on the January update (ending in .004)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting December Update
[Links to Patched_boot.img December.006.Magisk18 AndroidFileHost | Google Drive
Make sure you are already on the December update (ending in .006)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting November Update (Patched_boot.img does not work on this method so you have to do it the long way...)
November update is a bit different and we cant seem to get patched_boot.img method to work. So I will outline the process that works for rooting November below. Any guide below requires that you have the latest adb/fastboot installed and that you have an unlocked Bootloader.
If coming from rooted Sept software use this guide:
Uninstall all Magisk Modules then reboot.
Download the stock factory images for Nov.
Extract and find the "flashall.bat" .bat file
Right click > Edit
In the .bat find "-w" and DELETE it
Safe the file
After removing "-w" put phone into fastboot, plug it in, and run "flashall.bat"
Wait for it to get done and reboot
boot to system > go to settings > security and remove any pin or password or pattern
Download the latest Magisk Beta (17.3 as of writing this) and transfer to device internal storage
Now, head over to the TWRP thread and download the twrp_boot.img
Return to fastboot and open cmd in its download location
run "fastboot boot twrp-3.2.3-1-crosshatch.img" and give your device a minute or two to boot into TWRP
Once there, find and flash the magisk beta on the internal storage
reboot and test to make sure it says you're rooted
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
Rooting Sept software and software that shipped with the device
[Patched_boot.img for Sept Drive | AndroidFileHost]
Download the above zip and extract to desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Useful links
Magisk Thread
Link to my AndroidFileHost were all stock and patched boot images are
Direct Link to platform-tools for windows, mac and lunix from Google
Refrence for Pixel 3 XL information (factory images/vendor files/KST)
->This is the one I recommend for quick setup and newcomers 15-second adb for auto install that includes system-wide (got to post #1347 for the most upto date installer)
Manually install adb & fastboot doot drivers for WIndows 10 system wide
Installing for Lunix, MacOS and Windows thanks to the XDA Portal and Aurthor Doug Lynch
Credits
@topjohnwu (link to Magisk thread) He does amazing work; if you can donate to him
@MishaalRahman (link to his amazing instuctions on XDA Portal)
@doughLynch
and
@jlee08517
@ridobe
For being OGs and being here from the begining

This is a evolving and being updated post lol Sorry for the strange layout and poor instuctions at first

it is working now. I think you had to flashed both boot slots in order for it to work. Thank you for the post. It saved me

Thank you eqbirvin. I tried my own boot image from the factory image and tried the other boot image from another thread. (of course they both needed to be patched) I followed the directions to a "T" and kept getting stuck on the bootloader screen. I forgot word for word what it said lolol but something like cannot find secure boot slot. I used your pre patched boot image and worked the first time. Thank you again.

Does this factory reset your phone?

DarkPhoenix said:
Does this factory reset your phone?
Click to expand...
Click to collapse
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.

jrac86 said:
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.
Click to expand...
Click to collapse
Yeah that was a stupid question, I realized that I already knew the answer after I asked it lol.

i am getting a bootloop. my pixel 3 xl starts up to the google logo screen and does the animations but right before it displays the lock screen it crashes and restarts. i am on 030 version of pie and using the boot image that came with the factory images to root with magisk. if i flash just boot_a then i get the error no slot to boot. i have to flash both boot_a and boot_b to get to the logo screen. anyone come across this and have a fix?
also anyone notice the patched image is much smaller than the stock image?
edit: i got it to work. i had to change the patched_boot.img name to boot.img for it to work. also i used the canary build of magisk. this also works for the verizon version 031. 031 boot.img file is the one i patched. i took it from the factory images.

Got approved by androidfilehost so adding another mirror

PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"

Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
Did you flash to both slots or just one? also, follow the guide again and make sure that your downloaded and patched boot.imgs are both completely downloaded AND transfered to device correctly

Is there any way to get Magisk 17.3 installed now? I didn't get it done before John Wu took down 17.3 and now magisk manager will only find 17.2 to install.

Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
I keep getting the same error

I think that this has something to do with Magisk installing 17.2 and not 17.3

State.of.mind said:
I think that this has something to do with Magisk installing 17.2 and not 17.3
Click to expand...
Click to collapse
17.3 has been pulled for some bugs.

jlee08517 said:
17.3 has been pulled for some bugs.
Click to expand...
Click to collapse
So until there is an update
.. No root

State.of.mind said:
So until there is an update
.. No root
Click to expand...
Click to collapse
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.

jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
I've tried the pre patched method and for some reason I can't get that to work

My method should work using my patched boot. It was patched with 17.3. However, If he pulled it because of bugs, I recommend holding off until he updates again to fix the bugs. I will update my patched_boot as soon as I get word that he pushes an update.

jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
Tried the Canary build and I still get boot loops

Blackview BV9800 PRO Rugged Beast MAGISK ROOT REQUIRED

Hi everyone,
I have rooted my last few smartphones and was always happy with it. Now I got new Blackview BV9800 PRO and I want to root it with Magisk. but as the phone is new, there is lack of information on the internet, Anyway, I have found some information, but it is not complete and I believe You, smart guys, can help me to root my smartphone
This is the information I got:
How to root it with Magisk :
Download your rom from : viewtopic.php?f=285&t=532354 (you can alternatively extract it with SP Flash Tool and WWR)
Download and install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/rel ... v7.5.0.apk
Patch the boot image with Magisk Manager
Unlock the bootloader. (Wipe the phone! )
Flash the patched boot image with SP Flash Tool or Fastboot. (ONLY the boot image)
Reinstall Magisk Manager
This is what I did and what happened:
I installed latest Magisk apk from official sources. I opened the app, clicked on "Install Magisk", then via this app I downloaded the zip file, then tried to installed it via Magisk but got an error "Unsupported/Unknown image format".
Any ideas what have I done wrong? Did I have to flash boot image from the ROM, and not the one Magisk downloaded? P.S., the smartphone is new, nothing more then I written above is done to it (no oem unlocking, no usb debugging, etc).

RESERVED

I let Magisk manager patch the original boot.img. After flashing it with fastboot or SP Flash the phone stuck with message that verified boot didn't accept the signature.

Hm... Is there anyone who rooted BV9800 Pro successfuly and could guide us? ?

update fail.
I greet you, I accidentally deleted it when I updated, Nvram. on my phone. BV9800pro. It is possible to provide me with firmware recovered from a similar phone. I also posted on the forum at Blackview but without answer

Isn't there a full firmware download on Blackview website available? I thought I've seen it there

update fail
LGZACRO said:
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
Click to expand...
Click to collapse
Hello
Yesterday during an update, by accident, my equipment, BV9800pro, performed a complete formatting, "Full Format + Dowload", it seems that Nvram has also been rewritten. it is possible to provide us with a solution or file with this data, specific to our equipment. i need a original nvram.bin, and nvram.data, in firmware from Blackview site this its not exist..
if someone wants to help me, I send them a private message with their email address

My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?

LGZACRO said:
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
Click to expand...
Click to collapse
who guarantees this?
rooting worked for me with that solution given to the PM. I wanted to install AOSP, but I found that the thermal image did not work anymore, there were some problems when previewing the video files from Facebook, and I gave up. from the mistake as I mentioned I format + dowload and delete all important partitions. nvram .bin si nvdata. Nothing works properly, TEE and Google Key are inactive, the thermal image fails, some applications are closed immediately. This is the experience with rooting and installing AOSP on the BV9800Pro

Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?

LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
make total firmware dump and send the bakup , or nvram.bin nvdata.bin file,

I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?

LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
i dont now. i dont install twrp.

Ok, pm me your skype or signal or wickr or fb. We will try to do this in few hours

LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
I posted in their forum a detailed error report but the moderator deleted my post.
Don't bargain for help by them.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
As I mention there's no TWRP available for this phone yet.

I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.

I rooted it exactly like You and it worked perfectly! Thanks for auch detailed rooting guide!
By the way guys, I think we Should open the request for TWRP for BV9800Pro. How do You think?

After you unlocked bootloader, it changed to orange state, and it always shows "Your device has been unlocked and can't be trusted..Your device will boot in 5 seconds", it could be resolved by modified LK image.
Refer to
1. https://forum.hovatek.com/thread-31664.html
2. http://bbs.blackview.hk/viewtopic.php?f=286&t=532899 -- included modified LK image
Of course, you could reflash by fastboot, no need to use SP flash tool.

hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
james35888 said:
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
Click to expand...
Click to collapse

zlatkomas said:
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
Click to expand...
Click to collapse
Hi, I'm not rooted (yet) and my BV9800 PRO is having some issues with the loudspeaker, any media like YouTube or Spotify, play audio for a second or two and then just go mute, volume can be high but no audio at all, phone calls last longer but also go mute and have to go back to regular "ear-speaker" to keep listen to the other side. Are this the same problems you refer to? I can't remember if this happened after the OTA update tho. Thank you.

"device is corrupt" solution guide for Nubia Red Magic 3 / 3S

Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android 9 again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Looks like you've been using another cell

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
give me something i can contact with u in to help u

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
[email protected] u can contact me here sir

I need some help,
Last time i updated my phone to 5.09 cn rom after that when i got bugs i tried to downgrade to 3.34 and i bricked my phone , then i use unbrick tool and get back to asia version but now my phone doesnot have the charging animation in power off mode and also fastboot device is can't get the device in win7/win 10. I also tried 2-3 times by reflash the cn rom and again back to asian version.
Need help any guide please.
Thanx in advance..
I forgot to mention that adb is working, bootloader is unlocked, i can access bootloader by using keys and adb reboot-bootloader command, but can't get device in device manager in fastboot mode , i can also access 9008 mode and recovery mode. Everything working fine but i have that two issue now, also i have my device in 5.11cn rom now.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
I think I encountered this problem also when going from Android 11 (V5.11) to Android 10 (V3.34). What worked for me is the tool posted on nubia bbs.
It's on chinese but I put some screenshots on this link to be able to use it.
Red Magic 3 - Mediafire
To use the tool, put your Red Magic 3 on fastboot mode.
How to boot on Fastboot
1.) Turn off your NRM3.
2.) HOLD Volume down and power
3.) Your NRM3 should boot on fastboot
And for google play store, I'm currently using 5.09 and successfully root it with g-apps. Flashing magisk and g-apps is working ong V3.34 and V5.09.

I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now

cacaocaca said:
I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now
Click to expand...
Click to collapse
Have you tried to on the developer options and turn on USB debugging on your Red Magic 3?

How can I activate the debug if just show me that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance

Maybe it hardbrick

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
can u help me too pls

cacaocaca said:
How can I activate the debug if just show me that View attachment 5173669
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance
Click to expand...
Click to collapse
I think you should try service centre once.

jhonangelo30 said:
can u help me too pls
Click to expand...
Click to collapse
Okay pm me

3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school

johnbrinan1 said:
3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school
Click to expand...
Click to collapse
don't worry it can be fixed

RoseRahman said:
I think you should try service centre once.
Click to expand...
Click to collapse
My phone was in assistance and now it come back and work fine , no more device corrupt and no more slow charger , they did exachange the motherboard on my phone , if you will not ear the sound while plug the device to windows this mean problem motherboard maybe like me

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?

ZephyrOne said:
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?
Click to expand...
Click to collapse
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.

leipnacht said:
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.
Click to expand...
Click to collapse
Hello thanks for your help, the problem is that I do not enable oem unlocking in the system. Do you know if twrp can be installed without that option?

How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA

Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...​
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (from Android Studio) on your PC or you might be stuck at a later step (specifically, when rebooting to Fastbootd)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Optional steps, at end:
Once you've successfully booted to 11.2.2.2, I would recommend that you download the latest full OTA from OnePlus' support page (11.2.9.9 is in the DOWNLOAD LINKS, below) and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this local upgrade ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash. So now, both slots A and B should have solid functioning ROMs.
Good luck!
DOWNLOAD LINKS:
Fastboot ROM 11222AA zip:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Full OTA 11299AA zip
https://www.androidfilehost.com/?fid=7161016148664810093
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)

++This post is ONLY for those unfortunate souls who see <awaiting any device> in Fastboot mode for minutes while following the Instructions in Post #1++
- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes
- hit CTRL C to stop the flashing process
- go to Device Manager in Windows and look for the yellow-triangled ! device. LE2115 -- that's your unrecognized Fastboot device
- right click it and select update driver
- select "Browse my computer for drivers" and then "Let me pick from a list..."
- select ADB interface (and you might further need to pick the Universal or Samsung Android device) and install it
- once that driver window closes, go back to the PowerShell window
- type fastboot devices
=if you see a small string of characters, you're good. Go to the last step!
=if you only get another prompt, you need to unplug the OP9 and then reconnect it. Since you just updated the driver, Windows should now recognize and engage the driver for the Fastboot mode OP9. Confirm this by looking for a small string once you again type fastboot devices
=if you still don't get a small string confirming device recognition, try updating the driver again. And again. Because, you know, Windows. If you never succeed in getting Windows to recognize the OP9 in Fastboot mode, you might need to try downloading another ADB driver. But you really can't go further in this flashing process till the OP9 is recognized in Fastboot mode. Only then can you go on...
- the last step! Type rescuefastbootd.bat to complete the flashing process in Fastboot mode. With any luck, your OP9 will now flash the 2nd set of images and then reboot normally, on OOS 11.2.2 in slot B, and you will see the orbiting dots of a normal OOS boot. When you do, you can unplug your phone from the PC. Success!!

OPTIONAL: if you're reading this before catastrophe, I would suggest that you ensure you have working drivers for both Bootloader and Fastboot modes. (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) After driver installation on your PC, steps to do this look like:
- Settings>About Phone> tap Build number 7 times, then
- Settings>System>Developer Options>toggle Advanced Reboot.
- Hold the power button, select the 3-dot menu icon, tap Bootloader
- connect OP9 to your PC, and Windows 10 should install the right driver.
- On your PC, navigate to the Fastboot ROM downloaded unzipped folder.
- double-click cmd.bat and a PowerShell window opens.
- in the PowerShell window, type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager
- type: fastboot reboot fastboot
and your OP9 will reboot into Fastbootd mode; when you see a splash screen with a choice of languages...
- type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager (read over Post #2). Once that's done successfully (typing: fastboot devices and getting an identifying string), you want to reboot normally. Success!!

Yeah. Just in case.

Thank you

Nice write up, friend! Thank you for taking the time to do so.

reaper000 said:
Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...​
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Good luck!
DOWNLOAD LINK:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)
Click to expand...
Click to collapse
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).

Fireblast3 said:
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).
Click to expand...
Click to collapse
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!

reaper000 said:
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!
Click to expand...
Click to collapse
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"

Fireblast3 said:
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"
Click to expand...
Click to collapse
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip

reaper000 said:
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip
Click to expand...
Click to collapse
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.

Will this convert tmobile variant to global?

infamousvincci said:
Will this convert tmobile variant to global?
Click to expand...
Click to collapse
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.

reaper000 said:
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.
Click to expand...
Click to collapse
ooofff. gotcha. Thank you so much!

Fireblast3 said:
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
Click to expand...
Click to collapse
I've provided an AFH mirror for OOS' full OTA 11.2.4.4AA for convenient download.
Also, the recommendation I gave you is also now added to the OP.

I appreciate this. It would have definitely helped me back when I had these issues. Now it's here. I'm honestly scared to flash anything on this device.

I've redone the original post to reflect OnePlus' publication of 11.2.7.7AA as a downloadable full OTA and provided a mirror on AFH

My device bricked

I'm sorry to hear that. I'm not sure how much I can help, but perhaps you can please provide details? (device model, what circumstances led you here, what version of oos, what you've already tried, etc)

Please upload to MEGA or Google Drive or actually anywhere else as AFH is so slow it gives me 3 days for estimated download time. Thank you. Somebody sending a mirror would be much appreciated.

How To Guide [Unofficial] Unlocking the bootloader, rooting, and installing TWRP on Nokia 2.2 with Android 11

to moderators: this is my first thread ever, and thought a complete guide like this really has to be done. if it's not right or not in the right place, do what is right
Click to expand...
Click to collapse
Since there are only 3 useful guides about modifying this specific phone, and some really don't answer a few barriers placed in our way by HMD Global and its ridiculous OEM unlocking restrictions (-_-), and also Google probably dropped making OTA updates for it (which was very important to me, because Android 9 and 10 had bugs), I decided to mix them all up (I will give credits, obv) and add some more info I found and create a thread which will work on Android 11, which worked on my phone, not tested on another Nokia 2.2.
Hope it helps y'all!!
Part 0: Preparations
WARNING: Your storage will be wiped completely!! so make sure to back everything you need up before doing anything. Unless you have bricked/soft locked your phone, then in that case you can use MTK Client app to backup userdata.bin (more info on Part 1-2, marked with a )
Requirements:
A good computer
Obviously a network connection on your computer for downloading files, and on your phone if you wanna update thru OTA
USB cable, capable of transferring data, and without any annoying repeated disconnections or "has to be put in the right angle and position". Just use a fresh one
VCOM and adb drivers, which can be a little annoying getting them to work. Best option is to install 15 seconds minimal ADB and make sure you say Yes when it asks if you want to install device drivers.
Android SDK Platform tools, which can be downloaded from here (NOTE: You have to use Platform tools. minimal adb will NOT work with fastboot on this device. So go to C:\adb and delete everything in there, then extract platform tools in that folder instead)
and the most important of them all: MTK Client by Bkerler which can be downloaded from here. Follow the installation instructions in the link, install Git and Python and also usbdk installer featured in the Github instructions for MTK Client
All done? Great! moving to the next part
Part 1: Unlocking the bootloader
The most annoying part. Thanks to hikari_calyx for their awesome guide on how to unlock the bootloader for this phone. We will follow it step by step until we reach step 6, where we are about to flash all those backed up img's back using mtk-su. Here's the problem, you can use mtk-su only on Android 9. it doesn't work on Android 11 sadly. so we just make sure we have unlocked sec1.img and seccfg.img in a safe place, then install a fresh stock Android 9 rom om our phone with any method we are most comfortable with, like SP Flash tool like in the guide, or booting into recovery and sideloading thru adb or from sdcard. just search the net and I'm sure you will find a loooot of sites explaining how you can flash a stock android on your phone. Just make sure you won't mess IMEI and Serial Number up!!!
**There is a "unlock bootloader" option in the flash tools tab of MTK Client. haven't tried it out myself but you can give it a try**
Extra: Booting into stock recovery
There is another detailed guide on how to enter recovery mode, by foobar1123321 which you can see in here. You might need it to apply updates to your phone
After flashing and updating your OS to latest version of Android 11, it's time for Unlocking the bootloader again. but sadly, Unlocked OEM doesn't let OTA updates to be received, and trying to flash sec1.img and seccfg.img on Android 11 is not possible without root, and root is not possible without OEM unlocking :\
So here comes the neat part, MTK Client
Part 1-2: Unlocking the bootloader again
Go to the folder where you installed MTK Client (hopefully you know how git works and got it cloned and working, if no, then read Installation instructions carefully in their Github page), and open a CMD window there by typing in cmd in the address bar. then write python mtk_gui and hit enter. Do not use mtk_gui.bat since it will close the cmd and not work. Do NOT close this cmd tab. After a while, the app will start and asks you to connect your phone.
Shut down the phone, and after 5 seconds, press and hold both volume up and down keys (without the power button) and connect the phone to your computer via cable while still holding the volume buttons. If you have installed the drivers successfully, then you'll see some texts generate in the cmd window, and will (probably) wait for the Preloader VCOM.
you can let go of the volume keys.... but not for so long. Disconnect the USB cable, hold volume keys, and connect the phone again and you'll see that MTK Client successfully gets access to your phon. YAAAY!!
now you can let go of the volume keys
Go to "Read partitions" tab, and select Boot_a, Boot_b, sec1, and seccfg (make sure you wouldn't mistake them with unlocked sec1 and seccfg)
And then click on Read partitions button in the right side, and choose a location to save these partitions
You can also check userdata, if you have bricked/soft locked your phone and wanna backup your Internal storage data. You can flash it again with this app after you have fixed your phone. and if the problem wasn't caused by your data, you can use them again like you never wiped your phone
After everything is backed up, go to "Write partitions" tab, and find sec1 and seccfg, click on "set", browse and select the respective unlocked partitions we got in Part 1 (you may need to change their extension from .img to .bin for them to show up)
Click on "Write partitions", and done! You have unlocked your OEM on Android 11!! and if everything is done correctly, you'll see
Orange state Your device is unlocked and cannot be trusted Your device will boot in 5 seconds...
Click to expand...
Click to collapse
or something like this when powering it on, congrats!!
Part 2: Installing TWRP
from the official TRWP page for Nokia 2.2, download the latest TWRP image file and move it to c:\adb on your computer and rename it to twrp.img
you will also need to download a stock vbmeta image, which can be found here or simply by reading it from your phone via MTK Client (there will be two A/B partitions, any of them works) and rename the downloaded/grabbed file into vbmeta.img and move it to c:\adb
power off your phone, then boot into fastboot by holding Volume down + Power for a few seconds, until it says FASTBOOT MODE => then connect the phone to a PC, and write:
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
and then
fastboot flash boot twrp.img
Click to expand...
Click to collapse
Now we have the latest TWRP on our Nokia 2.2 , but seems like accessing TWRP is only possible by either rebooting to recovery when the phone is powered on, via Magisk, Termux, or any other app with power options (after rooting the phone), or writing this when the phone is in fastboot mode:
fastboot reboot recovery
Click to expand...
Click to collapse
You can use TWRP and all of its awesome features now, except for MTP, backup, reading userdata partition, etc. to fix that, you gotta wipe internal storage, so make a backup of your files before processing.
**IMPORTANT: Do not flash TWRP after rooting the phone or it will unroot it**
Part 3: Rooting via Magisk
I'm gonna use Magisk because... it's better than other SU apps. Get it from here and install it on your phone. Now that you have your OEM unlocked and boot partitions too, you just have to copy the partitions we got via MTK Client on your device, launch Magisk app, select Install Magisk, then choose a file, which is gonna be Boot_a.
Wait until patching is finished, and after it's done, go into downloads folder and rename it to Boot_a or you will get confused later
After that you can choose Boot_b to be patched, and after it's done, rename it to Boot_b too
Copy them both to C:\adb from your phone to your pc, and power off your phone
after you get sure device is not connected to the computer via cable, and is powered off, hold down the volume down key with power button, until your phone boots into fastboot mode
Now open a cmd in C:\adb, and write
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_b.img
Click to expand...
Click to collapse
when done, disconnect your device, and restart. You can check the Magisk app, and realize you now have superuser permissions!!!
**UPDATE** Part 3-2: Hiding Magisk
Hiding Magisk and bypassing SafetyNet is another challenging problem on this phone. Cause when you try to Hide the Magisk app, you'll come to a simple "Failed!" error which is most probably caused by SELinux status. To fix this we gotta install some modules
First of all, install Busybox from Google Play or any other source. It's not necessary, but it's good to have. simply just install it, no need to restart
Then we need to install a module called SELinux permissive (wow, how unique ;w; ) by evdenis, which can be found here. download the zip in your phone, open the Magisk app, and in the modules tab browse for our newly downloaded zip and wait until the operation is done. Reboot your phone, and you are now able to hide Magisk app without any problem.
So do so, open Magisk -> settings -> hide the Magisk app. Choose a name (settings by default) and wait until app launches itself, asking you to add a shortcut to your home screen (optional). This way, your Magisk app now has a random package name and signature and can't be detected by other apps. Now moving to the next part
Bypassing the SafetyNet:
First, in Magisk settings, enable Systemless hosts. it will add its module to the modules tab. check if it's enabled
Then toggle Zygisk in Magisk settings, and restart your phone again (2 restarts? alright no problem)
Once your phone booted up, on the main screen of Magisk, check if it says Yes in front of Zygisk. if yes, than congrats! we are not down yet tho
Go to Magisk settings and toggle Enforce DenyList, don't reboot for now (yes, there is a 3rd one coming ), but go to Configure DenyList and choose the following apps
Google Play Service
Google Play Store
Google Service Framework
Google Play Protect Service (which is probably not present, but wrote it just in case it is on your phone)
Click to expand...
Click to collapse
and also you can choose your banking apps, or any app that prevents you from using them like Netflix or some games. Now you gotta restart (third time is the charm )
Now we gotta install another module which is Universal SafetyNet fix by kdrag0n which can be found here. Download it to your phone, choose it in Magisk module browser, wait for it to finish, and restart (I'm losing my control!!! Hmph!)
Now that we did all this, we have to clear data of apps in our DenyList so they would never remember if we ever had root or no
Go to settings (the actual settings, not our now hidden Magisk app) -> Apps -> all apps -> tap the 3 dots on top -> show system apps, then find all the apps you added to your DenyList and clear their data (not cache, data itself)
Now that this is down, restart your phone ((╯°□°)╯︵ ┻━┻) it's the last time, so you can stop raging now (┬─┬ノ( º _ ºノ))
Now we can install an app like YASNAC and run SafetyNet attestation, if the results showed two pass checks, Congratulations, you bypassed SafetyNet!!!
Totally worth the restarts. (Thanks to Droidwin for their article)
And that's it!! Hope you enjoy your now rooted Nokia 2.2 phone with Android 11

Great guide, and yes mtkclients unlock will work but it may put Ur device into verity eio mode

¿Can I use the Part 3-2 to hide Magisk in Android 9 instead of 11?, I find stock Android 11 very laggy and unstable on my phone (using the camera on any app can take from 1 to 3 or 4 tries to get it working, for example), and Android 9 has served me waaaaay better. However, my banking app refuses to work with root.