Develop Bugs

[Solved] Manual Flash Stock Firmware

How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.

Anutter226 said:
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Click to expand...
Click to collapse
What happens with the flash-all.bat file?

delete

airmaxx23 said:
What happens with the flash-all.bat file?
Click to expand...
Click to collapse
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.

Your fastboot is likely too old and can't read the pixel partitions. Make sure your Google drivers and fastboot files are up to date and try again.
Sent from my Pixel XL using Tapatalk

Anutter226 said:
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Click to expand...
Click to collapse
I have used the flash all script several times and it works flawlessly.

Nevermind..

kiddiosky said:
Nevermind..
Click to expand...
Click to collapse
Mate somehow i too need the manuall commands Did you solved the problem/?

restore fake rom 8.0.10.0.0 gearbest

hi to all:
my phone have a camera problem, some parts are fuzzy
i'm going to return to gearbest under warranty, but i have a problem, the phone comes with a fake rom 8.0.10.0.0, i download oficial global stabale 8.0.3.0, put it on internal memory and update with updater program
and the fuzzy camera is still, i try with other camera apps and same problem
now, i have to restore to original rom because in gearbeset page says:
This Android/Windows device is designed to function specifically with the current Android/Windows OS installed on it. Any alterations such as upgrades, modding with custom ROMs, rooting or flashing the Android device with other firmware will automatically void the device's warranty.
i have restored the phone and the rom is the global stable 8.0.3.0, and i need to restore to 8.0.10.0.0
please, help
thanks in advance

blog.geekbuying.com index.php 2016 11 05 xiaomi-mi-5s-qualcomm-snapdragon-821-miui-8-android-6-0-smartphone-firmware-212277-161105
add slash

thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance

alexilou said:
thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance
Click to expand...
Click to collapse
I don't even know what in archive... I took it from other forum, but it should work. Can you send me a screenshot of file list that you unpacked?

Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )

awaaas said:
Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )
Click to expand...
Click to collapse
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.

Is the page u bought from says the Rom is a custom one? If not it's their problem not yours, as the item is not as described, plus he has malware, so contact paypal, they will help u

BlackJetCat said:
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.
Click to expand...
Click to collapse
Here is what inside the archive:
Code:
Xiaomi Mi 5S Qualcomm Snapdragon 821 MIUI 8 Android 6.0 Smartphone Firmware 212277 161104.rar
│ flash_all.bat
│
└───images
adspso.bin
boot.img
BTFM.bin
cache.img
cmnlib.mbn
cmnlib64.mbn
crclist.txt
cust.img
devcfg.mbn
devinfo.img
dummy.img
emmc_appsboot.mbn
Gboot.img
gpt_backup0.bin
gpt_backup1.bin
gpt_backup2.bin
gpt_backup3.bin
gpt_backup4.bin
gpt_backup5.bin
gpt_both0.bin
gpt_both1.bin
gpt_both2.bin
gpt_both3.bin
gpt_both4.bin
gpt_both5.bin
gpt_empty0.bin
gpt_empty1.bin
gpt_empty2.bin
gpt_empty3.bin
gpt_empty4.bin
gpt_empty5.bin
gpt_main0.bin
gpt_main1.bin
gpt_main2.bin
gpt_main3.bin
gpt_main4.bin
gpt_main5.bin
hyp.mbn
keymaster.mbn
lksecapp.mbn
logo.img
misc.img
NON-HLOS.bin
partition.xml
patch0.xml
patch1.xml
patch2.xml
patch3.xml
patch4.xml
patch5.xml
persist.img
pmic.elf
prog_ufs_firehose_8996_ddr.elf
rawprogram0.xml
rawprogram1.xml
rawprogram2.xml
rawprogram3.xml
rawprogram4.xml
rawprogram5.xml
recovery.img
rpm.mbn
splash.img
system.img
tz.mbn
userdata.img
xbl.elf
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).

awaaas said:
Here is what inside the archive:
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).
Click to expand...
Click to collapse
Users have troubles with EDL sometimes. But now we know that it is the fastboot ROM package)

hi to all:
i don't know...
phone is un fastboot mode, connetcted to pc, open miflash, select path where all +.bin and +. img are extracted, press flash and 1 second elapse, progress bar is green, flash done
but the same rom installed on phone
if i run flash_bat this mesagge appears fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A7" || echo Missmatching image and device
i don't know
thanks for your support

Can L-01 Rawprogram0 from GPT.img file

