Emmc fw read failed reason cmd timeout error

Содержание

Emmc fw read failed reason cmd timeout error
Easy JTAG PLUS Can’t init device, Reason: CMD Timeout Error
Mag25su
Layder
viktorfedynyak
Help KM3H6001CM not able to raed firmware
irfan111
Tres-Pedik
Hottstuff
Attachments
amir0179
Tres-Pedik
Hojiakbar
Проблема коннекта по ISP
Akir1
Emmc fw read failed reason cmd timeout error

В последнее время, я получаю эту ошибку, когда я пытаюсь обнаружить с emmc EasyJTAG,
Я получаю эту ошибку с большинством эммс я пытаюсь восстановить,
Хотя, я могу выявить и устранить много других эммс,
Я просто не знаю, что эта ошибка означает, и как с этим бороться

Мой сетевой адаптер:

Сначала я думал, что это связано с плохой паять провода, но я проверил «много» и я обнаружил, что каждый провод подключен к PIN-код,
Я также применяются 2res от 1,8 V до D0 и cmd, но это не помогло
Сегодня я отремонтировал J100H и шина N8000, но у меня H818p и i9200, который я не могу восстановить так как я не могу обнаружить из-за этой ошибки

Сейчас, мне просто нужно объяснение,
Почему я получаю эту ошибку?, Что это означает?, Как с этим бороться?,

Источник

Easy JTAG PLUS Can’t init device, Reason: CMD Timeout Error

Mag25su

Напряжение подтяжки линии CMD :2117 mV
Напряжение активной линии CMD :2493 mV
Box IO Level:2800 mV
CLK Rate:18000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
———- eMMC Device Information ———-

EMMC CID : 90014A4838473473920106B965022307
EMMC CSD : D02701320F5903FFFFFFFFE78A40002B
Изготовитель eMMC: ID: 0090 , OEM ID: 014A
EMMC Date: 02/2016 Rev.0x1
EMMC NAME: H8G4s , S/N: 112813314
EMMC NAME (HEX): 48384734732000
Can’t init EMMC, Reason: DATA RCV Timeout Error
Check Data Line!
Сделано.

Layder

Z3X-Team

Помогите пожалуйста! Реально уже устал бороться. Только купил Easy JTAG PLUS не в какую не могу подключиться по ISP пробовал подключить разные платы, везде один ответ:

Пробовал подключить эти платы через ATF цепляет без проблем. Полноценный лог. Телефоны живые, просто пока тренируюсь. Что я не так делаю?
Читал что может быть плохой пропай бокса. Все пропаял, результат отрицательный. Просто обидно, деньги на ветер.

viktorfedynyak

Easy JTAG PLUS Can’t init device

Помогите пожалуйста! Реально уже устал бороться. Только купил Easy JTAG PLUS не в какую не могу подключиться по ISP пробовал подключить разные платы, везде один ответ:
Пробовал питать от бокса, от USB, от АКБ, пробовал менять напряжения IQ. Пробовал подпаивать дополнительные сопротивления от 100 до 200 ом от линии 1.8 V на CMD и DATO. Нечего не получается.
Заметил если сначала подключить USB? а только потом подключиться к боксу, то лог получается таким.

Добрый День,
С новым боксом нужно использовать ISP адаптер, что идёт в комплекте (дополнительных сопротивлений не нужно).
Если исключить ошибки подпайки ISP к комплектному адаптеру и поискать возможные дефекты,
то проверьте наличие и сопротивление (100 Ом) резисторов R7, R8 внутри бокса,
проверьте пайку U3: pin92, pin 93, pin 94, pin 95, pin 88.
Pin 92 (U3), pin 93(U3), pin95(U3) и DAT0(выход бокса) должны быть соединены между собой (прозвонить омметром).
Если на других телефонах тоже самое и не получается исправить, то можно обратится к продавцу бокса с вопросом замены по гарантии.

Источник

Help KM3H6001CM not able to raed firmware

irfan111

Active Member

help taem not raed firmware KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254 emcp

hecking security .
Running:SAMSUNG: MoviNAND Firmware extraction.
Z3X EasyJtag Software ver. 3.7.0.24
Skip loading eMMC Addon Firmware
Box IO Level:2800 mV
CLK Rate:14000 kHz
Checking eMMC BootROM mode
Skip loading eMMC Addon Firmware
Box IO Level:2800 mV
CLK Rate:14000 kHz
— EasyJTAG Samsung eMMC Backup Tool —
EMMC CID : 150100334836434D4205CBEDAA0CA4B1
EMMC CSD : D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacturer ID: 0015 , OEM ID: 0100
EMMC Date: 10/2017 Rev.0x5
EMMC NAME: 3H6CMB , S/N: 3421350412
EMMC Part Number: KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254
IC Name: Samsung , KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254 ,
EMMC ROM1 (Main User Data) Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data.
EMMC FW Read Failed, Reason: CMD Timeout Error
Done.

Tres-Pedik

Member

Hottstuff

Junior Member

Attachments

amir0179

Junior Member

Tres-Pedik

Member

Hojiakbar

Friend’s Martview

