[Q] New finding about dead i9100G?

Search This thread
:confused::confused::confused:
Hi all the smart ppl there.
Few days ago I bricked my I9100g. its a complete brick. no download mode even with jig. just black screen. But as with a few other bricked G owners I could see the OMAP4430 appearing and disappearing in the windows device manager for a sec. But I found something that may trigger some smart mod....

Even without the battery if you connect the phone with pc, OMAP4430 will show for a sec in the dev manager. But if you connect while pressing the power button then OMAP will not show. so if we can temporarily keep the power button out of equation then there may be a chance to establish conn betwenn the pc and phone and thus repair it?:confused::confused::confused:
 

tariq2kn

Senior Member
May 8, 2010
1,093
171
Xiaomi Mi 11i
Do you get a small triangle & a computer icon when you switch on?
If so then you can flash the stock rom first, even if you dont get the download screen.
Else your phone is bricked. Then JTAG may rescue your phone.

...........................................
Sent from SGS II (GT-I9100)

Phone: XXLPQ
Modem: DDLP8
CSC: DDLP7
Root: CF-Root 5.4
Kernel: Siyah 3.0b7
 
Do you get a small triangle & a computer icon when you switch on?
If so then you can flash the stock rom first, even if you dont get the download screen.
Else your phone is bricked. Then JTAG may rescue your phone.

No. No triangle. No switch on. its dead. jtag doesn't work with i9100g. at least not yet. they tried. thats why i've posted my observation about the detection of OMAP processor. May be some sharp mind can think of something:)
 
Last edited:

ctomgee

Senior Member
Dec 21, 2010
3,563
901
No. No triangle. No switch on. its dead. jtag doesn't work with i9100g. at least not yet. they tried. thats why i've posted my observation about the detection of OMAP processor. May be some sharp mind can think of something:)

This is wrong. JTag for I9100G will need a different Riff box due to the OMAP processor. (google "jtag riff box i9100g" if you don't believe me)

Take it to a different place, because it sounds like the first place tried to use the same Riff box as for an I9100. Which of course, won't work.
 
This is wrong. JTag for I9100G will need a different Riff box due to the OMAP processor. (google "jtag riff box i9100g" if you don't believe me)

Take it to a different place, because it sounds like the first place tried to use the same Riff box as for an I9100. Which of course, won't work.

I've googled this many times and read details as well. The results are not definitive and in most cases confusing in gsmhosting or other sites. Some claims it works with i9108 and hence "should" also work with G. Lot of people are looking for right pinout of G and quite a few complaining failed resurrection.

I guess no hardware guy has read my first post. Because I thought it was a good finding.
 

sahibunlimited

Senior Member
Jul 13, 2011
6,839
2,442
Nagpur
I've googled this many times and read details as well. The results are not definitive and in most cases confusing in gsmhosting or other sites. Some claims it works with i9108 and hence "should" also work with G. Lot of people are looking for right pinout of G and quite a few complaining failed resurrection.

I guess no hardware guy has read my first post. Because I thought it was a good finding.

Try contacting AdamOutler he is a hardware guy and might be able to help you
(But i think you have to send your phone to him)
 

moschino_luv

Member
Dec 24, 2007
28
64
Only this method to recovered sleep/dead I9100G ;)


Code:
kozio -v -omap 3 -2 -p SDP_MDDR_HYNIX_4G -t 60 chip_erase NAND 0

  » OMAPTOOL  vX.X (MMM DD YYYY)

  » Please turn off device
  » Please turn on device
  » Waiting for device
  » Found device
  » Searching 2nd for: SDP_MDDR_HYNIX_4G 363007 07 GP
  » Loading second file Targets\2nd-Downloaders\dnld_startup_3630sdp_gp_hynix_4g.2nd
  » Transferring second file to target (0x5FF8 bytes)
  » Found device
  » Waiting for 2nd
  » Found 2nd
  » Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'
  » Sending data (11412 bytes) :::::::::::::::::::: [11412]
           Interface 'OMAPFLASH DRIVER v1'
           Driver 'NAND ONFI 16/8 BIT'
           NAND ONFIv2 VENDOR 0x2C MICRON
           NAND 16 BIT DEVICE 0xBC MT29F4G16ABC
           NAND 2048 BYTES/PAGE (SPARE 64)
           NAND 64 PAGES/BLOCK (131072 BYTES/BLOCK)
           NAND 4096 BLOCKS/UNIT (536870912 BYTES/UNIT)
           NAND 512 MB TOTAL SIZE
           NAND ONFI DRIVER INIT COMPLETE
  » Downloading complete
  » Elapsed time: 0:00.344 (33174 bytes/s)
  » End loading driver
  » Erasing
           name=NAND            address=0x28000000
           Erasing to end of device starting at 0x28000000
           Erase progress :::::::::::::::::::: [536870912]
           NAND ERASED 535691264 BYTES FROM ADDRESS 0x28000000 (9 BAD BLOCKS)
  » Elapsed time: 0:24.571


Code:
  kozio -omap 3 -2 -p SDP_MDDR_HYNIX_4G -t 60 chip_download NAND .\test_data\pattern_10M.bin

  » OMAPTOOL vX.X (MMM DD YYYY)

  » Please turn off device
  » Please turn on device
  » Waiting for device
  » Found device
  » Searching 2nd for: SDP_MDDR_HYNIX_4G 363007 07 GP
  » Loading second file Targets\2nd-Downloaders\dnld_startup_3630sdp_gp_hynix_4g.2nd
  » Transferring second file to target (0x5FF8 bytes)
  » Found device
  » Waiting for 2nd
  » Found 2nd
  » Downloading driver
  » Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'
  » Sending data (11412 bytes) :::::::::::::::::::: [11412]
  » Downloading complete
  » Elapsed time: 0:00.391 (29186 bytes/s)
  » End loading driver
  » Downloading
  » Downloading '.\test_data\pattern_10M.bin'
  » Sending data (10485760 bytes) :::::::::::::::::::: [10485760]
  » Downloading complete
  » Elapsed time: 0:35.095 (299593 bytes/s)
  » Elapsed time: 0:35.334
 
Last edited:
only this method to recovered sleep/dead i9100g ;)


