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

[crackp0d]

Originally Posted by crackp0d

Thanks for your replay
How to upload sbi in to phone Download mode is not coming please explain

yes i understand how to copy sbi in to phone let me try i will post results thanks

[Velko]

Please upload link again for i9250 .
Thanks

[k0nko]

Hello guys

Today morning i bricked my Galaxy Nexus i9250 gsm. I read whole internet how to get it back to life, and end up here. I did every step about 20 times, on 4 different computers with 4 different OS (XP, win7 32-64, win8 32) and my GNex is still dead. I cant get to system, fastboot, download mod or recovery. Nothing works

Can anybody help me please :/

this is what oamp4460_tuna_hs_pro says:

00483-353-RX:INFO: eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Co
unt
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
00463-354-TX ACK
00483-355-RX:INFO: eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum W
rite Performance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
00463-356-TX ACK
00483-357-RX:INFO: eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum R
ead Performance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
00463-358-TX ACK
00483-359-RX:INFO: eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum W
rite Performance for 8bit at 26MHz, for 4bit 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
00463-360-TX ACK
00483-361-RX:INFO: eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum R
ead Performance 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
00463-362-TX ACK
00483-363-RX:INFO: eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum W
rite Performance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
00463-364-TX ACK
00483-365-RX:INFO: eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum R
ead Performance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
00463-366-TX ACK
00483-367-RX:INFO: eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power cla
ss for 26MHz at 3.6V
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
00463-368-TX ACK
00483-369-RX:INFO: eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power cla
ss for 52MHz at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
00463-370-TX ACK
00483-371-RX:INFO: eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power cla
ss for 26MHz at 1.95V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
00463-372-TX ACK
00483-373-RX:INFO: eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power cla
ss for 52MHz at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
00463-374-TX ACK
00483-375-RX:INFO: eMMC EXT_CSD CARD_TYPE = 0x01 // Card type

eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
00463-376-TX ACK
00483-377-RX:INFO: eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD struc
ture version
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
00463-378-TX ACK
00483-379-RX:INFO: eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended
CSD revision
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
00463-380-TX ACK
00483-381-RX:INFO: eMMC EXT_CSD CMD_SET = 0x02 // Command s
et
eMMC EXT_CSD CMD_SET = 0x02 // Command set
00463-382-TX ACK
00483-383-RX:INFO: eMMC EXT_CSD CMD_SET_REV = 0x05 // Command s
et revision
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision

00463-384-TX ACK
00483-385-RX:INFO: eMMC EXT_CSD POWER_CLASS = 0x00 // Power cla
ss
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
00463-386-TX ACK
00483-387-RX:INFO: eMMC EXT_CSD HS_TIMING = 0x00 // High-spee
d interface timing
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
00463-388-TX ACK
00483-389-RX:INFO: eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width
mode
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
00463-390-TX ACK
00483-391-RX:INFO: eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased me
mory content
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
00463-392-TX ACK
00483-393-RX:INFO: eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot conf
iguration
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
00463-394-TX ACK
00483-395-RX:INFO: eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus
width1
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
00463-396-TX ACK
00483-397-RX:INFO: eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-dens
ity erase group definition
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
00463-398-TX ACK
00483-399-RX:INFO: EMMC eMMC DRIVER INIT COMPLETE
EMMC eMMC DRIVER INIT COMPLETE
00463-400-TX ACK
00554-401-RX:OKAY: driver downloaded
» Downloading complete
» Elapsed time: 0:00.485 (97237 bytes/s)
» End loading driver
» Downloading
00385-402-TX:write EMMC 80000 001C0000
00463-403-TX ACK
00554-404-RX:OKAY: expecting download
» Downloading 'Targets\Projects\tuna\sbl.img'
00385-405-TX:download:001c0000
00527-406-RX:data00018000
» Sending data (1835008 bytes) .................... [32768]
00148-407-TX 32768 bin bytes
00527-408-RX:data00018000
» Sending data (1835008 bytes) .................... [65536]
00148-409-TX 32768 bin bytes
00527-410-RX:data00018000
» Sending data (1835008 bytes) :................... [98304]
00148-411-TX 32768 bin bytes
00527-412-RX:data00018000
» Sending data (1835008 bytes) :................... [131072]
00148-413-TX 32768 bin bytes
00527-414-RX:data00018000
» Sending data (1835008 bytes) :................... [163840]
00148-415-TX 32768 bin bytes
00527-416-RX:data00018000
» Sending data (1835008 bytes) ::.................. [196608]
00148-417-TX 32768 bin bytes
00527-418-RX:data00018000
» Sending data (1835008 bytes) ::.................. [229376]
00148-419-TX 32768 bin bytes
00527-420-RX:data00018000
» Sending data (1835008 bytes) ::.................. [262144]
00148-421-TX 32768 bin bytes
00527-422-RX:data00018000
» Sending data (1835008 bytes) :::................. [294912]
00148-423-TX 32768 bin bytes
00527-424-RX:data00018000
» Sending data (1835008 bytes) :::................. [327680]
00148-425-TX 32768 bin bytes
00527-426-RX:data00018000
» Sending data (1835008 bytes) :::................. [360448]
00148-427-TX 32768 bin bytes
00527-428-RX:data00018000
» Sending data (1835008 bytes) ::::................ [393216]
00148-429-TX 32768 bin bytes
00527-430-RX:data00018000
» Sending data (1835008 bytes) ::::................ [425984]
00148-431-TX 32768 bin bytes
00527-432-RX:data00018000
» Sending data (1835008 bytes) :::::............... [458752]
00148-433-TX 32768 bin bytes
00527-434-RX:data00018000
» Sending data (1835008 bytes) :::::............... [491520]
00148-435-TX 32768 bin bytes
00527-436-RX:data00018000
» Sending data (1835008 bytes) :::::............... [524288]
00148-437-TX 32768 bin bytes
00527-438-RX:data00018000
» Sending data (1835008 bytes) ::::::.............. [557056]
00148-439-TX 32768 bin bytes
00527-440-RX:data00018000
» Sending data (1835008 bytes) ::::::.............. [589824]
00148-441-TX 32768 bin bytes
00527-442-RX:data00018000
» Sending data (1835008 bytes) ::::::.............. [622592]
00148-443-TX 32768 bin bytes
00527-444-RX:data00018000
» Sending data (1835008 bytes) :::::::............. [655360]
00148-445-TX 32768 bin bytes
00527-446-RX:data00018000
» Sending data (1835008 bytes) :::::::............. [688128]
00148-447-TX 32768 bin bytes
00527-448-RX:data00018000
» Sending data (1835008 bytes) :::::::............. [720896]
00148-449-TX 32768 bin bytes
00527-450-RX:data00018000
» Sending data (1835008 bytes) ::::::::............ [753664]
00148-451-TX 32768 bin bytes
00527-452-RX:data00018000
» Sending data (1835008 bytes) ::::::::............ [786432]
00148-453-TX 32768 bin bytes
00527-454-RX:data00018000
» Sending data (1835008 bytes) ::::::::............ [819200]
00148-455-TX 32768 bin bytes
00527-456-RX:data00018000
» Sending data (1835008 bytes) :::::::::........... [851968]
00148-457-TX 32768 bin bytes
00527-458-RX:data00018000
» Sending data (1835008 bytes) :::::::::........... [884736]
00148-459-TX 32768 bin bytes
00527-460-RX:data00018000
» Sending data (1835008 bytes) ::::::::::.......... [917504]
00148-461-TX 32768 bin bytes
00527-462-RX:data00018000
» Sending data (1835008 bytes) ::::::::::.......... [950272]
00148-463-TX 32768 bin bytes
00527-464-RX:data00018000
» Sending data (1835008 bytes) ::::::::::.......... [983040]
00148-465-TX 32768 bin bytes
00527-466-RX:data00018000
» Sending data (1835008 bytes) :::::::::::......... [1015808]
00148-467-TX 32768 bin bytes
00527-468-RX:data00018000
» Sending data (1835008 bytes) :::::::::::......... [1048576]
00148-469-TX 32768 bin bytes
00527-470-RX:data00018000
» Sending data (1835008 bytes) :::::::::::......... [1081344]
00148-471-TX 32768 bin bytes
00527-472-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::........ [1114112]
00148-473-TX 32768 bin bytes
00527-474-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::........ [1146880]
00148-475-TX 32768 bin bytes
00527-476-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::........ [1179648]
00148-477-TX 32768 bin bytes
00527-478-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::....... [1212416]
00148-479-TX 32768 bin bytes
00527-480-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::....... [1245184]
00148-481-TX 32768 bin bytes
00527-482-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::....... [1277952]
00148-483-TX 32768 bin bytes
00527-484-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::...... [1310720]
00148-485-TX 32768 bin bytes
00527-486-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::...... [1343488]
00148-487-TX 32768 bin bytes
00527-488-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::..... [1376256]
00148-489-TX 32768 bin bytes
00527-490-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::..... [1409024]
00148-491-TX 32768 bin bytes
00527-492-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::..... [1441792]
00148-493-TX 32768 bin bytes
00527-494-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::.... [1474560]
00148-495-TX 32768 bin bytes
00527-496-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::.... [1507328]
00148-497-TX 32768 bin bytes
00527-498-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::.... [1540096]
00148-499-TX 32768 bin bytes
00527-500-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::... [1572864]
00148-501-TX 32768 bin bytes
00527-502-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::... [1605632]
00148-503-TX 32768 bin bytes
00527-504-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::... [1638400]
00148-505-TX 32768 bin bytes
00527-506-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::::.. [1671168]
00148-507-TX 32768 bin bytes
00527-508-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::::.. [1703936]
00148-509-TX 32768 bin bytes
00527-510-RX:data00018000
» Sending data (1835008 bytes) ::::::::::::::::::.. [1736704]
00148-511-TX 32768 bin bytes
00527-512-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::::. [1769472]
00148-513-TX 32768 bin bytes
00527-514-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::::. [1802240]
00148-515-TX 32768 bin bytes
00527-516-RX:data00018000
» Sending data (1835008 bytes) :::::::::::::::::::: [1835008]
00148-517-TX 32768 bin bytes
» Sending data (1835008 bytes) :::::::::::::::::::: [1835008]
00463-518-TX ACK
00554-519-RX:OKAY: Write complete
» Downloading complete
» Elapsed time: 0:01.633 (1146880 bytes/s)
» cold_sw_reset
00385-520-TX:cold_sw_reset
00463-521-TX ACK
00554-522-RX:OKAY: Reseting
» Elapsed time: 0:07.329
Press any key to continue . . .

