GSM-Forum
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

GSM-Forum (https://forum.gsmhosting.com/vbb/)
-   Easy-Jtag / Easy-Jtag Plus (https://forum.gsmhosting.com/vbb/f672/)
-   -   redmi note 3 encryption unsuccessfull (https://forum.gsmhosting.com/vbb/f672/redmi-note-3-encryption-unsuccessfull-2504232/)

Bhagat20 11-07-2018 11:04
redmi note 3 encryption unsuccessfull
 
redmi note 3 (kenzo) encryption unsuccessfull, i flashed with mi flashtool but still same problem, i connected phone to easy jtag isp pinout but everytime getting below error:

Looking for EasyJTAG box...
EasyJTAG API ver. 2022
EasyJTAG Box Serial = 026862FABF5A25EA
Card Serial = AA0B-B341
EasyJTAG Box Firmware = 2.30

Changelog:

12.12.2017 (ver 1.4.9.0)
Fix: Bugs that have been found through your crash report
Fix: RandomVerify function
Fix: Creation of GPT for Samsung (write by vendor)
Fix: Failed to mount large Fat partitions (explorer)
Fix: Extraction from contact2.db (explorer)
Fix: Error in the "build.prop" parser
Fix: CID Parser
Add: Support for EasyJtag Plus Box
Add: Path for TempDir and InitialDir (option in settings)
Add: Unpack Lenovo QSB (utilities)
Add: Selecting a PIT file from CSC (write by vendor Samsung)
Add: Detect for encrypted dumps from GPG Box
Add: Detect for FullDiskEncryption Partition (explorer)
Add: LinearVerify of the Partition (read by vendor)
Add: Information base about emmc compatibility (thanks to phonemicrodb)
Add: Resizing the window (for small screen resolutions)
Add: Converting large partitions in SparseImage when reading by vendor (option in settings)
Add: Mounting SparseImage (explorer)
Add: Automatic backup of the EFS partition for Samsung (read by vendor)
Add: Formatting of EFS partition for Samsung on request (write by vendor)

Setting interface to EasyJtag2/ISP_HiPower
Setting bus width to 1 Bit
HiPower mode is ON
Setting frequence to 24 Mhz
CMD Pullup Level: 1804 mV
CMD Active Level: 2580 mV
Can't init device. Reason: CMD CRC Error

classic suite:

Z3X EasyJtag Software ver. 3.1.0.0
Loading eMMC GEN2 Firmware... IO: 3300 mV
Box S/N: 026862FABF5A25EA, ,FW Ver.: 02.30
CMD Pullup Level:1804 mV
CMD Active Level:2576 mV
Box IO Level:3300 mV
CLK Rate:36000 kHz
Bus Width:1bit,SDR
HiPower mode is ON!
Can't init device, Reason: CMD CRC Error
Done.

please suggest what is the problem?

layder 11-07-2018 16:24
Quote:
Originally Posted by Bhagat20 (Post 13402447)
redmi note 3 (kenzo) encryption unsuccessfull, i flashed with mi flashtool but still same problem, i connected phone to easy jtag isp pinout but everytime getting below error:

Setting interface to EasyJtag2/ISP_HiPower
Setting bus width to 1 Bit
HiPower mode is ON
Setting frequence to 24 Mhz
CMD Pullup Level: 1804 mV
CMD Active Level: 2580 mV
Can't init device. Reason: CMD CRC Error

please suggest what is the problem?
CMD CRC Error - Not correct connection.
Variants:
1) Try to set low clock
2) Try to connect correct mode (HiPower or ISP)
3) Set correct IO voltage

Bhagat20 11-07-2018 19:51
Quote:
Originally Posted by layder (Post 13403284)
CMD CRC Error - Not correct connection.
Variants:
1) Try to set low clock
2) Try to connect correct mode (HiPower or ISP)
3) Set correct IO voltage
Tried all the combinations but still not solved, when selecting other combination showing error "cmd timeout error"

layder 11-07-2018 20:27
Use Hipower ISP mode:
1) Set HiPower_ISP interface, Set 1.8v IO
2) Connecnt only CMD//CLK/D0/GND
3) Connect USB power to phone

