Please help me get data working
ha and aaa for frofile 1 and profile 0. after sending spc in qxdm and running "06:18:32.773 requestnvitemread ds_mip_ss_user_prof 0" i get all zeros in return for both secrets and both profiles. also need help with um tether nai and um user id in ppp config(see jpg attchment).
06:18:32.898 DIAG RX item:
06:18:32.898 index = 0
06:18:32.898 mn_ha_shared_secret_length = 0x00
06:18:32.898 mn_ha_shared_secret[0] = 0x00
06:18:32.898 mn_ha_shared_secret[1] = 0x00
06:18:32.898 mn_ha_shared_secret[2] = 0x00
06:18:32.898 mn_ha_shared_secret[3] = 0x00
06:18:32.898 mn_ha_shared_secret[4] = 0x00
06:18:32.898 mn_ha_shared_secret[5] = 0x00
06:18:32.898 mn_ha_shared_secret[6] = 0x00
06:18:32.898 mn_ha_shared_secret[7] = 0x00
06:18:32.898 mn_ha_shared_secret[8] = 0x00
06:18:32.898 mn_ha_shared_secret[9] = 0x00
06:18:32.898 mn_ha_shared_secret[10] = 0x00
06:18:32.898 mn_ha_shared_secret[11] = 0x00
06:18:32.898 mn_ha_shared_secret[12] = 0x00
06:18:32.898 mn_ha_shared_secret[13] = 0x00
06:18:32.898 mn_ha_shared_secret[14] = 0x00
06:18:32.898 mn_ha_shared_secret[15] = 0x00
06:18:32.898 mn_aaa_shared_secret_length = 0x00
06:18:32.898 mn_aaa_shared_secret[0] = 0x00
06:18:32.898 mn_aaa_shared_secret[1] = 0x00
06:18:32.898 mn_aaa_shared_secret[2] = 0x00
06:18:32.898 mn_aaa_shared_secret[3] = 0x00
06:18:32.898 mn_aaa_shared_secret[4] = 0x00
06:18:32.898 mn_aaa_shared_secret[5] = 0x00
06:18:32.898 mn_aaa_shared_secret[6] = 0x00
06:18:32.898 mn_aaa_shared_secret[7] = 0x00
06:18:32.898 mn_aaa_shared_secret[8] = 0x00
06:18:32.898 mn_aaa_shared_secret[9] = 0x00
06:18:32.898 mn_aaa_shared_secret[10] = 0x00
06:18:32.898 mn_aaa_shared_secret[11] = 0x00
06:18:32.898 mn_aaa_shared_secret[12] = 0x00
06:18:32.898 mn_aaa_shared_secret[13] = 0x00
06:18:32.898 mn_aaa_shared_secret[14] = 0x00
06:18:32.898 mn_aaa_shared_secret[15] = 0x00
ugggg. cant get my data working.
...........................................
nobody? c'mon
» 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 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» 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.txt
» 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 = 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 = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // 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:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
ME too
nirmalece19 said:
» 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 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» 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.txt
» 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 = 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 = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // 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:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
Click to expand...
Click to collapse
i think NAND error , cannot get into recovery mode, but get into dowload mode, flash via odin error
my phone is fully dead and i try to use the flasher and i got this error...
i also try to find a solution in the forum but some people are also looking for the solution.
so please guide us
» 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 8C C1 C5 D5 C6 CF F2 5D ED BD BC 7F A7 9E 6A
DE D7 57 94 CC
» 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.txt
» 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 0xF2055006
EMMC eMMC DRIVER DEINIT COMPLETE
» Download failed (final data response error): Remote: : Driver init error 0xF20
55006 - MMC CONFIG FAILURE
» Elapsed time: 0:05.485 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0xF2055006 - MMC CONFIG FAILURE)
» Elapsed time: 0:20.203
Press any key to continue . . .
Take it to someone who knows what they're doing/has experience using this equipment (you clearly don't). You might be waiting a very long time for someone who has experience on here with this sort of gear to read your thread. Most people here do the smart thing & take it to someone who already has the gear, knows how to use it & get it fixed for 30 bucks & no effort/grief.
atifbuitms said:
my phone is fully dead and i try to use the flasher and i got this error...
i also try to find a solution in the forum but some people are also looking for the solution.
so please guide us
» 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 8C C1 C5 D5 C6 CF F2 5D ED BD BC 7F A7 9E 6A
DE D7 57 94 CC
» 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.txt
» 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 0xF2055006
EMMC eMMC DRIVER DEINIT COMPLETE
» Download failed (final data response error): Remote: : Driver init error 0xF20
55006 - MMC CONFIG FAILURE
» Elapsed time: 0:05.485 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0xF2055006 - MMC CONFIG FAILURE)
» Elapsed time: 0:20.203
Press any key to continue . . .
Click to expand...
Click to collapse
same problem here.. we are in the same boar
I have this Gnex that was bricked few years ago..
And i need help unbricking this one..
Tried omapflash, but shows up these errors
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 off device
» 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 EE AD 48 C3 BD 1D D5 E8 F5 FC 6C 9A 18 33 90
B8 41 73 F6 FF
» 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 = 0x00
MMC card_type = 0x00
MMC data_width_support = 0x00
MMC transfer_clk_max = 0x00
MMC card_size = 0x00
MMC mmc_config return 0xF2055006
EMMC eMMC DRIVER DEINIT COMPLETE
» Download failed (final data response error): Remote: : Driver init error 0xF20
55006 - MMC CONFIG FAILURE
» Elapsed time: 0:05.415 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0xF2055006 - MMC CONFIG FAILURE)
» Elapsed time: 0:17.588
Press any key to continue . . .
please help
Thanks in advance
Hi,
I was looking to use the DJI Fly on Windows through WSA, I was able to install it just fine and it loads, but can't find a way to make it see the controller, can't find a mount option like yhe one find for example on VirtualBox, tried usbipd-win but it doesn't seem to recognize the Subsystem.
Has anyone been able to get any device "mounted"?
Thanks
Oscar
No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Renate said:
No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Click to expand...
Click to collapse
The controller is recognized as it should, I'm pretty sure, the device manager shows 3 types under the same device, with one being a com port which I suspect the DJI Fly app uses to communicate the controls, but I expect there to be some kind of menu or command that needs to be run to "attach" the device to the Android Subsystem.
Not knowing what the USB interfaces are I couldn't say anything intelligent.
That's why I asked you to tell me what they are in post #2.
This is what USB View gives when the controller is connected from the bottom port
Code:
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0xEF
bDeviceSubClass: 0x02
bDeviceProtocol: 0x01
bMaxPacketSize0: 0x40 (64)
idVendor: 0x2CA3
idProduct: 0x1020
bcdDevice: 0x0404
iManufacturer: 0x01
0x0409: "DJI"
iProduct: 0x02
0x0409: "C5"
iSerialNumber: 0x03
0x0409: "3QDCH950010H2U"
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x04
Open Pipes: 10
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Configuration Descriptor:
wTotalLength: 0x00BB
bNumInterfaces: 0x06
bConfigurationValue: 0x01
iConfiguration: 0x04
0x0409: "Configuration"
bmAttributes: 0xC0 (Bus Powered Self Powered )
MaxPower: 0x00 (0 Ma)
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x05
0x0409: "MA Channel"
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x06
0x0409: "HS-Data Channel"
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 02 02 02 02 01 07
Interface Descriptor:
bInterfaceNumber: 0x02
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x08
0x0409: "V1 ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 03
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 02 03
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x03
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x09
0x0409: "V1 ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 04 02 02 02 01 0A
Interface Descriptor:
bInterfaceNumber: 0x04
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x0B
0x0409: "Log ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 05
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 04 05
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x05
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x0C
0x0409: "Log ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
So, in short, you should have 4 "devices", that is 4 things with drivers.
There are two things that should appear in Device Manager as DJI things.
There are two things that should appear as generic Com Ports.
You can check the drivers for all four.
The last two should have usb2ser.sys
I would guess that the first two would just use WinUsb.
They should have under Details > Inf name something like oem123.inf
You can go to C:\Windows\INF\oem123.inf and see stuff there.
In any case, you should be able to find 4 happy devices in the Device Manager.
There are no Mass Storage devices here, so "mount" is used in some other context.
Code:
Device, VID/PID 2ca3/1020
The device class itself is ef:02:01, Miscellaneous class, Interface Association Descriptor
Unfortunately, you should only use this class:subclass:protocol in interfaces, not devices.
Interface #0
The interface is ff:43:01, proprietary, "MA Channel"
Bulk in/out is 512/8 bytes. Kind of unusual.
Interface #1
The interface is ff:43:01, proprietary, "HS-Data Channel"
Bulk in/out is 512/512
Generic serial port
{
Interface #2
The interface is 02:02:01, CDC control, "V1 ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #3
The interface is 0a:00:00, CDC data, "V1 ACM Data"
Bulk in/out is 512/512
}
Generic serial port
{
Interface #4
The interface is 02:02:01, CDC control, "Log ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #5
The interface is 0a:00:00, CDC data, "Log ACM Data"
Bulk in/out is 512/512
}
Yes I meant "mount" as in tell WSA to "connect" the devices to the Android system. In Device Manager the COM ports have drivers but the "HS-Data Channel" and "MA Channel" don't have drivers, as it was never meant to be used with Windows.
But you can see the two "Channels" in Device Manager?
No problem, just give them Zadig (WinUSB) drivers.
Zadig - USB driver installation made easy
You can't share anything from Windows to the Android subsystem unless it's a device with a driver (I think).