Unbrick dead Samsung GT-i9250 Galaxy Nexus, GT-I9100G , GT-I9300

[BABAK NURI]

Originally Posted by michaelmotes

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?

Hi
Imei Repair Not Supported By Riff-Box...

But.Please Contact Me Via Sonork

I'll explain to you how you can repair imei

[BABAK NURI]

Originally Posted by mrx3net

any help with this


stuck here » Found device (omap usb)
» Waiting for 2nd

Hi
It's Mean You Need Check HW.....
Usually is eMMC Problem
------
But..Please Don't use Battery or Power Supply
Just Connect Usb and Run Script
Maybe you need Try several times

[BABAK NURI]

Originally Posted by Softking

i faced like same prob
after i ressurect with riff and medusa
but phone still hang on logo
i also need solution for this

Hi
Did You Flash Phone Via Odin....?
---
if odin hang on flashing any partition,,,Please Contact me via sonork

[BABAK NURI]

Originally Posted by BouRRi_GSM

what about i9003 !!!

Hi
What's You need for i9003? Repair via USB?
Jtag interface already supported dead boot..

[BABAK NURI]

Originally Posted by QASSEM

hi
first tnx for this solution
now my fone is only on start and doesnt do to download mode see the pic

Hi
Some Case Need Reflash Phone After Repair..Did You Flash Phone..?

[BABAK NURI]

Hi
Unlocking Procedure Not Supported By Riff

[nespid]

is there anything like this for cdma model?

thank you

[Burnt Cobba]

Originally Posted by zaidi_mobile

plz help riff team

samsung galaxy s3 i9300 unlock possble?????

Just root and unlock with another box. Very easy job.

RIFF is for more intricate problems

[QASSEM]

Originally Posted by BABAK NURI

Hi
Some Case Need Reflash Phone After Repair..Did You Flash Phone..?

it doesnt recognize by pc or by odin i cant see the port to flash it help me how to reflash it tnxxx

[cartuchobahia]

by the way, none of the other box can repair efs from i9300 to fix imei (even the original one). all the tools works with android till 2.3.6, in phones with higher versions if you try to fix imei or efs you get the 0049.... and there's no way to fix it yet.

[alexdrew123]

I get stuck after "waiting for second, please help.

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 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 B0 E3 EB 46 24 23 64 B9 9F B7 3F FB 28 AB 38
3 38 9D A5 B7
AsicId root_key_hash 14 21 01 67 98 9B 35 54 CC 86 B4 67 32 47 05 36 74 E2
5 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
ned.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
Waiting for device (omap usb)
Found device (omap usb)
Waiting for 2nd
Unknown status message '?#??' during peripheral boot (waiting for 2nd)
ress any key to continue . . .

[dangoga]

it s stuck on writing mlo file

[dangoga]

nobody help? because not work at mine this solution

[lococastrado]

I am getting this message. Any idea on how to deal with it?

» 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
» -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.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

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 3D 1D 5B 09 13 EF 70 5E 6B 29 6D 2B 17 C2 DE
5C D8 C5 DB C0
» 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.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)

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
» Waiting for device (omap usb)
» Found device (omap usb)
» Waiting for 2nd
00463-004-TX ACK

00571-005-RX: 4 raw bytes: 78 ED 0D 00 'x???'
» Unknown status message 'x???' during peripheral boot (waiting for 2nd)
Press any key to continue . . .

C:\Users\Juan Carlos\Downloads\OMAPFlash_tuna\OMAPFlash>GOTO __loop

» 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
» -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.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

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 3D 1D 5B 09 13 EF 70 5E 6B 29 6D 2B 17 C2 DE
5C D8 C5 DB C0
» 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.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)

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
» Waiting for device (omap usb)
» Found device (omap usb)
» Waiting for 2nd
00463-004-TX ACK

00571-005-RX: 9 raw bytes: 78 ED 9B 02 18 FE 44 00 00 'x?????D??'
» Unknown status message 'x?????D??' during peripheral boot (waiting for 2nd)
Press any key to continue . . .

[Gsm_Shop]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung i9100 V1.0.4582.4854]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.81V, TCK Frequency is 800 kHz

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x000000000000