Payload.bin is a file which contains many imgs(system.img,boot.img...).
you can find some extracted files in: https://github.com/TadiT7/xiaomi_jasmine_dump
Requests:
Windows
Payload Drumper Download Here
Python Download Here
Fastboot Download Here
Bootloader unlocked
Step:
Extract rom zip and get payload.bin
Extract payload_drumper-win64 from zip
Put payload.bin in playload_input folder
Run payload_dumper.exe
Flash imgs using fastboot
For Mi A2:
Code:
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
if you see "invalid sparse file format at header magi" when flashing system and vendor, ignore it and wait.
if you needed root you can flash patched_boot.img
Code:
fastboot boot patch_boot.img
then Download Magisk installer and flash direct again Magisk.
or
Code:
fastboot flash boot_a patch_boot.img
This process take some time.
if you update O to P, frist boot will take long long time, you can force reboot(press 10s power button) to resolve it.
It may take a little time in frist screen.
so i need to copy all the img in to the adb folder for fastboot?
Rohit.ghosh said:
so i need to copy all the img in to the adb folder for fastboot?
Click to expand...
Click to collapse
Yup
I've just uploaded the images.
Here is the link: https://drive.google.com/open?id=1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4
Didn't test myself yet. If someone try it leave some feedback.
What is payload.bin and what will it do ?
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Windows detected virus on payload dumper?
Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
Restart the phone, I have this problem when I install the ROM using MiFlash, the phone only starts after I restart the smartphone. Try it there.
Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
Mine took more than normal, but under 5 minutes I'd say. Maybe it depends on how many things you've installed, idk.
Switch apps lags as hell by the way. Anyone with this problem? It's bothering me a lot.
Saurabhcr7 said:
How much time it will take to boot?
My phone is stuck at bootanimation since half an hour.
Click to expand...
Click to collapse
force reboot can resolve
help!!
I got a message "invalid sparse file format at header magi" in system and vendor images
I download again, use payload and use uploaded images, same error :crying:
in sideload using ota file I got "error in /sideload/packege.zip (status 1)
bootloader is unlocked
sinantuysuz said:
Windows detected virus on payload dumper?
Click to expand...
Click to collapse
yes
Olivatti said:
I got a message "invalid sparse file format at header magi" in system and vendor images
I download again, use payload and use uploaded images, same error :crying:
in sideload using ota file I got "error in /sideload/packege.zip (status 1)
bootloader is unlocked
Click to expand...
Click to collapse
invalid sparse file format at header mag" it is normal, can be continue
No it is normal. Wait for few minutes it will proceed.
is it mandatory to flash both slot?
---------- Post added at 04:51 PM ---------- Previous post was at 04:20 PM ----------
i am getting boot loop
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Hey, where's the link for patched_boot.img?
thanks
Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
Same, I just get bootloops every time.
Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
Same
rasputine said:
Hey, where's the link for patched_boot.img?
thanks
Click to expand...
Click to collapse
I have one here - https://sourceforge.net/projects/xioami/files/Mi A2/
---------- Post added at 01:54 AM ---------- Previous post was at 01:50 AM ----------
Adairo said:
I always ended flashing stock rom trough Mi flash because this method has never worked for me. When I try to flash all images trough fastboot I got the "invalid sparse file format at header magi", ok, if you wait the flash starts, but just after that fastboot is not longer working for me, it doesn't respond to any other comand, not even fastboot reboot so I have to power off my phone and boot again to fastboot, However after flashing all the images my phone just get stuck on "Mi" screen, the bootanimation doesn't even start, this has happened to me every single time I attempt to flash an ota dump, on every single build... any idea of what could be wrong? I've got the same problem on windows 10 and ubuntu 18.04, amdFX6300 8gb ram.
thanks in advance.
Click to expand...
Click to collapse
It will take some time (around 5-7 mins) to complete when flashing system & vendor to both a/b .. after it is done, fastboot will be active again then can proceed to next image flashing.
To make it easier ... make those commands in a single batch file. So after you connect your device to PC in fastboot mode, just run the batch file .. let it do its thing until it finish .. this will take around 30 mins to complete.
EDIT : Sharing my own batch file here if anyone want to try, so you don't need to write each line of fastboot flash *** one after another images.
https://forum.xda-developers.com/showpost.php?p=78123332&postcount=457
Related
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
I mean ... is the October fastboot rom ready to flash with miflash and comes with root?
rulezman said:
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
Click to expand...
Click to collapse
Heard that there are two Oct updates, may I know if yours is the latest?
.15 is the second (latest) October update.
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Can't flash through miui flasher. Is it possible to flash this through recovery?
Are U tested?
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Ind33d said:
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Click to expand...
Click to collapse
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Xyam said:
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Click to expand...
Click to collapse
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Ind33d said:
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Click to expand...
Click to collapse
Yup
i lost my wlan mac adress by flashing this, im flashing again now without without_data
anyone ever seen that problem?
nvm, the 3rd time it worked
9.6.16 is out can you provide fastboot archive?
hugopg said:
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Click to expand...
Click to collapse
I researched for such a long time on this, I'm exactly the same in your situation, rooted with magisk, camera2api substratum things like that on august patch.
Later on i figured myself a way to update without losing any data or wiping the phone which is :
1. download the full stock rom of august patch, it should be tgz files, extract it.
2. Make sure u got adb fastboot all the stuff installed on pc, and also mi a2 drivers.
3. On the phone, go to developer options and turn on usb debugging, guess u already done it since you rooted the phone.
4 now connect the phone to pc in fastboot mode.
5. After extract the tgz august stock rom, locate to folder "image".
6. Hold shift and right click open cmd or in my case open windows power shell.
7. Type fastboot devices to see if your phone is connected properly.
8. Paste these codes and hit enter.
9. After that the phone will be rebooted and after success booting go to settings > system update and start installing the ota without issues.
The codes :
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
Guess that every patches on mi a2 will work with thus method, haven't tested with any version other than august patch. Let me know if it's work !
pani690 said:
Can't flash through miui flasher. Is it possible to flash this through recovery?
Click to expand...
Click to collapse
Search google for mi a2 manually flash firmware.
The result that said "techdroider.com" will be the answer you looking for.
If you don't want to lose any data but still wanna update, remove line "fastboot....userdata.img"
No November update?
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
Flie link not exist plz give working link
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 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
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.
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Hi guys, i'm here again to ask for your support, actually with android 10 Google introduced a lot of changing, from dynamic partitions to the new keymaster 4 encryption/decryption. Teamwin is working hard to update TWRP but they will still take some time. Currently some things already work but there are difficulties in bringing them to the OnePlus 8/8 Pro, for example decryption already works but creates some problems on the OnePlus devices. That's why I decided to create a Paypal moneybox to be able to bring you the latest updates in the shortest time possible. As I have previously done, I assure you of a support of at least 2 years (within the limits of my possibilities). In addition to the TWRP I will improve the fastboot roms and add OnePlus 8/8 Pro to my TOOL ALL IN ONE (and maybe I will also bring the RevengeOS). By getting hold of a OnePlus 8 or 8 Pro I will also be able to improve the TWRP for OnePlus 7T and 7T Pro.
OnePlus 8/8 Pro PayPal MoneyBox: https://www.paypal.com/pools/c/8pfrIOL3Qa
If you are unable to participate in the PayPal moneybox, you can make a normal donation (perhaps specifying that it is for the moneybox), however all private donations that I will receive for this or other projects will be included in the moneybox.
Private PayPal Donations: https://www.paypal.me/MauronofrioTool
Why after flash it, it boot up to Qualcomm crashdump mode and how to fix?
sakun-ice said:
Branded devices is for example a Chinese version with HydrogenOS to which OxigenOS has been installed? If so, how can a branded device be recovered?
Thanks
Click to expand...
Click to collapse
I think unbranded devices mean the device bought from T-Mobile or Verizon. Nothing to do with chinese versiion flash oxygenOS, if I'm not wrong.
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Does anyone know where to find mobile oneplus 8 5g tmobile from mine is bricked I had same error as post above
KJStar said:
Can't seem to get this to work. I'm trying to flash a stock rom for my OnePlus 8 after bricking it during a rooting process.
The device' bootloader is obviously unlocked and i can get the phone into Fastboot mode and connected to my PC.
The only issue is when i execute the flash-all.bat file, it can't seem to flash any of the files and gives an error consisting of the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions').
What to do guys? Can anyone help me out.
Click to expand...
Click to collapse
Try to flash fastboot rom with "tool all in one),It worked for me.
I needed modem I forgot to fastboot reboot fastboot guy in post 6 that's all you need to do is reboot fastboot then flash all I was looking for different file
Never mind I fixed it by downloading ota and going to system updates in settings because fastboot won't flash to modem right
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
bluemoel said:
I am having issues flashing. flashing not allowed on critical partition. please help I tried to use the large address aware program but nothing has changed.
Click to expand...
Click to collapse
Make sure your on the latest update: 10.5.8
mauronofrio said:
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 8 in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8
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.
Click to expand...
Click to collapse
Hi, do you know if patching with local update a Oxygen OS Europe release from a Global release may cause problems to the fingerprint? I have a IN2010 with the Global OxygenOS but I would like to switch to the European versione becasue I live in Italy like you
Why not flash reserve.img?
nnyd said:
Why not flash reserve.img?
Click to expand...
Click to collapse
Because it is placed in userdata and not in a dedicated partition
I have an issue trying to flash on fastboot. It's says I can't flash on critical partitions. Yes I know alot of people are saying that but what I haven't seen is this:
This is my problem:
Fastboot get device-info
(Bootloader) device unlocked:true
(Bootloader) device critical unlock: false
(Bootloader) charger screen enabled: true
I have already tried "fastboot flashing unlock_critical"
It says bootloader already unlocked. I then re lock bootloader which I know is not a good idea( reflash stock with msm tool) and it lock then I try unlock critical command again and it still says device critical unlock: false
i need help please ..
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Alucardo1 said:
i tried this method not the latest version i tried the 10.5.4 global
so it gave me all failed and error to foramt and others
then it restart my phone to show me crashdump
what should i do ?
should i use latest version ?
i hope you replay fast .. thank you
Click to expand...
Click to collapse
Try again with 10.5.7. When it reboot to recovery, let it continue to run till it reboots on its own.
Unbrick from fastboot method
I hope I can help someone since I spent the whole night trying various methods to unbrick my Oneplus 8 and only this one worked for me JUST FOR INTERNATIONAL VERSION
You must have the drivers installed (Adb & Fastboot)
You must have your phone with the bootloader unlocked
1.- Download the file
2.-Unzip it
inside you will find Flash-all.bat
3.-Enter Fastboot mode
4.-Double click on the Flash-all.bat command
5.-It will direct you to the recovery, select the English language and restart in fastboot mode so that the process continues, wait for it to finish flashing everything and ready, the phone restarts on the latest version
https://mega.nz/folder/8tpUSSrR#7wH4NX_ccr2a6Ub8LXpsEA
Donate Link to support my work
https://paypal.me/pakomorales?locale.x=es_XC
cannot relock bootloader on oneplus 8
bro thanks for fastboot room for oneplus 8,i flash your fastboot room 10.5.9 everthing ok,but i relocked to boot loader it the phone be correpted. what should i do ,
please help me.
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.
Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot
Download any ROM you want. Extract the payload and put it in the payload input folder.
jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause
wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.
Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated
I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.
Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Reserved.
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.
You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)
Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse
MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.