Unbrick dead Samsung GT-i9250 Galaxy Nexus, GT-I9100G , GT-I9300 - Page 6 - GSM-Forum

p1ceus · 06-28-2012, 09:55

Hello guys,
I have a bricked Nexus that wont boot, only response is "OMAP4440" driver popping up in Windows. I installed the driver from the package from post #1 and this is what I get from cmd window:

Code:

» OMAPFlash v4.15 (Aug 12 2011)

» -v
» Entering parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt at line: 1
»     -omap 4
»     -t 36000
»     -p OMAP4460_TUNA_8G_HS_PRO
»     -2
»     -rxtx_trace
»     chip_download EMMC Targets\Projects\tuna\MLO_4460_HS_PRO
»     chip_download EMMC Targets\Projects\tuna\sbl.img
»     command cold_sw_reset
» Leaving parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
» @Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id

  00130-000-TX 4 raw bytes: 03 00 03 F0 '????'
» AsicId items 05
» AsicId id             01 05  01  44 40 07 01
» AsicId secure_mode    13 02  01  00
» AsicId public_id      12 15  01  F7 4E 95 42 0E 03 0F 91 21 E4 42 51 C9 0B CC 21 7D EC 40 FE
» AsicId root_key_hash  14 21  01  67 98 9B 35 54 CC 86 B4 67 32 47 05 36 74 E2 25 F0 9D A3 5C F4 59 B9 C9 3A 13 E0 B9 58 1E 5A BC
» AsicId checksum       15 09  01  22 9E 85 BA DC 58 74 BC

  00130-001-TX 4 raw bytes: 02 00 03 F0 '????'
» Searching 2nd for: OMAP4460_TUNA_8G_HS_PRO 444007 01 HS
» Loading second file Targets/2nd-Downloaders/dnld_startup_omap4_hs_8g_es2.s2.signed.2nd.hs_pro
» Entering parameter file:omapflash2nd.txt at line: 46
»     -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4460_tuna_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
»     -board_config Targets\Configurations\configuration_omap4460_tuna_8g.txt
» Leaving parameter file:omapflash2nd.txt
» Sending size of second file (0x000071B0 bytes)

  00130-002-TX 4 raw bytes: B0 71 00 00 '?q??'
» Transferring second file to target (0x71B0 bytes)

  00130-003-TX 29104 raw bytes: B0 1C 00 00 00 4D 00 00 00 00 00 00 00 00 00 00 '?????M??????????' ...
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
  00463-004-TX ACK
  00554-005-RX:OKAY: 2nd started
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 0 width 4 delay 9 rpapi_base 0x00030400
» Downloading driver
  00385-006-TX:driver EMMC sid 0 width 4 delay 9 rpapi_base 0x00030400
  00463-007-TX ACK
  00554-008-RX:OKAY: expecting download
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
  00385-009-TX:download:0000b838
  00527-010-RX:data00018000
» Sending data (47160 bytes) :::::::::::::....... [32768]
  00148-011-TX 32768 bin bytes
  00527-012-RX:data00013838
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
  00148-013-TX 14392 bin bytes
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
  00463-014-TX ACK
  00483-015-RX:INFO: Interface 'OMAPFLASH DRIVER v6'
          Interface 'OMAPFLASH DRIVER v6'
  00463-016-TX ACK
  00483-017-RX:INFO: Driver 'eMMC JESD84-A43'
          Driver 'eMMC JESD84-A43'
  00463-018-TX ACK
  00483-019-RX:INFO: Driver configuration: sid = 0x00000000
          Driver configuration: sid = 0x00000000
  00463-020-TX ACK
  00483-021-RX:INFO: Driver configuration: width = 0x00000004
          Driver configuration: width = 0x00000004
  00463-022-TX ACK
  00483-023-RX:INFO: Driver configuration: delay = 0x00000009
          Driver configuration: delay = 0x00000009
  00463-024-TX ACK
  00483-025-RX:INFO: Driver configuration: rpapi_base = 0x00030400
          Driver configuration: rpapi_base = 0x00030400
  00463-026-TX ACK
  00483-027-RX:INFO: MMC sid                = 0x00
          MMC sid                = 0x00
  00463-028-TX ACK
  00483-029-RX:INFO: MMC mmc_volt           = 0x01
          MMC mmc_volt           = 0x01
  00463-030-TX ACK
  00483-031-RX:INFO: MMC data_width         = 0x04
          MMC data_width         = 0x04
  00463-032-TX ACK
  00483-033-RX:INFO: MMC card_rca           = 0x00
          MMC card_rca           = 0x00
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x00
          MMC card_type          = 0x00
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x00
          MMC data_width_support = 0x00
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0x00
          MMC transfer_clk_max   = 0x00
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x00
          MMC card_size          = 0x00
  00463-042-TX ACK
  00483-043-RX:INFO: MMC mmc_config return 0x00FF8080
          MMC mmc_config return 0x00FF8080
  00463-044-TX ACK
  00483-045-RX:INFO: EMMC eMMC DRIVER DEINIT COMPLETE
          EMMC eMMC DRIVER DEINIT COMPLETE
  00463-046-TX ACK
  00494-047-RX:FAIL: Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Download failed (final data response error): Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Elapsed time: 0:05.445 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)
