[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions

Search This thread

firoz3321

Senior Member
Apr 30, 2011
590
47
Hyderabad
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 . . .
 

firoz3321

Senior Member
Apr 30, 2011
590
47
Hyderabad
Flash in fastbootd. Flash a recovery that has it, and then do "fastboot reboot recovery".

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
 

TalionDread

Senior Member
Oct 3, 2012
76
26
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Flash in fastbootd. Flash a recovery that has it, and then do "fastboot reboot recovery".