• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

dlembazo

New member
Jun 1, 2016
2
0
- 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)
Thanks for your HELP!!!

I just want to be sure of putting right everything, before starting!
How to use "SDK platform tools" to avoid to be stuck " at "a later step (specifically, when rebooting to Fastbootd)"
Thanks very much :)
 

reaper000

Senior Member
Aug 3, 2009
1,435
1,099
OnePlus 9
I would STRONGLY urge you to have the following in place before proceeding:
- SDK platform tools originally provide the FASTBOOT.EXE program and ADB and so forth for you to call upon with the command prompt in the DOS-like environment. If you didn't know this, I would urge you to read up on this stuff as much as possible before you attempt anything. Don't feel bad if you're a newbie-- we all have to begin somewhere -- so Google "Android Studio" and "SDK Platform Tools" and take it all in....
- This thread was meant for those on Android 11 ONLY. If you're on 12, I don't think this will work. At all.
- Download a functioning MSM Tool (last I checked it was India, look at all the MSM Tool threads in this forum) and be sure it can recognize your device because I'd say you now have a more than coin-flip's chance of having to use it.
- For goodness sakes, make sure your PC drivers work in bootloader mode beforehand -- I would even disable "driver signing" in Windows 10 (look at the link I provided on page 2 of this thread).
 
  • Like
Reactions: bitpushr

dlembazo

New member
Jun 1, 2016
2
0
I would STRONGLY urge you to have the following in place before proceeding:
- SDK platform tools originally provide the FASTBOOT.EXE program and ADB and so forth for you to call upon with the command prompt in the DOS-like environment. If you didn't know this, I would urge you to read up on this stuff as much as possible before you attempt anything. Don't feel bad if you're a newbie-- we all have to begin somewhere -- so Google "Android Studio" and "SDK Platform Tools" and take it all in....
- This thread was meant for those on Android 11 ONLY. If you're on 12, I don't think this will work. At all.
- Download a functioning MSM Tool (last I checked it was India, look at all the MSM Tool threads in this forum) and be sure it can recognize your device because I'd say you now have a more than coin-flip's chance of having to use it.
- For goodness sakes, make sure your PC drivers work in bootloader mode beforehand -- I would even disable "driver signing" in Windows 10 (look at the link I provided on page 2 of this thread).
Thanks for your quick response & advices, I really appreciate.
 

WhiteCloud24

Senior Member
Oct 1, 2018
57
132
++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!!
Hi i tried this after I cannot boot to edl, but I got stuck in the waiting for device situation, I typed CTRL C and now I cannot boot to fastboot at all, someone can help me? the pc is recognizing the phone but by the QCOM driver.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I would STRONGLY urge you to have the following in place before proceeding:
    - SDK platform tools originally provide the FASTBOOT.EXE program and ADB and so forth for you to call upon with the command prompt in the DOS-like environment. If you didn't know this, I would urge you to read up on this stuff as much as possible before you attempt anything. Don't feel bad if you're a newbie-- we all have to begin somewhere -- so Google "Android Studio" and "SDK Platform Tools" and take it all in....
    - This thread was meant for those on Android 11 ONLY. If you're on 12, I don't think this will work. At all.
    - Download a functioning MSM Tool (last I checked it was India, look at all the MSM Tool threads in this forum) and be sure it can recognize your device because I'd say you now have a more than coin-flip's chance of having to use it.
    - For goodness sakes, make sure your PC drivers work in bootloader mode beforehand -- I would even disable "driver signing" in Windows 10 (look at the link I provided on page 2 of this thread).
  • 8
    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:

    Stock Full OTA 11299AA zip

    Credits:
    - @Slikkster2k
    - @mauronofrio (please un-retire!)
    2
    Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
    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.
    1
    ++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!!
    1
    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!!
    1
    I would STRONGLY urge you to have the following in place before proceeding:
    - SDK platform tools originally provide the FASTBOOT.EXE program and ADB and so forth for you to call upon with the command prompt in the DOS-like environment. If you didn't know this, I would urge you to read up on this stuff as much as possible before you attempt anything. Don't feel bad if you're a newbie-- we all have to begin somewhere -- so Google "Android Studio" and "SDK Platform Tools" and take it all in....
    - This thread was meant for those on Android 11 ONLY. If you're on 12, I don't think this will work. At all.
    - Download a functioning MSM Tool (last I checked it was India, look at all the MSM Tool threads in this forum) and be sure it can recognize your device because I'd say you now have a more than coin-flip's chance of having to use it.
    - For goodness sakes, make sure your PC drivers work in bootloader mode beforehand -- I would even disable "driver signing" in Windows 10 (look at the link I provided on page 2 of this thread).