1 Jtag does’nt raded emmc fw Cmd time out error only
try anothe ffu from forums
after that emmc is dead (( trash

2 just flash emmc fw with UFI BOX with emmc tp

Init bus.
VCC: 3.3 V, VCCQ: 3.0 V
Bus: 1 bit (SDR 3MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) — High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: 000000 (0x303030303030), rev: 0x56, serial number: 0x20160613
Manufacturing date: июн 2016
CID: 15010030 30303030 30562016 061354D0
CSD: 90270132 0F5903FF F6DB7FE0 8A40403A
EXT_CSD revision: 1.5 (MMC v4.41)
Partition info:
Boot1: 512 KiB
Boot2: 512 KiB
RPMB: 128 KiB
User area: 0 B(2,197,796,421,632 bytes)
moviNAND Field firmware update.
Loading ffu: \emmcffumovinandnewKM3H6001CM-B515(5).ffu
fw hash code: 3335dc7433dded848f1e392a7ab8c929f81e96ef260404a1e3b21434228cb393, size: 300 KiB
part name: KM3H6001CM-B515
controller: VCT0
product name: 3H6CMB (0x334836434d42), rev: 0x05
You may disconnect the emergency boot mode TP by now (3)
Switch to boot mode(2). Done
Sending firmware block. Done
Waiting 13s for the card to be ready.
Firmware update verified.
Programming CID. Done
New CID: 15010033 4836434D 420599BC 13BE8512

After flash emmc ffu with ufi my emmc back to life again

Connection status: XHCI:HUB3:[#0]:USB 2.00 High-Speed
Interface: UFI High-Speed
Serial number: 0011-8842-2119
Boot version: 1.05, FW version: 1.13 (Aug 19 2019 23:46:09)
Insertion test. Done
Init bus.
VCC: 3.3 V, VCCQ: 3.0 V
Bus: 8 bit (HS SDR 52MHz)
Access mode: sector mode
Power supply: dual-voltage (1.70-1.95V, 2.7-3.6V)
Card/BGA: BGA (Discrete embedded) — High density MMC
Manufacturer ID: 0x15 (Samsung)
Product name: 3H6CMB (0x334836434d42), rev: 0x05, serial number: 0x99BC13BE
Manufacturing date: авг 2018
CID: 15010033 4836434D 420599BC 13BE8512
CSD: D0270132 0F5903FF F6DBFFEF 8E40400C
EXT_CSD revision: 1.8 (MMC v5.1)
Partition info:
Boot1: 4 MiB
Boot2: 4 MiB
RPMB: 4 MiB [Authentication Key not yet programmed]
User area: 58.24 GiB(62,537,072,640 bytes)
Cache size: 64 MiB
Partition configuration: 0x00
No boot acknowledge is sent (default)
Device is not boot-enabled (default)
Partitioning support: 0x07
Device support partitioning feature
Device can have enhanced technological features
Device partitioning possible
Boot configuration protection: 0x00
Boot bus conditions: 0x00
Boot area write protection: 0x00
EXT_CSD backup saved to «\%BACKUPS%3H6CMB_99BC13BE.ext_csd»
eMMC selected: [SAMSUNG] KM3H6001CM-B515/64GB (BGA254)

after back to life my emmc
backupped emmc fw with jtag
download from here

10000000% readed emmc of KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254 ,

Источник

Проблема коннекта по ISP

Akir1

Доброе время суток уважаемая поддержка Z3X!

Проясните ситуацию, что я делаю не так, до последнего времени не удавалось подцепить не одного «тела» по ISP, через переходник 1-Bit ISP REV2.1 «Не получилось инициализировать устройство. Причина: CMD Timeout Error» . Ни какие изменения настроек не помогают.

Через E-Socket все ок!

Вчера долго бился с Samsung SM-G355H, сначала висел на заставке, после заливки «древней» версии» пропало изо, после заливки последней имей «000000» и «лег на руках» после попытки заливки EFS, перестал подавать признаки жизни.

Compression if OFF
Z3X EasyJtag Software ver. 3.4.0.2
Loading eMMC GEN2 Firmware. IO: 1800 mV
Box S/N: xxx, ,FW Ver.: 02.31
Warning: CMD Pullup Level (54 mV) too low , check cables etc.!
Напряжение активной линии CMD :1400 mV
Box IO Level:1800 mV
CLK Rate:36000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
Can’t init device, Reason: CMD Timeout Error
Сделано.

Compression if OFF
Z3X EasyJtag Software ver. 3.4.0.2
Loading eMMC GEN2 Firmware. IO: 2800 mV
Box S/N: xxx, ,FW Ver.: 02.31
Warning: CMD Pullup Level (57 mV) too low , check cables etc.!
Напряжение активной линии CMD :2380 mV
Box IO Level:2800 mV
CLK Rate:36000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
Can’t init device, Reason: CMD Timeout Error
Сделано.

Compression if OFF
Z3X EasyJtag Software ver. 3.4.0.2
Loading eMMC GEN2 Firmware. IO: 3300 mV
Box S/N: xxx, ,FW Ver.: 02.31
Warning: CMD Pullup Level (61 mV) too low , check cables etc.!
Напряжение активной линии CMD :2656 mV
Box IO Level:3300 mV
CLK Rate:36000 kHz
Bus Width:1bit,SDR
HiPower mode is off!
Can’t init device, Reason: CMD Timeout Error
Сделано.

и чудом удалось подцепить с воткнутым кабелем USB, соединяется в любом из режимов и ISP и ISP_Hipower — у моего бокса проблема с питанием ? Хотя питание на пинах 1.8 и 2.8v присутствуют.

Лог коннекта с USB кабелем

Brand = samsung
Manufacturer = samsung
Device = kanas
Model = SM-G355H
Phone platform = sc8830
CPU Abi = armeabi-v7a
Android release = 4.4.2
Firmware version = KOT49H.G355HXXS0AQA6
Firmware date = Thu Jan 5 21:14:30 KST 2017

Установка интерфейса EasyJtag2/ISP_HiPower
Установка ширины шины 1 Bit
HiPower режим ON
Установка частоты 12 Mhz
CMD Уровень подтяжки: 2252 mV
CMD Активный уровень: 2806 mV
Не получилось инициализировать устройство. Причина: CMD Timeout Error

Установка интерфейса EasyJtag2/ISP_HiPower
Установка ширины шины 1 Bit
HiPower режим ON
Установка частоты 12 Mhz
CMD Уровень подтяжки: 1826 mV
CMD Активный уровень: 1876 mV
EMMC Информация :
EMMC CID: 1501004B3558594D4203C93CFE9642FB
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Производитель : SAMSUNG , EMMC Имя: K5XYMB , HEX: 4B3558594D42 , S/N: C93CFE96 , rev. 0x03
EMMC Производитель ID: 0x15 , OEM ID: 0x00 , Тип устройства: BGA (Discrete embedded) , Дата: 4/2015
EMMC ROM 1 (Данные пользователя) Объем: 3728 MB (0000E9000000)
EMMC ROM 2/3 (Загрузочный раздел 1/2) Объем: 4096 KB (000000400000)
eMMC RPMB (защищенный блок данных): емкость: 512 KB (000000080000)
EMMC Постоянная защита записи: Нет
EMMC Временная защита записи: Нет
Extended CSD информация :
Extended CSD ревизия: 1.6 (MMC 4.5, MMC 4.51)
Конфигурация загрузки [PARTITION_CONFIG]: 0x08 , Загрузка из: ROM2 (Boot partition 1)
Boot Bus Config: 0x00 , width 1bit
H/W Reset Function [RST_N_FUNCTION]: 0x00, RST_n сигнал временно отключен
Поддержка управления разделами [PARTITIONING_SUPPORT]: 0x07
Устройство поддерживает функции разбиения
Устройство может иметь расширенные технологические возможности в разделах и области пользовательских данных
Устройство может иметь атрибуты расширенных разделов
Свойства раздела [PARTITION_SETTING_COMPLETED]: 0x00
Бэкап сохранён: K5XYMB_C93CFE96_20190119_225033.extcsd
EMMC Инициализация выполнена.

Источник

Emmc fw read failed reason cmd timeout error

I am new to this forum so first let me say «Hi Everyone».

I am having this problem all the time (and I do mean all the time). I have tried 6 different (working) phones and 2 tabs and ALL come out with this error:

Z3X EasyJtag Software ver. 2.0.4.0
Loading eMMC Addon Firmware. IO: 2050 mV
Box S/N: XXXXXXXXXXXXXXXX, ,FW Ver.: 01.51
CMD Pullup Level:1330 mV
CMD Active Level:1784 mV
Can’t init EMMC, Reason: CMD Timeout Error

I have spent hours looking through this forum and online but can only find other people with the same problem and no solution such as

I am using a Z3X pro box and Z3X EasyJTag box but both have the same problem (after the first box broke I got a replacement and the replacement was able to detect the Emmc before that too came up with the same error). They worked at first (for about 3 or 4 times) but then just kept coming up with the same problem.

I have tried Windows 7 and Windows 10.

I have shorted pins 3, 9 and 11 on the Z3X pro box.

The ISP connections are perfect

The EMMC chips are working fine

I have tried providing external power (from a dedicated power supply)

The adapter Im using is the: EMMC adapter for Easy JTAG Box (Z3X-Pro) by GPG

I have completely reinstalled my PC, re-installed latest software and firmware, reset firmware on the Z3x box.

With a number of people having this problem, there must be someone who can provide an answer (other than the EMMC needs replacing)

Please please please help

Is there a way to reset the Z3X box back to factory settings

Источник

Весь текст не влазиет поэтому продолжение…. Может быть флешка плохая? Берем старый немодный ATF

Код:

17:17:14 : ======================================================
17:17:14 : ======================================================
17:17:14 :        eMMC Test Point Connection Module             
17:17:14 : ======================================================
17:17:14 : ======================================================
17:17:14 :                                                       
17:17:14 : 1. DO NOT USE THE PHONE"S BATTERY                     
17:17:14 : 2. Connect the Soldered TP Connections to ATF Box     
17:17:14 : 3. Disconnect the USB Cable and Wait until the        
17:17:14 :    the ATF Software will tell you to Connect the USB. 
17:17:14 :                                                       
17:17:14 : 
17:17:14 : Interface Reset OK!
17:17:14 : eMMC Access Type: SECTOR MODE
17:17:14 : eMMC Supported Voltage Range:
17:17:14 : 3.5-3.6V, 3.4-3.5V, 3.3-3.4V, 3.2-3.3V, 3.1-3.2V
3.0-3.1V, 2.9-3.0V, 2.8-2.9V, 2.7-2.8V, 1.9-2.0V
17:17:14 : 
17:17:14 : CID : 90014A484247346132A416C0B4424369
17:17:14 : CSD : D02701328F5903FFFFFFFFE78A400017
17:17:14 : 
17:17:14 : eMMC Boot Information
17:17:14 : Revision 1.x (For MMC v4.x)
17:17:14 : BOOT PARTITION     : USER AREA
17:17:14 : PARTITION ACCESS   : R/W USER PARTITION
17:17:14 : PERM_BOOT_CFG_PROT : DISABLED
17:17:14 : PWR_BOOT_CFG_PROT  : DISABLED
17:17:14 : BOOT MODE          : x1 SINGLE DATA RATE + LOW SPEED
17:17:14 : RESET BUS WIDTH    : ENABLED
17:17:14 : eMMC FirmW UPDATE  : DISABLED
17:17:14 : EMMC CACHE SIZE    : 0 KB
17:17:14 : SUPER PAGE SIZE    : 3072 KB
17:17:14 : HC ERASE GROUP SIZE: 512 KB
17:17:14 : USER AREA SIZE     : 31268536320 BYTES
17:17:14 : BOOT PARTITION SIZE: 4096 KB
17:17:14 : RPMB PARTITION SIZE: 4096 KB
17:17:14 : 
17:17:14 : 
17:17:14 : eMMC Device Information
17:17:14 : Manufacturer ID: HYNIX
17:17:14 : Device Type    : Embedded BGA
17:17:14 : Application ID : 4A
17:17:14 : Product Name   : HBG4a2
17:17:14 : Product Rev    : 10.4
17:17:14 : Product SN     : 16C0B442
17:17:14 : Manufactured   : January 2000
17:17:14 : 
17:17:14 : Card Specific Data
17:17:14 : CSD_STRUCTURE     : Extended
17:17:14 : SPEC_VERS         : Version 4.1/4.2/4.3
17:17:14 : TAAC              : 13 ns
17:17:14 : TRAN_SPEED        : 4000000 KHz
17:17:14 : READ_BL_LEN       : 512 Bytes
17:17:14 : C_SIZE            : HIGH CAPACITY
17:17:14 : WP_GRP_ENABLE     : YES
17:17:14 : WRITE_BL_LEN      : 512 Bytes
17:17:14 : CONTENT_PROT_APP  : NO
17:17:14 : PERM_WRITE_PROTECT: NO
17:17:14 : TMP_WRITE_PROTECT : NO
17:17:14 : 
17:17:14 : Extended CSD Saved:
17:17:14 : 90014A484247346132A416C0B4424369.ext_csd
17:17:14 : Backup Directory:
17:17:14 : C:AdvanceBox Turbo FlashereMMCEXT_CSD
17:17:14 : 
17:17:14 : 
17:17:14 : Dumping Custom Region
17:17:14 : Please wait for some time...
17:17:14 : Partition Selected: USER AREA
17:17:14 : (eMMC Clock 7500000 Hz)
17:17:14 : 
17:17:14 : Custom Block Read OK
17:17:14 : File Saved: C:AdvanceBox Turbo FlashereMMCRecoveredeMMC_GPT.bin
17:17:14 : 
17:17:14 : Total Elapsed Time 00:00:00
17:17:15 : 
17:17:15 : EFI Partition Table Header
17:17:15 : Signature:EFI PART
17:17:15 : Revision: 0x00000100
17:17:15 : Header Size: 0x0000005C
17:17:15 : Header CRC32: 0x4E205BDC
17:17:15 : Reserved: 0x00000000
17:17:15 : Current EFI Partition Header LBA: 0x0000000000000001
17:17:15 : Backup EFI Partition Header LBA: 0x0000000003A3DFFF
17:17:15 : First Usable LBA: 0x0000000000000022
17:17:15 : Last Usable LBA: 0x0000000003A3DFDE
17:17:15 : Disk GUID: 0x200C003DB32B6EA04BF2BBE298101B32
17:17:15 : LBA of EFI Partition Entries: 0x0000000000000002
17:17:15 : Number of Partition Entries: 48
17:17:15 : Size of each Parition Entry: 128
тут дальше длинный список партишенов не могу добавить на форум

Пробуем стереть через него

Код:

17:17:20 : Task Selected: Normal Factory Erase
17:17:20 : ======================================================
17:17:20 : For eMMC Revision 1.2 (for MMC v4.2) and LOWER
17:17:20 : --> This will ERASE USER AREA, BOOT1, BOOT2, and RPMB
17:17:20 : For eMMC Revision 1.3 (for MMC v4.3) and HIGHER
17:17:20 : --> This will ONLY ERASE USER AREA
17:17:20 : ======================================================
17:17:20 : This eMMC is: Revision 1.x (For MMC v4.x)
17:17:20 : 
17:17:20 : Factory Erasing Supported FLASH AREA...
17:17:21 : Normal Factory Erase Done!
17:17:21 : 
17:17:21 : ======================================================
17:17:21 :     WARNING - WARNING - WARNING - WARNING - WARNING   
17:17:21 : ======================================================
17:17:21 :  1. WRITE BOOT1 Image if Needed                       
17:17:21 :  2. WRITE BOOT2 Image if Needed                       
17:17:21 :  3. WRITE USER AREA Image if Needed                   
17:17:21 : ======================================================

Блин как так? за секунду затерлась… а может быть ATF нас обманывает? Переподключаем

Код:

17:17:30 : Interface Reset OK!
17:17:30 : eMMC Access Type: SECTOR MODE
17:17:30 : eMMC Supported Voltage Range:
17:17:30 : 3.5-3.6V, 3.4-3.5V, 3.3-3.4V, 3.2-3.3V, 3.1-3.2V
3.0-3.1V, 2.9-3.0V, 2.8-2.9V, 2.7-2.8V, 1.9-2.0V
17:17:30 : 
17:17:30 : CID : 90014A484247346132A416C0B4424369
17:17:30 : CSD : D02701328F5903FFFFFFFFE78A400017
17:17:30 : 
17:17:30 : eMMC Boot Information
17:17:30 : Revision 1.x (For MMC v4.x)
17:17:30 : BOOT PARTITION     : USER AREA
17:17:30 : PARTITION ACCESS   : R/W USER PARTITION
17:17:30 : PERM_BOOT_CFG_PROT : DISABLED
17:17:30 : PWR_BOOT_CFG_PROT  : DISABLED
17:17:30 : BOOT MODE          : x1 SINGLE DATA RATE + LOW SPEED
17:17:30 : RESET BUS WIDTH    : ENABLED
17:17:30 : eMMC FirmW UPDATE  : DISABLED
17:17:30 : EMMC CACHE SIZE    : 0 KB
17:17:30 : SUPER PAGE SIZE    : 3072 KB
17:17:30 : HC ERASE GROUP SIZE: 512 KB
17:17:30 : USER AREA SIZE     : 31268536320 BYTES
17:17:30 : BOOT PARTITION SIZE: 4096 KB
17:17:30 : RPMB PARTITION SIZE: 4096 KB
17:17:30 : 
17:17:30 : 
17:17:30 : eMMC Device Information
17:17:30 : Manufacturer ID: HYNIX
17:17:30 : Device Type    : Embedded BGA
17:17:30 : Application ID : 4A
17:17:30 : Product Name   : HBG4a2
17:17:30 : Product Rev    : 10.4
17:17:30 : Product SN     : 16C0B442
17:17:30 : Manufactured   : January 2000
17:17:30 : 
17:17:30 : Card Specific Data
17:17:30 : CSD_STRUCTURE     : Extended
17:17:30 : SPEC_VERS         : Version 4.1/4.2/4.3
17:17:30 : TAAC              : 13 ns
17:17:30 : TRAN_SPEED        : 4000000 KHz
17:17:30 : READ_BL_LEN       : 512 Bytes
17:17:30 : C_SIZE            : HIGH CAPACITY
17:17:30 : WP_GRP_ENABLE     : YES
17:17:30 : WRITE_BL_LEN      : 512 Bytes
17:17:30 : CONTENT_PROT_APP  : NO
17:17:30 : PERM_WRITE_PROTECT: NO
17:17:30 : TMP_WRITE_PROTECT : NO
17:17:30 : 
17:17:30 : Extended CSD Saved:
17:17:30 : 90014A484247346132A416C0B4424369.ext_csd
17:17:30 : Backup Directory:
17:17:30 : C:AdvanceBox Turbo FlashereMMCEXT_CSD
17:17:30 : 
17:17:31 : 
17:17:31 : Dumping Custom Region
17:17:31 : Please wait for some time...
17:17:31 : Partition Selected: USER AREA
17:17:31 : (eMMC Clock 7500000 Hz)
17:17:31 : 
17:17:31 : Custom Block Read OK
17:17:31 : File Saved: C:AdvanceBox Turbo FlashereMMCRecoveredeMMC_GPT.bin
17:17:31 : 
17:17:31 : Total Elapsed Time 00:00:00
17:17:31 : 
17:17:31 : EFI Partition Table Header
17:17:31 : ERROR: MBR + GPT Cannot be found!
17:17:31 : GUID Partition Table cannot be Extracted

Да нет, информации нет… Проверяем через Easy Tool

Код:

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.1

Loading eMMC Addon Firmware... IO: 1800 mV
Box С/Н: 1100D01D9A80AC56, ,Микропрограмма Вер.: 01.56
Напряжение подтяжки линии CMD :1680 mV
Напряжение активной линии CMD :1753 mV
Box IO Level:1800 mV
CLK Rate:14000 khz
HiPower mode is off!
---------- eMMC Device Information ----------


EMMC CID : 90014A484247346132A416C0B4424368

EMMC CSD : D02701328F5903FFFFFFFFE78A400016

Изготовитель eMMC: ID: 0090 , OEM ID: 014A
EMMC Date: 04/2016  Rev.0xA4
EMMC NAME: HBG4a2 , S/N:  381727810
EMMC NAME (HEX): 48424734613200 
EMMC ROM1 (Main User Data)   Capacity: 29820 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 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 Unknown)

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 W protect group size [HC_WP_GRP_SIZE: 0x00000000]

Partitioning Support [PARTITIONING_SUPPORT]: 0x07

 Device support partitioning feature

 Device can have enhanced tech.

Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00

---------------------------------------------

Backup saved: HBG4a2_ 381727810_20161207_1719.extcsd
Searching for partition tables...
Partitioning not detected...
Сделано.

Собственно, вопрос: как вы так добавили функционал и не проверили?

Проверяли на ряде флешей — в которые ваш хиникс или тип такой как ваш хиникс не вошел. Это Раз.
Два — никакого официального анонса о данной функциональности не было — значит еще проводим тестирования для
того чтобы все по православному терлось ) Прога висит — значит Force Erase не возвращает ответ. Разберемся.

Проверяли на ряде флешей — в которые ваш хиникс или тип такой как ваш хиникс не вошел. Это Раз.
Два — никакого официального анонса о данной функциональности не было — значит еще проводим тестирования для
того чтобы все по православному терлось ) Прога висит — значит Force Erase не возвращает ответ. Разберемся.

