Skip to content

GT I9300 dump results a 0k img file #58

Closed
nka11 opened this Issue Oct 5, 2012 · 7 comments

4 participants

@nka11
nka11 commented Oct 5, 2012

Ubuntu 12.04 x64
Heimdall 4.1RC1 patched with #56
device GT-I9300

heimdall dump --chip-type NAND --chip-id 5 --output boot.img --verbose --stdout-errors
Heimdall v1.4 RC1

Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 83
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error -2136414344 whilst receiving packet.

Protocol is not initialised.

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun with device of type: 0.

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

Attempt complete

$ ls -la
0 -rw-r--r--   1 root root         0 oct.   5 21:32 boot.img

I also tried with --delay 400 for the same result

@nka11
nka11 commented Oct 5, 2012

btw, just as a reminder, the pit :

Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: mx.pit
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5423104
Partition Block Count: 1146880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 6569984
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained

@getochkn getochkn referenced this issue Oct 17, 2012
Closed

T959W Support #66

@nickl-
nickl- commented Oct 28, 2012

I'm also getting nothing out of the dumps how are we supposed to identify the chip id? I tried 0 - 5 but get the same as per @nka11 's findings, the result is a 0K image file output.

Same device, i9300
Mac OS X 10.6

@Benjamin-Dobell
Owner

This might sound a little bit strange... but dumping has never actually worked. Let me explain...

Theoretically, the Odin protocol supported dumping of data from phones, however I've never encountered a device that actually implements this functionality in its secondary bootloader. My guess is that its either deprecated functionality, or you require a special secondary bootloader which Samsung don't distribute.

Unless someone who has somehow used this functionality chimes in, I'll remove the dump command from the final 1.4 build to prevent further confusion.

I should note that devices do actually support something known as Upload Mode. This isn't usually accessible, you first need to change a flag on the device from DLOW, to DMED or DHGH (or DHIG, I can't remember). Then its accessible through home and volume up, at least this is the case for the GT-I9000 anyway.

I haven't had a chance to look into Upload Mode yet, and for some reason it seems to have been largely ignored by third-party developers. When I finally have some free time I'll try look into it.

@nickl-
nickl- commented Oct 28, 2012

I haven't looked at the code so let me apologize in advance if it should be obvious.

@Benjamin-Dobell Can you shed some light on what the chip id represents or how we can locate its definition in the pit perhaps?

The fact that dump is not implemented on the front end was already an indication but I was hoping motivations were more leaning towards eventual implementation rather than complete removal. This would be extremely valuable as a non destructive means of storing initial state before the hacking begins. Which seems oddly missing from the currently suggested modus operandi. Is there another way perhaps to dump the recovery partition for example before flashing a custom recovery?

@trogdan
trogdan commented Nov 29, 2012

Using this reference, http://forum.xda-developers.com/showpost.php?p=27345435&postcount=19 you can set the debug level to DHGH via *#9900# System Dump Mode. When you press Power-High-Home the GS3 shows "Hardware Reset" and what looks to be some variable status. It Looks like Heimdall gets to the "Handshaking with Loke" then fails to receive a response. Will see what is going on at the code/usb level.

BTW, is this what Upload Mode looks like? https://dl.dropbox.com/u/89869044/CameraZOOM-20121113102842213-1.jpg

@trogdan
trogdan commented Nov 29, 2012

@Benjamin-Dobell Another Question, where is the secondary bootloader located? Would like to take a look at this. Rumor is that the samsung is releasing the source code for the exynos bootloader by the end of 2012, but I'm not holding my breath. http://rootzwiki.com/news/_/articles/announcements/samsung-to-unlock-exynos-4-series-source-code-by-end-of-2012-r1203

@Benjamin-Dobell
Owner

Dumping behaviour is no longer (and technically never was) supported. #97

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.