Bhagat20 11-08-2018 05:14
Quote:
Originally Posted by layder (Post 13403802)
Use Hipower ISP mode:
1) Set HiPower_ISP interface, Set 1.8v IO
2) Connecnt only CMD//CLK/D0/GND
3) Connect USB power to phone
Tried the above as well, all the things I tried still unable to connect via adapter, before also phones when I connect with ISP pinouts provided in support, I am unable to connect with adaptor but if I desolder emmc and connect via emmc socket, it connects, I think there is the problem in adaptor, I bought a new easy JTAG plus last month n its the new adaptor what we get with box, please suggest how can i check if that adaptor is working properly or not?

layder 11-08-2018 09:33
Quote:
Originally Posted by Bhagat20 (Post 13404115)
Tried the above as well, all the things I tried still unable to connect via adapter, before also phones when I connect with ISP pinouts provided in support, I am unable to connect with adaptor but if I desolder emmc and connect via emmc socket, it connects, I think there is the problem in adaptor, I bought a new easy JTAG plus last month n its the new adaptor what we get with box, please suggest how can i check if that adaptor is working properly or not?
We work to add quality for ISP connection. But I use ISP connection many times, and all good. I use 4 bit pcb adapter with 1 bit line.
Adapter have only capacitors for 1.8/2.8 lines, all other lines have direct connection

Bhagat20 11-08-2018 11:17
Quote:
Originally Posted by layder (Post 13404407)
We work to add quality for ISP connection. But I use ISP connection many times, and all good. I use 4 bit pcb adapter with 1 bit line.
Adapter have only capacitors for 1.8/2.8 lines, all other lines have direct connection
now getting below error:

Z3X EasyJtag Software ver. 3.1.0.0
Loading eMMC GEN2 Firmware... IO: 2800 mV
Box S/N: 026862FABF5A25EA, ,FW Ver.: 02.30
CMD Pullup Level:1982 mV
CMD Active Level:2521 mV
Box IO Level:2800 mV
CLK Rate:18000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
---------- eMMC Device Information ----------


eMMC CID : 110100303332473334008378D1AC435D

eMMC CSD : D02700328F5903FFFFFFFFE7864000A7

eMMC Manufacturer ID: 0011 , OEM ID: 0100
eMMC Date: 04/2016 Rev.0x0
eMMC NAME: 032G34 , S/N: 2205733292
eMMC NAME (HEX): 303332473334
Can't init EMMC, Reason: DATA RCV Timeout Error
Check Data Line!
Done.


and when changing io level then this error:

11/8/2018 3:49:46 PM> Looking for EasyJTAG box...
11/8/2018 3:49:46 PM> EasyJTAG API ver. 2022
11/8/2018 3:49:46 PM> Setting IO Levels to 1.8V
11/8/2018 3:49:46 PM> Setting frequence to 9 Mhz
11/8/2018 3:49:46 PM> EasyJTAG Box Serial = 026862FABF5A25EA
11/8/2018 3:49:46 PM> EasyJTAG Box Firmware = 2.30
11/8/2018 3:49:46 PM> Setting interface to EasyJtag2/ISP_HiPower
11/8/2018 3:49:46 PM> Setting bus width to 1 Bit
11/8/2018 3:49:46 PM> HiPower mode is ON
11/8/2018 3:49:51 PM> Setting frequence to 9 Mhz
11/8/2018 3:49:51 PM> CMD Pullup Level: 1766 mV
11/8/2018 3:49:51 PM> CMD Active Level: 1881 mV
11/8/2018 3:49:51 PM> eMMC Init returned = -103
11/8/2018 3:49:51 PM> Can't init device. Reason: OCR Ready Timeout Error [Check VCC or eMMC DEAD]