Огаааа))))) Виновник происшествия найден))))) А с командой ATF не пробовали поговорить? может они не жадные и поделятся решением? Просто там всегда секунды занимает и еще не видел чтобы живая флешка не стерлась.
PS. бочку ни на кого не качу, команда и так сделала очень много полезного. просто протестировал на том что под рукой было и тут же отрицательный результат, вот и отписался.

Огаааа))))) Виновник происшествия найден))))) А с командой ATF не пробовали поговорить? может они не жадные и поделятся решением? Просто там всегда секунды занимает и еще не видел чтобы живая флешка не стерлась.
PS. бочку ни на кого не качу, команда и так сделала очень много полезного. просто протестировал на том что под рукой было и тут же отрицательный результат, вот и отписался.

Разобрались — пробуем

купить чтобы получить доступ к скрытому контенту.

50 МБ
Просмотры: 101
50 МБ
Просмотры: 95
50 МБ
Просмотры: 99
24,5 МБ
Просмотры: 75

Последнее редактирование модератором: 10/12/16

KAPETZ

eMMC_tool Suite ver. 1.0.0.42
Microsoft Windows XP (32 bit) build 2600 (5.1.2600.6532)
На вкладке «Эксплорер»
«ечть данные из contact»(так написано по тому что текст больше чем кнопки, соседняя кнопка такая же)):icq03:

Я изначально был против смены языков, потому что вообще не представляю как кто-то может пользоваться программами с русским интерфейсом
Если сильно хочется чтобы всё влезало — можно изменить спец.программами перевод в файле default.mo в папке /Languages/ru/

Mumang

А там что русский был? Я лет 5-6 назад Ufs на русский переключил, исплевался и выключил) Приделать по adb из под root слитие разделов в rawprogram0.xml реально? Mprg+mbn сами подставим)))
Хотя бы бинарниками по размеру раздела, подрежем сами тоже,извращаться с донорскими по адресации уже усталось)

KAPETZ

EasyJtag Suite Classic ver.: 2.5.0.4 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows XP (build 2600, Service Pack 3). Admin rights FAIL
undefined
Android Explorer ver.: 1.0.0.19
eMMC ODIN ver.: 1.0.11.10
Successfully connected to box on COM10
Заметил такую штуку:
Если лью фулл с верфикацией (16Гб), через вкладку флешер, постоянно вывалюются ошибки в разных местах и обрывается запись в разных местах хотя галочка (остановки при ошибке) ВЫКЛЮЧЕНА!
Если лью фулл через вкладку «Regions» — вообще нет ошибок никаких…..
Если пишу через :
eMMC_tool Suite ver. 1.0.0.42
Microsoft Windows XP (32 bit) build 2600 (5.1.2600.6532)
Все ок, ошибки пытается перезаписать заново и бе3 проблем проливает все 16Гб:icq10:
Ещё замечания по Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4
Что не сохраняет логи(
Народ, проверьте пожалуйста у себя!

Последнее редактирование: 21/12/16

EasyJtag Suite Classic ver.: 2.5.0.4 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows XP (build 2600, Service Pack 3). Admin rights FAIL
undefined
Android Explorer ver.: 1.0.0.19
eMMC ODIN ver.: 1.0.11.10
Successfully connected to box on COM10
Заметил такую штуку:
Если лью фулл с верфикацией (16Гб), через вкладку флешер, постоянно вывалюются ошибки в разных местах и обрывается запись в разных местах хотя галочка (остановки при ошибке) ВЫКЛЮЧЕНА!
Если лью фулл через вкладку «Regions» — вообще нет ошибок никаких…..
Если пишу через :
eMMC_tool Suite ver. 1.0.0.42
Microsoft Windows XP (32 bit) build 2600 (5.1.2600.6532)
Все ок, ошибки пытается перезаписать заново и бе3 проблем проливает все 16Гб:icq10:
Ещё замечания по Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4
Что не сохраняет логи(
Народ, проверьте пожалуйста у себя!

Правили баг с логом. Если софта имеет права админимтратора то хранит логи рядом
если же нет то должна сохранять в следующих папках

В Microsoft Windows Vista & Windows 7 в :
C:ProgramDataZ3XAppData

В Microsoft Windows 98, Windows Me, Windows 2000, Windows 2003, и Windows XP :
C:Documents and SettingsAll UsersApplication DataZ3XAppData

KAPETZ

Спасибо, нашел!
C:Documents and SettingsAll UsersApplication DataZ3XAppsDataLogs (так будет точнее)

Потерял разделы махом при попытке слить dump firmware emmc

Код:

Running:SAMSUNG: MoviNAND Firmware extraction...
Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4

Загрузка Модуля eMMC
Напряжение подтяжки линии CMD :3186 mV
Напряжение активной линии CMD :3238 mV
Box IO Level:3300 mV
CLK Rate:3000 khz
--- EasyJTAG Samsung eMMC Backup Tool ---

EMMC CID : 150100434A4E423452070A0FE289532C

EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2016  Rev.0x7
EMMC NAME: CJNB4R , S/N:  168813193
EMMC Part Number: Unknown
EMMC ROM1 (Main User Data)   Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data...
EMMC FW Read Failed, Reason: CMD Timeout Error 
Сделано.

Done with error(s)

Running:SAMSUNG: MoviNAND Firmware extraction...
Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :3186 mV
Напряжение активной линии CMD :3238 mV
Box IO Level:3300 mV
CLK Rate:3000 khz
--- EasyJTAG Samsung eMMC Backup Tool ---

EMMC CID : 150100434A4E423452070A0FE289532C

EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2016  Rev.0x7
EMMC NAME: CJNB4R , S/N:  168813193
EMMC Part Number: Unknown
EMMC ROM1 (Main User Data)   Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data...
EMMC FW Read Failed, Reason: CMD Timeout Error 
Сделано.

Done with error(s)

Running:SAMSUNG: MoviNAND Firmware extraction...
Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :3186 mV
Напряжение активной линии CMD :3238 mV
Box IO Level:3300 mV
CLK Rate:3000 khz
--- EasyJTAG Samsung eMMC Backup Tool ---

EMMC CID : 150100434A4E423452070A0FE289532C

EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2016  Rev.0x7
EMMC NAME: CJNB4R , S/N:  168813193
EMMC Part Number: Unknown
EMMC ROM1 (Main User Data)   Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data...
EMMC FW Read Failed, Reason: CMD Timeout Error 
Сделано.

Done with error(s)

Running:SAMSUNG: MoviNAND Firmware extraction...
Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :3186 mV
Напряжение активной линии CMD :3238 mV
Box IO Level:3300 mV
CLK Rate:21000 khz
--- EasyJTAG Samsung eMMC Backup Tool ---

EMMC CID : 150100434A4E423452070A0FE289532C

EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2016  Rev.0x7
EMMC NAME: CJNB4R , S/N:  168813193
EMMC Part Number: Unknown
EMMC ROM1 (Main User Data)   Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data...
EMMC FW Read Failed, Reason: CMD Timeout Error 
Сделано.

Done with error(s)

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.4

Loading eMMC Addon Firmware... IO: 3300 mV
Box С/Н: 0C00C017991EA990, ,Микропрограмма Вер.: 01.58
Напряжение подтяжки линии CMD :3196 mV
Напряжение активной линии CMD :3238 mV
Box IO Level:3300 mV
CLK Rate:21000 khz
HiPower mode is off!
---------- eMMC Device Information ----------


EMMC CID : 150100434A4E423452070A0FE289532C

EMMC CSD : D02701320F5903FFF6DBFFEF8E40400C

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2016  Rev.0x7
EMMC NAME: CJNB4R , S/N:  168813193
EMMC NAME (HEX): 434A4E42345200 
EMMC ROM1 (Main User Data)   Capacity: 59640 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 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 Unknown)

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 W protect group size [HC_WP_GRP_SIZE: 0x00000000]

Partitioning Support [PARTITIONING_SUPPORT]: 0x07

 Device support partitioning feature

 Device can have enhanced tech.

Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00

---------------------------------------------

Backup saved: CJNB4R_ 168813193_20170201_1849.extcsd
Searching for partition tables...
Partitioning not detected...
Сделано.

Вот лог easy jtag 2.5.0.4 при попытке слить дамп прошивки флеши.Благо фулл слил до этого.Раздел user data правда не сливал.Но когда пролил фулл он воскрес вместе с данными.Я и не думал что при слитии дампа такое может быть.Windows 10 pro x64

Off-top
Блин честно у команды реально работа тяжелая!
Когда z3x team выпустили бету и пришло уведомление о первом баге)))

