Related
Here are the partitions for the Epic 4G Touch as identified by Heimdall. The .pit file was successfully created by odub303 and found here
After talking to Hacre he informed me that the partition Identifier is offset by -1.
So basically, if the partition identifier below says "7" for recovery.bin, then it means it is actually mmcblk0p6....
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.bin
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 614400
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 720896
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 753664
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1802240
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5996544
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 30130176
Partition Block Count: 638976
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
nice, needed this! thanks jerdog
just updated the OP to reflect that each partition number is offset by -1
does anyone know what factoryfs.img does?
Maybe u can flash that to zimage partition? Sorry for my idiotic questions, maybe someone can enlighten me, there's no instructions on any of this.
zedomax said:
does anyone know what factoryfs.img does?
Maybe u can flash that to zimage partition? Sorry for my idiotic questions, maybe someone can enlighten me, there's no instructions on any of this.
Click to expand...
Click to collapse
I hope you don't flash that to the zImage partition..... factoryfs.img is the stock /system image for the phone....
others can probably state it more eloquently though.
zedomax said:
does anyone know what factoryfs.img does?
Maybe u can flash that to zimage partition? Sorry for my idiotic questions, maybe someone can enlighten me, there's no instructions on any of this.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hacre said:
Click to expand...
Click to collapse
OMG. That's what u said.
Lets go over some of these...
Code:
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
This looks like a first in Loke history. Apparently this device is capable of writing to external SDCard? Be careful while flashing. Correct me if this is not external mmc.
Code:
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
this is the Primitive Bootloader. This is the first bit of firmware loaded on your device at boot time. It initializes memory and loads the SBL.
Code:
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
The EFS is a partiton which handles the serial number and carrier information on your device. be careful with this. You may lose service if you mess up this partition. make sure that you copy this partition. Google "EFS Backup STL3" for more information.
Code:
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
This is the Secondary bootloader. it can be considered an operating system on it's own. This is where loki (what Heimdall and Odin talk to) lives. It also has an SBL prompt which you can use over UART to talk to the device and load/delete partitions or make serious changes to the device. A wrong SBL can lead to bricking. Make sure you flash boot.bin and Sbl.bin at the same time. To be safe, flash params and repartition as well.
Code:
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
Usually this is a duplicate of SBL. It is intended for a backup but I'm not totally convinced it's operational. This is supposed to be like a backup SBL, but I've never found it useful especially because it won't boot if the PBL does not match.
Code:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
this is where SBL stores information. This is the settings for boot and contains the image you see on startup as well as the Download Mode image and others.
Code:
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
This partition is where the Linux kernel lives. Nuff said.
Code:
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.bin
This partition is a duplicate of the Kernel partition. It is intended to be used for a recovery but I have never found it useful. You can flash garbage to it and the phone will boot and enter recovery just fine. However, if you flash garbage to the kernel partition, this partition won't boot. I don't understand it's function really...
Code:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 614400
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
this is a partition for quick loading of apps and system data. it functions like any other cache.
Code:
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 720896
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
This is a firmware like the Linux kernel for the Modem. The modem contains an entire operating system on it. This is the reason we can talk and surf and play with apps at the same time. This firmware won't keep the phone from booting, but it can affect things like Phone, Data and GPS.
Code:
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 753664
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
This is the /system/ folder. it contains Android.
Code:
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1802240
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
This partition contains all of your apps which you download from the market. It's a general-purpose partition with read/write/execute permissions
Code:
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5996544
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:
I don't know what UMS is... I assume it's like a second modem on the device. It is likely the same as the MODEM device with a bit different functionality.
Code:
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 30130176
Partition Block Count: 638976
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
I've no experience with this partition.
Code:
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
this is not a real partition. it is 0 lenght
Anyone care to elaborate on UMS and Hidden?
I'd like to note that Voodoo LagFix is no longer required.. These are all EXT4 partitions!
btw... why is this stickied? The pit file is a useful tool. a printout won't help for anything.
Good to know - thanks. Unstickied.
zedomax said:
does anyone know what factoryfs.img does?
Maybe u can flash that to zimage partition? Sorry for my idiotic questions, maybe someone can enlighten me, there's no instructions on any of this.
Click to expand...
Click to collapse
LOL seriously, this coming from a guy who supposely makes kernel yet doesn't know what factoryfs is and asks if it can be flashed to zImage? ROFL.
Is there a key combo to zap the PRAM? That will most likely fix any issue anyone has! also kidding.
Sent from my SPH-D710 using xda premium
This is info and you did not create anything therefore this belongs in general section... You wanted to be technical so let's be technical
Sent from my SPH-D710 using xda premium
ervman1 said:
This is info and you did not create anything therefore this belongs in general section... You wanted to be technical so let's be technical
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Jerdog fixed that issue. I know the point you are making but lets be gentlemen and move past it. Thanks for the info Jerdog
Sent from my SPH-D710 using xda premium
ervman1 said:
This is info and you did not create anything therefore this belongs in general section... You wanted to be technical so let's be technical
AGREE.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App
ervman1 said:
This is info and you did not create anything therefore this belongs in general section... You wanted to be technical so let's be technical
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
But it's enough dev related to have it in here.
From this post and thanks to PIT Magic (own thread), here is the PIT analysis for this device.
Code:
----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: totoro_0623.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 15 (4 Bytes)
----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String: toto
Hexadecimal: 746F746F
----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #5 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data Length: (4 Bytes Per Block, 20 Bytes In Total.)
----------------------------------------------------------
Header Size: (28 Bytes)
----------------------------------------------------------
<<< PIT File Entries >>>
----------------------------------------------------------
----------------------------------------------------------
Entry Memory Address: 0x1C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 0
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: bcm_boot
Flash FileName: BcmBoot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 1
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: loke
Flash FileName: sbl.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 2
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: loke_bk
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 3
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: systemdata
Flash FileName: totoro.pit
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 1 (COM. PROCESSOR)
Device Type: 0 (UNKNOWN)
Identifier: 4
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 50
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: modem
Flash FileName: BcmCP.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 21
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: param_lfs
Flash FileName: param.lfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 5
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: boot
Flash FileName: boot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 6
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: boot_backup
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 20
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 920
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: system
Flash FileName: system.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 22
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 160
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: cache
Flash FileName: csc.rfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 23
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 789
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: userdata
Flash FileName: userdata.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 7
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: efs
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 8
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: sysparm_dep
Flash FileName: sysparm_dep.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 9
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: umts_cal
Flash FileName: HEDGE_NVRAM8_RF_LE.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 0 (UNKNOWN)
Identifier: 10
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 256
Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: cal
Flash FileName:
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------
PIT file: http://forum.xda-developers.com/attachment.php?attachmentid=1489509
blk
http://forum.xda-developers.com/showthread.php?p=23540706 earlier discussion on SGY partn
great tool.
which device name is the full NAND now ?
/dev/block/?????????
mai77 said:
http://forum.xda-developers.com/showthread.php?p=23540706 earlier discussion on SGY partn
great tool.
which device name is the full NAND now ?
/dev/block/?????????
Click to expand...
Click to collapse
Can you post the output of this command?
Code:
ls -lR /dev/block
Ok found it: http://forum.xda-developers.com/showpost.php?p=34302258&postcount=21
so this shell cmds gave me a 501 MB file which is probably the NAND dump :
adb shell
su
stop
dd if=/dev/block/bml0!c of=/sdcard/bml0c.outfile
## wait 2 minutes to finish
start
## wait 30 sec
mai77 said:
so this shell cmds gave me a 501 MB file which is probably the NAND dump :
adb shell
su
stop
dd if=/dev/block/bml0!c of=/sdcard/bml0c.outfile
## wait 2 minutes to finish
start
## wait 30 sec
Click to expand...
Click to collapse
Please run gptfdisk on the bml0!c raw file to see if has some partitions
scandiun said:
Please run gptfdisk on the bml0!c raw file to see if has some partitions
Click to expand...
Click to collapse
shows no partitions, 100 % free space on disk-image
neither mbr bsd apm nor GPT found by gptfdisk
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
tt is a oneNAND system
the dump contains all messages as plain string text
I used Heimdall and got this:
Code:
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/
Entry Count: 15
Unknown 1: 1869901684
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: bcm_boot
Flash Filename: BcmBoot.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: loke
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: loke_bk
Flash Filename:
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: systemdata
Flash Filename: totoro.pit
FOTA Filename:
--- Entry #4 ---
Binary Type: 1 (CP)
Device Type: 0 (OneNAND)
Identifier: 4
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 50
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: modem
Flash Filename: BcmCP.img
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 21
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: param_lfs
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: boot
Flash Filename: boot.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: boot_backup
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 20
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 920
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: system
Flash Filename: system.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 22
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 160
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: cache
Flash Filename: csc.rfs
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 23
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 789
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: userdata
Flash Filename: userdata.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 7
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: efs
Flash Filename:
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 8
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: sysparm_dep
Flash Filename: sysparm_dep.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: umts_cal
Flash Filename: HEDGE_NVRAM8_RF_LE.bin
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 256
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: cal
Flash Filename:
FOTA Filename:
GNU Parted 1.8.8.1.179-aef3
Using /dev/bml1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) version
version
version
GNU Parted 1.8.8.1.179-aef3
Copyright (C) 1998 - 2006 Free Software Foundation, Inc.
does seem to know oneNAND partns either
parted just can handle the sd card on SGY
Wow its not noob stuff
I wanna know how if we change partition size maybe we can got extra size for /data maybe
ya itz poss with PIT FILE MAGIC see above
look up the tags.
but which parted (editor) is working on on our SGY'S "oneNAND" and which partition manager ?
mai77 said:
shows no partitions, 100 % free space on disk-image
neither mbr bsd apm nor GPT found by gptfdisk
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
tt is a oneNAND system
the dump contains all messages as plain string text
Click to expand...
Click to collapse
Run both parted (linux version and ARM version with GPT support) on that raw file, if it doesn't contain a partition table the filesystem may be obtained somehow.
storage dumper
scandiun said:
Run both parted (linux version and ARM version with GPT support) on that raw file, if it doesn't contain a partition table the filesystem may be obtained somehow.
Click to expand...
Click to collapse
some individual partns filesystems can be obtained via magicISO, because RFS is FAT compatible.
still a nice oneNAND dump reader would be a nice thing.
mai77 said:
some individual partns filesystems can be obtained via magicISO, because RFS is FAT compatible.
still a nice oneNAND dump reader would be a nice thing.
Click to expand...
Click to collapse
ok but using parted on a single partition should always work if the filesystem is recognized
http://www.linux-mtd.infradead.org/
scandiun said:
ok but using parted on a single partition should always work if the filesystem is recognized
http://www.linux-mtd.infradead.org/
Click to expand...
Click to collapse
with that stuff one can implement "mobile ODIN" flasher for SGY-phone.
How about we hack gparted to accept PIT files as partition tables?
MarcoToo said:
How about we hack gparted to accept PIT files as partition tables?
Click to expand...
Click to collapse
ya but pit magic is already more powerful than friggin parted !
mai77 said:
ya but pit magic is already more powerful than friggin parted !
Click to expand...
Click to collapse
True, but it's closed source and Windows only.
MarcoToo said:
True, but it's closed source and Windows only.
Click to expand...
Click to collapse
Ask the developer to make it free software.
savie said:
Wow its not noob stuff
I wanna know how if we change partition size maybe we can got extra size for /data maybe
Click to expand...
Click to collapse
Just modify a kernel you like to boot off how ever much space you want for /data
hey, do you still have this file?
I need someone with a stock ROM rooted or not, deodexed, odexed are fine. Use will need heimdall, and common sesne
See image attached for instructions and please save the file as PIT_SGH-T889_16GB_12-28-2012.pit, zip it and upload it here. Thanks in advance, I am working on a ROM at the moment and need this ASAP to continue development.
C'mon folks !
Lots of people could use this.
Yep hopefully someone will see it and help us out.
I might as well supplement that request with one for the T889V .pit too.
Pretty sure they are the exact same bro. I'm going to T-Mobile now to see if they will exchange it for me, if so I will pull the .pit myself.
**bummer they closed as I wrote this. Will try tomorrow, if not Samsung already sent me a return label.
From SGH-889V I got ..but when I click detect device...it says devices detected.
Heimdall v1.3.2, 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...
ERROR: Failed to access device. libusb error: -12
You have to reset after you install the drivers.
Drivers from toolkit are not sufficient ? Need to install from package also ?
---------- Post added at 10:27 AM ---------- Previous post was at 09:52 AM ----------
This is from PRINT PIT
Heimdall v1.3.2, 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...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 20
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 19757
Unknown 5: 19780
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 80
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 0
Partition Block Count: 1734
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOTLOADER
Filename: sboot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 81
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 1734
Partition Block Count: 312
Unknown 2: 0
Unknown 3: 0
Partition Name: TZSW
Filename: tz.img
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 70
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 34
Partition Block Count: 16
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: t0.pit
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 71
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 50
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: MD5HDR
Filename: md5.img
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 1
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 8192
Partition Block Count: 8192
Unknown 2: 0
Unknown 3: 0
Partition Name: BOTA0
Filename: -
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 2
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 16384
Partition Block Count: 8192
Unknown 2: 0
Unknown 3: 0
Partition Name: BOTA1
Filename: -
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 3
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 24576
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 4
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 65536
Partition Block Count: 8192
Unknown 2: 0
Unknown 3: 0
Partition Name: m9kefs1
Filename: m9kefs1.bin
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 5
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 73728
Partition Block Count: 8192
Unknown 2: 0
Unknown 3: 0
Partition Name: m9kefs2
Filename: m9kefs2.bin
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 6
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 81920
Partition Block Count: 8192
Unknown 2: 0
Unknown 3: 0
Partition Name: m9kefs3
Filename: m9kefs3.bin
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.bin
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 106496
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.img
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 122880
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.img
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 139264
Partition Block Count: 180224
Unknown 2: 0
Unknown 3: 0
Partition Name: RADIO
Filename: modem.bin
--- Entry #14 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 319488
Partition Block Count: 524288
Unknown 2: 0
Unknown 3: 0
Partition Name: TOMBSTONES
Filename: tombstones.img
--- Entry #15 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 843776
Partition Block Count: 2621440
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #16 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 13
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 3465216
Partition Block Count: 3670016
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
--- Entry #17 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 14
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 7135232
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #18 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 15
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 7176192
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: OTA
Filename: -
--- Entry #19 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 16
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 7192576
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: USERDATA
Filename: userdata.img
Ending session...
Rebooting device...
---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------
================
This is from download PIT
Heimdall v1.3.2, 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...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Ending session...
---------- Post added at 10:31 AM ---------- Previous post was at 10:28 AM ----------
=====
Pit file is only 8K is it right ?
---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------
=====
Attaching PIT file
Forgot to add ...I am using MyROM v2...But I suppose pit should remain same no matter what
Much appreciated hkfan !
crap I think my phone is gonna be bricked. I used odin 3.07 with this pit and stock t889v MCT firmware and it's stuck on get pit mapping. been waiting half an hour
Did odin formatted anything yet ..if no then I suppose you can disconnect your phone and connect again after restarting odin( just dont restart phone) ...I used to have this issue with samsung vibrant......still let someone else confirm this
Cheunk said:
crap I think my phone is gonna be bricked. I used odin 3.07 with this pit and stock t889v MCT firmware and it's stuck on get pit mapping. been waiting half an hour
Click to expand...
Click to collapse
If you are having issues make sure to:
#1. Kill all background Kies processes.
#2. Pull battery for 2 minutes, 1 of which you are holding the power button.
#3. Restart ODIN & try again.
I got lucky it didn't write anything, but I can't seem to flash the rom. Tried different usb cables and odin versions. It gets stuck at get pit for mapping.
You're saying its stuck at "get pit for mapping" with or without the repartition option checked?
If any issues with pit then I can create again... I ll wait if it doesn't not work for multiple people
Sent from my SGH-T889 using xda premium
I didn't try anything with the file, but it seems there's quite a bit of padding at the end (0x00 bytes), which might cause Odin to fail.
hkfan said:
If any issues with pit then I can create again... I ll wait if it doesn't not work for multiple people
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
can you try again ?
Meh... nvm
hi!
I have an issue with internal sd
when my phone is waking from sleep android tells me "preparing sdcard..."
This occurs in all ROM's
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 62333952 sectors, 59.4M
Logical sector size: 512
Disk identifier (GUID): 17b21fb6-f50d-4cf6-9a00-664d68cc276f
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 62333918
Number Start (sector) End (sector) Size Code Name
1 2048 62332927 59.4M 0700
Code:
heimdall print-pit --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 18
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
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: 0
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SMD
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 6
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BCT
Flash Filename: bct.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PT
Flash Filename:
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EBT
Flash Filename: bootloader.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EB2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GP1
Flash Filename: fusetrigger.bin
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 24
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: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APP
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CAC
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 7681
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IMS
Flash Filename:
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MSC
Flash Filename:
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UDA
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 10
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SOS
Flash Filename: recovery.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LNX
Flash Filename: boot.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename:
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HID
Flash Filename: hidden.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 512
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GPT
Flash Filename:
FOTA Filename:
Ending session...
Releasing device interface...
Re-attaching kernel driver...
how to fix the partition table
I want to change the partitions, in such a way that only the FAT partition was on the memory card and delete the internal FAT and extended EXT partition for programs etc., but first I must fix partition table
croolyc said:
hi!
I have an issue with internal sd
when my phone is waking from sleep android tells me "preparing sdcard..."
This occurs in all ROM's
how to fix the partition table
I want to change the partitions, in such a way that only the FAT partition was on the memory card and delete the internal FAT and extended EXT partition for programs etc., but first I must fix partition table
Click to expand...
Click to collapse
are you sure its not just external sd card?
You may read http://forum.xda-developers.com/showthread.php?t=1503595
I can send you my pit file, and you can format internal sd card in TWRP recovery.
I created a new partition on the external memory card
Unfortunately, the message "preparing sd card" still appears
fdisk now show partitions correctlyon /dev/block/mmcblk1:
Code:
Disk /dev/block/mmcblk1: 31.9 GB, 31914983424 bytes
255 heads, 63 sectors/track, 3880 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 3825 30724281 b Win95 FAT32
/dev/block/mmcblk1p2 3826 3880 441787+ 82 Linux swap
but /dev/block/mmcblk0 still shows:
Code:
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
bubor said:
I can send you my pit file, and you can format internal sd card in TWRP recovery.
Click to expand...
Click to collapse
what is PIT file? is this something like MBR??
yes - in TWRP I can format, but i can't delete, resize, create paritions on internal storage
croolyc said:
I created a new partition on the external memory card
Unfortunately, the message "preparing sd card" still appears
fdisk now show partitions correctlyon /dev/block/mmcblk1:
Code:
Disk /dev/block/mmcblk1: 31.9 GB, 31914983424 bytes
255 heads, 63 sectors/track, 3880 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 3825 30724281 b Win95 FAT32
/dev/block/mmcblk1p2 3826 3880 441787+ 82 Linux swap
but /dev/block/mmcblk0 still shows:
Code:
Disk /dev/block/mmcblk0: 7733 MB, 7733248000 bytes
4 heads, 16 sectors/track, 236000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
what is PIT file? is this something like MBR??
yes - in TWRP I can format, but i can't delete, resize, create paritions on internal storage
Click to expand...
Click to collapse
Pit file contain partition table and more. Partition table simething like MBR.
You couldnt partition with recovery, and you may brick the phone when you try it.
Hello to all of you.
I recently got a used SM-T110 (Samsung Galaxy Tab 3 lite 7"). After resetting the Tablet I tried to install a custom Recovery using this guide. The guide recommends using ODIN. Because I did not like to boot windows to install ODIN I used heimdall. After flashing (probably) to the wrong partition, the tablet wont boot at all. The screen wont show anything. I am not sure if it turns on at all. I need your help to fix this.
Here is what I did:
1) I first tried to flash to RECOVERY but this did not seem to work. The recovery still looked like stock recovery. Command
Code:
sudo heimdall flash --RECOVERY ./T110.TWRP.2.7.0.1.tar.md5 --resume
2) At this point I got the PIT (see below) using
Code:
sudo heimdall print-pit --verbose --no-reboot
3) I flashed to the other partition that looked to me like a Recovery partition:
Code:
sudo heimdall flash --DTim.Recovery ./T110.TWRP.2.7.0.1.tar.md5 --resume
4) usually the tablet should have rebooted but that did not happen. I could not get pit data at this point. aFter I turned the device off, the screen never came on again. it does not show up as a USB device when plugging into a usb port.
This is what I found out so far:
The RECOVERY Partition has a size of 16MB (assuming 512 Byte block size)
The recovery images are about 8MB so each of them should fit the RECOVERY partition
The DTim.Recovery Partition is only 1024 Blocks (0.5MB) in size. I did not notice it bevore flashing.
Questions / Guesses:
I guess I flashed (at least) to the DTim.Recovery Partition, overwriting all of the previous content in the process
I do not know if I actually wrote to the RECOVERY Partition.
AFAIK the writing process should stop at the end of the partition if my file is too big. If writing did not stop at the end of the partition I also destroyed data on the following partitions (I still have to find out which).
Did I overwrite the bootloader (if not, why does it not start, or does it)?
Given I found a way to rewrite the storage: where would I get the original data? I doubt that all of this data is contained in the stock rom image.
Any Ideas are very appreciated. I am hoping for your help. Thanks in advance.
Below you find the terminal outputs for various commands I used in chronological order. I attached a file "ausgabe.txt" containing the full terminal output including also misspelt commands, etc. Hope the code below folds. if not, this post gets really long.
Spoiler
Code:
$ sudo heimdall print-pit --verbose --no-reboot --resume
Heimdall v1.4.2
Copyright (c) 2010-2017 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: "SAMSUNG USB"
Serial No: "SAMSUNG USB SERIAL"
length: 18
device class: 2
S/N: 3
VID:PID: 04E8:685D
bcdDevice: 0000
iMan:iProd:iSer: 1:2:3
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...
Setting up interface...
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
PIT file download successful.
Entry Count: 27
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 13641
Unknown 5: 12596
Unknown 6: 48
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/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TIMH
Flash Filename: timh.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: GOYAwifi.pit
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 8142
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD
Flash Filename: ReliableData.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 12288
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD_BK
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MEP2
Flash Filename:
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 20480
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: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 61440
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Reserved
Flash Filename: Reserved
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 91136
Partition Block Count: 3072
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LOKE_2ND
Flash Filename: loke_2nd.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 95232
Partition Block Count: 3072
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LOKE_1ST
Flash Filename: loke_1st.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 163840
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: boot.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 196608
Partition Block Count: 49152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: radio.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 245760
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NVM
Flash Filename: NVM.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 278528
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 688128
Partition Block Count: 704512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1392640
Partition Block Count: 3115008
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4507648
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USER
Flash Filename: userdata.img
FOTA Filename: remained
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OBM
Flash Filename: obm.bin
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.Recovery
Flash Filename: DTim.Recovery
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 94208
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.Primary
Flash Filename: DTim.Primary
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 74
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 196608
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MAIN
Flash Filename: CP_MAIN.bin
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 75
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 212992
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MSA
Flash Filename: CP_MSA.bin
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 76
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 217088
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MAIN2
Flash Filename: CP_MAIN2.bin
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 77
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 233472
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MSA2
Flash Filename: CP_MSA2.bin
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 78
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 237568
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.CP
Flash Filename: DTim.CP
FOTA Filename:
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Releasing device interface..
This was my first successful attempt to flash the recovery
Spoiler
Code:
$ sudo heimdall flash --RECOVERY ./T110.TWRP.2.7.0.1.tar.md5
Heimdall v1.4.2
Copyright (c) 2010-2017 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...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Spoiler
Code:
$ sudo heimdall print-pit --verbose --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 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: "SAMSUNG USB"
Serial No: "SAMSUNG USB SERIAL"
length: 18
device class: 2
S/N: 3
VID:PID: 04E8:685D
bcdDevice: 0000
iMan:iProd:iSer: 1:2:3
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...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
PIT file download successful.
Entry Count: 27
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 13641
Unknown 5: 12596
Unknown 6: 48
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/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TIMH
Flash Filename: timh.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: GOYAwifi.pit
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 8142
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD
Flash Filename: ReliableData.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 12288
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD_BK
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MEP2
Flash Filename:
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 20480
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: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 61440
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Reserved
Flash Filename: Reserved
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 91136
Partition Block Count: 3072
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LOKE_2ND
Flash Filename: loke_2nd.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 95232
Partition Block Count: 3072
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LOKE_1ST
Flash Filename: loke_1st.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 163840
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: boot.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 196608
Partition Block Count: 49152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: radio.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 245760
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NVM
Flash Filename: NVM.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 278528
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 688128
Partition Block Count: 704512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1392640
Partition Block Count: 3115008
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4507648
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USER
Flash Filename: userdata.img
FOTA Filename: remained
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OBM
Flash Filename: obm.bin
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.Recovery
Flash Filename: DTim.Recovery
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 94208
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.Primary
Flash Filename: DTim.Primary
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 74
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 196608
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MAIN
Flash Filename: CP_MAIN.bin
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 75
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 212992
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MSA
Flash Filename: CP_MSA.bin
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 76
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 217088
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MAIN2
Flash Filename: CP_MAIN2.bin
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 77
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 233472
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_MSA2
Flash Filename: CP_MSA2.bin
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 78
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 237568
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTim.CP
Flash Filename: DTim.CP
FOTA Filename:
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Releasing device interface...
Log of the second flash process
Spoiler
Code:
$ sudo heimdall flash --DTim.Recovery ./T110.TWRP.2.7.0.1.tar.md5 --resume
Heimdall v1.4.2
Copyright (c) 2010-2017 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...
Claiming interface...
Setting up interface...
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading DTim.Recovery
100%
DTim.Recovery upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
After that I tried to get PIT data:
Spoiler
Code:
$ sudo heimdall print-pit --verbose --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 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: "SAMSUNG USB"
Serial No: "SAMSUNG USB SERIAL"
length: 18
device class: 2
S/N: 3
VID:PID: 04E8:685D
bcdDevice: 0000
iMan:iProd:iSer: 1:2:3
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...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...