» Elapsed time: 0:20.860

(I first run the .bat file and then connect the phone without battery in it - but it is the same with battery inserted)

I also try this on W7 x64 and WXP x86 but no joy on any of these systems. Eve tried different USB cables, put the phone to fridge for few minutes (cuz I read about some heat sensor inside - also this trick helped me to fix my HTC Desire before

)

If I compare my log with log of xanders2615 (post #73) my differences starting here:

Code:

00483-033-RX:INFO: MMC card_rca           = 0x00
          MMC card_rca           = 0x00
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x00
          MMC card_type          = 0x00
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x00
          MMC data_width_support = 0x00
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0x00
          MMC transfer_clk_max   = 0x00
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x00
          MMC card_size          = 0x00

and he have it like this:

Code:

00483-033-RX:INFO: MMC card_rca           = 0x04
          MMC card_rca           = 0x04
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x03
          MMC card_type          = 0x03
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x08
          MMC data_width_support = 0x08
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0xBB80
          MMC transfer_clk_max   = 0xBB80
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x1D5A000
          MMC card_size          = 0x1D5A000

So just comes to my mind, is the internal memory broken/destroyed?

Thanks for the reply...

itsalllgood · 06-28-2012, 23:05

Mr legija..do you have any opnion on these logs...could a jtag resolve the ones that were not resurrected by this tool..is it possible to reformat the emmc..

cristipuc · 07-01-2012, 13:27

good work, i run this tool for my GN GSM version, and work great, no more rebooting !

BABAK NURI · 07-03-2012, 23:46

Quote:

00494-047-RX:FAIL: Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Download failed (final data response error): Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Elapsed time: 0:05.445 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)
» Elapsed time: 0:20.860

Hi
Yes,eMMC is damaged and need replace by new one

xanders2615 · 07-05-2012, 20:40

Quote:

Originally Posted by BABAK NURI

Hi
Yes,eMMC is damaged and need replace by new one

so p1ceus GN eMMC is damaged, mine is showing different information, Do you have any clue on what could be the issue with my GN? I try the OMAP Flash and it get stuck downloading data. Did you know if the JTAG could resurrect my phone?

Thank you.

sarahlegs · 07-12-2012, 05:06

Hi all,

I have a bricked 9250 Galaxy Nexus and tried using the awesome script that legjia so generously posted, but the tool appears to be hanging at one of the "Downloading" stages.

Any idea if there might be a setting I need to tweak, or do I just have dead memory/motherboard? If legjia, itsallgood or anyone else can help, I would be very grateful!

Output pasted below:

Code:

» OMAPFlash v4.15 (Aug 12 2011)

