i9023 no power no charge

[manule]

pls help phone not boot not charge no water damage

volt on battery pins

[starmobi]

what about lcd.....

check any short...

[rcf1106]

try reprogram the phone before hardware

[manule]

try reprogram the phone before hardware

No LCD is Gold condition

How u Jean short

[manule]

where u mean short pls any image

[manule]

also i have i9250 no power pls advise which component is damage faulty

[jamesjerss]

also i have i9250 no power pls advise which component is damage faulty

if yur mob is not water damaged or not other damages..try this dead boot repair method.

1st download tis file OMAPFlash_tuna

2nd you need to remove battery and then load driver for OMAP (4460usb) driver included

3rd run the bat file omap4460_tuna_hs_pro

after few second ,phone repair done

[jamesjerss]

pls help phone not boot not charge no water damage

volt on battery pins

oly jtag boxes can repair yur mobile

[manule]

» 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 40 07 01
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 9D 24 5C 2B B8 77 45 B8 C1 80 F7 CE 9A 31 28
98 41 CC F1 CB
» 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 filemapflash2nd.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 filemapflash2nd.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 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.055 (9430 bytes/s)
» Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)




is mmc damaged?

[jamesjerss]

@manule ya its seems lik tat.. need to clean emmc ..use any jtag tool to repair emmc or need to emmc ic

[manule]

ok bro where is emmc locatet

[jamesjerss]

ok bro where is emmc locatet

the chip name is sandisk .in this pic 1st chip