Windows On ARM laptops with EMMC
Similar to #3 but worse.
Those devices have the boot chain on the same EMMC as the OS, akin to android devices. Altering any partition (except windows or efi esp) on those may result in an unrecoverable brick.
Example partition table on Acer Aspire 1
NAME SIZE LABEL PARTLABEL MOUNTP
mmcblk1 58.2G
├─mmcblk1p1 2M modemst1
├─mmcblk1p2 2M modemst2
├─mmcblk1p3 1M fsc
├─mmcblk1p4 2M fsg
├─mmcblk1p5 1M DPP
├─mmcblk1p6 1M SMBIOS
├─mmcblk1p7 1M SSD
├─mmcblk1p8 1M CDT
├─mmcblk1p9 4M XBL
├─mmcblk1p10 1M XBL_CONFIG
├─mmcblk1p11 1M limits
├─mmcblk1p12 1M DDR
├─mmcblk1p13 1M SECDATA
├─mmcblk1p14 1M APDP
├─mmcblk1p15 16M LogFS
├─mmcblk1p16 1M AOP
├─mmcblk1p17 4M TZ
├─mmcblk1p18 1M DEVCFG
├─mmcblk1p19 1M HYP
├─mmcblk1p20 1M QUP
├─mmcblk1p21 2M TZAPPS
├─mmcblk1p22 1M ToolsFv
├─mmcblk1p23 1M ImageFv
├─mmcblk1p24 16M ADSP
├─mmcblk1p25 1M multiimgoem
├─mmcblk1p26 2M PLAT
├─mmcblk1p27 1M SYSFW_VERSION
├─mmcblk1p28 1M EnterpriseFv
├─mmcblk1p29 70M UpdateCapsule
├─mmcblk1p30 120M NHLOS
├─mmcblk1p31 1M BACKUP_DPP
├─mmcblk1p32 1M BACKUP_SMBIOS
├─mmcblk1p33 4M BACKUP_XBL
├─mmcblk1p34 1M BACKUP_XBL_CONFIG
├─mmcblk1p35 1M BACKUP_AOP
├─mmcblk1p36 4M BACKUP_TZ
├─mmcblk1p37 1M BACKUP_DEVCFG
├─mmcblk1p38 1M BACKUP_HYP
├─mmcblk1p39 1M BACKUP_QUP
├─mmcblk1p40 2M BACKUP_TZAPPS
├─mmcblk1p41 1M BACKUP_ToolsFv
├─mmcblk1p42 1M BACKUP_ImageFv
├─mmcblk1p43 16M BACKUP_ADSP
├─mmcblk1p44 2M BACKUP_PLAT
├─mmcblk1p45 1M BACKUP_multiimgoem
├─mmcblk1p46 1M BACKUP_EnterpriseFv
├─mmcblk1p47 260M ESP EFI system partition
├─mmcblk1p48 16M Microsoft reserved partition
├─mmcblk1p49 55.8G Acer Basic data partition
└─mmcblk1p50 1023M Recovery Basic data partition This can probably just be a corner case for android devices install path, the issue is there so it's not missed.
Edited by jenneron