Code:
omapflash -v -omap 3 -2 -p sdp_mddr_hynix_4g -t 60 chip_erase nand 0

  » omapflash vx.x (mmm dd yyyy)

  » please turn off device
  » please turn on device
  » waiting for device
  » found device
  » searching 2nd for: Sdp_mddr_hynix_4g 363007 07 gp
  » loading second file targets\2nd-downloaders\dnld_startup_3630sdp_gp_hynix_4g.2nd
  » transferring second file to target (0x5ff8 bytes)
  » found device
  » waiting for 2nd
  » found 2nd
  » downloading 'targets\flash-drivers\nand_onfi_16bit_8bit.bin'
  » sending data (11412 bytes) :::::::::::::::::::: [11412]
           interface 'omapflash driver v1'
           driver 'nand onfi 16/8 bit'
           nand onfiv2 vendor 0x2c micron
           nand 16 bit device 0xbc mt29f4g16abc
           nand 2048 bytes/page (spare 64)
           nand 64 pages/block (131072 bytes/block)
           nand 4096 blocks/unit (536870912 bytes/unit)
           nand 512 mb total size
           nand onfi driver init complete
  » downloading complete
  » elapsed time: 0:00.344 (33174 bytes/s)
  » end loading driver
  » erasing
           name=nand            address=0x28000000
           erasing to end of device starting at 0x28000000
           erase progress :::::::::::::::::::: [536870912]
           nand erased 535691264 bytes from address 0x28000000 (9 bad blocks)
  » elapsed time: 0:24.571


Code:
  omapflash -omap 3 -2 -p sdp_mddr_hynix_4g -t 60 chip_download nand .\test_data\pattern_10m.bin

  » omapflash vx.x (mmm dd yyyy)

  » please turn off device
  » please turn on device
  » waiting for device
  » found device
  » searching 2nd for: Sdp_mddr_hynix_4g 363007 07 gp
  » loading second file targets\2nd-downloaders\dnld_startup_3630sdp_gp_hynix_4g.2nd
  » transferring second file to target (0x5ff8 bytes)
  » found device
  » waiting for 2nd
  » found 2nd
  » downloading driver
  » downloading 'targets\flash-drivers\nand_onfi_16bit_8bit.bin'
  » sending data (11412 bytes) :::::::::::::::::::: [11412]
  » downloading complete
  » elapsed time: 0:00.391 (29186 bytes/s)
  » end loading driver
  » downloading
  » downloading '.\test_data\pattern_10m.bin'
  » sending data (10485760 bytes) :::::::::::::::::::: [10485760]
  » downloading complete
  » elapsed time: 0:35.095 (299593 bytes/s)
  » elapsed time: 0:35.334
thanks! But how do i do that. What device do i need?