На версии 2.5.0.7 финалка ,которую NoName выложил не смог запустить direct emmc samsung flasher. Точнее он запустился и завис…и так три раза .Мож установилось криво чего.

Extended CSD rev 1.8 (MMC Unknown)

Что за флеха? И с какого аппарата?

KAPETZ

Extended CSD rev 1.8 (MMC Unknown)

Что за флеха? И с какого аппарата?

А что удивительного?
Вот к примеру :
Xiaomi NOTE 3

Напряжение подтяжки линии CMD :2464 mV
Напряжение активной линии CMD :2547 mV
Box IO Level:3300 mV
CLK Rate:21000 khz
HiPower™ mode is off!
eMMC Device Information
EMMC CID : 110100303136473332007F7C25B3C2F2
EMMC CSD : D02700328F5903FFFFFFFFE7864000A6
Изготовитель eMMC: ID: 0011 , OEM ID: 0100
EMMC Date: 12/2015 Rev.0x0
EMMC NAME: 016G32 , S/N: 2138842547
EMMC NAME (HEX): 30313647333200
EMMC ROM1 (Main User Data) Capacity: 15028 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD rev 1.8 (MMC Unknown)
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 W protect group size [HC_WP_GRP_SIZE: 0x00]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00

Extended CSD rev 1.8 (MMC Unknown)

Что за флеха? И с какого аппарата?

Samsung eMMC 5.1…

А что удивительного?
Вот к примеру :
Xiaomi NOTE 3

Напряжение подтяжки линии CMD :2464 mV
Напряжение активной линии CMD :2547 mV
Box IO Level:3300 mV
CLK Rate:21000 khz
HiPower™ mode is off!
eMMC Device Information
EMMC CID : 110100303136473332007F7C25B3C2F2
EMMC CSD : D02700328F5903FFFFFFFFE7864000A6
Изготовитель eMMC: ID: 0011 , OEM ID: 0100
EMMC Date: 12/2015 Rev.0x0
EMMC NAME: 016G32 , S/N: 2138842547
EMMC NAME (HEX): 30313647333200
EMMC ROM1 (Main User Data) Capacity: 15028 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD rev 1.8 (MMC Unknown)
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 W protect group size [HC_WP_GRP_SIZE: 0x00]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00

Нечего удивительного, впервые вижу rev1.8 (5.1) eMMC. По этому спросил с какого аппарата.

Нечего удивительного, впервые вижу rev1.8 (5.1) eMMC. По этому спросил с какого аппарата.

При возможности — сообщите цоклевку флешки — добавим в поддержку.

Флеша с xiaomi mi max цоклёвка KLMCG4JENB ,а над этой надписью сверху B041

При возможности — сообщите цоклевку флешки — добавим в поддержку.

Я сам впервые вижу логии из rev 1.8 (5.1).

Подскажите пожалуйста это торба флешке?

Код:

EasyJtag Suite Classic ver.: 2.5.0.7 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows 8 (build 9200), 64-bit edition. Admin rights FAIL
undefined
Android Explorer ver.: 1.0.0.23 
eMMC ODIN ver.: 1.0.11.2 
Бокс найден на порте COM3 , все чип топ )))
Box С/Н: , ,Микропрограмма Вер.: 01.58
Режим Работы Бокса : JTAG Интерфейс
Вы используете самые свежие драйвера: 3.0.1.0 .
Z3X Card Serial :  ver: 22 
Z3X Card Activation [LG] : NOT ACTIVATED
Z3X Card Activation [SAMS] : ACTIVATED
Z3X Card Activation [JTAG] : ACTIVATED


Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7

Loading eMMC Addon Firmware... IO: 1850 mV
Box С/Н: 0C00C017991EA990, ,Микропрограмма Вер.: 01.58
Напряжение подтяжки линии CMD :2134 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
HiPower mode is off!
---------- eMMC Device Information ----------

EMMC CID : 3701FF454D4330384710F60000A12362
EMMC CSD : D00F01320F5903FFFFFFFFEF8E40407A
Изготовитель eMMC: ID: 0037 , OEM ID: 01FF
EMMC Date: 02/2016  Rev.0x10
EMMC NAME: EMC08G , S/N: 4127195297
EMMC NAME (HEX): 454D4330384700 
EMMC ROM1 (Main User Data)   Capacity: 7376 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 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.7 (MMC 5.0)
Boot configuration [PARTITION_CONFIG: 0x48] Boot from:ROM2 (Boot Partition 1)
Boot bus config [177]: 0x00 , width 1bit  , Partition config [179]: 0x48.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
 Device support partitioning feature
 Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: EMC08G_4127195297_20170215_2326.extcsd
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :2155 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
Erasing 200000000 bytes from 00000000 ...ROM1
Full Verify Enabled!
Erase Length has been corrected to 0x0001CD000000 bytes...
Verify Erased Block Failed , block #0x00000000
Verify Erased Block Failed , block #0x00000100
Verify Erased Block Failed , block #0x00000200
Verify Erased Block Failed , block #0x00000300
Erasing flash page stopped by user request
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :2145 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
Erasing 00400000 bytes from 00000000 ...ROM2
Full Verify Enabled!
Erase Done.

Короче пишется-читается только ром 2-3,а вот ром 1 ни вкакую.Флеша с полудохлого тела.После любых операций с ром 1 подвисает,нужно передёргивать питание чтоб виделась.На помойку её?

KAPETZ

Подскажите пожалуйста это торба флешке?

Код:

EasyJtag Suite Classic ver.: 2.5.0.7 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows 8 (build 9200), 64-bit edition. Admin rights FAIL
undefined
Android Explorer ver.: 1.0.0.23 
eMMC ODIN ver.: 1.0.11.2 
Бокс найден на порте COM3 , все чип топ )))
Box С/Н: , ,Микропрограмма Вер.: 01.58
Режим Работы Бокса : JTAG Интерфейс
Вы используете самые свежие драйвера: 3.0.1.0 .
Z3X Card Serial :  ver: 22 
Z3X Card Activation [LG] : NOT ACTIVATED
Z3X Card Activation [SAMS] : ACTIVATED
Z3X Card Activation [JTAG] : ACTIVATED


Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7

Loading eMMC Addon Firmware... IO: 1850 mV
Box С/Н: 0C00C017991EA990, ,Микропрограмма Вер.: 01.58
Напряжение подтяжки линии CMD :2134 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
HiPower mode is off!
---------- eMMC Device Information ----------

EMMC CID : 3701FF454D4330384710F60000A12362
EMMC CSD : D00F01320F5903FFFFFFFFEF8E40407A
Изготовитель eMMC: ID: 0037 , OEM ID: 01FF
EMMC Date: 02/2016  Rev.0x10
EMMC NAME: EMC08G , S/N: 4127195297
EMMC NAME (HEX): 454D4330384700 
EMMC ROM1 (Main User Data)   Capacity: 7376 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 4096 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 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.7 (MMC 5.0)
Boot configuration [PARTITION_CONFIG: 0x48] Boot from:ROM2 (Boot Partition 1)
Boot bus config [177]: 0x00 , width 1bit  , Partition config [179]: 0x48.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
 Device support partitioning feature
 Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
---------------------------------------------
Backup saved: EMC08G_4127195297_20170215_2326.extcsd
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :2155 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
Erasing 200000000 bytes from 00000000 ...ROM1
Full Verify Enabled!
Erase Length has been corrected to 0x0001CD000000 bytes...
Verify Erased Block Failed , block #0x00000000
Verify Erased Block Failed , block #0x00000100
Verify Erased Block Failed , block #0x00000200
Verify Erased Block Failed , block #0x00000300
Erasing flash page stopped by user request
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.5.0.7
Skip loading eMMC Addon Firmware
Напряжение подтяжки линии CMD :2145 mV
Напряжение активной линии CMD :1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
Erasing 00400000 bytes from 00000000 ...ROM2
Full Verify Enabled!
Erase Done.

