[TOOLS] Unbrick dead Samsung GT-i9250 Galaxy Nexus 32GB / Prime via USB cable

Search This thread
By:
Advanced…
DR_MOOSAVI

DR_MOOSAVI

Senior Member
Sep 27, 2008
65
426
SHIRAZ
First you need to remove battery and then load driver for OMAP (4460usb), then its working. Looks like TI recovery procedure.

But unfortunatelly it recovered bootloader (sbl) only, in my case eMMC pda image partition still damaged and eMMC need to be formatted completely.
 
  • Like
Reactions: md6080
D

dropback

Senior Member
Apr 21, 2012
71
28
I dont think so. There are no 32Gb Nexus on the market.
(Hat der MM bestimmt nur falsch ausgezeichnet, es gibt keine 32Gb Nexus.);)
€: Really? 32 Gb Nexus? Never seen one or read that someone got one...ok, seems there are a few in the US, but officially none in Germany.
I hope i will not need the tool from the op, but nice to see that there might be a solution if you really brick it:)
 
Last edited:
jwais

jwais

Senior Member
Aug 26, 2007
94
3
E:V:A

E:V:A

Inactive Recognized Developer
Dec 6, 2011
1,447
2,222
-∇ϕ
Does someone understand how it is done?
(I.e. what is the OMAPflash utility actually doing?)

This info could be very useful for resurrecting other devices...

EDIT: Actually the accompanying documentation explains quite well! :)
 
Last edited:
p1ceus

p1ceus

Member
Mar 26, 2010
30
2
Brno
Hello guys,
I have a bricked Nexus (non-branded, unlocked, Europe GSM) that wont boot, only response is "OMAP4440" driver popping up in Windows. I installed the driver from the package from post #1 and this is what I get from cmd window:
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
»     -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.txt
» @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  F7 4E 95 42 0E 03 0F 91 21 E4 42 51 C9 0B CC 21 7D EC 40 FE
» 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.signed.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)

  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
» Found device (omap usb)
» Waiting for 2nd
  00463-004-TX ACK
  00554-005-RX:OKAY: 2nd started
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 0 width 4 delay 9 rpapi_base 0x00030400
» Downloading driver
  00385-006-TX:driver EMMC sid 0 width 4 delay 9 rpapi_base 0x00030400
  00463-007-TX ACK
  00554-008-RX:OKAY: expecting download
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
  00385-009-TX:download:0000b838
  00527-010-RX:data00018000
» Sending data (47160 bytes) :::::::::::::....... [32768]
  00148-011-TX 32768 bin bytes
  00527-012-RX:data00013838
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
  00148-013-TX 14392 bin bytes
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
  00463-014-TX ACK
  00483-015-RX:INFO: Interface 'OMAPFLASH DRIVER v6'
          Interface 'OMAPFLASH DRIVER v6'
  00463-016-TX ACK
  00483-017-RX:INFO: Driver 'eMMC JESD84-A43'
          Driver 'eMMC JESD84-A43'
  00463-018-TX ACK
  00483-019-RX:INFO: Driver configuration: sid = 0x00000000
          Driver configuration: sid = 0x00000000
  00463-020-TX ACK
  00483-021-RX:INFO: Driver configuration: width = 0x00000004
          Driver configuration: width = 0x00000004
  00463-022-TX ACK
  00483-023-RX:INFO: Driver configuration: delay = 0x00000009
          Driver configuration: delay = 0x00000009
  00463-024-TX ACK
  00483-025-RX:INFO: Driver configuration: rpapi_base = 0x00030400
          Driver configuration: rpapi_base = 0x00030400
  00463-026-TX ACK
  00483-027-RX:INFO: MMC sid                = 0x00
          MMC sid                = 0x00
  00463-028-TX ACK
  00483-029-RX:INFO: MMC mmc_volt           = 0x01
          MMC mmc_volt           = 0x01
  00463-030-TX ACK
  00483-031-RX:INFO: MMC data_width         = 0x04
          MMC data_width         = 0x04
  00463-032-TX ACK
  00483-033-RX:INFO: MMC card_rca           = 0x00
          MMC card_rca           = 0x00
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x00
          MMC card_type          = 0x00
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x00
          MMC data_width_support = 0x00
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0x00
          MMC transfer_clk_max   = 0x00
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x00
          MMC card_size          = 0x00
  00463-042-TX ACK
  00483-043-RX:INFO: MMC mmc_config return 0x00FF8080
          MMC mmc_config return 0x00FF8080
  00463-044-TX ACK
  00483-045-RX:INFO: EMMC eMMC DRIVER DEINIT COMPLETE
          EMMC eMMC DRIVER DEINIT COMPLETE
  00463-046-TX ACK
  00494-047-RX:FAIL: Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Download failed (final data response error): Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE
» Elapsed time: 0:05.445 (8730 bytes/s)
» Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE)
» Elapsed time: 0:20.860

(I first run the .bat file and then connect the phone without battery in it - but it is the same with battery inserted)

I also try this on W7 x64 and WXP x86 but no joy on any of these systems. Eve tried different USB cables, put the phone to fridge for few minutes (cuz I read about some heat sensor inside - also this trick helped me to fix my HTC Desire before :))

Thanks for the reply...

EDIT:
If I compare my log with log of this guy
HTML: 
http://forum.gsmhosting.com/vbb/8522426-post73.html
my differences starting here:
Code: 
00483-033-RX:INFO: MMC card_rca           = 0x00
          MMC card_rca           = 0x00
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x00
          MMC card_type          = 0x00
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x00
          MMC data_width_support = 0x00
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0x00
          MMC transfer_clk_max   = 0x00
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x00
          MMC card_size          = 0x00

and he have it like this:
Code: 
00483-033-RX:INFO: MMC card_rca           = 0x04
          MMC card_rca           = 0x04
  00463-034-TX ACK
  00483-035-RX:INFO: MMC card_type          = 0x03
          MMC card_type          = 0x03
  00463-036-TX ACK
  00483-037-RX:INFO: MMC data_width_support = 0x08
          MMC data_width_support = 0x08
  00463-038-TX ACK
  00483-039-RX:INFO: MMC transfer_clk_max   = 0xBB80
          MMC transfer_clk_max   = 0xBB80
  00463-040-TX ACK
  00483-041-RX:INFO: MMC card_size          = 0x1D5A000
          MMC card_size          = 0x1D5A000

So just comes to my mind, is the internal memory broken/destroyed?
 
Last edited:
X

xrCore

Senior Member
Feb 19, 2010
96
3
I have a GNex that won't go into bootloader or recovery or download mode. This tool runs but nothing happens after, nothing changes. I can't get this phone fixed at all!
 
You must log in or register to reply here.

Similar threads

franciscofranco
[KERNEL] [GPL] [GN] franco.Kernel r398
Replies
45K
Views
8M
C
Ctzokas
L
Post your Galaxy Nexus home screens
Replies
14K
Views
4M
O
ohussain
osm0sis
[REF] [RADIO] [GSM] Galaxy Nexus GT-i9250 Baseband Collection & Discussion
Replies
3K
Views
1M
T
TG09
kaluoshi
  • Locked
[ROM] [4.4.4] [OFFICIAL] ParanoidAndroid 4.6
Replies
41K
Views
8M
M
malybru
PlayfulGod
[ROM] [UNOFFICIAL] [01122014] CyanogenMod 11 for the Samsung Galaxy Nexus
Replies
4K
Views
971K
PlayfulGod
PlayfulGod

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 27
    A
    androidtoy09
    People actually brick this phone!?! Seriously, what do they do? flash windows mobile on it?!
    View
    25
    DR_MOOSAVI
    DR_MOOSAVI
    https://rapidshare.com/files/1168981527/OMAPFlash_tuna.zip

    Just execute *.bat file from this package.
    Installing drivers first would be pretty smart idea too.

    Repair boot = OMAPFlash
    Repair baseband,bootloader,recovery = adb commands
    Enjoy !
    View
    1
    DR_MOOSAVI
    DR_MOOSAVI
    First you need to remove battery and then load driver for OMAP (4460usb), then its working. Looks like TI recovery procedure.

    But unfortunatelly it recovered bootloader (sbl) only, in my case eMMC pda image partition still damaged and eMMC need to be formatted completely.
    View
    1
    DR_MOOSAVI
    DR_MOOSAVI
    it's simple and easy....after install driver run bat file ,after few second ,phone repair done..
    View
    1
    matteventu
    matteventu
    Ehm... I think there's an error in the thread's title: the Galaxy Nexus GSM (i9250) in 32GB variant... doesn't exist :D
    View

New posts