11/8/2018 3:39:21 PM> Looking for EasyJTAG box...
11/8/2018 3:39:21 PM> EasyJTAG API ver. 2022
11/8/2018 3:39:21 PM> Setting IO Levels to 1.8V
11/8/2018 3:39:21 PM> Setting frequence to 6 Mhz
11/8/2018 3:39:21 PM> EasyJTAG Box Serial = 026862FABF5A25EA
11/8/2018 3:39:21 PM> EasyJTAG Box Firmware = 2.30
11/8/2018 3:39:22 PM> Setting interface to EasyJtag2/ISP
11/8/2018 3:39:22 PM> Setting bus width to 1 Bit
11/8/2018 3:39:33 PM> Setting frequence to 6 Mhz
11/8/2018 3:39:33 PM> CMD Pullup Level: 1770 mV
11/8/2018 3:39:33 PM> CMD Active Level: 1878 mV
11/8/2018 3:39:33 PM> eMMC Init returned = -3
11/8/2018 3:39:33 PM> Can't init device. Reason: DATA RCV Timeout Error

sir i am using 1 bit adaptor, should i use 4bits?

layder 11-08-2018 13:57
Quote:
Originally Posted by Bhagat20 (Post 13404580)
now getting below error:

eMMC CID : 110100303332473334008378D1AC435D
eMMC CSD : D02700328F5903FFFFFFFFE7864000A7
eMMC Manufacturer ID: 0011 , OEM ID: 0100
eMMC Date: 04/2016 Rev.0x0
eMMC NAME: 032G34 , S/N: 2205733292
eMMC NAME (HEX): 303332473334
Can't init EMMC, Reason: DATA RCV Timeout Error
Check Data Line!
Done.
This is tell about CLK/CMD is good connection and bad "Dat_0" connection

Quote:
Originally Posted by Bhagat20 (Post 13404580)
and when changing io level then this error:

11/8/2018 3:49:46 PM> Setting interface to EasyJtag2/ISP_HiPower
11/8/2018 3:49:46 PM> Setting bus width to 1 Bit
11/8/2018 3:49:46 PM> HiPower mode is ON
11/8/2018 3:49:51 PM> Setting frequence to 9 Mhz
11/8/2018 3:49:51 PM> CMD Pullup Level: 1766 mV
11/8/2018 3:49:51 PM> CMD Active Level: 1881 mV
11/8/2018 3:49:51 PM> eMMC Init returned = -103
11/8/2018 3:49:51 PM> Can't init device. Reason: OCR Ready Timeout Error [Check VCC or eMMC DEAD]
OCR timeout error - no answer from CMD line

Quote:
Originally Posted by Bhagat20 (Post 13404580)
11/8/2018 3:39:33 PM> Can't init device. Reason: DATA RCV Timeout Error

sir i am using 1 bit adaptor, should i use 4bits?
Also CLK/CMD is good connection and bad "Dat_0" connection

No differents within adapters. You can use it as like.

You need to use rules:
1) Lenght of CMD/CLK/D0 is need to be some (no more then 1-2 sm differents)
2) GND line is need to be told

Bhagat20 11-08-2018 14:18
Quote:
Originally Posted by layder (Post 13404851)
This is tell about CLK/CMD is good connection and bad "Dat_0" connection



OCR timeout error - no answer from CMD line



Also CLK/CMD is good connection and bad "Dat_0" connection

No differents within adapters. You can use it as like.

You need to use rules:
1) Lenght of CMD/CLK/D0 is need to be some (no more then 1-2 sm differents)
2) GND line is need to be told
Sir thank you for your support, I connected usb cable to phones PCB, now phone connected well and showing all the information OK in easy JTAG plus tool after emmc flash, but showing error in easy JTAG classic suite --- "Caution: invalid backup GPT header, but valid main header!"
Please suggest why this error only in easy JTAG classic suite?

layder 11-08-2018 18:55
Quote:
Originally Posted by Bhagat20 (Post 13404901)
Sir thank you for your support, I connected usb cable to phones PCB, now phone connected well and showing all the information OK in easy JTAG plus tool after emmc flash, but showing error in easy JTAG classic suite --- "Caution: invalid backup GPT header, but valid main header!"
Please suggest why this error only in easy JTAG classic suite?
Backup GPT is not strongly needed. EasyJTAG plus software does not check it