Верно мыслите

Привет парни, почему не хочет писать прошивку целиком не подскажете???

Код:

Размер последней секции был обновлен

HiPower режим OFF
CMD Уровень подтяжки: 2145 mV
CMD Активный уровень: 2743 mV
EMMC Информация :
EMMC CID: 150100424A4E4234520736C7E82863B8
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400C
EMMC Manufacture Name: SAMSUNG
EMMC Имя: BJNB4R , S/N: 36C7E828 , версия. 07
eMMC имя (HEX): 424A4E423452
EMMC ROM 1 (Данные пользователя) Объем: 29820 MB (000747C00000)
EMMC ROM 2/3 (Загрузочный раздел 1/2) Объем: 4096 KB (000000400000)
eMMC RPMB (защищенный блок данных): емкость: 4096 KB (000000400000)
Бэкап сохранён: BJNB4R_36C7E828_20170402_084025.extcsd
EMMC Инициализация выполнена.

Операция: Запись по вендору (MediaTek)

Имя раздела: preloader
Имя файла: preloader_s2_plus.bin, смещение: 000000000000, размер файла: 191228 байт
Переключение eMMC на ROM2
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 199,86 Kb/s
Имя раздела: recovery
Имя файла: recovery-verified.img, смещение: 000000008000, размер файла: 20039680 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 639,04 Kb/s
Имя раздела: lk
Имя файла: lk-verified.bin, смещение: 00000F800000, размер файла: 428368 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 614,36 Kb/s
Имя раздела: boot
Имя файла: lk-verified.bin, смещение: 00000F900000, размер файла: 428368 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 635,20 Kb/s
Имя раздела: logo
Имя файла: logo-verified.bin, смещение: 000010900000, размер файла: 1307200 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 665,90 Kb/s
Имя раздела: system
Имя файла: system.img, смещение: 000012800000, размер файла: 2101381396 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Sparse image найдено v.1.0  Всего частей: 3946
Ошибка записи по адресу: 000013F9A000... Попытка #1
Ошибка записи по адресу: 0000147FE000... Попытка #1
Ошибка записи по адресу: 0000157F5000... Попытка #1
Ошибка записи по адресу: 0000157F5000... Попытка #2
Ошибка записи по адресу: 00001CFC5000... Попытка #1
Ошибка записи по адресу: 0000247B3000... Попытка #1
Ошибка записи по адресу: 0000247B3000... Попытка #2
Ошибка записи по адресу: 0000257EA000... Попытка #1
Ошибка записи по адресу: 0000257EA000... Попытка #2
Ошибка записи по адресу: 0000257EA000... Попытка #3
Ошибка записи по адресу: 0000297EB000... Попытка #1
Ошибка записи по адресу: 00002D7FF000... Попытка #1
Ошибка записи по адресу: 0000305EC000... Попытка #1
Ошибка записи по адресу: 0000307EC000... Попытка #1
Ошибка записи по адресу: 0000307EC000... Попытка #2
Ошибка записи по адресу: 000033FEF000... Попытка #1
Ошибка записи по адресу: 0000347EF000... Попытка #1
Ошибка записи по адресу: 0000347EF000... Попытка #2
Ошибка записи по адресу: 000036FBF000... Попытка #1
Ошибка записи по адресу: 00003B7FF000... Попытка #1
Ошибка записи по адресу: 00003BD7F000... Попытка #1
Ошибка записи по адресу: 00003DFFF000... Попытка #1
Ошибка записи по адресу: 00003DFFF000... Попытка #2
Ошибка записи по адресу: 00003DFFF000... Попытка #3
Ошибка записи по адресу: 00003E7FF000... Попытка #1
Ошибка записи по адресу: 00003F37F000... Попытка #1
Ошибка записи по адресу: 00003F7FF000... Попытка #1
Ошибка записи по адресу: 00003F7FF000... Попытка #2
Ошибка записи по адресу: 0000417F3000... Попытка #1
Ошибка записи по адресу: 000042FFE000... Попытка #1
Ошибка записи по адресу: 000042FFE000... Попытка #2
Ошибка записи по адресу: 000042FFE000... Попытка #3
Ошибка записи по адресу: 000044FE4000... Попытка #1
Ошибка записи по адресу: 000045FCE000... Попытка #1
Ошибка записи по адресу: 000048805000... Попытка #1
Ошибка записи по адресу: 000049C5A000... Попытка #1
Ошибка записи по адресу: 000049FDA000... Попытка #1
Ошибка записи по адресу: 000049FDA000... Попытка #2
Ошибка записи по адресу: 000049FDA000... Попытка #3
Слишком много ошибок. Запись была остановлена

Вот ещё один лог

Код:

HiPower режим OFF
CMD Уровень подтяжки: 2134 mV
CMD Активный уровень: 2753 mV
EMMC Информация :
EMMC CID: 150100424A4E4234520736C7E82863B8
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400C
EMMC Manufacture Name: SAMSUNG
EMMC Имя: BJNB4R , S/N: 36C7E828 , версия. 07
eMMC имя (HEX): 424A4E423452
   EMMC ROM 1 (Данные пользователя) Объем: 29820 MB (000747C00000)
   EMMC ROM 2/3 (Загрузочный раздел 1/2) Объем: 4096 KB (000000400000)
   eMMC RPMB (защищенный блок данных): емкость: 4096 KB (000000400000)
Бэкап сохранён: BJNB4R_36C7E828_20170402_094618.extcsd
EMMC Инициализация выполнена.

Операция: Запись по вендору (MediaTek)

Создание GPT разметки
GPT разметка сделана

Имя раздела: preloader
Имя файла: preloader_s2_plus.bin, смещение: 000000000000, размер файла: 191228 байт
Переключение eMMC на ROM2
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 199,54 Kb/s
Имя раздела: scp1
Имя файла: tinysys-scp.bin, смещение: 00000F100000, размер файла: 198656 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 606,07 Kb/s
Имя раздела: scp2
Имя файла: tinysys-scp.bin, смещение: 00000F200000, размер файла: 198656 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 604,69 Kb/s
Имя раздела: tee1
Имя файла: trustzone.bin, смещение: 000011100000, размер файла: 478880 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 796,83 Kb/s
Имя раздела: tee2
Имя файла: trustzone.bin, смещение: 000011600000, размер файла: 478880 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Выполнена запись раздела. Write speed: 799,71 Kb/s
Имя раздела: system
Имя файла: system.img, смещение: 000012800000, размер файла: 2101381396 байт
Переключение eMMC на ROM1
Стирание раздела...
Запись раздела...
Sparse image найдено v.1.0  Всего частей: 3946
Ошибка записи по адресу: 000013F9A000... Попытка #1
Ошибка записи по адресу: 0000157F5000... Попытка #1
Ошибка записи по адресу: 0000157F5000... Попытка #2
Ошибка записи по адресу: 0000157F5000... Попытка #3
Ошибка записи по адресу: 000015FED000... Попытка #1
Ошибка записи по адресу: 00001CFC5000... Попытка #1
Ошибка записи по адресу: 00001CFC5000... Попытка #2
Ошибка записи по адресу: 000022FFE000... Попытка #1
Ошибка записи по адресу: 000022FFE000... Попытка #2
Ошибка записи по адресу: 0000277F9000... Попытка #1
Ошибка записи по адресу: 00002AFFF000... Попытка #1
Ошибка записи по адресу: 00002AFFF000... Попытка #2
Ошибка записи по адресу: 00002AFFF000... Попытка #3
Слишком много ошибок. Запись была остановлена

Последнее редактирование: 2/4/17

А сами не догадываетесь ?
Попробуйте сделать Format+Reset и снова записать прошивку. Если также будут сыпаться ошибки — выбросьте флэшку.

А сами не догадываетесь ?
Попробуйте сделать Format+Reset и снова записать прошивку. Если также будут сыпаться ошибки — выбросьте флэшку.

я понял сейчас попробую, а вообще должны же все файлы записатся?

Источник

