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.
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
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...