Hi my friends.
Please I need Your experience.
I have a Can L-01 bricked after install an update wrong rom. So I watch some videos on Youtube and I Found a method to extract Rawprogram0 and patch0 firmware to try unbrick a lg phone.
So I have donloaded a full rom, a bulgarian rom.
So There are a file and three folders
update.app
default
eu
normal.
I used Huawei Extract Firmware to extract firmware from update.app file.
I copied GPT.img File in a folder and I opened it by Qualcomm Premium tool.
I selected all Files, I selected 3GB ram, so i extracted Firmware and Partition.
So i had these files:
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
partition.xml
patch0.xml
rawprogram0.xml
rawprogram0_BLANK.xml
zeros_1sector.bin
zeros_33sectors.bin
In Video, user moved gpt_backup0.bin, gpt_both0.bin, gpt_main0.bin, patch0.xml, rawprogram0.xml in Extracted firmware ro., Then He opened rawprogram0.xml by notepad, and he renamed filename string adding file extension for example sbl1 in sbl1.bin. His files are .bin files, while my files are .img.
How Rename I this file? In .img files? Sometime user in the video change file extension for example a .mbn file in .bin file or modem.bin into NON_HLOS.bin, and He deleted some strings where there are useless file name.
I can't attach link of the original Rawprogram0 and Patch0 xml files in zip archive because I'm new member. Can someone receive this files in PM to check rawprogram file? If I try to flash by Qfil, there's Saharai connect fail
Files Extracted from update.app are these:
ABOOT.img
ABOOT.img.header
AMSS_VER.img
AMSS_VER.img.header
AMSS_VERLIST.img
AMSS_VERLIST.img.header
APDP.img
APDP.img.header
BOOT.img
BOOT.img.header
CACHE.img
CACHE.img.header
CMNLIB.img
CMNLIB.img.header
CMNLIB64.img
CMNLIB64.img.header
CRC.img
CRC.img.header
CUST.img
CUST.img.header
DVCFG.img
DEVCFG.img.header
DSP.img
DSP.img.header
ERECOVERY.img
ERECOVERY.img.header
GPT.img
GPT.img.header
KEYMASTER.img
KEYMASTER.img.header
LKSECAPP.img
LKSECAPP.img.header
MODEM.img
MODEM.img.header
MSADP.img
MSADP.img.header
OEMSBL_VER.img
OEMSBL_VER.img.header
OEMSBL_VERLIST.img
OEMSBL_VERLIST.img.header
RECOVERY.img
RECOVERY.img.header
RPM.img
RPM.img.header
SBL1.img
SBL1.img.header
SHA256RSA.img
SHA256RSA.img.header
SYSTEM.img
SYSTEM.img.header
TZ.img
TZ.img.header
USERDATA.img
USERDATA.img.header
Thanks in advance for help

hello friend , i am with a problem , sound like your ,with a Huawei nova plus with
skynet_t800 said:
Hi my friends.
Please I need Your experience.
I have a Can L-01 bricked after install an update wrong rom. So I watch some videos on Youtube and I Found a method to extract Rawprogram0 and patch0 firmware to try unbrick a lg phone.
So I have donloaded a full rom, a bulgarian rom.
So There are a file and three folders
update.app
default
eu
normal.
I used Huawei Extract Firmware to extract firmware from update.app file.
I copied GPT.img File in a folder and I opened it by Qualcomm Premium tool.
I selected all Files, I selected 3GB ram, so i extracted Firmware and Partition.
So i had these files:
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
partition.xml
patch0.xml
rawprogram0.xml
rawprogram0_BLANK.xml
zeros_1sector.bin
zeros_33sectors.bin
In Video, user moved gpt_backup0.bin, gpt_both0.bin, gpt_main0.bin, patch0.xml, rawprogram0.xml in Extracted firmware ro., Then He opened rawprogram0.xml by notepad, and he renamed filename string adding file extension for example sbl1 in sbl1.bin. His files are .bin files, while my files are .img.
How Rename I this file? In .img files? Sometime user in the video change file extension for example a .mbn file in .bin file or modem.bin into NON_HLOS.bin, and He deleted some strings where there are useless file name.
I can't attach link of the original Rawprogram0 and Patch0 xml files in zip archive because I'm new member. Can someone receive this files in PM to check rawprogram file? If I try to flash by Qfil, there's Saharai connect fail
Files Extracted from update.app are these:
ABOOT.img
ABOOT.img.header
AMSS_VER.img
AMSS_VER.img.header
AMSS_VERLIST.img
AMSS_VERLIST.img.header
APDP.img
APDP.img.header
BOOT.img
BOOT.img.header
CACHE.img
CACHE.img.header
CMNLIB.img
CMNLIB.img.header
CMNLIB64.img
CMNLIB64.img.header
CRC.img
CRC.img.header
CUST.img
CUST.img.header
DVCFG.img
DEVCFG.img.header
DSP.img
DSP.img.header
ERECOVERY.img
ERECOVERY.img.header
GPT.img
GPT.img.header
KEYMASTER.img
KEYMASTER.img.header
LKSECAPP.img
LKSECAPP.img.header
MODEM.img
MODEM.img.header
MSADP.img
MSADP.img.header
OEMSBL_VER.img
OEMSBL_VER.img.header
OEMSBL_VERLIST.img
OEMSBL_VERLIST.img.header
RECOVERY.img
RECOVERY.img.header
RPM.img
RPM.img.header
SBL1.img
SBL1.img.header
SHA256RSA.img
SHA256RSA.img.header
SYSTEM.img
SYSTEM.img.header
TZ.img
TZ.img.header
USERDATA.img
USERDATA.img.header
Thanks in advance for help
Click to expand...
Click to collapse
hello friend i have with same problem with u , i have a huawei nova plus hardbricked , i am trying get the files xml and rawprogrammer do you got sucess ?

