This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

I9100G Omap 4430 Error

Other Parts Discussed in Thread: 4430

hi,
Can somebody helping me.


my i9100g, after long period of cyanogenmod 10.1.3 stable all ok
one morning on radio live, crash.. booting it , no starting


1-making cwm recovery on last backup cyanogen
error /system


2-no booting, no logo, no cwm no download mode...
i search about same trouble, i found omap 4430 procedure, usb driver on xp ok


3-starting flash omap 4430 .bat with no battery

i have this error
"MMC CONFIG FAILURE"

4-trying with the mlo, param.lfs, sbl.bin of my official tar of my country "algeria"
the same error.

any solution...
thks


Quote:
» OMAPFlash v4.15 (Aug 12 2011)

» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ. txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ. txt
» @Targets\Projects\espresso\omap4430hs_1200MHZ.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 2F BB C0 3B 1A FA F9 A7 69 47 9F 1D 09 77 D1
F6 8A 60 A8 33
» 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: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.t xt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 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 1 width 4 delay 9 rpap
i_base 0x00028400
» 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 = 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 = 0x00
MMC card_type = 0x00
MMC data_width_support = 0x00
MMC transfer_clk_max = 0x00
MMC card_size = 0x00
MMC mmc_config return 0x00FF8080
EMMC eMMC DRIVER DEINIT COMPLETE
» Download failed (final data response error): Remote: : Driver init error 0x00F
F8080 - MMC CONFIG FAILURE
» Elapsed time: 0:05.453 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)

» Elapsed time: 0:27.328

  • Hi there,

    Unfortunately we don't support the cyanogenmod officialy.

    But you can find support in the xda forums for sure.

    http://forum.xda-developers.com/showthread.php?t=1701471&page=3

  • thanks you for the response.

    Now the problem is not cyanogenmod, but only reconstruct the boot of my dead  i9100G

    So my question , what is this error with emmc omap 4430 ?

    "0x00FF8080 - MMC CONFIG FAILURE"

     

    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
    » 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 = 0x00
    MMC card_type = 0x00
    MMC data_width_support = 0x00
    MMC transfer_clk_max = 0x00
    MMC card_size = 0x00
    MMC mmc_config return 0x00FF8080
    EMMC eMMC DRIVER DEINIT COMPLETE
    » Download failed (final data response error): Remote: : Driver init error 0x00F
    F8080 - MMC CONFIG FAILURE
    » Elapsed time: 0:05.453 (8730 bytes/s)
    » Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)

  • hi,

    Yes the problem may be isn't due to the OS but  the way the device is de-bricked isn't  a feature we  provide here in the forums. The forums I suggested to you have already struggled with that problem and as far as I read there are solutions you can use. Sorry that I cannot provide additional details on that topic.

    Regards,

    Boyko