RPMB - questions

[Jane1]

When I try to read RPMB I receive
Not supported yet ...


What do I wrong?

Next question
I read http://forum.gsmhosting.com/vbb/f672...at-do-2587891/

and there is a text

For the end user, it is enough to know the status of the RPMB partiton in order to select the used eMMC chips that can be put into devices with Exynos CPU line Samsung N8000 (of that require a clean RPMB).

how can I find out the status of RPMB partition?

Thanks

[layder]

Originally Posted by Jane1

When I try to read RPMB I receive
Not supported yet ...


What do I wrong?

Next question
I read http://forum.gsmhosting.com/vbb/f672...at-do-2587891/

and there is a text



how can I find out the status of RPMB partition?

Thanks

please, post screenshot of error

may be you use old software

you need use latest software

[Jane1]

I use eMMC tool suite ver. 1.6.2.0 release date 30.06.2019. Is this the latest version?

In eMMC General tab I choose ROM to access there RPMB ( Protected Data Block) and when I click on Read eMMC, I receive Not supported yet ... in the log window.
Is there any other method for RPMB ?
Thanks

[layder]

eMMC tool shuite have no read RPMB function
use classic software

[layder]

we did not add reading RPMB to eMMC tool shuite, because it carries no practical value

[Jane1]

Thanks for your reply.
I have
EMMC Device Information :
EMMC CID: 450100444134303634013D6D55043582
EMMC CSD: D00F00328F5903FFFFFFFFEF8A404022
EMMC Manufacture : SANDISK , EMMC NAME: DA4064 , HEX: 444134303634 , S/N: 3D6D5504 , rev. 0x01
EMMC Manufacture ID: 0x45 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 3/2018
EMMC ROM 1 (Main User Data) Capacity: 59640 MB (000E8F800000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 309 , Response: Not Clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x00 , width 1bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00


So, does it mean that RPMB is not empty and I can not replace that eMMC with a new eMMC because I can not write RPMB?
Or why is the counter NOT zero?Does it mean the operating systen checks if the eMMC is original?

[layder]

I explained everything quite clearly in the thread: http://forum.gsmhosting.com/vbb/f672...at-do-2587891/

it clearly says that we cannot write RPMB without a key, and it says that the RPMB counter increases when each block is written. RPMB can not be erased - only written with key (and it is increace the counter)

[Jane1]

Thanks for the reply.
So, if the Counter is positive like this
RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 309 , Response: Not Clean
it means CPU wrote to RPMB.
Does it mean that if the Counter is positive , the old eMMC can not be replaced with a new
eMMC, because I can not read the RPMB from the old eMMC and write to RPMB of the new eMMC?

[layder]

Originally Posted by Jane1

Thanks for the reply.
So, if the Counter is positive like this
RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 309 , Response: Not Clean
it means CPU wrote to RPMB.
Does it mean that if the Counter is positive , the old eMMC can not be replaced with a new
eMMC, because I can not read the RPMB from the old eMMC and write to RPMB of the new eMMC?

Some brands/firmware not used PRMB (MTK CPU usally, old devices)
Some brands/firmware not needed Clean RPMB, when eMMC is replaced (some Qualcomm)
Some brands/firmware not started/freezed on boot if RPMB not CLean at new eMMC (Exynos-Samsung)
Some brands/firmware not started/freezed on boot if RPMB no have security info (Xiaomi)

[layder]

UFI team is declared read-writed RPMB area one-two years ago.

Out team can't hack RPMB key at eMMC and replace it to some new

I can't help you more then this

[Jane1]

Thanks for the reply.
But is there any way ,how to know:

if Exynos-Samsung based phone does not start that it is a result of not CLean RPMB problem and not something else? Is there any list such Exynos-Samsung based phones that needs clean RPMB?

if Xiaomi does not start it is security info problem and not something else?

[layder]

Originally Posted by Jane1

Thanks for the reply.
But is there any way ,how to know:

if Exynos-Samsung based phone does not start that it is a result of not CLean RPMB problem and not something else? Is there any list such Exynos-Samsung based phones that needs clean RPMB?

if Xiaomi does not start it is security info problem and not something else?

Yes, most Exynos need clean RPMB when eMMC change (from N8000 and later)
We add info about RPMB status for this

Xiaomi Qualcom bootloader check data at RPMB, and freezed on boot if eMMC change

[galaxycompue]

EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000) Counter: 1175 , Response: Not Clean

or

EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000) Counter: 0 , Response: Maybe not clean

or

EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000) Counter: 0 , Response: Clean

LYDER SIR U GIVE THIS THREE LOG, PLZ CLEAR WHEN I READ ANY LOG AND RPMB SHOW NOT CLEAN, MAYBE NOT CLEAN THEN CAN I USE THIS EMMC OR NOT PLZ CLEAR THIS.

[layder]

Originally Posted by galaxycompue

LYDER SIR U GIVE THIS THREE LOG, PLZ CLEAR WHEN I READ ANY LOG AND RPMB SHOW NOT CLEAN, MAYBE NOT CLEAN THEN CAN I USE THIS EMMC OR NOT PLZ CLEAR THIS.