Checking security …
Running:SAMSUNG: MoviNAND Firmware extraction…
Z3X EasyJtag Software ver. 3.7.0.23
Skip loading eMMC Addon Firmware
Box IO Level:2800 mV
CLK Rate:14000 kHz
Checking eMMC BootROM mode
Skip loading eMMC Addon Firmware
Box IO Level:2800 mV
CLK Rate:14000 kHz
— EasyJTAG Samsung eMMC Backup Tool —
EMMC CID : 150100334836434D4205C72DACA584B7
EMMC CSD : D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacturer ID: 0015 , OEM ID: 0100
EMMC Date: 08/2017 Rev.0x5
EMMC NAME: 3H6CMB , S/N: 3341659301
EMMC Part Number: KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254
IC Name: Samsung , KM3H6001CM-B515/64GB+LPDDR4 48Gb @FBGA254 ,
EMMC ROM1 (Main User Data) Capacity: 59640 MB
EMMC ROM2 (Boot Partition 1/2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
Reading eMMC Boot Identification Data…
EMMC FW Read Failed, Reason: CMD Timeout Error
Done.

Done with error(s)

i’m Try to read EMMC FW DUMP Face this error And EMMC dead ALL userpart lost Please FiX THis issue I try VIA isp same and disold EMMC And try to read

Источник

вот лог

eMMC_tool Suite ver. 1.6.4.0 (release date: 30.12.2020)
Microsoft Windows 7 (64 bit) build 7601 (6.1.7601.17965)

Поиск EasyJTAG …
EasyJTAG API версия. 3403
EasyJTAG серийный номер = AC4C5CD32E70D72E
Серийный номер карты = AA20BF4E
EasyJTAG прошивка = 2.5301

Список изменений:

30.12.2020 (ver 1.6.4.0)
Add: New keys for Oppo unpack
Fix: Fix LG Parser
Fix: Bugs that have been found through your crash report
Add: new version 2.0.0.0 (qualcomm, samsung)

Установка интерфейса EasyJtag2/ISP
Установка ширины шины 4 Bit
Установка частоты 18 MHz
CMD Уровень подтяжки: 1785 mV
CMD Активный уровень: 1815 mV
Не получилось инициализировать устройство. Причина: CMD Timeout Error

Установка интерфейса EasyJtag2/ISP
Установка ширины шины 4 Bit
Установка частоты 24 MHz
CMD Уровень подтяжки: 1793 mV
CMD Активный уровень: 1817 mV
Не получилось инициализировать устройство. Причина: CMD Timeout Error

Установка интерфейса EasyJtag2/ISP
Установка ширины шины 4 Bit
Установка частоты 24 MHz
CMD Уровень подтяжки: 1788 mV
CMD Активный уровень: 1860 mV
Не получилось инициализировать устройство. Причина: CMD Timeout Error

Установка интерфейса EasyJtag2/ISP
Установка ширины шины 1 Bit
Установка частоты 24 MHz
CMD Уровень подтяжки: 1806 mV
CMD Активный уровень: 1873 mV
Не получилось инициализировать устройство. Причина: CMD Timeout Error

Источник

prateek244024

New member

Joined: Sep 15, 2016

Messages: 10

Reaction score: 0

Points: 0

Location: nagaur

every time i get this error
Loading eMMC Addon Firmware… IO: 1850 mV
Box S/N: 1900402096A7CE47, ,FW Ver.: 01.58
CMD Pullup Level:1773 mV
CMD Active Level:1804 mV
Box IO Level:1850 mV
CLK Rate:14000 khz
HiPower mode is ON!
Can’t init device, Reason: CMD Timeout Error
Done.

mymobile36

New member

Joined: Mar 26, 2016

Messages: 41

Reaction score: 0

Points: 0

Location: Chandwad

Same problem plz Help Expect My adaptar
Jtag- isp Adaptar MOORC ADAPTAR

try this jumper ways and post result

Attachments

21557473_117859768882816_7176062489899981120_n.jpg

67 KB

· Views: 2,533

try this jumper ways and post result

sem problem

gpg adapter sw and 3v3 means

Roshan.Rj

Member

Joined: Apr 22, 2017

Messages: 35

Reaction score: 0

Points: 6

Age: 27

Location: Bramhpuri

us gpg adapter
and connect usb in mobile

— — — Updated — — —

always us only gpg adapter

Источник

26.02.2016, 13:24

Проблема с восстановлением брикнутых EMMC

Всем привет.
Заранее извиняюсь если не в том разделе…
Ситуация следующая:

Накопилось достаточное количество брикнутых EMMC, которые до сих пор не могу восстановить. Конкретно это fw 4.41, которые штатно стояли в N8000, P5100, N7000, I9100.
Из оборудования z3x Easy Jtag, ATF, RIFF (бета тест EMMC)
Флешки которые восстанавливаются без проблем:

KMVTU000LM-B503 (I9300,N7100 16Gb)

KMV3W000LM-B310 (I9500 16Gb) — после восстановления приходится править имя в CID тем не менее полностью работает

KLMCG8GE4A-A001 (N8000 64Gb) — после восстановления правлю имя в CID, т.к. 0000, но полностью работает

KLMAG2GE2A-A001 (гда стоит не помню, 16Gb)

А вот флешки которые не могу восстановить никак:

KLMAG2GE4A-A001 (16Gb штатно стоит в Lenovo K900) 2шт

KLMAG2GE4A-A002 (16Gb штатно стоит в N8000, P5100) 10шт

KMV3U000LM-B304 (8Gb штатно вроде в I9100) 4шт

KMVYL000LM-B503 (I9100 16Gb) 5шт

Вопрос к тем кто восстанавливал. Как, чем (какой бокс, версия софта) и собственно логи…
На данный момент нахожу в сети логи удачных восстановлений z3x Jtag версия 2.0.1.0 этих флешек:
KLMAG2GE4A-A001
KMV3U000LM-B304
Но пробелма в том что сейчас не могу нигде найти эту версию. Спрашивал у NoName он отписался что выложит и прошло пол года…
Можно было бы сказать что EMMC бракованные если бы не их количество. Одна из KLMAG2GE4A-A001 брикнулась у меня на руках. При замыкании Nand_RE естесственно в режим прошивки падают и восстановление проходит до момента зписи CID после этого труп. KLMAG2GE4A-A001, KLMAG2GE4A-A002 прошиваются до конца прошивкой от KLMAG2GE2A-A001 после чего постоянно висят в режиме прошивки что наводит на мысли о недоработке основного софта-прародителя (ATF)
Заранее спасибо за ответ.

Примеры логов:

KMV3U000LM-B304
Код:
Z3X EasyJtag Box JTAG Софт версия. 2.0.7.3
Loading eMMC Addon Firmware... IO: 1800 mV
Box С/Н: ****, ,Микропрограмма Вер.: 01.52
Напряжение подтяжки линии CMD :1959 mV
Напряжение активной линии CMD :1773 mV
HiPower™ mode is ON!
eMMC Device Information
EMMC CID : 150100303030303030002010021200E6

EMMC CSD : D02701320F5903FFF6DBFFE796404052

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 00/2013  Rev.0x0
EMMC NAME: <b>000000</b> , S/N:  537920018
EMMC NAME (HEX): 30303030303000 
EMMC ROM1 (Main User Data)   Capacity: 8192 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 1024 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 1024 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 1024 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
  Extended CSD rev 1.5 (MMC 4.41)

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]: 0x00

Backup saved: 000000_ 537920018_20160226_1234.extcsd
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.0.7.3
Loading eMMC Addon Firmware... IO: 1800 mV
Box С/Н: ****, ,Микропрограмма Вер.: 01.52
Напряжение подтяжки линии CMD :1959 mV
Напряжение активной линии CMD :1773 mV
Setup firmware update mode, wait 2..30 sec... 
Success!
Sending eMMC firmware...
Success!
Verifying eMMC firmware...
Success!
Flashing eMMC firmware...
Success!
Repairing eMMC CID...
Now Reconnect all eMMC Lines [POWER, CMD, CLK, DAT0]!
Do it until progress bar is moving (20 sec timeout)!
Can't write eMMC CID, Reason: CARD Ready Timeout Error 
Сделано.
KLMAG2GE4A-A001/KLMAG2GE4A-A002
Код:
Z3X EasyJtag Box JTAG Софт версия. 2.0.7.3
Loading eMMC Addon Firmware... IO: 1800 mV
Box С/Н: ***, ,Микропрограмма Вер.: 01.52
Напряжение подтяжки линии CMD :1938 mV
Напряжение активной линии CMD :1773 mV
HiPower™ mode is off!
eMMC Device Information
EMMC CID : 1501004D414732474156201107265842

EMMC CSD : 902701320F5903FFF6DBFFEF8A404022

Изготовитель eMMC: ID: 0015 , OEM ID: 0100
EMMC Date: 05/2005  Rev.0x56
EMMC NAME: <b>MAG2GA</b> , S/N:  537986854
EMMC NAME (HEX): 4D414732474100 
EMMC ROM1 (Main User Data)   Capacity: 16384 MB
EMMC ROM2 (Boot Раздел 1) Емкость: 512 kB
EMMC ROM3 (Boot Раздел 2) Емкость: 512 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 128 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
  Extended CSD rev 1.5 (MMC 4.41)

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]: 0x00

Backup saved: MAG2GA_ 537986854_20160226_1434.extcsd
Searching for partition tables...
Partitioning not detected...
Сделано.

Z3X EasyJtag Box JTAG Софт версия. 2.0.7.3
Loading eMMC Addon Firmware... IO: 1800 mV
Box С/Н: ***, ,Микропрограмма Вер.: 01.52
Напряжение подтяжки линии CMD :1949 mV
Напряжение активной линии CMD :1763 mV
Setup firmware update mode, wait 2..30 sec... 
Success!
Sending eMMC firmware...
Success!
Flashing eMMC firmware...
Success!
Repairing eMMC CID...
Now Reconnect all eMMC Lines [POWER, CMD, CLK, DAT0]!
Do it until progress bar is moving (20 sec timeout)!
Can't init device, Reason: OCR Ready Timeout Error [Check VCC or eMMC DEAD] 
Сделано.
PS. Если у кого-то все таки остался EASY JTAG 2.0.1.0 выложите плиз. Благодарю

8 участника(ов) поблагодарили slaventiy76 за его сообщение:

amdnow! (28.11.2017),

F2D (09.04.2021),

IDLER (24.08.2017),

mshibo (09.04.2017),

neytrone (14.07.2016),

Radiotrance (29.06.2016),

renat_d (01.07.2017),

Олегъ (04.12.2017)

Источник

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

16Gb eMMC died

I purchased an Odroid-U2, a 16Gb eMMC and a 5V/2A Adaptor back in January. At first I had some trouble getting data to the eMMC through the microSD adapter. Non of my card readers were able to detect it. But I bought some more card-readers and finally found one that worked. I filled the eMMC with the Linaro Ubuntu dist and everything was fine and rosy.

The yesterday I got some alarming errors with failures writing to the file-system. I tried to reboot, but it just locked up. I cut the power an turned it back on. The blue LED never starts to flash so something was seriosly broken. I can’t read the eMMC throuh the microSD converter either. Stone dead

Could this be anything other than a HW failure?

How do I go about to do an RMA?

Thanks!

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Tue Mar 05, 2013 3:48 pm

Do you have any microSD card to test your U2?
Let’s check whether your U2 is okay or not first.

Here are steps..
Make a bootable microSD and test your board without eMMC.
If your board is okay with microSD, plug eMMC and Micro-SD at the same time to find a solution.

Do you have a USB-UART kit? If yes, it will be very helpful to fix the issue,

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Wed Mar 06, 2013 3:00 pm

Hi,

Yes I have a microSD. I just loaded it with Linaro Ubuntu and it booted right off. No problems.

The board won’t boot when both eMMC and the microSD are connected though. The blue LED is not flashing, just constant dim light.

No, I’m sorry but I don’t have an USB-UART kit

Thanks,

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Wed Mar 06, 2013 3:52 pm

One more question.
When you installed the only eMMC, what was the state of blue LED?
Is it solid dim light?

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Wed Mar 06, 2013 4:47 pm

Yes, the behavior when having just the eMMC was as far as I could see identical to when having both eMMC and microSD connected. Constant dim blue light.

Thanks,

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Wed Mar 06, 2013 7:14 pm

Your eMMC is still alive.
The dim blue light means boot-loader is loaded and running.

Can you try other USB momory card reader?

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Thu Mar 07, 2013 2:00 am

Ah right, I see, that’s good news then
There is no blue dim light with no media is connected at all. Great.

Regarding card reader. As I wrote before, I had some problems finding one that worked to begin with. Only one worked. I’ve tried all again and none work now. Do you know what is is that make it work with some readers and others not? Does not give the best impression stability wise.

Maybe I can access it through the U2.
Is there any way to boot from the microSD when the eMMC is connected?
or
Is there any way to get the eMMC visiable in Linaro Ubuntu if it’s connected after Linao Ubunto has been booted from the microSD?

Thanks

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Thu Mar 07, 2013 4:50 pm

I think our eMMC reader has a mechanical tolerance issue on thickness.
We are using a cheap USB memory card reader of Transcend.

If the eMMC driver is a module(.ko), you can load it after booting from microSD card.
But it is not a module driver…

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Thu Mar 07, 2013 6:32 pm

Ok thanks.

If the problem is purely mechanical I can try to fiddle a bit more with my current readers. I did shave of some of the edges in my attempts to get the first readers to work. I never experiences any random stability. The one reader that worked, worked all the time. On the other hand I didn’t try too many times. Once I flashed the eMMC it went into the U2

