[ROM][STOCK][FASTBOOT][OP7P] Stock Fastboot ROMs for OnePlus 7 Pro/ 7 Pro 5G

Search This thread

bobo31

Senior Member
Oct 20, 2011
326
24
OnePlus 11
What android number are you on that makes a significant difference
You may have to do it manually and go through all of the images and Flash manually but the boot image and recovery image are the main two that you have to have right right

And that Boot image and recovery image have to be from the same room and they have to both be stock not Rooted
 

@soka

Senior Member
Aug 8, 2014
583
208
Glencoe
You may have to do it manually and go through all of the images and Flash manually but the boot image and recovery image are the main two that you have to have right right

And that Boot image and recovery image have to be from the same room and they have to both be stock not Rooted
Yes, i found that you need to use the same fastboot version rom as the rom version you were currently on.
 

Zakku

Member
Sep 5, 2018
31
0
I followed the LineageOS 17.1 -> 18.1 upgrade guide on the official website. Like others in this thread have mentioned, it was a complete ****show. I am forever stuck in the bootload screen. I can flash all these things, but nothing changes, even with successful messages. It even says I successfully used the boot command to get into TWRP (from the official website), but it never boots into it. I cannot get into the recovery screen, whatsoever. The directions from the first post isn't working for me. Just forever stuck in the bootloader bootloop.

Any suggestions?
 

Udaydas88

Senior Member
May 29, 2015
78
3
Dhaka,Bangladesh
OnePlus 10 Pro
do you want to contact me on telegram? Maybe i can help you better
I was on stock, tried to install twrp, and after installing twrp i flash dot os and it seem install properly but after pressing reboot to system phone stuck in fastboot mode.I tried to flash fastboot rom but it always stuck and shows that
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."



those missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever

the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...

finished. total time: 153.005s
Press any key to exit..."

and then the phone tries to boot and get to fastboot mode again...
I also extract image file and try to flash flash all partition, fastboot, recovery criticals but doesn't work.
my phone model is GM21AA please help me.
 

Zakku

Member
Sep 5, 2018
31
0
I followed the LineageOS 17.1 -> 18.1 upgrade guide on the official website. Like others in this thread have mentioned, it was a complete ****show. I am forever stuck in the bootload screen. I can flash all these things, but nothing changes, even with successful messages. It even says I successfully used the boot command to get into TWRP (from the official website), but it never boots into it. I cannot get into the recovery screen, whatsoever. The directions from the first post isn't working for me. Just forever stuck in the bootloader bootloop.

Any suggestions?
I could not get the method from this thread to work, so I took like 50hrs of messing with other methods, MSMDownloadTool, included, before I could finally restore my phone. I thought my phone was bricked and wouldn't shut off nor turn on, but it turns out I had it in EDL mode. Irony being, once I learned enough about MSMDownloadTool, it was forever before I could finally get it back in EDL mode. Haha

Anyway, I have the stock image back, and now to attempt the LOS18.1 upgrade, once again...

[EDIT] Btw, "TOOL ALL IN ONE" is completely useless offline. It gives errors about not being able to connect to his website. Why require an internet connection? It makes no sense.
 

sudo_make

Member
Apr 18, 2020
11
1
Colchester
OnePlus 7 Pro
I've followed your guide, but I have stumbled onto an issue; After running the flash-all script, I am now stuck on the bootloader unlocked warning screen. I have waited for a good 20 mins but to no avail. I have attempted to boot into recovery mode and erase everything, but nothing seems to work.

I have also attempted this several times before, using different versions of Fastboot roms, and always face the same issue.

Edit: Seems flashing version 9.5.9-GM21AA-OnePlus7ProOxygen_21.O.12 got me booting, but now my WiFi is borked :/


EDIT 2: Solution: Flashed stock using GSM tool
 
Last edited:

espositodnl86

Member
Aug 28, 2021
31
4
@mauronofrio Hey, I have a OnePlus 7 Pro (GM1913) and I'm on the latest OxygenOS version (11.0.4.1). I have Widevine L3 issues and haptic feedback is very weak. If I understood correctly flashing persist.img could solve these issues... am I right? If yes, is it safe for me to try to flash the persist.img file you have uploaded?

Grazie 1000!
 

king0r

Senior Member
Oct 28, 2015
90
8
Just tried to flash persist image only. Always getting such error message:

Writing 'persist' FAILED (remote: 'Flashing is not allowed for Critical Partitions​

')​

fastboot: error: Command failed​


How can I fix it? Thanks!
 

rookey

Member
Sep 5, 2009
38
7
Hello, I'm using this tool with a OnePlus 7 Pro, unlocked, but am confronted with the following error when flashing:
Booting TWRP...
Sending 'boot.img' (31692 KB) OKAY [ 0.729s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Waiting the TWRP boots...
What can I do?
 

GUGUITOMTG4

Senior Member
Oct 26, 2011
875
329
GuGuPlace
Hello, I'm using this tool with a OnePlus 7 Pro, unlocked, but am confronted with the following error when flashing:

What can I do?
Not sure what exactly your are doing, but Use command "fast boot flash boot_a twrp.img" then, repeat replacing "_a" with_b. Then reboot into recovery.
BTW make sure you have TWRP.img in the folder where the .imgs are
 
Last edited:

rookey

Member
Sep 5, 2009
38
7
That worked well, thanks!!

However, now I'm kind of stuck now ... booting into 'system' and recovery both opens TWRP (but I don't have my LineageOS ROM zip on there, phone is 'empty'), and fastboot / bootloader mode doesn't allow me to flash any zips either... :-o

Not sure what exactly your are doing, but Use command "fast boot flash boot_a twrp.img" then, repeat replacing "_a" with_b. Then reboot into recovery.
BTW make sure you have TWRP.img in the folder where the .imgs are
 

GUGUITOMTG4

Senior Member
Oct 26, 2011
875
329
GuGuPlace
That worked well, thanks!!

However, now I'm kind of stuck now ... booting into 'system' and recovery both opens TWRP (but I don't have my LineageOS ROM zip on there, phone is 'empty'), and fastboot / bootloader mode doesn't allow me to flash any zips either... :-o
You could have 1 of 2 problems here, a phone without Rom or a Rom that was previously rooted but now doesn't have magisk. For installing a Rom you could use this guide on OP to flash all factory images or use "adb sideload romname.zip" or even just transfer your rom to phone storage via adb push while on TWRP or drag and dropping and then flash on twrp.
 