Bhagat20 11-09-2018 12:22
Quote:
Originally Posted by layder (Post 13405373)
Backup GPT is not strongly needed. EasyJTAG plus software does not check it
sir please suggest how to repair this, userdata is showing 0b(Error: Mount [data] failed PartType: LINUX) how to format userdata with classikc suite (regions)?


11/9/2018 3:11:21 PM> Looking for EasyJTAG box...
11/9/2018 3:11:21 PM> EasyJTAG API ver. 2100
11/9/2018 3:11:21 PM> Setting IO Levels to 2.8V
11/9/2018 3:11:21 PM> Setting frequence to 18 Mhz
11/9/2018 3:11:21 PM> EasyJTAG Box Serial = 026862FABF5A25EA
11/9/2018 3:11:21 PM> EasyJTAG Box Firmware = 2.30
11/9/2018 3:11:21 PM> Setting interface to EasyJtag2/ISP
11/9/2018 3:11:21 PM> Setting bus width to 1 Bit
11/9/2018 3:11:21 PM> Setting frequence to 18 Mhz
11/9/2018 3:11:21 PM> CMD Pullup Level: 1947 mV
11/9/2018 3:11:21 PM> CMD Active Level: 2497 mV
11/9/2018 3:11:21 PM> eMMC Init returned = 0
11/9/2018 3:11:21 PM> EMMC Device Information :
11/9/2018 3:11:21 PM> EMMC CID: 110100303332473334008378D1AC435D
11/9/2018 3:11:21 PM> EMMC CSD: D02700328F5903FFFFFFFFE7864000A7
11/9/2018 3:11:21 PM> EMMC Manufacture : TOSHIBA , EMMC NAME: 032G34 , HEX: 303332473334 , S/N: 8378D1AC , rev. 0x00
11/9/2018 3:11:21 PM> EMMC Manufacture ID: 0x11 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 4/2016
11/9/2018 3:11:21 PM> EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
11/9/2018 3:11:21 PM> EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
11/9/2018 3:11:21 PM> EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000)
11/9/2018 3:11:21 PM> EMMC Permanent Write Protection: No
11/9/2018 3:11:21 PM> EMMC Temporary Write Protection: No
11/9/2018 3:11:21 PM> Extended CSD Information :
11/9/2018 3:11:21 PM> Extended CSD rev: 1.8 (MMC 5.1)
11/9/2018 3:11:21 PM> Boot configuration [PARTITION_CONFIG]: 0x38 , Boot from: ROM1 (Main User Area)
11/9/2018 3:11:21 PM> Boot Bus Config: 0x00 , width 1bit
11/9/2018 3:11:21 PM> H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
11/9/2018 3:11:21 PM> Supported partition features [PARTITIONING_SUPPORT]: 0x07
11/9/2018 3:11:21 PM> Device supports partitioning features
11/9/2018 3:11:21 PM> Device can have enhanced technological features in partitions and user data area
11/9/2018 3:11:22 PM> Device can have extended partitions attribute
11/9/2018 3:11:22 PM> Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
11/9/2018 3:11:22 PM> Backup saved: 032G34_8378D1AC_20181109_151122.extcsd
11/9/2018 3:11:22 PM> EMMC Init completed.
11/9/2018 3:11:22 PM>
11/9/2018 3:11:22 PM> Scanning soft partitions
11/9/2018 3:11:22 PM> GPT header is found and is valid
11/9/2018 3:11:22 PM> Partition: modem, [000004000000 - 000009400000], size: 000005400000 (84.0 MB)
11/9/2018 3:11:22 PM> Partition: fsc, [00000C000000 - 00000C000400], size: 000000000400 (1.00 KB)
11/9/2018 3:11:22 PM> Partition: ssd, [00000C000400 - 00000C002400], size: 000000002000 (8.00 KB)
11/9/2018 3:11:22 PM> Partition: sbl1, [00000C002400 - 00000C082400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: sbl1bak, [00000C082400 - 00000C102400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: rpm, [00000C102400 - 00000C182400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: rpmbak, [00000C182400 - 00000C202400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: tz, [00000C202400 - 00000C402400], size: 000000200000 (2.00 MB)
11/9/2018 3:11:22 PM> Partition: tzbak, [00000C402400 - 00000C602400], size: 000000200000 (2.00 MB)
11/9/2018 3:11:22 PM> Partition: hyp, [00000C602400 - 00000C682400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: hypbak, [00000C682400 - 00000C702400], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: dsp, [00000C702400 - 00000D702400], size: 000001000000 (16.0 MB)
11/9/2018 3:11:22 PM> Partition: modemst1, [00000D702400 - 00000D882400], size: 000000180000 (1.50 MB)
11/9/2018 3:11:22 PM> Partition: modemst2, [00000D882400 - 00000DA02400], size: 000000180000 (1.50 MB)
11/9/2018 3:11:22 PM> Partition: DDR, [000010000000 - 000010008000], size: 000000008000 (32.0 KB)
11/9/2018 3:11:22 PM> Partition: fsg, [000010008000 - 000010188000], size: 000000180000 (1.50 MB)
11/9/2018 3:11:22 PM> Partition: sec, [000010188000 - 00001018C000], size: 000000004000 (16.0 KB)
11/9/2018 3:11:22 PM> Partition: splash, [000014000000 - 000014B00000], size: 000000B00000 (11.0 MB)
11/9/2018 3:11:22 PM> Partition: aboot, [000018000000 - 000018100000], size: 000000100000 (1.00 MB)
11/9/2018 3:11:22 PM> Partition: abootbak, [000018100000 - 000018200000], size: 000000100000 (1.00 MB)
11/9/2018 3:11:22 PM> Partition: boot, [000018200000 - 00001C200000], size: 000004000000 (64.0 MB)
11/9/2018 3:11:22 PM> Partition: recovery, [00001C200000 - 000020200000], size: 000004000000 (64.0 MB)
11/9/2018 3:11:22 PM> Partition: devinfo, [000020200000 - 000020300000], size: 000000100000 (1.00 MB)
11/9/2018 3:11:22 PM> Partition: system, [000020300000 - 0000C0300000], size: 0000A0000000 (2.50 GB)
11/9/2018 3:11:22 PM> Partition: cache, [0000C4000000 - 0000D4000000], size: 000010000000 (256. MB)
11/9/2018 3:11:22 PM> Partition: persist, [0000D4000000 - 0000D6000000], size: 000002000000 (32.0 MB)
11/9/2018 3:11:22 PM> Partition: misc, [0000D6000000 - 0000D6100000], size: 000000100000 (1.00 MB)
11/9/2018 3:11:22 PM> Partition: keystore, [0000D6100000 - 0000D6180000], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: config, [0000D6180000 - 0000D6188000], size: 000000008000 (32.0 KB)
11/9/2018 3:11:22 PM> Partition: oem, [0000D6188000 - 0000DA188000], size: 000004000000 (64.0 MB)
11/9/2018 3:11:22 PM> Partition: limits, [0000DC000000 - 0000DC008000], size: 000000008000 (32.0 KB)
11/9/2018 3:11:22 PM> Partition: mota, [0000E0000000 - 0000E0080000], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: devcfg, [0000E0080000 - 0000E00C0000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: dip, [0000E00C0000 - 0000E01C0000], size: 000000100000 (1.00 MB)
11/9/2018 3:11:22 PM> Partition: mdtp, [0000E01C0000 - 0000E21C0000], size: 000002000000 (32.0 MB)
11/9/2018 3:11:22 PM> Partition: cust, [0000E21C0000 - 0001021C0000], size: 000020000000 (512. MB)
11/9/2018 3:11:22 PM> Partition: syscfg, [0001021C0000 - 000102240000], size: 000000080000 (512. KB)
11/9/2018 3:11:22 PM> Partition: mcfg, [000102240000 - 000102640000], size: 000000400000 (4.00 MB)
11/9/2018 3:11:22 PM> Partition: cmnlib, [000104000000 - 000104040000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: keymaster, [000104040000 - 000104080000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: cmnlibbak, [000104080000 - 0001040C0000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: keymasterbak, [0001040C0000 - 000104100000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: apdp, [000108000000 - 000108040000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: msadp, [000108040000 - 000108080000], size: 000000040000 (256. KB)
11/9/2018 3:11:22 PM> Partition: dpo, [000108080000 - 000108082000], size: 000000002000 (8.00 KB)
11/9/2018 3:11:22 PM> Partition: userdata, [000108082000 - 000108082000], size: 000000000000 (0 B)
11/9/2018 3:11:22 PM> GPT header successfully parsed
11/9/2018 3:11:22 PM>
11/9/2018 3:11:22 PM> Get firmware version
11/9/2018 3:11:22 PM>
11/9/2018 3:11:23 PM> Error: Mount [data] failed PartType: LINUX
11/9/2018 3:11:23 PM> Brand = Xiaomi
11/9/2018 3:11:23 PM> Manufacturer = Xiaomi
11/9/2018 3:11:23 PM> Model = Redmi Note 3
11/9/2018 3:11:23 PM> Phone platform = msm8952
11/9/2018 3:11:23 PM> CPU Abi = arm64-v8a
11/9/2018 3:11:23 PM> Android release = 6.0.1
11/9/2018 3:11:23 PM> Firmware version = MMB29M
11/9/2018 3:11:23 PM> Firmware date = Fri Mar 24 15:36:11 CST 2017

layder 11-09-2018 15:53
Quote:
Originally Posted by Bhagat20 (Post 13406503)
sir please suggest how to repair this, userdata is showing 0b(Error: Mount [data] failed PartType: LINUX) how to format userdata with classikc suite (regions)?
You need to do wipe from recovery

Bhagat20 11-09-2018 19:16
Quote:
Originally Posted by layder (Post 13406896)
You need to do wipe from recovery
Sir please review this thread-- same problem.....
http://forum.gsmhosting.com/vbb/f672...licon-2499885/

That person has given this resolution-- Look Userdata size=0. Need format Userdata partition. Emmc File Manager or EasyJtag Classic - regions......? Please suggest?

If unable to mount data phone will be hang on logo only?

Bhagat20 11-10-2018 09:23
Quote:
Originally Posted by layder (Post 13406896)
You need to do wipe from recovery
sir now phone not powering on, only red led blinking
please see the logs after flash:

Z3X EasyJtag Software ver. 3.1.0.0
Loading eMMC GEN2 Firmware... IO: 2800 mV
Box S/N: 026862FABF5A25EA, ,FW Ver.: 02.30
CMD Pullup Level:1962 mV
CMD Active Level:2508 mV
Box IO Level:2800 mV
CLK Rate:18000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
---------- eMMC Device Information ----------

eMMC CID : 110100303332473334008378D1AC435D
eMMC CSD : D02700328F5903FFFFFFFFE7864000A7
eMMC Manufacturer ID: 0011 , OEM ID: 0100
eMMC Date: 04/2016 Rev.0x0
eMMC NAME: 032G34 , S/N: 2205733292
eMMC NAME (HEX): 303332473334
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG: 0x38] Boot from:ROM1 (Main User Area)
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x38.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity WP group size [HC_WP_GRP_SIZE: 0x00002000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: 032G34_2205733292_20181110_1236.extcsd
Partition table scan:
GPT: present
Found valid GPT with protective MBR; using GPT.
Real (Hardware) Disk/Image size: 3A3E000 sectors 29.1 GiB
Soft (Partitioned) Disk/Image size: 3A3DFBC sectors 29.1 GiB
Logical sector size: 0x200 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
First usable sector: 34
Last usable sector: 61071326
Found Data areas (firmware parts) count is: 46
Partition info successfully found
---------------------------------------------
P0 (MODEM) [0x4000000 0x5400000] Size: 84.0MB
P1 (FSC) [0xc000000 0x400] Size: 1.0KB
P2 (SSD) [0xc000400 0x2000] Size: 8.0KB
P3 (SBL1) [0xc002400 0x80000] Size: 512.0KB
P4 (SBL1BAK) [0xc082400 0x80000] Size: 512.0KB
P5 (RPM) [0xc102400 0x80000] Size: 512.0KB
P6 (RPMBAK) [0xc182400 0x80000] Size: 512.0KB
P7 (TZ) [0xc202400 0x200000] Size: 2.0MB
P8 (TZBAK) [0xc402400 0x200000] Size: 2.0MB
P9 (HYP) [0xc602400 0x80000] Size: 512.0KB
P10 (HYPBAK) [0xc682400 0x80000] Size: 512.0KB
P11 (DSP) [0xc702400 0x1000000] Size: 16.0MB
P12 (MODEMST1) [0xd702400 0x180000] Size: 1.500MB
P13 (MODEMST2) [0xd882400 0x180000] Size: 1.500MB
P14 (DDR) [0x10000000 0x8000] Size: 32.0KB
P15 (FSG) [0x10008000 0x180000] Size: 1.500MB
P16 (SEC) [0x10188000 0x4000] Size: 16.0KB
P17 (SPLASH) [0x14000000 0xb00000] Size: 11.0MB
P18 (ABOOT) [0x18000000 0x100000] Size: 1.0MB
P19 (ABOOTBAK) [0x18100000 0x100000] Size: 1.0MB
P20 (BOOT) [0x18200000 0x4000000] Size: 64.0MB
P21 (RECOVERY) [0x1c200000 0x4000000] Size: 64.0MB
P22 (DEVINFO) [0x20200000 0x100000] Size: 1.0MB
P23 (SYSTEM) [0x20300000 0xa0000000] Size: 2.500GB
P24 (CACHE) [0xc4000000 0x10000000] Size: 256.0MB
P25 (PERSIST) [0xd4000000 0x2000000] Size: 32.0MB
P26 (MISC) [0xd6000000 0x100000] Size: 1.0MB
P27 (KEYSTORE) [0xd6100000 0x80000] Size: 512.0KB
P28 (CONFIG) [0xd6180000 0x8000] Size: 32.0KB
P29 (OEM) [0xd6188000 0x4000000] Size: 64.0MB
P30 (LIMITS) [0xdc000000 0x8000] Size: 32.0KB
P31 (MOTA) [0xe0000000 0x80000] Size: 512.0KB
P32 (DEVCFG) [0xe0080000 0x40000] Size: 256.0KB
P33 (DIP) [0xe00c0000 0x100000] Size: 1.0MB
P34 (MDTP) [0xe01c0000 0x2000000] Size: 32.0MB
P35 (CUST) [0xe21c0000 0x20000000] Size: 512.0MB
P36 (SYSCFG) [0x1021c0000 0x80000] Size: 512.0KB
P37 (MCFG) [0x102240000 0x400000] Size: 4.0MB
P38 (CMNLIB) [0x104000000 0x40000] Size: 256.0KB
P39 (KEYMASTER) [0x104040000 0x40000] Size: 256.0KB
P40 (CMNLIBBAK) [0x104080000 0x40000] Size: 256.0KB
P41 (KEYMASTERBAK) [0x1040c0000 0x40000] Size: 256.0KB
P42 (APDP) [0x108000000 0x40000] Size: 256.0KB
P43 (MSADP) [0x108040000 0x40000] Size: 256.0KB
P44 (DPO) [0x108080000 0x2000] Size: 8.0KB
P45 (USERDATA) [0x108082000 0x63fb79c00] Size: 24.995GB
------ Android information ------
Detected LINUX(Android) SYSTEM : 0x0020300000 (2.500GB)
Build ID: MMB29M
Display Build ID: MMB29M
Release ID: 6.0.1
Device Model: Redmi Note 3
Device Name: kenzo
Architecture ABI: arm64-v8a
Device Platform: msm8952
Product ID: kenzo
Build Description: kenzo-user 6.0.1 MMB29M V8.2.2.0.MHOMIDL release-keys
Device manufacturer: Xiaomi
---------------------------------------------
Done.

ali_imran 11-10-2018 17:11
still set show comport?


All times are GMT +1. The time now is 12:39.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -

Page generated in 0.26469 seconds with 6 queries

SEO by vBSEO