» -v
» Entering parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt at line
: 1
»     -omap 4
»     -t 36000
»     -p OMAP4460_TUNA_8G_HS_PRO
»     -2
»     chip_download EMMC Targets\Projects\tuna\MLO_4460_HS_PRO
»     chip_download EMMC Targets\Projects\tuna\sbl.img
»     command cold_sw_reset
» Leaving parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
» @Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id             01 05  01  44 40 07 01
» AsicId secure_mode    13 02  01  00
» AsicId public_id      12 15  01  5A A8 E8 A8 53 BD EE 8C D6 05 C2 49 0C 2C 43
E0 CB D6 17 C7
» AsicId root_key_hash  14 21  01  67 98 9B 35 54 CC 86 B4 67 32 47 05 36 74 E2
25 F0 9D A3 5C F4 59 B9 C9 3A 13 E0 B9 58 1E 5A BC
» AsicId checksum       15 09  01  22 9E 85 BA DC 58 74 BC
» Searching 2nd for: OMAP4460_TUNA_8G_HS_PRO 444007 01 HS
» Loading second file Targets/2nd-Downloaders/dnld_startup_omap4_hs_8g_es2.s2.si
gned.2nd.hs_pro
» Entering parameter file:omapflash2nd.txt at line: 46
»     -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4460
_tuna_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
»     -board_config Targets\Configurations\configuration_omap4460_tuna_8g.txt
» Leaving parameter file:omapflash2nd.txt
» Sending size of second file (0x000071B0 bytes)
» Transferring second file to target (0x71B0 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 0 width 4 delay 9 rpap
i_base 0x00030400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
          Interface 'OMAPFLASH DRIVER v6'
          Driver 'eMMC JESD84-A43'
          Driver configuration: sid = 0x00000000
          Driver configuration: width = 0x00000004
          Driver configuration: delay = 0x00000009
          Driver configuration: rpapi_base = 0x00030400
          MMC sid                = 0x00
          MMC mmc_volt           = 0x01
          MMC data_width         = 0x04
          MMC card_rca           = 0x04
          MMC card_type          = 0x03
          MMC data_width_support = 0x08
          MMC transfer_clk_max   = 0xBB80
          MMC card_size          = 0x1D5A000
          eMMC CID MID                      = 0x15       // Manufacturer ID
          eMMC CID CBX                      = 0x01       // Card/BGA
          eMMC CID OID                      = 0x00       // OEM/Application ID
          eMMC CID PNM                      = 0x34280000BEFB // Product name
          eMMC CID PRV                      = 0x25       // Product revision
          eMMC CID PSN                      = 0x0000BEFB // Product serial numbe
r
          eMMC CID MDT                      = 0xBE       // Manufacturing date
          eMMC CID CRC                      = 0x7D       // CRC7 checksum
          eMMC CSD CSD_STRUCTURE            = 0x03       // CSD structure
          eMMC CSD SPEC_VERS                = 0x04       // System specification
 version
          eMMC CSD TAAC                     = 0x27       // Data read access-tim
e 1
          eMMC CSD NSAC                     = 0x01       // Data read access-tim
e 2 in CLK cycles (NSAC*100)
          eMMC CSD TRAN_SPEED               = 0x32       // Max. bus clock frequ
ency
          eMMC CSD CCC                      = 0x00F5     // Card command classes

          eMMC CSD READ_BL_LEN              = 0x09       // Max. read data block
 length
          eMMC CSD READ_BL_PARTIAL          = 0x00       // Partial blocks for r
ead allowed
          eMMC CSD WRITE_BLK_MISALIGN       = 0x00       // Write block misalign
ment
          eMMC CSD READ_BLK_MISALIGN        = 0x00       // Read block misalignm
ent
          eMMC CSD DSR_IMP                  = 0x00       // DSR implemented
          eMMC CSD C_SIZE                   = 0x00FF     // Device size
          eMMC CSD VDD_R_CURR_MIN           = 0x06       // Max. read current @
VDD min
          eMMC CSD VDD_R_CURR_MAX           = 0x06       // Max. read current @
VDD max
          eMMC CSD VDD_W_CURR_MIN           = 0x06       // Max. write current @
 VDD min
          eMMC CSD VDD_W_CURR_MAX           = 0x06       // Max. write current @
 VDD max
          eMMC CSD C_SIZE_MULT              = 0x01       // Device size multipli
er
          eMMC CSD ERASE_GRP_SIZE           = 0x1F       // Erase group size
          eMMC CSD ERASE_GRP_MULT           = 0x1F       // Erase group size mul
tiplier
          eMMC CSD WP_GRP_SIZE              = 0x0F       // Write protect group
size
          eMMC CSD WP_GRP_ENABLE            = 0x01       // Write protect group
enable
          eMMC CSD DEFAULT_ECC              = 0x00       // Manufacturer default
 ECC
          eMMC CSD R2W_FACTOR               = 0x02       // Write speed factor
          eMMC CSD WRITE_BL_LEN             = 0x09       // Max. write data bloc
k length
          eMMC CSD WRITE_BL_PARTIAL         = 0x00       // Partial blocks for w
rite allowed
          eMMC CSD CONTENT_PROT_APP         = 0x00       // Content protection a
pplication
          eMMC CSD FILE_FORMAT_GRP          = 0x00       // File format group
          eMMC CSD COPY                     = 0x01       // Copy flag (OTP)
          eMMC CSD PERM_WRITE_PROTECT       = 0x00       // Permanent write prot
ection
          eMMC CSD TMP_WRITE_PROTECT        = 0x00       // Temporary write prot
ection
          eMMC CSD FILE_FORMAT              = 0x00       // File format
          eMMC CSD ECC                      = 0x00       // ECC code
          eMMC CSD CRC                      = 0x33       // CRC
          eMMC EXT_CSD S_CMD_SET            = 0x00       // Supported Command Se
ts
          eMMC EXT_CSD BOOT_INFO            = 0x15       // Boot information
          eMMC EXT_CSD BOOT_SIZE_MULTI      = 0x0A       // Boot partition size
          eMMC EXT_CSD ACC_SIZE             = 0x07       // Access size
          eMMC EXT_CSD HC_ERASE_GRP_SIZE    = 0x00       // High-capacity erase
unit size
          eMMC EXT_CSD ERASE_TIMEOUT_MULT   = 0x04       // High-capacity erase
timeout
          eMMC EXT_CSD REL_WR_SEC_C         = 0x07       // Reliable write secto
r count
          eMMC EXT_CSD HC_WP_GRP_SIZE       = 0x01       // High-capacity write
protect group size
          eMMC EXT_CSD S_C_VCC              = 0x01       // Sleep current (VCC)
          eMMC EXT_CSD S_C_VCCQ             = 0x01       // Sleep current (VCCQ)

          eMMC EXT_CSD S_A_TIMEOUT          = 0x07       // Sleep/awake timeout
          eMMC EXT_CSD SEC_COUNT            = 0x01D5A000 // Sector Count
          eMMC EXT_CSD MIN_PERF_W_8_52      = 0xA0       // Minimum Write Perfor
mance for 8bit at 52MHz
          eMMC EXT_CSD MIN_PERF_R_8_52      = 0x00       // Minimum Read Perform
ance for 8bit at 52MHz
          eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00       // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
          eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00       // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
          eMMC EXT_CSD MIN_PERF_W_4_26      = 0x00       // Minimum Write Perfor
mance for 4bit at 26MHz
          eMMC EXT_CSD MIN_PERF_R_4_26      = 0x00       // Minimum Read Perform
ance for 4bit at 26MHz
          eMMC EXT_CSD PWR_CL_26_360        = 0x00       // Power class for 26MH
z at 3.6V
          eMMC EXT_CSD PWR_CL_52_360        = 0x00       // Power class for 52MH
z at 3.6V
          eMMC EXT_CSD PWR_CL_26_195        = 0x00       // Power class for 26MH
z at 1.95V
          eMMC EXT_CSD PWR_CL_52_195        = 0x00       // Power class for 52MH
z at 1.95V
          eMMC EXT_CSD CARD_TYPE            = 0x01       // Card type
          eMMC EXT_CSD CSD_STRUCTURE        = 0x00       // CSD structure versio
n
          eMMC EXT_CSD EXT_CSD_REV          = 0x00       // Extended CSD revisio
n
          eMMC EXT_CSD CMD_SET              = 0x02       // Command set
          eMMC EXT_CSD CMD_SET_REV          = 0x05       // Command set revision

          eMMC EXT_CSD POWER_CLASS          = 0x00       // Power class
          eMMC EXT_CSD HS_TIMING            = 0x00       // High-speed interface
 timing
          eMMC EXT_CSD BUS_WIDTH            = 0x00       // Bus width mode
          eMMC EXT_CSD ERASED_MEM_CONT      = 0x00       // Erased memory conten
t
          eMMC EXT_CSD BOOT_CONFIG          = 0x00       // Boot configuration
          eMMC EXT_CSD BOOT_BUS_WIDTH       = 0x00       // Boot bus width1
          eMMC EXT_CSD ERASE_GROUP_DEF      = 0x00       // High-density erase g
roup definition
          EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:01.965 (24820 bytes/s)
» End loading driver
» Downloading

LEENO · 07-19-2012, 20:55

i have i9100g bad flashed, now dead,
i used omapflash but it still not go in download mode

Quote:

» OMAPFlash v4.15 (Aug 12 2011)

» -v
» Entering parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.tx t at line
: 1
» -omap 4
» -t 36000
» -p OMAP4460_TUNA_8G_HS_PRO
» -2
» chip_download EMMC Targets\Projects\tuna\MLO_4460_HS_PRO
» chip_download EMMC Targets\Projects\tuna\sbl.img
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.tx t
» @Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 E8 93 BC F5 1D E7 1F 81 6B C4 4E D8 FA F5 F9
69 43 5E 77 5A
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4460_TUNA_8G_HS_PRO 443007 04 HS
» Error no 2nd for: OMAP4460_TUNA_8G_HS_PRO 443007 04 HS
Premere un tasto per continuare . . .

Quote:

» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x477100003F79 // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00003F79 // Product serial numbe
r
eMMC CID MDT = 0x3F // Manufacturing date
eMMC CID CRC = 0x3C // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes

eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)

eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision

eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:01.812 (26200 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::::::::::::::::: [262144]
» Downloading complete
» Elapsed time: 0:00.250 (1048576 bytes/s)
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
EMMC eMMC DRIVER DEINIT COMPLETE
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x477100003F79 // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00003F79 // Product serial numbe
r
eMMC CID MDT = 0x3F // Manufacturing date
eMMC CID CRC = 0x3C // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes

eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)

eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision

eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:01.796 (27740 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\Sbl.bin'
» Sending data (1310720 bytes) :::::::::::::::::::: [1310720]
» Downloading complete
» Elapsed time: 0:00.906 (1446710 bytes/s)
» cold_sw_reset
» Elapsed time: 0:11.500
Premere un tasto per continuare . . .

chad_petree · 07-19-2012, 22:27

I got the drivers to install on a computer with windows 8 32 bits,( no luck with 64 bits) when the driver installation was done , i got a message saying the device may not work, and indeed on device manager shows up with a yellow exclamation symbol but at least its recognized it says"omap flash driver" or "locosto usb drive or " Omap 4460" it shows the name of any driver i choose to install but with a yellow sign , by the way is the nexus's screen supposed to turn on when i plug it to the usb? because it doesnt it just stays off and when i run the omap.bat it keeps saying waiting for the device.

This is the error screen after i install the drivers and this is how the drivers appear on device manager

Pulka · 07-20-2012, 22:39

@LEENO
Hi.
I had same problem with dead i9100G,after resurection with Omapflash Tool no Download Mode,only Samsung Logo,after reset Device again dead.
I have successfull repair with this Guide:
Start Omap Tool and connect the i9100G without Battery,after successfull write SBL.bin

Code:

» Downloading 'Targets\Projects\espresso\Sbl.bin'
» Sending data (1310720 bytes) :::::::::::::::::::: [1310720]
» Downloading complete
» Elapsed time: 0:00.906 (1446710 bytes/s)
» cold_sw_reset
» Elapsed time: 0:11.500
Premere un tasto per continuare . . .

quickly disconnect USB Cable and put Battery in to i9100G and use USB JIG,you have now Download Mode and can flash with ODIN 3-Parts Firmware(Boot,PDA,Phone,CSC),only this Methode work by me on i9100G after flash wrong Firmware from i9100.

BABAK NURI · 07-21-2012, 02:08

Quote:

Originally Posted by chad_petree

I got the drivers to install on a computer with windows 8 32 bits,( no luck with 64 bits) when the driver installation was done , i got a message saying the device may not work, and indeed on device manager shows up with a yellow exclamation symbol but at least its recognized it says"omap flash driver" or "locosto usb drive or " Omap 4460" it shows the name of any driver i choose to install but with a yellow sign , by the way is the nexus's screen supposed to turn on when i plug it to the usb? because it doesnt it just stays off and when i run the omap.bat it keeps saying waiting for the device.

This is the error screen after i install the drivers and this is how the drivers appear on device manager

Hi
Please install correct driver from "usb_drv_windows" Folder

..

or maybe You need remove old driver first,Then reboot pc,,,and install correct driver

gridl0ck · 07-21-2012, 17:14

How do you use this to fix dead phone? My phone i9250 doesn't go into download mode or recovery it's just plain blank screen. I tried to plugin without battery via usb but program still doesnt pick up device. Thanks.

chad_petree · 07-21-2012, 19:09

Quote:

Originally Posted by BABAK NURI

Hi
Please install correct driver from "usb_drv_windows" Folder

..

or maybe You need remove old driver first,Then reboot pc,,,and install correct driver

but which one is the correct one? i select omap_winusb and then get a list with drivers to install, is it

chad_petree · 07-21-2012, 19:19

Quote:

Originally Posted by chad_petree

but which one is the correct one? i select omap_winusb and then get a list with drivers to install, is it

should i choose "omap flash driver" or "locosto usb drive or " Omap 4460" it seems no of those work

, i have a i9100

michaelmotes · 07-22-2012, 00:04

I have I9250 with corrupt imei, just shows generic 00499...

I am willing to solder on the JTAG pins but this box does not yet have IMEI repair feature via resurrection dll for I9250. How else can I repair IMEI?

sbata-team · 07-22-2012, 00:12

legija the king of jtag and the dead boot

07-20-2012, 22:39	#84 (permalink)
Pulka Freak Poster Join Date: Jan 2009 Location: Germany/NRW Posts: 420 Member: 936229 Status: Offline Sonork: 1606911 Thanks Meter: 115	@LEENO Hi. I had same problem with dead i9100G,after resurection with Omapflash Tool no Download Mode,only Samsung Logo,after reset Device again dead. I have successfull repair with this Guide: Start Omap Tool and connect the i9100G without Battery,after successfull write SBL.bin Code: » Downloading 'Targets\Projects\espresso\Sbl.bin' » Sending data (1310720 bytes) :::::::::::::::::::: [1310720] » Downloading complete » Elapsed time: 0:00.906 (1446710 bytes/s) » cold_sw_reset » Elapsed time: 0:11.500 Premere un tasto per continuare . . . quickly disconnect USB Cable and put Battery in to i9100G and use USB JIG,you have now Download Mode and can flash with ODIN 3-Parts Firmware(Boot,PDA,Phone,CSC),only this Methode work by me on i9100G after flash wrong Firmware from i9100.

07-22-2012, 00:04	#89 (permalink)
michaelmotes Junior Member Join Date: Jul 2012 Posts: 6 Member: 1786134 Status: Offline Thanks Meter: 0	IMEI Repair I have I9250 with corrupt imei, just shows generic 00499... I am willing to solder on the JTAG pins but this box does not yet have IMEI repair feature via resurrection dll for I9250. How else can I repair IMEI?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
need ericsson 88 cable	migdamas	Old Ericsson Phones & Sony Phones	2	03-24-2017 16:24
need software for 5161 by cable	mln2000	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	6	08-29-2010 20:17
I am looking for information about GSM-CABLES.NE	DUPOND	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	5	08-03-1999 15:29
Selling original Nokia DAU9P cable	TheDon	Main Sales Section	0	07-21-1999 15:44
8810 mbus-cable	zfrank	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	05-19-1999 13:12

06-28-2012, 23:05	#77 (permalink)
itsalllgood Junior Member Join Date: Apr 2012 Posts: 19 Member: 1752435 Status: Offline Thanks Meter: 1	Mr legija..do you have any opnion on these logs...could a jtag resolve the ones that were not resurrected by this tool..is it possible to reformat the emmc..

07-01-2012, 13:27	#78 (permalink)
cristipuc Junior Member Join Date: Jul 2012 Posts: 1 Member: 1779216 Status: Offline Thanks Meter: 0	good work, i run this tool for my GN GSM version, and work great, no more rebooting !

07-19-2012, 22:27	#83 (permalink)
chad_petree Junior Member Join Date: Jul 2012 Posts: 3 Member: 1787065 Status: Offline Thanks Meter: 0	I got the drivers to install on a computer with windows 8 32 bits,( no luck with 64 bits) when the driver installation was done , i got a message saying the device may not work, and indeed on device manager shows up with a yellow exclamation symbol but at least its recognized it says"omap flash driver" or "locosto usb drive or " Omap 4460" it shows the name of any driver i choose to install but with a yellow sign , by the way is the nexus's screen supposed to turn on when i plug it to the usb? because it doesnt it just stays off and when i run the omap.bat it keeps saying waiting for the device. This is the error screen after i install the drivers and this is how the drivers appear on device manager

07-21-2012, 17:14	#86 (permalink)
gridl0ck Insane Poster Join Date: Feb 2011 Posts: 81 Member: 1517645 Status: Offline Thanks Meter: 9	How do you use this to fix dead phone? My phone i9250 doesn't go into download mode or recovery it's just plain blank screen. I tried to plugin without battery via usb but program still doesnt pick up device. Thanks.

07-22-2012, 00:12	#90 (permalink)
sbata-team Freak Poster Join Date: Nov 2008 Location: MOROCCO Posts: 316 Member: 909860 Status: Offline Sonork: +212600693045 Thanks Meter: 120	legija the king of jtag and the dead boot