[Samsung Galaxy S7 Guides, News, & Discussion] kevin71246:
Android OS & Everything about it

Engboot kernel write protection seems to be off, so it appears you can use dd to write to normally write protected partitions such as the bootloaders (ex: "dd if=/sdcard/aboot of=/dev/block/sdd10"). In my testing I was successfully "dd" a backed up aboot (secondary bootloader) partition and also write to the modem partition and have it stick [MENTION=7402674]qwewqa[/MENTION]

MBN files: Multi boot binary firmware. Mostly used with Samsung, binary data for storing the device's memory partitions, such as the resources and power manager, secondary boot loader, AP boot loader, and trust zone. Can't just edit, need source then compiling creates mbn files? Info: https://www.quora.com/What-is-mbn-file-format-where-is-it-used https://xdaforums.com/showpost.php?p=29787988&postcount=31

Create MBN: https://xdaforums.com/showpost.php?p=28145975&postcount=198 Moreinfo: https://xdaforums.com/showpost.php?p=28149932&postcount=212

Cook custom ROM: https://xdaforums.com/showthread.php?t=901417

Extract mbn files using unyaffsmbn: https://xdaforums.com/showpost.php?p=6303911&postcount=827

How to get existing versions, eg, bootloader version? (Many versions are in Phone->Settings->About device)

Partitions... needed to be modified(?) [MENTION=7402674]qwewqa[/MENTION] https://xdaforums.com/tmobile-s7-edge/help/potential-to-unlock-bootloader-t3544220

- rpm (Resource and Power Manager / Primary Bootloader) located at /dev/block/sdd1 (/dev/block/bootdevice/by-name/rpm)

- aboot (AP Bootloader / Secondary Bootloader) located at /dev/block/sdd10 (/dev/block/bootdevice/by-name/aboot)

- xbl (Extended Bootloader) located at /dev/block/sdb1 (/dev/block/bootdevice/by-name/xbl)

- ? located at /dev/block/sdc1

- Sdd1 is the primary bootloader

Boot Process [MENTION=7402674]qwewqa[/MENTION]

RPM = Resource and Power Manager = Primary Bootloader

ABoot = AP Bootloader = Secondary Bootloader

I believe the boot process is "RPM > ABoot > boot.img (Main OS)", so both the rpm and aboot file would be needed

Partitions

(Correct? via [MENTION=6914738]silentwind827[/MENTION])

https://xdaforums.com/android/general/info-android-device-partitions-basic-t3586565

https://source.android.com/devices/bootloader/partitions-images

http://davinci-michelangelo-os.com/2017/01/22/edit-init-rc-android/

ls -l /dev/block/bootdevice/by-name/

cat /proc/partitions

/dev/block/sda1 => modemst1

/dev/block/sda2 => modemst2

/dev/block/sda3 => fsc

/dev/block/sda4 => ssd

/dev/block/sda5 => persist

/dev/block/sda6 => efs

/dev/block/sda7 => param

/dev/block/sda8 => misc

/dev/block/sda9 => keystore

/dev/block/sda10 => devcfg

/dev/block/sda11 => frp

/dev/block/sda12 => bota

/dev/block/sda13 => fota

/dev/block/sda14 => persistent [edited]

/dev/block/sda15 => apnhlos

/dev/block/sda16 => modem

/dev/block/sda17 => boot (Kernel, RAMdisk, & boot images get flashed here see link above for details)

/dev/block/sda18 => recovery

/dev/block/sda19 => persdata

/dev/block/sda20 => system

/dev/block/sda21 => cache

/dev/block/sda22 => userdata

/dev/block/sdb1 => xbl

/dev/block/sdd1 => rpm

/dev/block/sdd2 => tz

/dev/block/sdd3 => hyp

/dev/block/sdd4 => fsg

/dev/block/sdd5 => sec

/dev/block/sdd6 => pmic

/dev/block/sdd7 => dsp

/dev/block/sdd8 => dip

/dev/block/sdd9 => mdtp

/dev/block/sdd10 => aboot

/dev/block/sdd11 => devinfo

/dev/block/sdd12 => bluetooth

/dev/block/sdd13 => lksecapp

/dev/block/sdd14 => keymaster

/dev/block/sdd15 => cmnlib

/dev/block/sdd16 => cmnlib64

/dev/block/sdd17 => apdp

/dev/block/sdd18 => msadp

/dev/block/sdd19 => dpo

/dev/block/sdd20 => ddr

/dev/block/sdd21 => pad