[topline]

Originally Posted by BABAK NURI

Hi
This is Just Copy/Paste From Original Document Repair,Released By Samsung...They Not Have Any News

I have a master i9300 that I can use for testing:
please tell me what tests I can do to revive the device i9300?
thanks are at your disposal

[3cush]

linlk doesnt work.. help me i need that file!!

[comeon123]

Someone please create an image file of the sd-card for i9300 - the howto can be found on page 16 of this thread, it only takes a minute.

thanks

[topline]

Originally Posted by BABAK NURI

Hi All

Please Note : About I9300

in this case Jtag Disabled for 90%...So We Need Use SD_Method

in 10% Jtag Access is Possible....And We Have I9300.DLL And RIFF-Box Can Resurrect This Model.....

----
Please Note Again:
** We Can Repair All Bricked I9300 With SD_Method If Phone Bricked By Wrong SW**





* We Can't Repair I9300 if Phone Dead Suddenly*
* We Can't Repair I9300 if Product Name in "Downloading" is empty*
* We Can't Repair I9300 if Odin Say "No Pit Partition" *
* We Can't Repair I9300 if Odin Hang On "Set Partition" *
* We Can't Repair I9300 if Odin Faild Write Any Partition "
* We Can't Repair I9300 if You see "SD card download failed"
-------- All is HW PROBLEM and Needed Replace eMMC ---------

-------
Please Note About Jtaging I9300
if you want check phone for disabled or enabled Jtag Access :
Solder Jtag Wires
Select I9100.dll or Exynus.dll
Goto DCC Read/Write Page
Select Any Size
Press "Read Memory"
if Read Memory Started,I'ts Mean phone is enabled
if You Got error like "self test faild" or No response from riffbox" It's Mean Jtag Disabled
-------
If Any One Have I9300 With Jtag enabled...Please Contact Me or Mr.Legija for dll-------------

About Making Boot on the SD:
We Need Alive Phone With Old Bootloader
if you use alive phone with new bootloader ,Odin Can't Copy Sboot on the SD...So,if you check SD after copy,,,You See SD is empty...
Currect SD Must Blank after Copy Bootloader(Like SD_Magic for I9003)
--------------------------
I Hope all my explain can stop all quistion about this model

----
Last Note: If Any One Need eMMC,,,I Have original eMMC(PreProgramed)
It's Mean Phone Turn One After Replace.
No Need Jtag
No Need SD Method
No Need Flashing Firmware(Phone Compeletly Turn On After Replace)
So,I can Replace eMMC or Sell Only Chip

I came across a samsung i9300 which is visible pin jtag!

[wahid]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung T999V V1.0.4660.46001]

Connecting to the dead body...ERROR
ERROR: The RTCK Signal does not respond.

[wahid]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung T999V V1.0.4660.46001]

Connecting to the dead body...ERROR
ERROR: The RTCK Signal does not respond.

[patric]

how to solve logo.jpg draw failed ??

[BABAK NURI]

Originally Posted by ..::AllGsmStore::..

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung T999V V1.0.4660.46001]

Connecting to the dead body...ERROR
ERROR: The RTCK Signal does not respond.

Hi
You Can't use T999v.dll
You Need Select I9100.dll or Exynos.dll

[littmanr]

Hi babak , please post method for repair n7100 totally bricked.
Can we to use same method sd like i9300? So question its, recovery.img its same? What about short resistance?
Thanks brother.

[BABAK NURI]

Originally Posted by littmanr

Hi babak , please post method for repair n7100 totally bricked.
Can we to use same method sd like i9300? So question its, recovery.img its same? What about short resistance?
Thanks brother.

Hi
Of Course Guides is same and Recovery file(Sboot) is Different

So,Please Contact me Via Sonork For Test New File(N7100)

[BABAK NURI]

Originally Posted by MUTUAL

i get this error when i m trying to flash the boot recovery file

what to do
i copy boot-recovery file to sd card i leave the sd card in the phone
i put phone is download mode and the i select boot-recovery file to boot section
and i try to flash i get this error can some one tell me what to do?

Hi
Please Note...:

Your Phone Have A New Bootloader....So,You need downgrade to 4.0.4 with old sboot,Then Try Write Repair Boot

[nicolati]

Guys I don't have RIFF box, but I have a UK GT-I9300 which has the JTAG pins visible.
The phone has no power, no charging and so on...

Can it be helpful ?

Thanks,
Fra