If the program can determine that RPMB is clean, it writes it. if can’t - it can't

[galaxycompue]

LYDER SIR WHY CPU WRITE DATA IN RPMB PARTITIONS, WHEN U NOT GIVEN LOGS IN OLD VERSION WE HAVE NO IDEA TO CHECK RPMB PARTITION BUT NOW WE ARE WATCHING VERY FEW IC CLEAN OTHERWISE MAXIMUM IC ARE WASTE NO ENOUGH STOCK TO RECOVER HANDSETS I HAVE ONE HANDSET LYF LS-5010 HANG ON LOGO WHEN I TRY TO FLASH IT GIVE ERROR IN LAST SO FINALLY WHEN I CHECK EMMC IT SHOW RPMB NOT CLEAN-

After reconnect, make sure that the size of ROM1 has been changed.

Setting interface to EasyJtag2/E-Socket
Setting bus width to 8 Bit
Setting frequence to 42 MHz
EMMC Device Information :
EMMC CID: 150100463732324D420058BFE00BB251
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: F722MB , HEX: 463732324D42 , S/N: 58BFE00B , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2015
EMMC ROM 1 (Main User Data) Capacity: 7456 MB (0001D2000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 512 KB (000000080000) Counter: 25 , Response: Not Clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
Boot configuration [PARTITION_CONFIG]: 0x38 , Boot from: ROM1 (Main User Area)
Boot Bus Config: 0x00 , width 1bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: F722MB_58BFE00B_20191026_152307.extcsd
EMMC Init completed.

Scanning soft partitions
GPT header is found and is valid
Partition: fsg, [000004000000 - 000004180000], size: 000000180000 (1.50 MB)
Partition: sbl1, [000008000000 - 000008080000], size: 000000080000 (512. KB)
Partition: aboot, [000008080000 - 000008180000], size: 000000100000 (1.00 MB)
Partition: rpm, [000008180000 - 000008200000], size: 000000080000 (512. KB)
Partition: tz, [000008200000 - 000008280000], size: 000000080000 (512. KB)
Partition: hyp, [000008280000 - 000008300000], size: 000000080000 (512. KB)
Partition: pad, [000008300000 - 000008400000], size: 000000100000 (1.00 MB)
Partition: modemst1, [000008400000 - 000008580000], size: 000000180000 (1.50 MB)
Partition: modemst2, [000008580000 - 000008700000], size: 000000180000 (1.50 MB)
Partition: misc, [000008700000 - 000008800000], size: 000000100000 (1.00 MB)
Partition: fsc, [000008800000 - 000008800400], size: 000000000400 (1.00 KB)
Partition: ssd, [000008800400 - 000008802400], size: 000000002000 (8.00 KB)
Partition: splash, [000008802400 - 000009202400], size: 000000A00000 (10.0 MB)
Partition: keystore, [000009202400 - 000009282400], size: 000000080000 (512. KB)
Partition: config, [000009282400 - 000009302400], size: 000000080000 (512. KB)
Partition: oem, [000009302400 - 00000D302400], size: 000004000000 (64.0 MB)
Partition: sbl1bak, [00000D302400 - 00000D382400], size: 000000080000 (512. KB)
Partition: rpmbak, [00000D382400 - 00000D402400], size: 000000080000 (512. KB)
Partition: tzbak, [00000D402400 - 00000D482400], size: 000000080000 (512. KB)
Partition: hypbak, [00000D482400 - 00000D502400], size: 000000080000 (512. KB)
Partition: abootbak, [000010000000 - 000010100000], size: 000000100000 (1.00 MB)
Partition: modem, [000010100000 - 000014100000], size: 000004000000 (64.0 MB)
Partition: DDR, [000014100000 - 000014108000], size: 000000008000 (32.0 KB)
Partition: sec, [000014108000 - 00001410C000], size: 000000004000 (16.0 KB)
Partition: boot, [00001410C000 - 00001610C000], size: 000002000000 (32.0 MB)
Partition: system, [00001610C000 - 00009610C000], size: 000080000000 (2.00 GB)
Partition: persist, [00009610C000 - 00009810C000], size: 000002000000 (32.0 MB)
Partition: cache, [00009810C000 - 0000A810C000], size: 000010000000 (256. MB)
Partition: recovery, [0000A810C000 - 0000AA10C000], size: 000002000000 (32.0 MB)
Partition: userdata, [0000AA10C000 - 0001D1FFBE00], size: 000127EEFE00 (4.62 GB)
GPT header successfully parsed

Get firmware version

Brand = LYF
Manufacturer = JSR
Device = LS-5010
Model = LS-5010
Phone platform = msm8916
CPU Abi = arm64-v8a
Android release = 5.1.1
Firmware version = LYF_LS-5010_01_05_15
Firmware date = Sun May 15 00:31:35 CST 2016



I TRY TO MAKE GP PARTITIONS BUT ALL SAME AS BEFORE THIS IS NEW TROUBLE FOR US TO REPAIR EMMC.