Markon101

Member
May 20, 2011
44
27
Thank you so much! I needed to quickly get my wiped phone back to stock to sell it! Works great! EDIT: Well now Oxygen won't boot even after "Erase Everything" step in recovery. I followed instructions to a T and it is not a branded device.

Edit2: Trying TWRP plus an official OTA now (sideloading after the fastboot flash)

Edit3: That did not work. I am going to try to get Lineage going again and flash another way.

Edit4: Installing OTA through TWRP doesn't boot either. Acts like it'll boot but doesn't. Lineage works fine.

Never mind! Works great! I just didn't wait long enough for OxygenOS to boot!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 102
    Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.

    HOW TO FLASH
    This version is only for not branded devices
    Download the zip;
    Unpack the zip in a folder;
    Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
    Connect the OnePlus 7 Pro to PC;
    Run flash-all.bat flasher you need;
    Wait until the process end;
    The phone will automatically reboot.

    FLASHER ADVANCED GUIDE
    flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
    flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
    flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
    flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
    flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .

    Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .


    DOWNLOAD

    All roms on AFH: https://www.androidfilehost.com/?w=files&flid=294300
    All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro
    OnePlus 7 Pro Persist: https://androidfilehost.com/?fid=6006931924117929081

    BRANDED PHONE
    For now branded device are not supported

    MANUAL FLASH: Windows - OSX - Linux

    If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)

    Fastboot Partitions:
    Code:
    fastboot flash aop_a aop.img
    fastboot flash aop_b aop.img
    fastboot flash bluetooth_a bluetooth.img
    fastboot flash bluetooth_b bluetooth.img
    fastboot flash boot_a boot.img
    fastboot flash boot_b boot.img
    fastboot flash dsp_a dsp.img
    fastboot flash dsp_b dsp.img
    fastboot flash dtbo_a dtbo.img
    fastboot flash dtbo_b dtbo.img
    fastboot flash modem_a modem.img
    fastboot flash modem_b modem.img
    fastboot flash oem_stanvbk oem_stanvbk.img
    fastboot flash qupfw_a qupfw.img
    fastboot flash qupfw_b qupfw.img
    fastboot flash storsec_a storsec.img
    fastboot flash storsec_b storsec.img
    fastboot flash system_a system.img
    fastboot flash system_b system.img
    fastboot flash vbmeta_a vbmeta.img
    fastboot flash vbmeta_b vbmeta.img
    fastboot flash vendor_a vendor.img
    fastboot flash vendor_b vendor.img
    fastboot flash LOGO_a LOGO.img
    fastboot flash LOGO_b LOGO.img
    If you need also persist partition, this is the command:
    Code:
    fastboot flash persist persist.img

    Criticals Partitions, for these you need to boot the TWRP:
    Code:
    fastboot boot TWRP.img
    When you are in TWRP you need to run these commands to push and flash all criticals partitions:
    Code:
    adb push abl.img /sdcard/abl.img
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
    adb push cmnlib.img /sdcard/cmnlib.img
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
    adb push cmnlib64.img /sdcard/cmnlib64.img
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
    adb push devcfg.img /sdcard/devcfg.img
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
    adb push hyp.img /sdcard/hyp.img
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
    adb push keymaster.img /sdcard/keymaster.img
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
    adb push xbl.img /sdcard/xbl.img
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
    adb push xbl_config.img /sdcard/xbl_config.img
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
    adb push odm.img /sdcard/odm.img
    adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
    adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
    adb push tz.img /sdcard/tz.img
    adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
    adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b

    REMEMBER
    "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.

    These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.

    If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.

    If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide

    If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/

    Thanks to @SaiBork for first time tested

    If you got some problems like write error or no partition, check this: https://xdaforums.com/showpost.php?p=76658555&postcount=34

    DONATE LINK

    If you want to support this and others my projects please consider making a donation, thanks.

    10
    Chance to get 9.5.9 fastboot?

    Guys, give me some times, i'm not a machine.
    8
    Guys these roms are not made to update your phone, but to restore your phone when you are in bootloop or something similar, to update you should use twrp or local update option to flash the full rom released from oneplus
    6
    Thank you! You revived my phone!

    Perfect, like for others oneplus devices i will continue to support them, if you want to contribute and help me, please consider making a donation, thanks.

    4
    I know you said not for branded devices, are the partitions different for these devices?

    Yes, sometimes also the rom is different. Actually the branded devices can't use this rom also if they want, because to use this rom you need to have an unlocked bootloader