I’ll try to fiddle some more to rule out the the purely mechanical aspect.

You say the eMMC driver isn’t a module. Is this true for all OS:es or just Ubuntu? There is no way I can flash it bu booting say Android from the uSD and connect the eMMC post boot?

Thanks

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Fri Mar 08, 2013 1:28 am

After countless attempts I’m quite confident it’s not due to simple mechanical issues. The eMMC is simply not responding as it used to.

Again:
You say the eMMC driver isn’t a module. Is this true for all OS:es or just Ubuntu? There is no way I can flash it bu booting say Android from the uSD and connect the eMMC post boot?

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Fri Mar 08, 2013 10:46 am

Yes, the eMMC driver is built in by default.. It can’t be a module due to some driver design.

Yes, you can flash from Android! However U2 will always attempt boot via eMMC instead of SD.

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Fri Mar 08, 2013 5:34 pm

Contact «odroid at hardkernel dot com» for RMA.
She will let you know how to do RMA.

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Thu Mar 14, 2013 1:21 am

The one I got working, at least before my eMMC died was «SKU 7134» from a Chinese web shop known for it’s dirt-cheap electronics and free world-wide shipping

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Thu Mar 14, 2013 1:36 am

I think a small warning is in order here. Note that the accessories only have 2 weeks of «warranty» and the only shipping option is the enormously expensive Fedex one. In short; the accessories better work or you are smoked!

Anyway, I move on. As I don’t have a 1.8v UART or can’t seem to get one shipped to me for a reasonable price, I simply made my own with an FPGA board. Works just fine

When I try to boot from the eMMC I get:

Code: Select all

U-Boot 2010.12-svn (Dec 21 2012 - 19:44:04) for Exynox4412


CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
APLL = 1000MHz, MPLL = 880MHz
DRAM:  2047 MiB

PMIC VERSION : 0x00, CHIP REV : 2
TrustZone Enabled BSP
BL1 version: 20121128


Checking Boot Mode ... EMMC4.41
REVISION: 2.0
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
MMC Device 0: 0 MB
MMC Device 1: 0 MB
MMC Device 2 not found
[ERROR] response timeout error : 00000104 cmd 18
mmc read failed
*** Warning - using default environment

ModeKey Check... run normal_boot
Net:   No ethernet found.
Hit any key to stop autoboot:  0
error during transfer: 0x00000204
mmc read failed
error during transfer: 0x00000204
mmc read failed
>>> Load Boot Script from mmc 0:1 <<<
error during transfer: 0x00000204
mmc read failed
there are pending interrupts 0x00000008
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
>>> Load Boot Script from mmc 0:2 <<<
error during transfer: 0x0000020c
mmc read failed
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
** Can't read from device 0 **

** Unable to use mmc 0:2 for fatload **
>>> Run Default Bootcmd <<<
reading kernel..device 0 Start 2455, Count 16384
MMC read: dev # 0, block # 2455, count 16384 ... [ERROR] response timeout error : 00000104 cmd 18
mmc read failed
-19 blocks read: ERROR
completed
reading RFS..device 0 Count 18839, Start 2048
MMC read: dev # 0, block # 18839, count 2048 ... [ERROR] response timeout error : 00000104 cmd 18
mmc read failed
-19 blocks read: ERROR
completed
Wrong Image Format for bootm command
ERROR: can't get kernel image!

I then tried the trick explained here http://fw.hardijzer.nl/?p=200

But the eMMC won’t play along

Various eMMC errors:

Code: Select all

...
[    3.504196] dw_mmc dw_mmc: Using internal DMA controller.
[    3.509420] mmc0: no vmmc regulator found
[    3.513615] dw_mmc dw_mmc: Version ID is 240a
[    3.517693] dw_mmc dw_mmc: DW MMC controller at irq 141, 32 bit host data width, 128 deep fifo
[    3.526489] sdhci: Secure Digital Host Controller Interface driver
[    3.532425] sdhci: Copyright(c) Pierre Ossman
[    3.536836] s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (440000000 Hz)
[    3.540050] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 400000Hz, actual 400000HZ div = 125)
[    3.553279] mmc1: no vmmc regulator found
[    3.557446] mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
[    3.564316] s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (440000000 Hz)
[    3.571155] mmc2: no vmmc regulator found
[    3.575305] mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
...
[    3.654463] mmc0: card has unknown MMCA version 6
...
[    3.837901] mmc0: error -22 whilst initialising MMC card
...
[    3.865042] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 300000Hz, actual 299401HZ div = 167)
...
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[    4.018979] mmc0: card has unknown MMCA version 6
[    4.019960] mmc0: error -22 whilst initialising MMC card
[    4.055055] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 200000Hz, actual 200000HZ div = 250)
[    4.195769] mmc0: card has unknown MMCA version 6
[    4.195832] mmc0: error -22 whilst initialising MMC card
[    4.230038] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 196079Hz, actual 196078HZ div = 255)
[    4.370870] mmc0: card has unknown MMCA version 6
[    4.370924] mmc0: error -22 whilst initialising MMC card
[    4.405106] mmc1: cmd 52 command timeout error
[    4.405249] mmc1: cmd 52 command timeout error
[    4.412586] mmc1: cmd 5 command timeout error
[    4.412737] mmc1: cmd 5 command timeout error
[    4.417073] mmc1: cmd 5 command timeout error
[    4.421409] mmc1: cmd 5 command timeout error
[    4.465222] mmc1: new high speed SDHC card at address aaaa
[    4.465566] mmcblk0: mmc1:aaaa SU08G 7.40 GiB 
[    4.470907]  mmcblk0: p1 p2
[    4.504968] mmc2: Internal clock never stabilised.
[    4.550043] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 400000Hz, actual 400000HZ div = 125)

Please also find the complete log attached.

The initial

Code: Select all

[    3.509420] mmc0: no vmmc regulator found

does not sound too good. Any idea what is wrong? Is it beyond any repair?

Thanks

Attachments

Odroid-U2.log: Complete log; (29.63 KiB) Downloaded 250 times

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Thu Mar 14, 2013 1:54 am

Is the eMMC seating ok? It comes with a small double-sided tape that sometimes cause it to not seat properly.
We saw this on the past. Do you fell a «click» when you connect it?
If you put a slightly force on the eMMC the errors appears?

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Thu Mar 14, 2013 2:32 am

Yeah, it clicks in nicely. The tape does not seem to be in the way.

I’ve tried booting while applying slight pressure to the card, but with the same results.

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Sat Mar 23, 2013 6:57 am

Could I please get any comment on what kind of error the log files suggest?

Thanks

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Sat Mar 23, 2013 7:08 am

It looks like that you got uart now ?

If so, try to boot with eMMC connected

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Sun Mar 24, 2013 11:29 pm

mdrjr wrote:It looks like that you got uart now ?

If so, try to boot with eMMC connected

Yep, used a old FPGA board I had laying around to do the level convertion of the UART.

I tried booting from the eMMC. See the first log in my previous post.

I then tried powering on the board with only uSD card attached, but interrupted autoboot, attached eMMC and continued to boot from uSD. Please see the second log in my previous post (also full log attached as file).

Both logs seem to indicate that the eMMC is not working properly. I’m wondering if these error messages give you an indication of what type of error it is.

Thanks

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Mon Mar 25, 2013 6:46 am

Its really weird. Its reading the eMMC, its loading the bootloaders from it.
However it can’t recognize the size.

I think its a defective module.

please contact odroid@hardkernel.com
with the thread link

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Tue Mar 26, 2013 12:36 am

I already did, but the 2 weeks of warranty is over
Service fee + two-way shipping would be too costly for me.

Thanks anyway

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Tue Mar 26, 2013 12:40 am

Since you look like someones that does have a good knowledge.

Here’s a idea… not sure if it will work ok?

1. Boot on the board with only eMMC connected.
2. Interrupt the boot sequence.
3. Type fastboot
4. Make sure you have a microUSB cable connected to the board and the latest Android SDK installed (that’s where fastboot is.)
5. Download -> http://www.mdrjr.net/odroid/mirror/dn.o … nel.tar.gz
6. On the sd_fuse folder run the emmc_fastboot_fusing.sh

It will replace your bootloaders with latest ones.

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Tue Mar 26, 2013 12:52 am

mdrjr wrote:Since you look like someones that does have a good knowledge.

Here’s a idea… not sure if it will work ok?

1. Boot on the board with only eMMC connected.
2. Interrupt the boot sequence.
3. Type fastboot
4. Make sure you have a microUSB cable connected to the board and the latest Android SDK installed (that’s where fastboot is.)
5. Download -> http://www.mdrjr.net/odroid/mirror/dn.o … nel.tar.gz
6. On the sd_fuse folder run the emmc_fastboot_fusing.sh

It will replace your bootloaders with latest ones.

It is possible if he has the USB-UART kit.

I think we need to make a special micro-SD card image which can recover the corrupted eMMC.
Here is the basic sequence of method.
Booting a Ubuntu image form SD card without eMMC.
And plug the eMMC module on ODROID and enable the one of power rail of PMIC for eMMC.
I’ll check the feasibility of this method with hardware guys.

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Wed Mar 27, 2013 3:23 am

mdrjr wrote:Since you look like someones that does have a good knowledge.

Here’s a idea… not sure if it will work ok?

1. Boot on the board with only eMMC connected.
2. Interrupt the boot sequence.
3. Type fastboot
4. Make sure you have a microUSB cable connected to the board and the latest Android SDK installed (that’s where fastboot is.)
5. Download -> http://www.mdrjr.net/odroid/mirror/dn.o … nel.tar.gz
6. On the sd_fuse folder run the emmc_fastboot_fusing.sh

It will replace your bootloaders with latest ones.

Thanks a lot!
I made it through all the steps. But it looks like the eMMC is still just failing

Code: Select all

U-Boot 2010.12-svn (Dec 21 2012 - 19:44:04) for Exynox4412


CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
APLL = 1000MHz, MPLL = 880MHz
DRAM:  2047 MiB

PMIC VERSION : 0x00, CHIP REV : 2
TrustZone Enabled BSP
BL1 version: 20121128


Checking Boot Mode ... EMMC4.41
REVISION: 2.0
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
MMC Device 0: 0 MB
MMC Device 1: 0 MB
MMC Device 2 not found
[ERROR] response timeout error : 00000104 cmd 18
mmc read failed
*** Warning - using default environment

ModeKey Check... run normal_boot
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Exynos4412 #
Exynos4412 #
Exynos4412 #
Exynos4412 #
Exynos4412 # fastboot
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
[Partition table on MoviNAND]
ptn 0 name='fwbl1' start=0x8 len=N/A (use hard-coded info. (cmd: movi))
ptn 1 name='bl2' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 2 name='bootloader' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 3 name='tzsw' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 4 name='kernel' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 5 name='ramdisk' start=N/A len=0x4000(~16777216KB) (use hard-coded info. (cmd: movi))
OTG cable Connected!
Starting download of 15360 bytes

