GSM-Forum

GSM-Forum (https://forum.gsmhosting.com/vbb/)
-   Easy-Jtag / Easy-Jtag Plus (https://forum.gsmhosting.com/vbb/f672/)
-   -   Dying HTC's M9 EMMC chips (https://forum.gsmhosting.com/vbb/f672/dying-htcs-m9-emmc-chips-2221433/)

kwaku85 05-05-2017 10:22
Dying HTC's M9 EMMC chips
 
Hello supporters.
Some time ago I notice that many HTC M9 with Hynix EMMC chips died without any reason. Some cannot be repaired because they cannot be flashed anymore (only reset sectors without any write), some can be repaired, but most of them back after short time with same problems. After latest EasyJTAG plus update there is possibility to read SMART info from this chips. How to read those informations axactly? Here is log from some M9 with broken EMMC:

Code:
2017-05-05 10:54:57> eMMC_tool Suite  ver. 1.0.0.45
2017-05-05 10:54:57> Microsoft Windows 7 (64 bit) build 7601 (6.1.7601.18015)
2017-05-05 10:54:57>
2017-05-05 10:54:57> Looking for EasyJTAG box...
2017-05-05 10:54:57> EasyJTAG API ver. 2008
2017-05-05 10:54:57> Setting IO Levels to 2.8V
2017-05-05 10:54:57> Setting frequence to 21 Mhz
2017-05-05 10:54:57> HiPower mode is OFF
2017-05-05 10:54:58> OpenUSB returned = 0
2017-05-05 10:54:58> Power Controller returned = 0
2017-05-05 10:54:58> EasyJTAG Box Serial = xxxxxxxxxxx
2017-05-05 10:55:04> Card Serial = xxxxxxxxx
2017-05-05 10:55:04> CardAttr = xxxxxxxxxxxxxxxxxxxxxxx
2017-05-05 10:55:04> EasyJTAG Box Firmware = 01.58
2017-05-05 10:55:04>
2017-05-05 10:55:11> Looking for EasyJTAG box...
2017-05-05 10:55:11> EasyJTAG API ver. 2008
2017-05-05 10:55:11> Setting IO Levels to 2.8V
2017-05-05 10:55:11> Setting frequence to 21 Mhz
2017-05-05 10:55:11> HiPower mode is OFF
2017-05-05 10:55:12> OpenUSB returned = 0
2017-05-05 10:55:12> Power Controller returned = 0
2017-05-05 10:55:12> EasyJTAG Box Serial = xxxxxxxxxxxxxxx
2017-05-05 10:55:12> EasyJTAG Box Firmware = 01.58
2017-05-05 10:55:12> HiPower mode is OFF
2017-05-05 10:55:12> CMD Pullup Level: 2062 mV
2017-05-05 10:55:12> CMD Active Level: 2547 mV
2017-05-05 10:55:12> eMMC Init returned = 0
2017-05-05 10:55:12> EMMC Device Information :
2017-05-05 10:55:12> EMMC CID: 90014A48424734650507B3A4DD612264
2017-05-05 10:55:12> EMMC CSD: D02701320F5903FFFFFFFFEF8A4040D2
2017-05-05 10:55:12> EMMC Manufacture Name: SKHYNIX
2017-05-05 10:55:12> EMMC Manufacture ID: 0x90 , OEM ID: 014A
2017-05-05 10:55:12> EMMC Manufacture Date: 2/2015 , Rev: 07
2017-05-05 10:55:12> EMMC NAME: HBG4e , S/N: B3A4DD61 , rev. 07
2017-05-05 10:55:12> EMMC NAME (HEX): 484247346505
2017-05-05 10:55:12>    EMMC ROM 1 (Main User Data) Capacity: 29824 MB (000748000000)
2017-05-05 10:55:12>    EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
2017-05-05 10:55:12>    EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000)
2017-05-05 10:55:12> EMMC Permanent Write Protection: No
2017-05-05 10:55:12> EMMC Temporary Write Protection: No
2017-05-05 10:55:12> Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
2017-05-05 10:55:12> Boot configuration [PARTITION_CONFIG]: 0x00 , Boot from: no boot
2017-05-05 10:55:12> Boot Bus Config: 0x00 , width 1bit
2017-05-05 10:55:12> H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
2017-05-05 10:55:12> Supported partition features [PARTITIONING_SUPPORT]: 0x07
2017-05-05 10:55:12> Device supports partitioning features
2017-05-05 10:55:12> Device can have enhanced technological features in partitions and user data area
2017-05-05 10:55:12> Device can have extended partitions attribute
2017-05-05 10:55:12> Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
2017-05-05 10:55:12> Backup saved: HBG4e_B3A4DD61_20170505_105512.extcsd
2017-05-05 10:55:12> EMMC Init completed.
2017-05-05 10:55:12>
2017-05-05 10:55:12> Reading S.M.A.R.T Report ...
2017-05-05 10:55:12>
2017-05-05 10:55:12> Supported modes [493]: 0x01
2017-05-05 10:55:12>      FFU is supported by the device
2017-05-05 10:55:12>      Vendor Specific Mode (VSM) is not supported by the device
2017-05-05 10:55:12> FFU Features [492]: 0x00
2017-05-05 10:55:12>      Device does not support MODE_OPERATION_CODES field
2017-05-05 10:55:12> Operation Codes Timeout [491]: 0x17  838,86 s
2017-05-05 10:55:12> FFU Argument [497_490]: 0x00006600
2017-05-05 10:55:12> Number of FW sectors correctly programmed [302_305]: 0x00000000
2017-05-05 10:55:12> Vendor Proprietary Health Report [301_270]:
2017-05-05 10:55:12>      VENDOR_PROPRIETARY_HEALTH_REPORT [301]: 0x00
2017-05-05 10:55:12>      VENDOR_PROPRIETARY_HEALTH_REPORT [300]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [299]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [298]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [297]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [296]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [295]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [294]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [293]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [292]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [291]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [290]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [289]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [288]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [287]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [286]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [285]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [284]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [283]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [282]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [281]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [280]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [279]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [278]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [277]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [276]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [275]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [274]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [273]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [272]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [271]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [270]: 0x00
2017-05-05 10:55:13> Device Life Time Estimation Type B [269]: 0x0B
2017-05-05 10:55:13>      Exceeded its maximum estimated device life time
2017-05-05 10:55:13> Device Life Time Estimation Type A [268]: 0x01
2017-05-05 10:55:13>      0% - 10% device life time used
2017-05-05 10:55:13> Pre EOL information [267]: 0x03
2017-05-05 10:55:13>      Urgent
2017-05-05 10:55:13>
2017-05-05 10:55:13> Optimal Read Size [266]: 0x40  256 KB
2017-05-05 10:55:13> Optimal Write Size [265]: 0x40  256 KB
2017-05-05 10:55:13> Optimal Trim Unit Size [264]: 0x07  28 KB
2017-05-05 10:55:13>
2017-05-05 10:55:13> Device Version [263_262]: 0x05 - 0x42
2017-05-05 10:55:13> Firmware version [261_254]:
2017-05-05 10:55:13>      FIRMWARE_VERSION [261]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [260]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [259]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [258]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [257]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [256]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [255]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [254]: 0x07
2017-05-05 10:55:13>
2017-05-05 10:55:13> Done
This is interesting part:

2017-05-05 10:55:13> Device Life Time Estimation Type B [269]: 0x0B
2017-05-05 10:55:13> Exceeded its maximum estimated device life time

but have no idea what is LifeTime Type B exactly.

How to use all of this informations?

NoName® 05-06-2017 01:03
1 Attachment(s)
Quote:
Originally Posted by kwaku85 (Post 12483129)
Hello supporters.
Some time ago I notice that many HTC M9 with Hynix EMMC chips died without any reason. Some cannot be repaired because they cannot be flashed anymore (only reset sectors without any write), some can be repaired, but most of them back after short time with same problems. After latest EasyJTAG plus update there is possibility to read SMART info from this chips. How to read those informations axactly? Here is log from some M9 with broken EMMC:

Code:
2017-05-05 10:54:57> eMMC_tool Suite  ver. 1.0.0.45
2017-05-05 10:54:57> Microsoft Windows 7 (64 bit) build 7601 (6.1.7601.18015)
2017-05-05 10:54:57>
2017-05-05 10:54:57> Looking for EasyJTAG box...
2017-05-05 10:54:57> EasyJTAG API ver. 2008
2017-05-05 10:54:57> Setting IO Levels to 2.8V
2017-05-05 10:54:57> Setting frequence to 21 Mhz
2017-05-05 10:54:57> HiPower mode is OFF
2017-05-05 10:54:58> OpenUSB returned = 0
2017-05-05 10:54:58> Power Controller returned = 0
2017-05-05 10:54:58> EasyJTAG Box Serial = xxxxxxxxxxx
2017-05-05 10:55:04> Card Serial = xxxxxxxxx
2017-05-05 10:55:04> CardAttr = xxxxxxxxxxxxxxxxxxxxxxx
2017-05-05 10:55:04> EasyJTAG Box Firmware = 01.58
2017-05-05 10:55:04>
2017-05-05 10:55:11> Looking for EasyJTAG box...
2017-05-05 10:55:11> EasyJTAG API ver. 2008
2017-05-05 10:55:11> Setting IO Levels to 2.8V
2017-05-05 10:55:11> Setting frequence to 21 Mhz
2017-05-05 10:55:11> HiPower mode is OFF
2017-05-05 10:55:12> OpenUSB returned = 0
2017-05-05 10:55:12> Power Controller returned = 0
2017-05-05 10:55:12> EasyJTAG Box Serial = xxxxxxxxxxxxxxx
2017-05-05 10:55:12> EasyJTAG Box Firmware = 01.58
2017-05-05 10:55:12> HiPower mode is OFF
2017-05-05 10:55:12> CMD Pullup Level: 2062 mV
2017-05-05 10:55:12> CMD Active Level: 2547 mV
2017-05-05 10:55:12> eMMC Init returned = 0
2017-05-05 10:55:12> EMMC Device Information :
2017-05-05 10:55:12> EMMC CID: 90014A48424734650507B3A4DD612264
2017-05-05 10:55:12> EMMC CSD: D02701320F5903FFFFFFFFEF8A4040D2
2017-05-05 10:55:12> EMMC Manufacture Name: SKHYNIX
2017-05-05 10:55:12> EMMC Manufacture ID: 0x90 , OEM ID: 014A
2017-05-05 10:55:12> EMMC Manufacture Date: 2/2015 , Rev: 07
2017-05-05 10:55:12> EMMC NAME: HBG4e , S/N: B3A4DD61 , rev. 07
2017-05-05 10:55:12> EMMC NAME (HEX): 484247346505
2017-05-05 10:55:12>    EMMC ROM 1 (Main User Data) Capacity: 29824 MB (000748000000)
2017-05-05 10:55:12>    EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
2017-05-05 10:55:12>    EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000)
2017-05-05 10:55:12> EMMC Permanent Write Protection: No
2017-05-05 10:55:12> EMMC Temporary Write Protection: No
2017-05-05 10:55:12> Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
2017-05-05 10:55:12> Boot configuration [PARTITION_CONFIG]: 0x00 , Boot from: no boot
2017-05-05 10:55:12> Boot Bus Config: 0x00 , width 1bit
2017-05-05 10:55:12> H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
2017-05-05 10:55:12> Supported partition features [PARTITIONING_SUPPORT]: 0x07
2017-05-05 10:55:12> Device supports partitioning features
2017-05-05 10:55:12> Device can have enhanced technological features in partitions and user data area
2017-05-05 10:55:12> Device can have extended partitions attribute
2017-05-05 10:55:12> Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
2017-05-05 10:55:12> Backup saved: HBG4e_B3A4DD61_20170505_105512.extcsd
2017-05-05 10:55:12> EMMC Init completed.
2017-05-05 10:55:12>
2017-05-05 10:55:12> Reading S.M.A.R.T Report ...
2017-05-05 10:55:12>
2017-05-05 10:55:12> Supported modes [493]: 0x01
2017-05-05 10:55:12>      FFU is supported by the device
2017-05-05 10:55:12>      Vendor Specific Mode (VSM) is not supported by the device
2017-05-05 10:55:12> FFU Features [492]: 0x00
2017-05-05 10:55:12>      Device does not support MODE_OPERATION_CODES field
2017-05-05 10:55:12> Operation Codes Timeout [491]: 0x17  838,86 s
2017-05-05 10:55:12> FFU Argument [497_490]: 0x00006600
2017-05-05 10:55:12> Number of FW sectors correctly programmed [302_305]: 0x00000000
2017-05-05 10:55:12> Vendor Proprietary Health Report [301_270]:
2017-05-05 10:55:12>      VENDOR_PROPRIETARY_HEALTH_REPORT [301]: 0x00
2017-05-05 10:55:12>      VENDOR_PROPRIETARY_HEALTH_REPORT [300]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [299]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [298]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [297]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [296]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [295]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [294]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [293]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [292]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [291]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [290]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [289]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [288]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [287]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [286]: 0xEE
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [285]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [284]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [283]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [282]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [281]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [280]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [279]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [278]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [277]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [276]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [275]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [274]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [273]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [272]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [271]: 0x00
2017-05-05 10:55:13>      VENDOR_PROPRIETARY_HEALTH_REPORT [270]: 0x00
2017-05-05 10:55:13> Device Life Time Estimation Type B [269]: 0x0B
2017-05-05 10:55:13>      Exceeded its maximum estimated device life time
2017-05-05 10:55:13> Device Life Time Estimation Type A [268]: 0x01
2017-05-05 10:55:13>      0% - 10% device life time used
2017-05-05 10:55:13> Pre EOL information [267]: 0x03
2017-05-05 10:55:13>      Urgent
2017-05-05 10:55:13>
2017-05-05 10:55:13> Optimal Read Size [266]: 0x40  256 KB
2017-05-05 10:55:13> Optimal Write Size [265]: 0x40  256 KB
2017-05-05 10:55:13> Optimal Trim Unit Size [264]: 0x07  28 KB
2017-05-05 10:55:13>
2017-05-05 10:55:13> Device Version [263_262]: 0x05 - 0x42
2017-05-05 10:55:13> Firmware version [261_254]:
2017-05-05 10:55:13>      FIRMWARE_VERSION [261]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [260]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [259]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [258]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [257]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [256]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [255]: 0x00
2017-05-05 10:55:13>      FIRMWARE_VERSION [254]: 0x07
2017-05-05 10:55:13>
2017-05-05 10:55:13> Done
This is interesting part:

2017-05-05 10:55:13> Device Life Time Estimation Type B [269]: 0x0B
2017-05-05 10:55:13> Exceeded its maximum estimated device life time

but have no idea what is LifeTime Type B exactly.

How to use all of this informations?

According to HYNIX PDF on that chips - TYPE B is MLC Cells Health Status.Exceeded its maximum estimated device life time means that device used all reserved backup cells for bad block relocation. Normally it need replacement or firmware upgrade for reseting counters. At this moment procedures for that are private and nothin we can do ;-(

kwaku85 05-08-2017 10:03
That's ok. Chip is changed to other one and phone is working again. Good information we can check it and make decision to replace EMMC or try to fix bootloader.
I have question about contacts restoring yet. I have try read contacts from this phone but program said "bad file". File for SMS not exist inside telephony folder. Did Android 7 store contacts and SMS in other way?


All times are GMT +1. The time now is 03:16.


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

Page generated in 0.13741 seconds with 6 queries

SEO by vBSEO