No mi friend. I didn't resolve. Sorry
Inviato dal mio Redmi Note 4 utilizzando Tapatalk

do you need the files specific to board rev. in qualcomm do you need the rawprogram0.xml and Patch0 and the loader msm_8xxx.mbn depend your processor model , in the rawprogram0.xml contains the partition schema where appears the non.hlos, boot, system, recovery, an others img

[STOCK][FASTBOOT] Fastboot Flashable Images For OnePlus 7T

Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
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 logo_a logo.img
fastboot flash logo_b logo.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
Credits :
jamflux
Regards,
acervenky

reserved

Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.

RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky

acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.

acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b

RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky

acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?

RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky

acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.

RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?

How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"

cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky

acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.

FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!

I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?

Is this for EU Model?

Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky

Ok that is bad. Wait for EU Version.

for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected

[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12

As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
Massive Update! Someone found a way to recover the phone using EDL Deep Flash Cable.
XDA Thread Link
(Even though I tried it when it happened to me all this time ago and it didn't work, but it does seem to work for few people who used a Black & White cable from AliExpress (maybe there's some hidden tech inside) so give it a try and report, there's also a chance that maybe some devices don't get burned out but simply refuse to boot because voltage is too high, and others might be fried forever, we will see with time I guess. Nonetheless, Good Luck!)
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
Update: Double check Your RAM just in case!
Post #3
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.

ProtoDeVNan0 said:
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
View attachment 5578875
View attachment 5578877
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.
Click to expand...
Click to collapse
This is so F'ing insane

Some extra warnings:
1. OnePlus 8T/9R also has LPDDR4x variant, make sure the variants before flashing.
2. The DDR detection process was artificially killed, stay away from the Magisk modules to keep safe.
3. TWRP is no longer recommended, use OxygenOS modified recovery or other ROM's recovery instead.
4. Flash/Root has huge risks, all operations need to be careful.
OnePlus 8 - LPDDR4x
OnePlus 8 Pro - LPDDR5
OnePlus 8T - LPDDR4x/LPDDR5
OnePlus 9R - LPDDR4x/LPDDR5

Thank you

Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.

Holy ****...
These are the images of IN2025_11_C_OTA_1100
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
product.img
qupfw.img
recovery.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
xbl_config_lp5.img
xbl_lp5.img
And these are the images of 11.0.11.11
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
odm.img
product.img
qupfw.img
recovery.img
reserve.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
Usually i use this script after changing a rom and after using MSM tool.
Code:
fastboot -w
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
If i would have used this with OOS12 i would have bricked my phone on both slots instantly.....
Im so glad that i was sceptical because OOS12 had more .img files compared to OOS11 and i did not use the script.
People need to know this...
Am i right that as long as we stay on OOS11 and dont use anything from OOS12 we are good to go like before?

FYI. This is what I did to kill my phone, link below
"Warning" Total Brick After Flashing Android 12 Beta
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot. I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from...
forum.xda-developers.com

ProfEngr said:
Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.
Click to expand...
Click to collapse
Don't go to 12, it's LAME, Stay on 11, might even consider Samsung over OOS12

Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)

Niekdeg said:
Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)
Click to expand...
Click to collapse
Are you on Android 12 or 11?

nkhater said:
Are you on Android 12 or 11?
Click to expand...
Click to collapse
android 12

Niekdeg said:
android 12
Click to expand...
Click to collapse
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?

Niekdeg said:
android 12
Click to expand...
Click to collapse
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.

nkhater said:
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?
Click to expand...
Click to collapse
i have that but my device isn't there... i have install the driver but noting..

FreshlyBaked 420 said:
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.
Click to expand...
Click to collapse
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same

Niekdeg said:
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same
Click to expand...
Click to collapse
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4

nkhater said:
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Click to expand...
Click to collapse
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so

Niekdeg said:
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so
Click to expand...
Click to collapse
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
here

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
i do but problem is my phone don't boot to edl mode