downloading of 15360 bytes finished
flashing 'fwbl1'
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing FWBL1 ..device 0 Start 0, Count 30
MMC write: dev # 0, block # 0, count 30 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
partition 'fwbl1' flashed
Starting download of 14592 bytes

downloading of 14592 bytes finished
flashing 'bl2'
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing BL2 ..device 0 Start 30, Count 32
MMC write: dev # 0, block # 30, count 32 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
partition 'bl2' flashed
Starting download of 295108 bytes

downloading of 295108 bytes finished
flashing 'bootloader'
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing bootloader..device 0 Start 62, Count 2048
MMC write: dev # 0, block # 62, count 2048 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
[ERROR] response timeout error : 00000114 cmd 25
mmc write failed
partition 'bootloader' flashed
Starting download of 159744 bytes

downloading of 159744 bytes finished
flashing 'tzsw'
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing 0 TrustZone S/W.. Start 2110, Count 312
MMC write: dev # 0, block # 2110, count 312 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
partition 'tzsw' flashed

It was worth a try though! Thanks a lot!

Last edited by phr33 on Wed Mar 27, 2013 3:50 am, edited 2 times in total.

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Wed Mar 27, 2013 3:30 am

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Wed Mar 27, 2013 3:50 am

Man you are quick!
I just updated my previous post as I succeed in compiling uboot. But it looks like the eMMC is borken beyond repair

Thanks

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Wed Mar 27, 2013 3:56 am

Yes sadly…

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Mon Apr 01, 2013 8:57 pm

Hi there,

Got a similar issue with my 16GB eMMC. It worked just fine until I have unplugged it from the board to write Ubuntu on it. Did not even get to that stage as I have realised I only have an microSD adapter (could not find my microSD reader) and I was not sure if this is going to work with an adapter. Thus, I have ordered an microSD reader from eBay. I am still waiting for that reader but in the meanwhile I have plugged in my eMMC back, it clicked so it was in place but the U2 did not boot anymore. I only got a solid red light showing it is powered.

I have also tried the board with both eMMC and an microSd card connected and I get a dim blue light as mentioned previously. I think my eMMC died as well. My U2 starts ok with an microSD card. I have written an image on the microSD card and tried it that way and it worked just fine. I have emailed Hardkernel but I was told to post my issue on the forum. The thing is that I have already ordered some other accessories a few days ago and until I am fixing the problem with my current eMMC I have ordered a second one. However, I would like to know what to do to get the one that I currently have sorted.

I would love to get a replacement but also if there is any solution that I have not tried please let me know.

Thanks.

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Mon Apr 01, 2013 11:12 pm

I’ll release a updated win32DiskImager tomorrow. Give me 24hours.
I hope it can resolve your eMMC issue.

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Wed Apr 03, 2013 4:41 pm

Thanks!

I’ll have a look at it when I get home. Unfortunately I don’t see how it could work though. It’s not recognized in windows as a drive.

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Wed Apr 03, 2013 6:08 pm

I still have a doubt about the USB memory reader.
Some readers have the mechanical contact issue.

Anyway, we are making a special SD card image can recover the broken bootloader in eMMC.
Here is a preliminary instruction.
1. Flash eMMC recovery image on your SD card.
2. Boot with only the SD card and wait 3~4 seconds
3. plug the eMMC module on U2 and plug micro-USB cable which is connected to PC.
4. Wait 10 seconds
And your eMMC will be recovered and accessible in your PC.

I think we can release this tool within couple of days.

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Thu Apr 04, 2013 2:02 am

Is the recovery image available or is it going to be available soon? I have the same issue here. I have received my microSD reader but my eMMC is not recognised on my PC. I have tried it with both microSD reader and adapter and no joy.

Thanks.

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Thu Apr 04, 2013 7:09 am

imdag wrote:Is the recovery image available or is it going to be available soon? I have the same issue here. I have received my microSD reader but my eMMC is not recognised on my PC. I have tried it with both microSD reader and adapter and no joy.

Thanks.

Its really the same problem?
Do you have a uart kit ? What’s the output say?

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Thu Apr 04, 2013 4:11 pm

I forgot to get an uart kit when I have ordered extra peripherals from Gatekeeper, thus I do not have one. Now the order has been dispatched and it would be to expensive to order it now as it has to come in UK . I will try this tool later today.

Thanks.

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Thu Apr 04, 2013 4:16 pm

Also, yesterday I have realised that when I connect the card reader with the eMMC attached it appears in My Computer and then disappears. I have searched for it in devices and it says No Media.

phr33: Posts: 18; Joined: Tue Feb 26, 2013 6:15 pm; languages_spoken: english; ODROIDs: U2; Location: Europe; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by phr33 » Fri Apr 05, 2013 4:14 am

I just tried the eMMC recover image. It seems to work as intended, but my eMMC is probably broken beyond repair.

Here is the UART output of the failed recovery for reference:

Code: Select all

U-Boot 2010.12-svn (Apr 03 2013 - 18:05:01) for Exynox4412


CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
APLL = 1000MHz, MPLL = 880MHz
DRAM:  2047 MiB

PMIC VERSION : 0x00, CHIP REV : 2
TrustZone Enabled BSP
BL1 version: 20121128


Checking Boot Mode ... SDMMC
MMC Device 0: 7580 MB
MMC Device 1 not found
*** Warning - using default environment

Insert eMMC Module before usb connect....
Trigger Detected... read boot.scr form SDMMC & boot
>>> Load Boot Script from mmc 0:1 <<<
Partition1: Start Address(0x30d40), Size(0x5000)
reading boot.scr
Warning : Reads a file that is smaller than the cluster size.

1342 bytes read
## Executing script at 40008000
emmc reset...
REVISION: 2.0
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
Device: S5P_MSHC4
Manufacturer ID: 3c
OEM: 3c00
Name: Tran Speed: 0
Rd Block Len: 1
MMC version 0.0
High Capacity: No
Size: 0MB (block: 4)
Bus Width: 1-bit
Boot Partition Size: 0 KB
Partition1: Start Address(0x30d40), Size(0x5000)
reading bl1.bin

15360 bytes read
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing FWBL1 ..device 1 Start 0, Count 30
MMC write: dev # 1, block # 0, count 30 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
Partition1: Start Address(0x30d40), Size(0x5000)
reading bl2.bin

16384 bytes read
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing BL2 ..device 1 Start 30, Count 32
MMC write: dev # 1, block # 30, count 32 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
Partition1: Start Address(0x30d40), Size(0x5000)
reading tzsw.bin

159744 bytes read
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing 1 TrustZone S/W.. Start 2110, Count 312
MMC write: dev # 1, block # 2110, count 312 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
Partition1: Start Address(0x30d40), Size(0x5000)
reading u-boot.bin

277164 bytes read
eMMC OPEN Success.!!
                        !!!Notice!!!
!You must close eMMC boot Partition after all image writing!
!eMMC boot partition has continuity at image writing time.!
!So, Do not close boot partition, Before, all images is written.!
writing bootloader..device 1 Start 62, Count 2048
MMC write: dev # 1, block # 62, count 2048 ... [ERROR] response timeout error : 00000114 cmd 25
mmc write failed
-19 blocks written: ERROR
completed
eMMC CLOSE Success.!!
[ERROR] response timeout error : 00000114 cmd 24
mmc write failed
error during transfer: 0x00000204
mmc read failed
Start format MMC&d partition&d ...
there are pending interrupts 0x00000008
[ERROR] response timeout error : 00000104 cmd 17
mmc read failed
** Can't read from device 1 **
Format failure!!!

Thanks

odroid: Site Admin; Posts: 40594; Joined: Fri Feb 22, 2013 11:14 pm; languages_spoken: English, Korean; ODROIDs: ODROID; Has thanked:
3021 times; Been thanked:
1676 times; Contact:

Re: 16Gb eMMC died

Post

by odroid » Fri Apr 05, 2013 9:21 pm

phr33 wrote:I just tried the eMMC recover image. It seems to work as intended, but my eMMC is probably broken beyond repair.

Yes..
Please contact odroid at hardkernel dot com.
She will help your RMA process.

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Sat Apr 06, 2013 1:04 am

Same here, the recovery image worked as described but nothing changed in the eMMC case. I actually bought the exact same card reader as the one on the forum, transcend. However, my PC does not recognize my eMMC. Monday or Tuesday I will receive the second eMMC and I can try the board with the eMMC to see if this works. Unfortunately I cannot debug as I do not have the uart module.

Thanks.

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Wed Apr 10, 2013 6:48 am

Hi there, after testing everything I have sent an email for an RMA, so far no reply. What do I need to do to get my eMMC replaced.

Thanks.

mdrjr: Site Admin; Posts: 11834; Joined: Fri Feb 22, 2013 11:34 pm; languages_spoken: english, portuguese; ODROIDs: —; Location: Brazil; Has thanked:
1 time; Been thanked:
65 times; Contact:

Re: 16Gb eMMC died

Post

by mdrjr » Wed Apr 10, 2013 7:35 am

imdag wrote:Hi there, after testing everything I have sent an email for an RMA, so far no reply. What do I need to do to get my eMMC replaced.

Thanks.

Wait ~24 hours for your e-mail to be replied. Timezones. ;(

imdag: Posts: 7; Joined: Mon Apr 01, 2013 8:37 pm; languages_spoken: english; ODROIDs: Odroid U2; Has thanked:
0; Been thanked:
0; Contact:

Re: 16Gb eMMC died

Post

by imdag » Fri Apr 12, 2013 6:06 am

Hi,

Yes, i honestly know about timezones . I got a reply and i think it was more than 24hours. Never mind, that is not an issue.
Thanks for the hard work.

All the best.

Who is online

Users browsing this forum: No registered users and 0 guests

Источник

Emmc fw read failed reason cmd timeout error

Easy JTAG PLUS Can’t init device, Reason: CMD Timeout Error

Mag25su

Layder

Z3X-Team

viktorfedynyak

Help KM3H6001CM not able to raed firmware

irfan111

Active Member

Tres-Pedik

Member

Hottstuff

Junior Member

Attachments

amir0179

Junior Member

Tres-Pedik

Member

Hojiakbar

Friend’s Martview

Проблема коннекта по ISP

Akir1

Emmc fw read failed reason cmd timeout error

prateek244024

New member

mymobile36

New member

Attachments

Roshan.Rj

Member

Проблема с восстановлением брикнутых EMMC

8 участника(ов) поблагодарили slaventiy76 за его сообщение:

16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Re: 16Gb eMMC died

Who is online

Читайте также: