Develop Bugs

[INFO] Samsung Galaxy Y GT-S5360 PIT File Analysis

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?

Samsung Galaxy s3 wrong partition flashed

Okay I need help!!
i will try to explain what happen to my samsung galaxy s3 model gt_i9300
I flashed the stock rom in it using heimdall 1.3 running on opensuse 12.2
I made a mistake and flashed the iz.img to the BOTA1 partition when I should of flashed it in tzsw partition....
now my phone seem to be unable to save config...
that boat1 partition look like swap to me but i dont have android deep knowledge...
Is there a way flash that partion back with maybe a good soul wiiling to upload to me?
Here is the output of heimdall print-pit
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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: 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 ---
Unused: No
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
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: mx.pit
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
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
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 65536
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.bin
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 81920
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 98304
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.img
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 114688
Partition Block Count: 65536
Unknown 2: 0
Unknown 3: 0
Partition Name: RADIO
Filename: modem.bin
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 180224
Partition Block Count: 2097152
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 2277376
Partition Block Count: 3145728
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 5423104
Partition Block Count: 1146880
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 6569984
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: OTA
Filename: -
--- Entry #15 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 6586368
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: USERDATA
Filename: userdata.img
Ending session...
Rebooting device...
Re-attaching kernel driver...

[DEV][REQ] .Pit for SGH-T889

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

R&D: Lets get this bootloader unlocked.

Alright guys, I wanna start this off with a nice healthy "I told you so". I said once Verizon was allowed to lock devices with Samsung, the rest of the carriers would follow suit. I was met with resistance on that statement, but the AT&T bootloader is now just as locked as Verizon. We need to unlock it. This forum will be pretty darn dead until we are able to do this.
The rules
Keep this thread clean. I'm asking for strict moderation. If your comment doesn't advance the thread, it will be reported and put in que to be deleted. The whole point of this thread is to maintain high information density. This isn't a support thread. If someone has a "user-level" question about something, take it to a new thread in the Q&A forums. The mission isn't to support everything.. We're focusing on just one thing and that's:
Lets get this bootloader unlocked
First up, lets make it perfectly clear. This device is bootloader locked.
Odin Mode
{
"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"
}
Partition Structures.. Here's the output from heimdall print-pit
Code:
Heimdall v1.4 RC2
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: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
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: 82
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: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 33
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 13881
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
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: 25544
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 33736
Partition Block Count: 105528
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139264
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139520
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl2.mbn
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 140032
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL3
Flash Filename: sbl3.mbn
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 141056
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 145152
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 147200
Partition Block Count: 33792
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename:
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180992
Partition Block Count: 27904
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 208896
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 215040
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 221184
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 222744
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 224304
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 225864
Partition Block Count: 5652480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5878344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename:
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5894728
Partition Block Count: 4239360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10134088
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10166856
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10187336
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10207816
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10220104
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10226248
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10226264
Partition Block Count: 18432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 27
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10244696
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
FOTA Filename:
--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 28
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10285656
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img.ext4
FOTA Filename:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 29
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10326616
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
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: MSM8960.pit
FOTA Filename:
--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
--- Entry #32 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Here's the partitions on the device from /dev/block/platform/msm_sdcc.1/by-name :
Code:
lrwxrwxrwx root root 1970-01-02 02:12 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 02:12 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 02:12 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 02:12 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 02:12 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 02:12 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 02:12 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 02:12 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 02:12 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 02:12 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 02:12 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 02:12 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 02:12 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 02:12 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 02:12 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 02:12 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 02:12 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 02:12 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 02:12 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 02:12 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 02:12 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 02:12 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 02:12 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 02:12 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 02:12 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 02:12 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 02:12 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 02:12 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 02:12 userdata -> /dev/block/mmcblk0p29
The following partitions do not have links to /dev/block.
Code:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
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: MSM8960.pit
FOTA Filename:
--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
--- Entry #32 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
Teardown
I did a teardown of the GS4 as soon as I received it. Here is some video footlage
If you're looking for information about individual chips, start here at 35 minutes in:
UART
UART output video analysis: http://www.youtube.com/watch?feature=player_detailpage&v=wK7Te0lWxDA#t=4514s
UART output text: http://pastebin.ubuntu.com/5609061/
System files
The files contained here come directly from my device. I will not guarantee that they will flash. In fact, the SYSTEM partition has been modified so it will likely not flash. However, this is a copy of ALL THE partitions on my device. Odin Flashable ROM: http://d-h.st/BHF
To my knowledge we don't have a version of Odin that will work properly with this device yet.
These are my device-specific files. I am posting them in hopes they will be helpful. I recommend NEVER flashing them to a live device otherwise you will end up with some funky stuff and probably under the same surveillance that I am under . Basically, this will change your serial numbers and stuff and they will no longer be right. Don't flash them:http://d-h.st/8Hc
root
djrbliss has attained root here: http://forum.xda-developers.com/showthread.php?t=2252248
I've packaged a CASUAL method based 100% on @djrbliss method. I prefer CASUAL as the same file will work on all platforms and it's contained within a single executable. http://d-h.st/64i
Heimdall
heimdall is broken. Here is an output
Code:
[email protected]:~/Desktop/GS4CASUAL/partitions/new$ sudo heimdall flash --BOOT ./boot.img --verbose
Heimdall v1.4 RC2
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: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
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: 82
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: 01
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.
Protocol is not initialised.
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%File Part #0... Response: 0 0 0 0 0 0 0 0
12%
File Part #1... Response: 0 0 0 0 1 0 0 0
25%
File Part #2... Response: 0 0 0 0 2 0 0 0
38%
File Part #3... Response: 0 0 0 0 3 0 0 0
50%
File Part #4... Response: 0 0 0 0 4 0 0 0
63%
File Part #5... Response: 0 0 0 0 5 0 0 0
76%
File Part #6... Response: 0 0 0 0 6 0 0 0
88%
File Part #7... Response: 0 0 0 0 7 0 0 0
100%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/Desktop/GS4CASUAL/partitions/new$
Tasks/moving forward
[*]Obtain stock System.img WITHOUT A SINGLE MODIFICATION. We need to figure out a way to get @djrbliss's exploit to attain root permissions, then simply copy the /dev/block/platform/msm_sdcc.1/by-name/system partition off the device. Stock Firmware is here: http://forum.xda-developers.com/showthread.php?t=2261573
[*]Heimdall is having problems with this device so Heimdall will require an update. If someone would, please follow @Benjamin Dobell's tutorial here and submit a log of a simple package so we can get heimdall working. http://www.xda-developers.com/android/heimdall-and-usb-logging-tutorial-xda-developer-tv/
[*]This relies on two unknowns, but we need a bootloader set which does not have signature checks enabled. Possibly from a developer version. It may be possible to replace the SBL1,2,3 and aboot with an unsigned bootloader set which will break the chain of trust above the bootloader Will not work because of signatures
[*]Figure out how the PARAM partitioning works. I see that there is support for partition tables in the PARAM partition based on the Little Kernel bootloader output from above. This means it's possible we can boot from SD.
[*]Determine the possibility of loading custom firmware with Samsung Knox
[*]Once we have the items above done, we can move on to writing the exploits. [/LIST]
This is an open-forum discusson. But, please, please... keep it professional and on-track. Strict moderation is in effect. Anyone else have insight? If you can contribute to any of the goals here, please do. It will help the community.

Awesome work, bad news on it being locked. I assume rooting and doing some minor /system mods like disabling some bloat won't soft brick. Another fun challenge!

ookba said:
Awesome work, bad news on it being locked. I assume rooting and doing some minor /system mods like disabling some bloat won't soft brick? How cautious do we have to be? How does the Bootloader monitor modifications to the partitions? Or does it? Another fun challenge!
Click to expand...
Click to collapse
this thread isn't for you. Ask questions like those in Q&A.

AdamOutler said:
this thread isn't for you. Ask questions like those in Q&A.
Click to expand...
Click to collapse
Haha. I guess I can see why you would say that. I've actually unlocked and assisted unlocking plenty of HTC bootloaders and SPLs back in day. I will help as much as I can here.

adam your root Jar does not work on OSX
4/28/13 7:44:59.080 PM [0x0-0xd90d9].com.apple.JarLauncher: java.lang.UnsupportedClassVersionError: CASUAL/CASUALApp : Unsupported major.minor version 51.0
is what console is showing... im not sue if its on my end but i just wanted to let you know

cant wait to see what happens with this! my system only boots into recovery and download mode if there is anything i can do to help let me know!

ookba said:
Haha. I guess I can see why you would say that. I've actually unlocked and assisted unlocking plenty of HTC bootloaders and SPLs back in day. I will help as much as I can here.
Click to expand...
Click to collapse
Read up on it and come back when you have something to contribute or update.
howtomen said:
adam your root Jar does not work on OSX
4/28/13 7:44:59.080 PM [0x0-0xd90d9].com.apple.JarLauncher: java.lang.UnsupportedClassVersionError: CASUAL/CASUALApp : Unsupported major.minor version 51.0
is what console is showing... im not sue if its on my end but i just wanted to let you know
Click to expand...
Click to collapse
you don't belong here either. your java is out of date. blame mac, and update java. Go to Q&A for further support. I swear to god, we're not running a daycare and this is EXACTLY what I posted in the rules.

AdamOutler said:
Read up on it and come back when you have something to contribute or update.
you don't belong here either. your java is out of date. blame mac, and update java. Go to Q&A for further support. I swear to god, we're not running a daycare and this is EXACTLY what I posted in the rules.
Click to expand...
Click to collapse
AdamOutler said:
Alright guys, I wanna start this off with a nice healthy "I told you so". I said once Verizon was allowed to lock devices with Samsung, the rest of the carriers would follow suit. I was met with resistance on that statement, but the AT&T bootloader is now just as locked as Verizon. We need to unlock it. This forum will be pretty darn dead until we are able to do this.
I've packaged a CASUAL method based 100% on @djrbliss method. I prefer CASUAL as the same file will work on all platforms and it's contained within a single executable. http://d-h.st/64i
Click to expand...
Click to collapse
listen i know what your trying do the reason i was informing u is because u claimed as stated in bold above that it works on all platforms which it does not... and i am running the latest java. not starting flame anything just letting u know. this isnt a daycare... i was just testing ur file and found a flaw.

howtomen said:
listen i know what your trying do the reason i was informing u is because u claimed as stated in bold above that it works on all platforms which it does not... and i am running the latest java. not starting flame anything just letting u know. this isnt a daycare... i was just testing ur file and found a flaw.
Click to expand...
Click to collapse
A) Please stay on topic on this post
B) if you are going to report a bug that appears to be releated to the runtime, say which you are running (ie Oracle version X, Apple version X, openjre version X etc). I'm going to bet you are using apple's, which is both up to date (to apple), and out of date (compared to oracle). I run into similar problems (with other software).

This should be moved to orginal development IMHO.

Off-topic intro: Good to see you again, AdamOutler. It's been a great pleasure working with you in the past. Love the video - you're like a surgeon with that thing.
Somewhat related part: I've looked into the USB chip a little bit from an external perspective (playing with resistors on the ID pin). I've achieved two different types of UART output and "Factory Mode" (see next section), but unfortunately that's all I've seen. It seems older Samsung devices had the FSA9480 (or similar), and we had lists of different resistances we could try... but none of these other resistances work now on the S4.
Possibly useful part: When using 301k resistance, we get "Factory Mode" instead of "Odin Mode". I don't know if this makes any difference, but I figured it would be worth pointing out here. See attached screenshot.
Question regarding UART: Previously, we were able to get an SBL prompt using UART. Is this not possible, or is this the "console=null" part you were looking at in the UART output? If we got to this prompt, I would imagine this to be quite useful.
Request for info: Can you shed any light on the USB chip? We're trying to find out which resistances enable different modes, such as car dock mode (if it still exists) and anything else that might be useful. Heck, there may be some fancy new modes that might be useful for unlocking this bootloader (unlikely).
Thanks again for your amazing contributions to the community.

Hi Adam,
Was hoping you would get this going. Started looking into some of those unknown chips and then I came across this.
http://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947/2
Looks like they did their own tear down of the AT&T Galaxy S4 and provide some nice information about what each chip is and who manufacturers the chip. Hopefully this is helpful in diagnosing the board itself and some insight on how the board is laid out to figure out how to crack this bootloader.
DX

Aou said:
Possibly useful part: When using 301k resistance, we get "Factory Mode" instead of "Odin Mode". I don't know if this makes any difference, but I figured it would be worth pointing out here. See attached screenshot.
Click to expand...
Click to collapse
generally Factory Mode and Odin Mode are the same I have never come across a practical difference except the words. However, we can figure out more once we get a bootloader analysis.
Question regarding UART: Previously, we were able to get an SBL prompt using UART. Is this not possible, or is this the "console=null" part you were looking at in the UART output? If we got to this prompt, I would imagine this to be quite useful.
Click to expand...
Click to collapse
Probly. However, I'm 100% sure null console is embedded into the boot.img. I'm 90% sure the entire boot.img is signed.
Code:
[email protected]:~/Desktop/GS4CASUAL/partitions/new$ cp ../boot.img ./
[email protected]:~/Desktop/GS4CASUAL/partitions/new$ abootimg -x ./boot.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
[email protected]:~/Desktop/GS4CASUAL/partitions/new$ cat ./bootimg.cfg
bootsize = 0xa00000
pagesize = 0x800
kerneladdr = 0x80208000
ramdiskaddr = 0x82200000
secondaddr = 0x81100000
tagsaddr = 0x80200100
name =
cmdline = console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
[email protected]:~/Desktop/GS4CASUAL/partitions/new$
Request for info: Can you shed any light on the USB chip? We're trying to find out which resistances enable different modes, such as car dock mode (if it still exists) and anything else that might be useful. Heck, there may be some fancy new modes that might be useful for unlocking this bootloader (unlikely).
Click to expand...
Click to collapse
I can't at this time. However, I would bet it's an FSA**** chip being that they've always used that for resistance monitoring between pins 4 and 5 (aka x and 4).
I got a phone call from Josh (@Connexion2005 ) from MobileTechVideos.COM . He managed to do a JTAG on this device. You can seee more here. http://www.youtube.com/watch?v=PkfEhu4trRY He's just as interested as anyone else in getting this device unlocked. Here's some highlights/relevant information from our conversation which pertains to this unlock
@Connexion2005 has the ability to recover ANY bootloader problem at this time. This will bring "Hard Bricked" devices to Working or "Soft Bricked" states.
He did not grab the SYSTEM partition because this is generally provided by SAMSUNG. His reference device is now rooted which invalidates the SYSTEM partition. The SYSTEM partition must be torn from an unrooted device.
The Flash Counter and mod status has been located in the PARAM in the past. We need to get this torn from a live, unmodified device.
Josh has volunteered to provide a 100% stock SYSTEM and PARAM if somone can provide him a device
So, if anyone wishes to ship their 100% stock device out to MobileTechVideos.com , he will be able to provide us a 100% back to stock as torn from a live Galaxy S4 device.

I just got the system files up and online bootloaders, kernel, modem, system, and everything else. it's a 1.7gig tar.md5.gz file. 3Gigs uncompresed! Even though it's in Odin format, because it contains a rooted SYSTEM partition, it will not flash properly. Again, do not flash this file. http://d-h.st/BHF ping @Ralekdev

AdamOutler said:
I just got the system files up and online bootloaders, kernel, modem, system, and everything else. it's a 1.7gig tar.md5.gz file. 3Gigs uncompresed! Even though it's in Odin format, because it contains a rooted SYSTEM partition, it will not flash properly. Again, do not flash this file. http://d-h.st/BHF ping @Ralekdev
Click to expand...
Click to collapse
Not to hijack this thread gents, but curious as to how to check if the bootloader is locked on USCC (uscellular) devices.
Here's a screenshot I uploaded:
http://imgur.com/ci5h1k9

kallell said:
Not to hijack this thread gents, but curious as to how to check if the bootloader is locked on USCC (uscellular) devices.
Here's a screenshot I uploaded:
http://imgur.com/ci5h1k9
Click to expand...
Click to collapse
Code:
Write Protection: Enable
Yep, you're locked. Also, don't hijack the thread, please.

breakingspell said:
Code:
Write Protection: Enable
Yep, you're locked. Also, don't hijack the thread, please.
Click to expand...
Click to collapse
Fairly certain "WRITE PROTECTION: ENABLE" its not a determining factor.

Maybe we could start a donation fund for some developers to get devices. What do you guys think?

slider2828 said:
Maybe we could start a donation fund for some developers to get devices. What do you guys think?
Click to expand...
Click to collapse
Bounties are ok, as in "I will give X to whomever does X first".
Threads with the intent just to buy dev devices are not (unless a more senior mod wants to step in and clarify the rules more).

Hey guys. My friend has a stock AT&T S4 that he could possibly send to josh, to create a flash.
Side question - Would it be possible to do the same to a stock T-Mobile S4 and load the boot to an AT&T S4?
Thanks

SD mount issues

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.