[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions - OnePlus 8 Questions & Answers

I messed up trying to install TWRP on c.17 OOS12
Now the mobile is bricked.
1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device.
2. I tried the ALL IN ON TOOL, but getting "UNHANDLED EXCEPTION has occured in your application" error
Tried the FASTBOOT ROM, but i am getting "'Flashing is not allowed for Critical Partitions" below is the complete log
Please Help
11.0.0-INDIA-OnePlus8Oxygen_15.I.30_FASTBOOT> .\flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.110s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 211034776 (103044 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600
Info: Overprovision ratio = 0.620%
Info: Overprovision segments = 646 (GC reserved = 330)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.008s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.001s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 16.812s
Sending 'boot_b' (98304 KB) OKAY [ 2.313s]
Writing 'boot_b' OKAY [ 0.601s]
Finished. Total time: 3.202s
Sending 'dtbo' (8192 KB) OKAY [ 0.301s]
Writing 'dtbo' OKAY [ 0.031s]
Finished. Total time: 0.383s
Sending 'modem_b' (234332 KB) OKAY [ 5.439s]
Writing 'modem_b' OKAY [ 1.159s]
Finished. Total time: 7.298s
Sending 'recovery' (102400 KB) OKAY [ 2.377s]
Writing 'recovery' OKAY [ 0.664s]
Finished. Total time: 3.368s
Sending 'vbmeta' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.041s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_system' OKAY [ 0.007s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1996 KB) OKAY [ 0.049s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.011s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (652 KB) OKAY [ 0.020s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.013s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.007s]
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.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.389s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'featenabler' (88 KB) OKAY [ 0.005s]
Writing 'featenabler' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (436 KB) OKAY [ 0.001s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.002s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (252 KB) OKAY [ 0.007s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'logo' (7780 KB) OKAY [ 0.182s]
Writing 'logo' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'mdm_oem_stanvbk' (3776 KB) OKAY [ 0.082s]
Writing 'mdm_oem_stanvbk' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'multiimgoem' (16 KB) OKAY [ 0.017s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'odm' (42716 KB) OKAY [ 0.924s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
fastboot: error: cannot load 'opproduct.img': No such file or directory
Sending 'qupfw' (56 KB) OKAY [ 0.008s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'spunvm' (348 KB) OKAY [ 0.013s]
Writing 'spunvm' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'storsec' (20 KB) OKAY [ 0.012s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'tz' (3096 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.000s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3404 KB) OKAY [ 0.082s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (96 KB) OKAY [ 0.006s]
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/2 (786300 KB) OKAY [ 17.603s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (786249 KB) OKAY [ 17.529s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (786356 KB) OKAY [ 18.018s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Press any key to continue . . .
Click to expand...
Click to collapse

Flash in fastbootd. Flash a recovery that has it, and then do "fastboot reboot recovery".

Xryphon said:
Flash in fastbootd. Flash a recovery that has it, and then do "fastboot reboot recovery".
Click to expand...
Click to collapse
I wasnt aware of fastbootd, can you direct me to a post or link ?
My device luckily got rectified. The MSM tool detected the deivce after the above FASTBOOT rom failure. Looks like though some partitions were not programmed, atleast the one that needed for the MSM tool to work were loaded.
However i do need to look into your suggestion about fastbootd

The "flashing is not allowed for critical partitions" issue is a driver problem. I spent hours trying to flash a fastboot rom and didn't even think to try updating the driver. This post from SilverZero led me to download the drivers from this post by FoxyDrew. This fixed the problem of not being allowed to flash critical partitions. Everything worked swimmingly after that.

Thank you so much @TalionDread !!! You are a savior! I wasn't able to convert my IN2017 to Global for the past year. I tried all the approaches but was getting "Flashing is not allowed for critical partitions". I read the posts that you mentioned and I finally see the OP boot up screen rather than TMO one! Thank you so much!

Are you getting 5G on any other carrier besides t-mobile? I'm trying to find out if I can flash the global ROM which makes the phone look for 5G from other towers besides T-Mobile I'm still on the T-Mobile version I can edit the carrier policy and make it do that but I would rather go to the global version and just have it done for me can you tell me if you're getting true 5G unlike Verizon after you flash the rom.
Because the phone has all the bands and the radios as the regular OnePlus so there should be no problem about picking up the 5G but the phone itself is not physically looking for 5G from Verizon's towers it's only looking for them for T-Mobile's towers so when you edit the carrier policy you make it look at all the towers of the bands it has of what carrier you're using and then it ends up working so I'm just curious if the global round also does this if it programs a global carrier policy.
iaggarwal said:
Thank you so much @TalionDread !!! You are a savior! I wasn't able to convert my IN2017 to Global for the past year. I tried all the approaches but was getting "Flashing is not allowed for critical partitions". I read the posts that you mentioned and I finally see the OP boot up screen rather than TMO one! Thank you so much!
Click to expand...
Click to collapse

intheb0x said:
Are you getting 5G on any other carrier besides t-mobile? I'm trying to find out if I can flash the global ROM which makes the phone look for 5G from other towers besides T-Mobile I'm still on the T-Mobile version I can edit the carrier policy and make it do that but I would rather go to the global version and just have it done for me can you tell me if you're getting true 5G unlike Verizon after you flash the rom.
Because the phone has all the bands and the radios as the regular OnePlus so there should be no problem about picking up the 5G but the phone itself is not physically looking for 5G from Verizon's towers it's only looking for them for T-Mobile's towers so when you edit the carrier policy you make it look at all the towers of the bands it has of what carrier you're using and then it ends up working so I'm just curious if the global round also does this if it programs a global carrier policy.
Click to expand...
Click to collapse
=

intheb0x said:
Are you getting 5G on any other carrier besides t-mobile? I'm trying to find out if I can flash the global ROM which makes the phone look for 5G from other towers besides T-Mobile I'm still on the T-Mobile version I can edit the carrier policy and make it do that but I would rather go to the global version and just have it done for me can you tell me if you're getting true 5G unlike Verizon after you flash the rom.
Because the phone has all the bands and the radios as the regular OnePlus so there should be no problem about picking up the 5G but the phone itself is not physically looking for 5G from Verizon's towers it's only looking for them for T-Mobile's towers so when you edit the carrier policy you make it look at all the towers of the bands it has of what carrier you're using and then it ends up working so I'm just curious if the global round also does this if it programs a global carrier policy.
Click to expand...
Click to collapse
Hey @intheb0x,
I recently realized that I'm not getting any signal on the converted OP8, let alone T-mobile one XD. I came back to this thread to see if I did something wrong. I'll get back to you once I successfully get all the networks. Just to let you know, when I was on TMO earlier, I unlocked the bootloader and after that I could get all the networks just fine. I was using Mint Mobile and got its 5G properly, if that helps.
@FoxyDrew,
Do you have any idea what could have gone wrone in coversion? I was thinking of going to android 11 and hoping it to rectify this situation, would this be a correct approach?

Related

Hate to be the type of guy to beg, but please help me fix my bricked phone...I've been trying for 5 hours now to fix it.

Basically, I tried installing Pixel Experience and in the end, ended up completely wiping everything.
Things I can do:
Flash TWRP
Get into Fastboot
Get into EDL/Crashdump
Things that don't work:
I tried flashing a stock ROM through FastBoot, and didn't work, got the following:
Spoiler
C:\Users\bstei\Downloads\adb>fastboot flash aop aop.img
Sending 'aop' (200 KB) OKAY [ 0.013s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash bluetooth bluetooth.img
Sending 'bluetooth' (652 KB) OKAY [ 0.026s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.854s]
Writing 'boot_a' OKAY [ 0.241s]
Finished. Total time: 3.819s
C:\Users\bstei\Downloads\adb>fastboot flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 1.946s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.029s]
Finished. Total time: 0.291s
C:\Users\bstei\Downloads\adb>fastboot flash LOGO LOGO.img
Sending 'LOGO' (7780 KB) OKAY [ 0.244s]
Writing 'LOGO' FAILED (remote: '(LOGO_a) No such partition')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash modem modem.img
Sending 'modem_a' (240188 KB) OKAY [ 7.226s]
Writing 'modem_a' OKAY [ 0.846s]
Finished. Total time: 8.094s
C:\Users\bstei\Downloads\adb>fastboot flash oem_stanvbk oem_stanvbk.img
fastboot: error: cannot load 'oem_stanvbk.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot flash qupfw qupfw.img
Sending 'qupfw' (56 KB) OKAY [ 0.009s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash storsec storsec.img
Sending 'storsec' (20 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash multiimgoem multiimgoem.img
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (124 KB) OKAY [ 0.005s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.073s]
Writing 'recovery' OKAY [ 0.294s]
Finished. Total time: 3.380s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.020s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.030s
C:\Users\bstei\Downloads\adb>fastboot flash opproduct opproduct.img
fastboot: error: cannot load 'opproduct.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
Tried using the MSM unbrick tool but every single time I tried to use it, I get the Sahara Communications failed. I tried on two different computers with two different USB cords, one Intel based and one AMD based.
Guys, please help me, you're my last hope.
HorseyMD said:
Basically, I tried installing Pixel Experience and in the end, ended up completely wiping everything.
Things I can do:
Flash TWRP
Get into Fastboot
Get into EDL/Crashdump
Things that don't work:
I tried flashing a stock ROM through FastBoot, and didn't work, got the following:
Spoiler
C:\Users\bstei\Downloads\adb>fastboot flash aop aop.img
Sending 'aop' (200 KB) OKAY [ 0.013s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash bluetooth bluetooth.img
Sending 'bluetooth' (652 KB) OKAY [ 0.026s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.854s]
Writing 'boot_a' OKAY [ 0.241s]
Finished. Total time: 3.819s
C:\Users\bstei\Downloads\adb>fastboot flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 1.946s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.029s]
Finished. Total time: 0.291s
C:\Users\bstei\Downloads\adb>fastboot flash LOGO LOGO.img
Sending 'LOGO' (7780 KB) OKAY [ 0.244s]
Writing 'LOGO' FAILED (remote: '(LOGO_a) No such partition')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash modem modem.img
Sending 'modem_a' (240188 KB) OKAY [ 7.226s]
Writing 'modem_a' OKAY [ 0.846s]
Finished. Total time: 8.094s
C:\Users\bstei\Downloads\adb>fastboot flash oem_stanvbk oem_stanvbk.img
fastboot: error: cannot load 'oem_stanvbk.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot flash qupfw qupfw.img
Sending 'qupfw' (56 KB) OKAY [ 0.009s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash storsec storsec.img
Sending 'storsec' (20 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash multiimgoem multiimgoem.img
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (124 KB) OKAY [ 0.005s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.073s]
Writing 'recovery' OKAY [ 0.294s]
Finished. Total time: 3.380s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.020s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.030s
C:\Users\bstei\Downloads\adb>fastboot flash opproduct opproduct.img
fastboot: error: cannot load 'opproduct.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
Tried using the MSM unbrick tool but every single time I tried to use it, I get the Sahara Communications failed. I tried on two different computers with two different USB cords, one Intel based and one AMD based.
Guys, please help me, you're my last hope.
Click to expand...
Click to collapse
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
If I remember correctly, I tried both, but I'll go try again
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
Seems like I've gotten further this time, as it seems to be attempting to boot into Pixel Experience. How exactly do I get into FastbootD as opposed to normal fastboot?
EDIT: IT WORKS! YOU'RE A LIFESAVER
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
Thank you so much for the help, the successful flashing of at least a few images seems to have made the MSM tool work, right now it's booting up, hoping it will be successful...we'll see here in a second, I guess...
IT WORKED!!!!!

FB not flashing one these

hi
its op8 os12 when ever i try FB os12 rom to flash i always get bootload and not flashing these files only
even device is in FBD mode
Code:
Writing 'my_bigball_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_carrier_b my_carrier.img
Sending 'my_carrier_b' (340 KB) OKAY [ 0.000s]
Writing 'my_carrier_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_company_b my_company.img
Sending 'my_company_b' (328 KB) OKAY [ 0.016s]
Writing 'my_company_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_engineering_b my_engineering.img
Sending 'my_engineering_b' (328 KB) OKAY [ 0.016s]
Writing 'my_engineering_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

soft bricked oneplus nord

when i flashed a boot image patched by magisk, i got a boot loop and dont know how to get out of it, i tried to reinstall an older version of oxygenOS, through the sdk tools (fastboot) but there i get a bunch of errors like "FAILED (remote: 'Partition not found') " and "FAILED (remote: 'Flashing is not allowed for Critical Partitions." can anyone help?
Code:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.159s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
D:\Downloads\platform-tools_r33.0.3-windows/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Sending 'boot_b' (98304 KB) OKAY [ 2.107s]
Writing 'boot_b' OKAY [ 0.548s]
Finished. Total time: 2.669s
Sending 'dtbo' (8192 KB) OKAY [ 0.183s]
Writing 'dtbo' OKAY [ 0.028s]
Finished. Total time: 0.222s
Sending 'modem_b' (153804 KB) OKAY [ 3.336s]
Writing 'modem_b' OKAY [ 0.642s]
Finished. Total time: 3.991s
Sending 'recovery' (102400 KB) OKAY [ 2.200s]
Writing 'recovery' OKAY [ 0.486s]
Finished. Total time: 2.696s
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.016s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.025s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (192 KB) OKAY [ 0.012s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (220 KB) OKAY [ 0.011s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'devcfg' (44 KB) OKAY [ 0.003s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.407s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'featenabler' (88 KB) OKAY [ 0.004s]
Writing 'featenabler' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (404 KB) OKAY [ 0.012s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (524 KB) OKAY [ 0.022s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (232 KB) OKAY [ 0.011s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'logo' (6532 KB) OKAY [ 0.151s]
Writing 'logo' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2108 KB) OKAY [ 0.051s]
Writing 'oem_stanvbk' OKAY [ 0.012s]
Finished. Total time: 0.074s
Sending 'odm' (916 KB) OKAY [ 0.028s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Sending 'qupfw' (56 KB) OKAY [ 0.009s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3104 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3256 KB) OKAY [ 0.077s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (80 KB) OKAY [ 0.011s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending sparse 'system' 1/3 (782171 KB) OKAY [ 16.926s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'vendor' 1/2 (784607 KB) OKAY [ 17.020s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (784643 KB) OKAY [ 16.892s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
Press any key to continue . . .
you have the same problem like me, you cant manage to get into FastbootD mode, thats whats supposed to happen in the first restart, but theres an error

Oneplus 8 IN2017 Error while flashing Global rom.

I got this error while flashing global rom in oneplus 8 In2017. Please assist me.
I unlocked the bootloader and just press flash-all file in Global rom file and now my phone is stuck in Fastmode and this error occurs in windows 11 pc. SDK tools are up-to-date, fastboot version is 33.03 I just downloaded them from their official site.
I also tried:
fastboot flashing unlock
fastboot flashing unlock_critical
but it said ,Device Already: Unlocked
Please help me otherwise I'll lost my device.
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.117s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\khateeb\Desktop\G-Rom Flash Oneplus 8 5G\10.5.12-GLOBAL-OnePlus8Oxygen_15.O.21_OTA_021_all_2008080054_906daa239-FASTBOOT/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Sending 'boot_a' (98304 KB) OKAY [ 3.290s]
Writing 'boot_a' OKAY [ 0.518s]
Finished. Total time: 3.871s
Sending 'dtbo' (8192 KB) OKAY [ 0.276s]
Writing 'dtbo' OKAY [ 0.025s]
Finished. Total time: 0.350s
Sending 'modem_a' (524288 KB) OKAY [ 17.560s]
Writing 'modem_a' OKAY [ 2.063s]
Finished. Total time: 19.678s
Sending 'recovery' (102400 KB) OKAY [ 3.386s]
Writing 'recovery' OKAY [ 0.337s]
Finished. Total time: 3.767s
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.059s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.008s]
Finished. Total time: 0.075s
current-slot: a
Finished. Total time: 0.010s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1996 KB) OKAY [ 0.070s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.009s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (460 KB) OKAY [ 0.022s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'devcfg' (48 KB) OKAY [ 0.004s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.117s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'featenabler' (88 KB) OKAY [ 0.011s]
Writing 'featenabler' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (436 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.009s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.018s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'logo' (7784 KB) OKAY [ 0.233s]
Writing 'logo' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'mdm_oem_stanvbk' (3776 KB) OKAY [ 0.118s]
Writing 'mdm_oem_stanvbk' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'multiimgoem' (16 KB) OKAY [ 0.012s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'odm' (960 KB) OKAY [ 0.032s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'opproduct' (48828 KB) OKAY [ 1.580s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'qupfw' (56 KB) OKAY [ 0.010s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'spunvm' (348 KB) OKAY [ 0.013s]
Writing 'spunvm' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3236 KB) OKAY [ 0.120s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3392 KB) OKAY [ 0.116s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (96 KB) OKAY [ 0.007s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Khateeb2110 said:
I got this error while flashing global rom in oneplus 8 In2017. Please assist me.
I unlocked the bootloader and just press flash-all file in Global rom file and now my phone is stuck in Fastmode and this error occurs in windows 11 pc. SDK tools are up-to-date, fastboot version is 33.03 I just downloaded them from their official site.
Click to expand...
Click to collapse
You are a candidate for the MSM Tool to revert back to stock.
-- Did you follow this guide to alleviate the pain of converting to Global?
rodken said:
You are a candidate for the MSM Tool to revert back to stock.
-- Did you follow this guide to alleviate the pain of converting to Global?
Click to expand...
Click to collapse
Yes similar procedure , I got bootloader unlock token from oneplus site.
then I just unlocked the bootloader and run flash-all file in Global rom folder. Then I got this error.
then I tried :
fastboot flashing unlock
fastboot flashing unlock_critical
It said that device is unlocked but still facing this error.
I think that error is from this command:
fastboot reboot fastboot
I got this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
after that no more commands are able to run properly.
Khateeb2110 said:
I think that error is from this command:
fastboot reboot fastboot
I got this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
after that no more commands are able to run properly.
Click to expand...
Click to collapse
Try to avoid using the flash-all bat file. Run each command separately and switch slots to see if you hit paydirt.
rodken said:
Try to avoid using the flash-all bat file. Run each command separately and switch slots to see if you hit paydirt.
Click to expand...
Click to collapse
what do you mean by switching slots?
Khateeb2110 said:
what do you mean by switching slots?
Click to expand...
Click to collapse
How to manually switch the active slot - link.
rodken said:
How to manually switch the active slot - link.
Click to expand...
Click to collapse
Thankyou so much bro that error got solved but now getting a new error:
Writing 'product' FAILED (remote: 'No such file or directory')
i rechecked the file name also tried by dragg in drop but still not working.
Khateeb2110 said:
Thankyou so much bro that error got solved but now getting a new error:
Writing 'product' FAILED (remote: 'No such file or directory')
i rechecked the file name also tried by dragg in drop but still not working.
Click to expand...
Click to collapse
In some cases, you might need a high-end USC-C cable or reinstall your ADB drivers from a different source.
rodken said:
In some cases, you might need a high-end USC-C cable or reinstall your ADB drivers from a different source.
Click to expand...
Click to collapse
I'm using original cable of oneplus 8 and also downloaded sdk tools from official android site and also tried from some other sites. but still getting this error at last step of flashing rom.
Khateeb2110 said:
I'm using original cable of oneplus 8 and also downloaded sdk tools from official android site and also tried from some other sites. but still getting this error at last step of flashing rom.
Click to expand...
Click to collapse
Is there a reason as to why you haven't skipped the last step to see if the device will boot?
Ye
rodken said:
Is there a reason as to why you haven't skipped the last step to see if the device will
Click to expand...
Click to collapse
Yeah! I tried once but it goes to Qualcomm CrashDump Mode.
Khateeb2110 said:
Ye
Yeah! I tried once but it goes to Qualcomm CrashDump Mode.
Click to expand...
Click to collapse
It's clearly the ROM that you are flashing.
-- Are you in FastbootD mode when flashing?
rodken said:
It's clearly the ROM that you are flashing.
-- Are you in FastbootD mode when flashing?
Click to expand...
Click to collapse
Yes when I run:
fastboot reboot fastboot
My phone reboots and open in fastbootd mode. and fastbootd is written on the top of phone. so i'm sure about that.
I also tried by installing Indian version. but it also got the same error.
All the files got flashed successfully. but at the end the :
fastboot flash product product.img
is not working properly.
Khateeb2110 said:
All the files got flashed successfully. but at the end the :
fastboot flash product product.img
is not working properly.
Click to expand...
Click to collapse
Indication points to the fact that the ROM is somewhat corrupted.
Have you tried to run the commands in Fastboot mode and not FastbootD mode?
When I tried this in fast boot it said "no such partition". but when i flash in fastbootd mode it said "no such file or directory".
Khateeb2110 said:
When I tried this in fast boot it said "no such partition". but when i flash in fastbootd mode it said "no such file or directory".
Click to expand...
Click to collapse
Wondering if the flash-all file within in the Global ROM folder corrupted a file or two.
So you are saying that the files are corrupted???
Khateeb2110 said:
So you are saying that the files are corrupted???
Click to expand...
Click to collapse
Just the file that is seeming to be a problem child in 'writing'.
-- Bear in mind that not all ROMs are created equal regarding stability even after downloading it and flashing it.
-- Have you seen this thread as of yet?
rodken said:
Just the file that is seeming to be a problem child in 'writing'.
-- Bear in mind that not all ROMs are created equal regarding stability even after downloading it and flashing it.
-- Have you seen this thread as of yet?
Click to expand...
Click to collapse
I tried by changing Rom file global and indian but both are showing same error.
Brother Now I switched the slot and used the latest global rom. All files are flashed successfully but phone is not booting, when I turn on the phone it opens in fastboot mode. Any solution.
Khateeb2110 said:
Brother Now I switched the slot and used the latest global rom. All files are flashed successfully but phone is not booting, when I turn on the phone it opens in fastboot mode. Any solution.
Click to expand...
Click to collapse
Have you tried to redownload the ROM and try again?

Flashing indian rom Fastboot Error: Writing 'product' FAILED (remote: 'No such file or directory')

Please assist me, got stuck at last step.
Oneplus 8 In2017 converting t mobile to indian version
fastboot flash product product.img
Invalid sparse file format at header magic
Sending sparse 'product' 1/6 (261800 KB) OKAY [ 9.148s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Categories

Resources