[DISCUSSION] Unbrick using OMAP flasher

Search This thread

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
Ever since I saw this thread, I was curious about OMAP flasher. Could it be ported as a way to unbrick some of the people with tabs that show, "no driver found for OMA4430" on USB connection? Last night, I finally found a working link to OMAPFlash in post 46 of this thread. I tried to create a new config for the p5113, but I'm not sure it will work. Could someone with a hard-bricked p5xxx please try it on his or her device? Here are the instructions:

  1. go to the directory of the downloaded files.
  2. shift-right-click and choose open command window here
  3. go into device manager and right-click on OMAP4430. Click choose a file on the disk, and go to the OMAPFlash Recovery p5113/usb_drv_windows.
  4. once the driver is installed, go to the command prompt and type
    Code:
    OMAPFlash.exe -v fastboot flash recovery recovery.img
  5. copy the text from the command prompt and put it on this thread.

Here's the OMAPFlash download:
V1 NOT WORKING https://www.dropbox.com/s/hg1qauhhl73qiyx/OMAPFlash recovery p5113.zip
V2: for p5100 ONLY
 
Last edited:

merka_zh

Member
Sep 27, 2012
33
4
MultipleMonomials, i have bricked p5100. Just checked, following your instructions. Couldn't repair:

Code:
C:\OMAPFlash recovery p5113>OMAPFlash.exe fastboot flash recovery recovery.img

п OMAPFlash v4.15 (Aug 12 2011)

п Waiting for device (omap usb)  - [COLOR="Red"]MY COMMENT: here is nothing happens until i connect device. When I connected device - see next log:[/COLOR]
п Waiting for device (fastboot)In Fastboot Mode..

п Sending 'recovery' (5680 KB)
п Operation FAILED ()
п Elapsed time: 0:11.109
 
Last edited:
  • Like
Reactions: MultipleMonomials

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
I think I know what the problem is. Unfortunately, I have to wait for the stock ROM to download. In the meantime, does anyone know if all the tabs use the same bootloader?

Posted from my Galaxy Tab 2 with CM10.1
 

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,138
Bekasi
I think I know what the problem is. Unfortunately, I have to wait for the stock ROM to download. In the meantime, does anyone know if all the tabs use the same bootloader?

Posted from my Galaxy Tab 2 with CM10.1
From Samsung x-loader source, all Tab 2 using the same config file. I build the bootloader but the resulted MLO file much smaller than the stock MLO and too scare to trying it on my device.
 

merka_zh

Member
Sep 27, 2012
33
4
Nothing, it is same as previous time:
Code:
C:\OMAPFlash recovery p5113>OMAPFlash.exe -v fastboot flash recovery recovery.img

п OMAPFlash v4.15 (Aug 12 2011)

п -v
п fastboot
п flash recovery recovery.img
п Waiting for device (omap usb)
п Waiting for device (fastboot)In Fastboot Mode..

п Sending 'recovery' (5680 KB)
п Operation FAILED ()
п Elapsed time: 0:11.094
 

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
Try the commands
Code:
OMAPFlash chip_download EMMC@20000 Targets\Projects\p5113\MLO_4430_HS
and
Code:
OMAPFlash chip_download EMMC@80000 Targets\Projects\p5113\Sbl.bin
 

merka_zh

Member
Sep 27, 2012
33
4
Try the commands
Code:
OMAPFlash chip_download EMMC@20000 Targets\Projects\p5113\MLO_4430_HS
and
Code:
OMAPFlash chip_download EMMC@80000 Targets\Projects\p5113\Sbl.bin

Code:
E:\OMAPFlash recovery p5113>OMAPFlash chip_download EMMC@20000 Targets\Projects\
p5113\MLO_4430_HS

» OMAPFlash v4.15 (Aug 12 2011)

» Waiting for device (omap usb)
» Looking for a driver for 'EMMC'
» Error no driver found in board configuration for 'EMMC'
» Downloading

Code:
E:\OMAPFlash recovery p5113>OMAPFlash chip_download EMMC@80000 Targets\Projects\
p5113\Sbl.bin

» OMAPFlash v4.15 (Aug 12 2011)

» Waiting for device (omap usb)
» Looking for a driver for 'EMMC'
» Error no driver found in board configuration for 'EMMC'
» Downloading

Each time when "Downloading" line appears in log - application craches (OMAPFlash.exe has stopped working - Windows message) or "Operation FAILED" appears in log:
Code:
E:\OMAPFlash recovery p5113>OMAPFlash chip_download EMMC@20000 Targets\Projects\
p5113\MLO_4430_HS

» OMAPFlash v4.15 (Aug 12 2011)

» Waiting for device (omap usb)
» Found device (omap usb)
» Looking for a driver for 'EMMC'
» Error no driver found in board configuration for 'EMMC'
» Downloading
» Operation FAILED (Unknown status message '??;?')
» Elapsed time: -23:-1.-677
 

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
OK, I figured out why it's not working. I'm using the wrong device/USB ID in the config file so when OMAPFlash tries to download the bootloader, it uses a config file that doesn't specify the EMMC driver. What I need is the "id number provided by the OMAP device during perfipheral boot over UART or USB along with the <omap version> number". It should look similar to "443007". Go to the properties of OMAP4430 in Device Manager and see if you can find a number that looks similar. Thanks.
 

