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

[ROM][STOCK][FASTBOOT][OP7T] Stock Fastboot ROMs for OnePlus 7T

Search This thread

pxrave

Senior Member
Apr 7, 2010
1,155
487
root
px-coding.org
Google Nexus 4
OnePlus 3
Hello! Please tell me where you can download the fastboot version for 10.0.16 for reflashing? Where can you find? Drop the link please
fastboot rom for all 10.0.16 AA Global

Magisk patched root is also inside but you need flash seperat


@mauronofrio you can add to first pageß :) thanks
 

catharsis724

Senior Member
Dec 26, 2014
128
34
Android Wear
Google Pixel 3a
The biggest problem I've had with payload dumper method for newer ROMs is that it does not help create the new "system_partition" that is present on newest OOS11 and OB_.

So you can't just dump and use flash-all.

I think there should be a way of fixing this with an oos11 fastboot ROM, if possible.

The only way to update to oos11 seems to be through local upgrade on a existing oos10 install? This creates the partitions too iirc...
 

shrimpboyho3

New member
Jun 17, 2016
1
0
fastboot rom for all 10.0.16 AA Global

Magisk patched root is also inside but you need flash seperat


@mauronofrio you can add to first pageß :) thanks
Hi, I know this is off topic, but I don't think you have seen my message to you. Please take a look at it. Your messages are probably full as you are developer but to sum it up, I would like the Android Lollipop ROM you have developed for the Amazon Kindle Fire 7HD 3rd gen (soho-kfsowi). It was much more stable than the newest, but abandoned Evervolv ROM. If you have a copy please send it over as all links in that thread don't work anymore.

Thanks so much!
 

ltrain9

New member
May 16, 2021
1
0
Can/should I switch the active slot? I'm running via linux by running all the command in `flash_all.bat`.

I set my active slot from a -> b

I ran into 2 problems:
1) reserve_b says no such partition (and I'm unsure if I use my active slot 1 if that would resolve).
2) I got "Flashing is not allowed for Critical Partitions" on abl

I'm unlocked (I get the warning message every reboot). This is a tmoble OnePlus 7T (HD1907)
After running into the critical partition roadblock, I set current back to b and my phone still worked.

Code:
./fastboot flash reserve reserve.img
Sending 'reserve' (250164 KB)                      OKAY [  6.990s]
Writing 'reserve'                                  FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed

./fastboot flash abl abl.img
Sending 'abl' (1164 KB)                            OKAY [  0.045s]
Writing 'abl'                                      FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
 

iamslimshady

