Scribd
Upload
3 views

01-Boot Config

The document outlines the process for writing Boot configuration to an eMMC chip, detailing the necessary extCSD registers and methods for configuration. It describes various methods for writing Boot config, including using extcsd files, predefined options, or manual input, and provides specific instructions for different processor types such as Mediatek, Intel, Qualcomm, Exynos, HiSilicon, SpreadTrum, and Broadcomm. Each processor type has unique requirements and steps for successful device recovery and firmware flashing.

Uploaded by

Greymer acosta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
3 views

01-Boot Config

The document outlines the process for writing Boot configuration to an eMMC chip, detailing the necessary extCSD registers and methods for configuration. It describes various methods for writing Boot config, including using extcsd files, predefined options, or manual input, and provides specific instructions for different processor types such as Mediatek, Intel, Qualcomm, Exynos, HiSilicon, SpreadTrum, and Broadcomm. Each processor type has unique requirements and steps for successful device recovery and firmware flashing.

Uploaded by

Greymer acosta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 5

First and foremost, it is necessary to write Boot config to the eMMC chip.

Boot config is 3 extCSD registers:

1) Boot Partition [179] - a register that indicates which eMMC section the
boot is in for boot

2) Bus Config [177] - bus width data and boot mode

3) H / W Reset Function [162] - RST eMMC output control mode ( if it


should be 0x01 , then it must be set, if it should not be 0x01 - it does not
matter, 0x00, 0x01 or 0x02 ).

There are 4 ways to do this:

1) from an extcsd file saved from the same device;

2) from an extcsd file saved from the same device during eMMC firmware;

3) using predefined options;

4) manually.

Boot configuration [PARTITION_CONFIG: 0x00] No boot partition


configured.

Boot bus config [177]: 0x00, width 1bit, Partition config [179]: 0x00

H / W reset function [RST_N_FUNCTION]: 0x01

where:

Boot configuration:

Partition config [179]: 0x 00 - register value 179;

Boot bus config [177]: 0x 00 - value of the register 177;

H / W reset function [RST_N_FUNCTION]: 0x 01 - the value of the register


162.
From extcsd, you can write Boot config using Repair Extcsd -> Only Boot
config.

For further reduction , use Boot config 0x 48 , 0x 00 , 0x 01then the values


of the registers are 179, 177, 162, respectively.

In order to get a connection with a computer for subsequent device


recovery using computer software for devices based on processors:

1) Mediatek (MTK) ( Boot config: 0x 48 , 0x 00 , 0x 01 )

- for devices based on MT6589 / 8389 processors, check that the sizes of
ROM2 / 3 / RPMB are no more than 2MB, otherwise the microcircuit will not
work (for Samsung microcircuits it is possible to change the size of ROM2 /
3 / RPMB);

- write Boot cfg, and erase eMMC (the device is detected as MTK USB
Port );

or

- write Boot cfg, and write "Preloader" to ROM2 (3) via "Write by vendor"
(the device is defined as MTK Virtual VCOM Port );

or

- write Boot cfg, and write the saved backup ROM2 (3) via "eMMC General"
- "Write ROM" (the device is defined as MTK Virtual VCOM Port ).

In the future, most devices on MTK processors are programmed (flashed)


by the computer through the native FlashTool for MTK.

2) Intel . Intel has devices with a GP1 partition and there are without it. (
Boot config: 0x 00 , 0x 00 , 0x 0x , Boot config: 0x 00 , 0x 06 , 0x 01 )

- create (if necessary) the GP1 partition;

- write Boot cfg, and erase eMMC (the device is defined as a CloverView
Device or another). In this option, in the future, you will need to record
the bootloader using the xfstk utility and then according to the
instructions;
or

- write Boot cfg, create (if necessary) the GP1 partition, and write to
eMMC: ROM2, ROM3, GP1, and at least about 300-500MB of ROM1 backup
for different models. In this version, the device will be able to boot into
DroidBoot , from where it can be flashed with firmware via a computer.

3) Qualcomm , ( Boot config: 0x 00 , 0x 00 , 0x 0x ), (Boot config: 0x 38 , 0x


00 , 0x 01 )

- write Boot cfg, and erase eMMC (the device is detected as HS QD9008
Loader ). For many devices, there are service firmware for QPST in bin /
xml format, with which you can later restore the device.

or

- write Boot cfg, and write part of the firmware (bootloaders, boot,
recovery) via "Write by vendor - Qualcomm / Samsung" to get the device
running in FastBoot / Recovery and then write the firmware to it via a
computer or SD card;

or

- write Boot cfg, and write the beginning of the dump ROM1 (100-500MB),
which contains bootloaders, boot, recovery and other necessary sections
to start the device in FastBoot / Recovery and then write the firmware to it
through a computer or SD card.

4) Exynos , ( Boot config: 0x 48 , 0x 01 , 0x 0x )

- write Boot cfg, and erase eMMC, in the future such a device can only be
restored using a specially prepared SD card for a specific device;

or

- write Boot cfg, and write part of the firmware (bootloaders, boot,
recovery) via "Write by vendor - Samsung" to get a device that starts in
FastBoot / Recoveryand then write firmware to it through a computer or
SD card;

or

- write Boot cfg, write ROM2 and write the beginning of the dump ROM1
(100-500MB), which contains bootloaders, boot, recovery and other
necessary sections to start the device in FastBoot / Recovery and then
write the firmware to it via a computer or SD card .

5) HiSilicon , ( Boot config: 0x 08 , 0x 02 , 0x 01 )

- write Boot cfg, and write part of the firmware (bootloaders, boot,
recovery) via "Write by vendor - HiSilicon" to get a device that starts in
FastBoot / Recoveryand then write firmware to it through a computer or
SD card;

or

- write Boot cfg, write ROM2, the beginning of the dump ROM1 (100-
500MB), which contains bootloaders, boot, recovery and other necessary
sections for starting the device in FastBoot / Recovery and then writing
the firmware to it via a computer or SD card.

6) SpreadTrum , ( Boot config: 0x 08 , 0x 00 , 0x 0x )

- write Boot cfg, and write part or full firmware (bootloaders, boot,
recovery) via "Write by vendor - SpreadTrum" to get a device that starts in
FastBoot / Recoveryand in the future (if a part was recorded), write
firmware to it through the computer;

or

- write Boot cfg, write ROM2 / 3 dumps (containing bootloaders), write


(optional) the beginning of ROM1 dump (100-500MB), which contains boot,
recovery, and other necessary sections for starting the device in Recovery
and later write firmware to it through a computer or SD card.

7) Broadcomm , ( Boot config: 0x 00 , 0x 00 , 0x 0x )

- write Boot cfg, and write part of the firmware (bootloaders, boot,
recovery) via "Write by vendor - Qualcomm / HiSilicon" to get a device that
starts in FastBoot / Recoveryand then write firmware to it through a
computer or SD card;

or

- write Boot cfg, write ROM2 and write the beginning of the dump ROM1
(100-500MB), which contains bootloaders, boot, recovery and other
necessary sections to start the device in FastBoot / Recovery and then
write the firmware to it via a computer or SD card .

You might also like