merka_zh

Member
Sep 27, 2012
33
4
MultipleMonomials, no similar information in Windows Device Manager...
but when i played with OMAPFlash with pre-builded configurations for other platforms i seen massages like this:

Code:
Searching 2nd for: OMAP4430_1GHZ_8G_HS 443007 04 HS
and
Code:
Error no 2nd for: OMAP4460_TUNA_8G_HS_PRO 443007 04 HS

I'm sure that 443007 - this value read from device because here was other value for other devices but same configuration files when i testing it.

Also when i run OMAPFlash without any configuration files (all configs with OMAP string and 443007 deleted) it is displays same value for my P5100 too:

Code:
C:\OMAPFlash recovery p5113>OMAPFlash -t 36000 -2

п OMAPFlash v4.15 (Aug 12 2011)

п Looking for device (omap usb)
п Please turn on device
п Waiting for device (omap usb)
п Found device (omap usb)
п Requesting ASIC id
п Searching 2nd for: (null) 443007 04 HS
п Error no 2nd for: (null) 443007 04 HS


---------- Post added at 01:27 AM ---------- Previous post was at 01:20 AM ----------

Maybe this log will helpfully for you too, i have tried to repair P5100 with other pre-builded .bat file - but unsuccessful

Code:
C:\1\omap4430hs_espresso>"omap4430hs_espresso.bat"

п OMAPFlash v4.15 (Aug 12 2011)

п -v
п Entering parameter file:Targets\Projects\espresso\omap4430hs_1000MHZ.txt at li
ne: 1
п     -omap 4
п     -t 36000
п     -p OMAP4430_1GHZ_8G_HS
п     -2
п     chip_download EMMC Targets\Projects\espresso\MLO
п     chip_download EMMC Targets\Projects\espresso\Sbl.bin
п     command cold_sw_reset
п Leaving parameter file:Targets\Projects\espresso\omap4430hs_1000MHZ.txt
п @Targets\Projects\espresso\omap4430hs_1000MHZ.txt
п Looking for device (omap usb)
п Please turn on device
п Waiting for device (omap usb)               [COLOR="Red"] # HERE OMAPFLASH WAITING FOR DEVICE CONNECTED + POWER BUTTON[/COLOR]
п Found device (omap usb) 
п Requesting ASIC id
п AsicId items 05
п AsicId id             01 05  01  44 30 07 04
п AsicId secure_mode    13 02  01  00
п AsicId public_id      12 15  01  F2 8C F5 50 1D C8 E6 8D BA F0 DD CB 95 CA 73
75 54 92 D2 71
п AsicId root_key_hash  14 21  01  B5 85 AC F1 DD 15 B0 6A 74 81 3B FD DD 6E CD
64 22 7C E4 C9 06 58 C6 5B 4C 53 AC 22 9B 4C 6D C0
п AsicId checksum       15 09  01  9C 66 9A D9 68 2A DC CF
п Searching 2nd for: OMAP4430_1GHZ_8G_HS 443007 04 HS
п Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs.1GHZ
п Entering parameter file:omapflash2nd.txt at line: 46
п     -pheriphalboot_reopen
п Reading board configuration file Targets\Configurations\configuration_omap4430
_8g_ver416.txt
п Reading definition file .\Targets\Definitions\definitions_omap4.txt
п     -board_config Targets\Configurations\configuration_omap4430_8g_ver416.txt
п Leaving parameter file:omapflash2nd.txt
п Sending size of second file (0x000079B0 bytes)
п Transferring second file to target (0x79B0 bytes)
п Closing boot connection               [COLOR="Red"] # HERE IS DEVICE TURNED OFF[/COLOR]
п Waiting for device (omap usb)              [COLOR="Red"] # HERE IS OMAPFLASH WAITING AGAIN FOR POWER BUTTON PRESSED[/COLOR]
п Found device (omap usb)
п Waiting for 2nd
п Unknown status message 'h????????' during peripheral boot (waiting for 2nd)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I hope someone donating me a hard bricked P31xx or P51xx :D Thinking about flashing standard OMAP4 x-loader and u-boot. Booting standard Ubuntu Desktop from Linaro project will be super cool :)
    1
    MultipleMonomials, i have bricked p5100. Just checked, following your instructions. Couldn't repair:

    Code:
    C:\OMAPFlash recovery p5113>OMAPFlash.exe fastboot flash recovery recovery.img
    
    п OMAPFlash v4.15 (Aug 12 2011)
    
    п Waiting for device (omap usb)  - [COLOR="Red"]MY COMMENT: here is nothing happens until i connect device. When I connected device - see next log:[/COLOR]
    п Waiting for device (fastboot)In Fastboot Mode..
    
    п Sending 'recovery' (5680 KB)
    п Operation FAILED ()
    п Elapsed time: 0:11.109
    1
    Hello. I have a Kindle HD 8.9. Can I use this utility to flash u-boot.bin. CPU OMAP 4470. I flash script FIRE FIRE FIRE and erase all: u-boot, boot.img and recovery from EMMC. Can you help me please.