New member
May 23, 2021
2
0
please i need urgent help iam so worried.
okay , so i flashed a custom rom on my oneplus 7t. There were some errors but i managed to boot in and use it. Now i want to go back to stock oos11 but i just cant. I also removed twrp from phone.
I tried your method and this is what Iam getting

Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.014s]
Writing 'userdata' OKAY [ 0.004s]
Erasing 'metadata' OKAY [ 0.007s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 8.295s
Sending 'boot_a' (98304 KB) OKAY [ 2.159s]
Writing 'boot_a' OKAY [ 0.316s]
Finished. Total time: 3.650s
Sending 'dtbo' (16384 KB) OKAY [ 0.364s]
Writing 'dtbo' OKAY [ 0.067s]
Finished. Total time: 0.766s
Sending 'modem_a' (165396 KB) OKAY [ 3.737s]
Writing 'modem_a' OKAY [ 0.685s]
Finished. Total time: 6.581s
Sending 'reserve' (250164 KB) OKAY [ 5.717s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.214s]
Writing 'recovery' OKAY [ 0.334s]
Finished. Total time: 4.439s
Sending 'vbmeta' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.054s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.041s
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.038s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.018s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.015s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.032s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.021s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.612s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'hyp' (480 KB) OKAY [ 0.023s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.015s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.015s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.162s]
Writing 'LOGO' OKAY [ 0.040s]
Finished. Total time: 0.568s
Sending 'multiimgoem' (16 KB) OKAY [ 0.010s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'odm' (912 KB) OKAY [ 0.031s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.061s]
Writing 'oem_stanvbk' OKAY [ 0.013s]
Finished. Total time: 0.356s
Sending 'opproduct' (298584 KB) OKAY [ 6.812s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'qupfw' (72 KB) OKAY [ 0.008s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'storsec' (24 KB) OKAY [ 0.007s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'tz' (3092 KB) OKAY [ 0.079s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.014s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl' (3120 KB) OKAY [ 0.078s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.010s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784708 KB) OKAY [ 17.993s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.020s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.058s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.009s
Press any key to continue . . .
 

HueyT

Senior Member
Apr 3, 2014
4,375
2,031
New Albany, IN
OnePlus 7T
Force reboot into bootloader and repeat the flash--sometimes it doesn't take 1st flash as it did not enter fastbootD for the 2nd half of the flash (system partitions)
 

HueyT

Senior Member
Apr 3, 2014
4,375
2,031
New Albany, IN
OnePlus 7T
Great. I also want to go back from an A11 custom ROM to OOS11. Could you please make a tutorial of some sort/list the exact steps in sequenc
Msm tool to go to OOS10 and then oxygen updater to go to OOS11. OR, payload dumper to extract payload.bin into files and the fastboot flash all images. OR flash OOS11 zip via adb sideload in custom recovery--switch slot and repeat to other slot too
 

sandeep_kumar

Senior Member
Feb 21, 2017
514
128
Indore
@mauronofrio
I did not understand about the
"
HOW TO FLASH
This version is only for not branded devices
".
what is branded device for which it is written that branded devices are not supported.

I am from India and I think every Oneplus phone is a branded phone.
How can I know my device is not branded and only then I can use these fastboot ROM.
 
Last edited:

HueyT

Senior Member
Apr 3, 2014
4,375
2,031
New Albany, IN
OnePlus 7T
@mauronofrio
I did not understand about the
"
HOW TO FLASH
This version is only for not branded devices
".
what is branded device for which it is written that branded devices are not supported.

I am from India and I think every Oneplus phone is a branded phone.
How can I know my device is not branded and only then I can use these fastboot ROM.
You can use this if your phone is bootloader unlocked
 
  • Like
Reactions: sandeep_kumar

Plainsrus

New member
Jun 19, 2021
1
0
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) 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 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.


DOWNLOAD

All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T

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 the latest sdk platform tools, you can find it here

Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot

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.

If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.

These ROMs can't be used to update or downgrade your phone but just to restore your phone.

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/

If you got some problems like write error or no partition, check this: https://forum.xda-developers.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.

I need help with my OP7T. It is an unlocked T-mobile device, and I want to covert it into an international version. I tried the downloads, and they are so confusing to a non developer like me. Please IM me if you can help, or know someone that can help.
 

sandeep_kumar

Senior Member
Feb 21, 2017
514
128
Indore
Hello friend @mauronofrio
I am from India and my device is HD1901

I have seen a video on youtube that using this fastboot ROM, the device got to stock perfectly and the person who uploaded the video also locked the bootloader.

But in the thread you have clearly mentioned that
These ROMs can't be used to update or downgrade your phone but just to restore your phone.

So I want to confirm from your side that
1) Can I go to stock ROM completely using your fastboot ROM?
if yes, Can I update the ROM with system updater or from oxygen updater on play store on unlocked bootloader?
2) As in the youtube video, After flashing the ROM, bootloader is locked .
Is it really true? I do not hard brick my device if I go to stock completely from some reason.

Please answer.
Thanks
 

sandeep_kumar

Senior Member
Feb 21, 2017
514
128
Indore
Now the confusion starts,
Should I flash full fastboot ROM through flash-all.bat and then change the slot by the command
fastboot set_active other
and then again run flash-all.bat.

But no one has used to change the slot in this thread to flash this fastboot ROM.
may I know please, which one is correct or both are correct.
 

ToughDBlue

Member
Apr 19, 2020
27
0
I have the OnePlus 7T HD1905. I'm going to flash eOS to my phone as they just released official documentation for installation to the 7T. My question is how do I go back to Oxygen OS if I don't like eOS? Never flashed a phone before and the eOS install documentation is easy to follow. Is there an easy to follow guide to go back to Oxygen OS from eOS?
 

dubbme

New member
Mar 31, 2019
3
0
I have the problem that I unlocked the bootloader on my device with Oxygene 11 and then installed the latest TWRP. Then I tried to install Lineageos 18.1. It was installed on the slot B. The installation was apparently not finished and the device went into bootloop. All rescue attempts with MSM and this variant under Fastboot failed. I can't get into recovery now either. I can now only get into fastboot mode or into the bootloop of Lineageos 18.1. What can I do now to save the device?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) 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 7T in fastboot-bootloader mode (Power and volume + and volume-);
    Connect the OnePlus 7T to PC;
    Run flash-all.bat flasher you need;
    Wait until the process end;
    The phone will automatically reboot.


    DOWNLOAD

    All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
    All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T

    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 the latest sdk platform tools, you can find it here

    Is reccomended to format data or the rom cannot boot:
    Code:
    fastboot -w
    Others Commands to flash a fastboot rom
    Code:
    fastboot flash aop aop.img
    fastboot flash bluetooth bluetooth.img
    fastboot flash boot boot.img
    fastboot flash dsp dsp.img
    fastboot flash dtbo dtbo.img
    fastboot flash LOGO LOGO.img
    fastboot flash modem modem.img
    fastboot flash oem_stanvbk oem_stanvbk.img
    fastboot flash qupfw qupfw.img
    fastboot flash storsec storsec.img
    fastboot flash multiimgoem multiimgoem.img
    fastboot flash uefisecapp uefisecapp.img
    fastboot flash recovery recovery.img
    fastboot --disable-verity flash vbmeta vbmeta.img
    fastboot --disable-verity flash vbmeta_system vbmeta_system.img
    fastboot flash opproduct opproduct.img
    fastboot reboot fastboot
    fastboot flash system system.img
    fastboot flash vendor vendor.img
    fastboot flash product product.img
    fastboot reboot

    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.

    If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.

    These ROMs can't be used to update or downgrade your phone but just to restore your phone.

    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/

    If you got some problems like write error or no partition, check this: https://forum.xda-developers.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.

    6
    Unfortunately i have not tested this fastboot rom, i did some tests with an user and nothing else, actually you can't flash from normal fastboot mode system, vendor and product images, you need to use "fastboot reboot fastboot" command to reboot in stock recovery with fastbootd enabled, after that using the fastboot commands you can flash system, vendor and product images.

    If you have any problems with this fastboot rom or you see errors during the script execution, contact me
    3
    D
    Deleted member 5408779
    Any new fasboot images of latest OOS 7T versions..?

    I have OB6 if you are interested.
    https://mega.nz/file/xBFFVIBQ#zTOmecylCIr8ZkK902U_O_VRcAHhW7mXWMFJX5M2_Dw

    @mauronofrio I'll delete if you don't like I post it.
    2
    Really thanks for this.
    Any update on root ?

    Unfortunately no, i will check in the next hours, but without a tester should be not easy
    2
    please help me Bro My wifi is not working and if someone calls me it auto rejected all call

    Do you want to wipe all the data ( Reccomended )[Y/N]?y
    Erasing 'userdata' OKAY [ 0.421s]
    mke2fs 1.44.4 (18-Aug-2018)
    Creating filesystem with 56734085 4k blocks and 14188544 inodes
    Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

    4096000, 7962624, 11239424, 20480000, 23887872

    Allocating group tables: done
    Writing inode tables: done
    Creating journal (262144 blocks): done
    Writing superblocks and filesystem accounting information: done

    Sending 'userdata' (5024 KB) OKAY [ 0.125s]
    Writing 'userdata' OKAY [ 0.000s]
    Erasing 'metadata' OKAY [ 0.016s]
    Erase successful, but not automatically formatting.
    File system type raw not supported.
    Finished. Total time: 1.638s
    Sending 'aop' (200 KB) OKAY [ 0.016s]
    Writing 'aop' OKAY [ 0.000s]
    Finished. Total time: 0.031s
    Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
    Writing 'bluetooth' OKAY [ 0.000s]
    Finished. Total time: 0.078s
    Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
    Writing 'boot_a' OKAY [ 0.421s]
    Finished. Total time: 4.072s
    Sending 'dsp' (65536 KB) OKAY [ 1.466s]
    Writing 'dsp' OKAY [ 0.234s]
    Finished. Total time: 2.496s
    Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
    Writing 'cmnlib' FAILED (remote: 'Flashing is
    not allowed for Critical Partitions
    ')
    fastboot: error: Command failed
    Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
    Writing 'cmnlib64' FAILED (remote: 'Flashing is
    not allowed for Critical Partitions
    ')
    fastboot: error: Command failed
    Sending 'devcfg' (52 KB) OKAY [ 0.000s]
    Writing 'devcfg' FAILED (remote: 'Flashing is
    not allowed for Critical Partitions

    And others partitions?