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
Related
Hi,
I actually try to root my Galaxy Tab 3 according to this thread: http://forum.xda-developers.com/showthread.php?t=2433853
But I dont want to install Windows intentionally for this stuff so I try it under Arch Linux (64bit)... I downloaded the JOdin3CASUAL-linux-R991.tar.gz (the browserversion runs neither with jre7-openjdk nor jre from AUR) and installed Heimdall via AUR
But JOdin tells that the automatically generated pit is invalid (The PIT file was corrupt. We cannot continue without a PIT file.)
Code:
Entry Count: 20
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 22608
Unknown 4: 14657
Unknown 5: 14392
Unknown 6: 22616
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: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PBL
Flash Filename: PBL.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: LT02.pit
FOTA Filename:
--- Entry #2 ---
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: 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: 2048
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: 10240
Partition Block Count: 2048
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: 12288
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename:
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: loke_2nd.bin
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: 28672
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename: loke_pxa988.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 36864
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 61440
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
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: 77824
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: radio.img
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: 102400
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: boot.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: 126976
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.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: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MISC
Flash Filename:
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: 172032
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: 1 (FOTA)
Partition Block Size/Offset: 204800
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MEP
Flash Filename:
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: 212992
Partition Block Count: 2945024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.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: 3158016
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.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: 3567616
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3977216
Partition Block Count: 11284480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USER
Flash Filename: userdata.img
FOTA Filename: remained
Does anybody has experience with Heimdall under Linux?
Okay..I didnt get JOdin running correctly (still getting corrupted pit file message), but I got my device rooted via heimdall frontend (thanks to zibrah3ed).
If other linux users are having trouble rooting their devices - you can try this:
1.) download T210.CWM.6.0.4.5.recovery.tar.zip and android-armeabi-universal-root-signed.zip from here
2.) copy android-armeabi-universal-root-signed.zip to internal or external sdcard of device
3.) decompress T210.CWM.6.0.4.5.recovery.tar.zip (should give you recovery.tar.md5)
4.) rename recovery.tar.md5 to recovery.tar.gz
5.) decompress recovery.tar.gz (now you should have a file named recovery.img)
6.) put device into download mode with "home+vol down+power" and connect it
7.) verify device is detected via terminal:
# heimdall detect
8.) download pit file from your device via terminal:
# heimdall download-pit --output smt210.pit
(file is saved at the current folder you are situated in the terminal)
9.) let device auto-reboot, then reenter download mode
10.) start heimdall-frontend (I did it with gksudo heimdall-frontend) and click "Detect" (@Utilities tab of Heimdall)
11.) click on Flash tab of Heimdall
12.) browse for the downloaded pit file (@Options PIT)
Make sure "Repartition" is NOT checked/selected
13.) click on "Add" (@Partitions (Files))
14.) change Partition Name to RECOVERY (@Partition Details)
15.) browse for the decompressed recovery.img (@File (recovery.img))
16.) uncheck "No Reboot" & "Resume"
17.) hit start
18.) the device will automatically reboot when finished...
19.) turn off the device and press "home+vol up+power", when the Samsung logo shows up release power button but keep pressing "vol up+home" until you enter CWM Recovery mode (takes little while)
20.) install zip android-armeabi-universal-root-signed.zip (the navigation is a littlebit weird, but well explained here)
21.) reboot device
After the reboot my PlayStore was broken (displaying "no connection" although I was able to surf on websites in the browser)
Doing a factory reset in CWM Recovery mode helped and I was able to install Superuser.
Would be cool if I get JOdin running because its easier to handle.. but I have no idea how.
Anyways I think this problem is more releated to JOdin thread so mods feel free to close this one.
Can you send me The pit-file, i need it for tab.
Can i usw this file for re partion With Odin ?
Thanks for your help.
bierma32 said:
Can you send me The pit-file, i need it for tab.
Can i usw this file for re partion With Odin ?
Thanks for your help.
Click to expand...
Click to collapse
sry forget to activate thread subscription
here's my pit file downloaded via: heimdall download-pit --output smt210.pit
you can verify that it is the same as from the first post (factory setting) with heimdall frontend
go to Utilities, @ Print PIT check [O] Local File, @ PIT File Browse for smt210.pit, then click on "Print"
regarding Odin: sry no idea, because I dont use Windows and therefore I dont have much experiance with Odin..but I think it should be possible as long as the PIT-files are standardised
you can also try this
randallskii said:
sry forget to activate thread subscription
here's my pit file downloaded via: heimdall download-pit --output smt210.pit
you can verify that it is the same as from the first post (factory setting) with heimdall frontend
go to Utilities, @ Print PIT check [O] Local File, @ PIT File Browse for smt210.pit, then click on "Print"
regarding Odin: sry no idea, because I dont use Windows and therefore I dont have much experiance with Odin..but I think it should be possible as long as the PIT-files are standardised
Click to expand...
Click to collapse
Can this pit file be use for the Sprint Galaxy tab 3 7.0?
my PIT file comes from a branded device (german isp 1&1, of which a logo is shown when booting)
but I cant tell if that is problematic, because I dont have another device to test this
well i was dooped on another thread saying with root u could sim unlock your phone on your own. it required root according to the thread. so i rooted then found i still had to pay for a unlock code.
so now i want to return my sm-g920p to stock and i can't get it to flash with odin because it hangs on get pit for mapping step. seems my .pit file on my phone is missing or corrupt. is there anyone who has a link to the .pit file for a 128 gig sprint galaxy s6? i have found what seems to be a pretty easy way to pull off the pit file from your phone but mine doesn't seem to be there.
http://techbeasts.com/2015/04/07/how-to-extract-pit-file-from-samsung-devices/
it has to be from a 128 gig SM-G920P from what i have read. if i can get some help i would really appreciate it. doesnt seem i can unroot it without it
i did find a pit magic app that says u can create a pit file from scratch but i can't seem to find any tutorials on how to actually use it
sand1303 said:
well i was dooped on another thread saying with root u could sim unlock your phone on your own. it required root according to the thread. so i rooted then found i still had to pay for a unlock code.
so now i want to return my sm-g920p to stock and i can't get it to flash with odin because it hangs on get pit for mapping step. seems my .pit file on my phone is missing or corrupt. is there anyone who has a link to the .pit file for a 128 gig sprint galaxy s6? i have found what seems to be a pretty easy way to pull off the pit file from your phone but mine doesn't seem to be there.
http://techbeasts.com/2015/04/07/how-to-extract-pit-file-from-samsung-devices/
it has to be from a 128 gig SM-G920P from what i have read. if i can get some help i would really appreciate it. doesnt seem i can unroot it without it
i did find a pit magic app that says u can create a pit file from scratch but i can't seem to find any tutorials on how to actually use it
Click to expand...
Click to collapse
That article will not work for extracting the PIT from a GS6. You need to change the copy statement:
from: dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
to: dd if=/dev/block/sda of=/sdcard/phone.pit bs=4 count=801 skip=6144
Got this from here. This from G920F. Can't besure if it is the same for G920P. I extracted for my G920P - 64GB. It sort of looks like what I got from my S4.
---------- Post added at 11:06 AM ---------- Previous post was at 10:41 AM ----------
todivefor said:
That article will not work for extracting the PIT from a GS6. You need to change the copy statement:
from: dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
to: dd if=/dev/block/sda of=/sdcard/phone.pit bs=4 count=801 skip=6144
Got this from here. This from G920F. Can't besure if it is the same for G920P. I extracted for my G920P - 64GB. It sort of looks like what I got from my S4.
Click to expand...
Click to collapse
This appears to work. I loaded the extracted PIT into Heimdall and printed it and got this:
Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 14153
Unknown 5: 12852
Unknown 6: 48
Unknown 7: 3
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 1
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 90
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 2
File Size (Obsolete): 0
Partition Name: CM
Flash Filename: cm.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 2048
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3072
Partition Block Count: 5120
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: 8 (Unknown)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13312
Partition Block Count: 7168
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 8704
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 29184
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 31232
Partition Block Count: 19456
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 50688
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50944
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DNT
Flash Filename: dnt.ssw
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 51200
Partition Block Count: 192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSISTENT
Flash Filename:
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 51392
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEADY
Flash Filename:
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 51456
Partition Block Count: 2304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 53760
Partition Block Count: 3840
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBFS
Flash Filename:
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 57600
Partition Block Count: 957440
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1015040
Partition Block Count: 76800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1091840
Partition Block Count: 11520
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
when i run it in terminal it tells me no such file or directory
i ran a adb command and it gave me this
801 +0 records in
801+0 records out
3204 bytes transferred in 0.012 secs
i have a file in my sd card phone.pit
if i try to open it with pit magic it tells me an error occured when opening file. does that mean that my pit file is bad on my phone? and if i try flashing it with the pit file and odin i could screw it up?
ok so i checked out the heimdall app and tried to print the pit file directly from device and got this
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
so when i open local file on the pc that i pulled directly from my sd card i get this
Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 14153
Unknown 5: 12852
Unknown 6: 48
Unknown 7: 3
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 1
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 90
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 2
File Size (Obsolete): 0
Partition Name: CM
Flash Filename: cm.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 2048
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3072
Partition Block Count: 5120
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: 8 (Unknown)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13312
Partition Block Count: 7168
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 8704
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 29184
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 31232
Partition Block Count: 19456
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 50688
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50944
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DNT
Flash Filename: dnt.ssw
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 51200
Partition Block Count: 192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSISTENT
Flash Filename:
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 51392
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEADY
Flash Filename:
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 51456
Partition Block Count: 2304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 53760
Partition Block Count: 3840
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBFS
Flash Filename:
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 57600
Partition Block Count: 957440
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1015040
Partition Block Count: 76800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1091840
Partition Block Count: 11520
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 0
Attributes: 741780788 (Read-Only)
Update Attributes: 201346999 (FOTA, Secure)
Partition Block Size/Offset: 3141696
Partition Block Count: 3141840
File Offset (Obsolete): 3141984
File Size (Obsolete): 3142128
Partition Name: €ò/
Flash Filename:
FOTA Filename: ˜û/
i am still not sure what is safe to flash and what isn't
sand1303 said:
i am still not sure what is safe to flash and what isn't
Click to expand...
Click to collapse
I think that is a legitimate PIT. Would I flash with it? NO! Not with the knowledge I have about PITs. You'll have to look/ask around in the other threads that Koop pointed you to in the OI1 thread.
@sand1303, seriously I would refer back to the link that I posted and ask someone with more expertise than we here can provide.
Thanks for the input. I switched cables last night and it flashed 2nd try. I did try two other samsung branded cables originally but i guess the last one i tried was the newest one. Too bad knox is tripped and samsung pay will never work on it unless someone finds a way to reset it
Sent from my SM-N920P using XDA Free mobile app
Having the same issue
Just Softbricked by device this morning while trying to update to Ol1, idk what happened but something failed and now i can only go into download mode or to a screen that says "An error has occurred while updating the device software" tried to download again from sammobile and flash through odin and it gives me an error telling me there is no pit partition, tried flashing a recovery, got nowhere there either, if im not mistaken, the only thing left to do would be to flash the pit and the firmware from sammobile, i cant seem to find a downloadable pit file online, and i cant get it off my phone obviously.. SM-G920P 32GB
Hello,
I've seen guides using ODIN to flash the T705XXU1BOL2_T705OLB1BOL2_T705DXU1BOJ1_HOME.tar.md5 file.
However, I'm using Heimdall. In that case, which partition should I flash to?
This is the output of print-pit:
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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: 24
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: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 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: -
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: 2048
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: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
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: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
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: 73728
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
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: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
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: 114688
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.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: 131072
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.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: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 172032
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash Filename: modem_cdma.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 98304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
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: 278528
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.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: 286720
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: tdata.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: 294912
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RESERVED2
Flash Filename: -
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 327680
Partition Block Count: 4894720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5222400
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5632000
Partition Block Count: 471040
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6103040
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Thanks!
Just use twrp to flash the system.img
do what ashyx said or use odin in virtualbox
Thanks ashyx and Nandr0idC0nsumer.
I didn't realise that you could simply flash stock ROM using TWRP. All guides I have seen pointed to Odin or Heimdall.
In that case, how can I get system.img from T705XXU1BOL2_T705OLB1BOL2_T705DXU1BOJ1_HOME.tar.md5?
Rename the .tar.md5 to .tar. Now open it with WinRAR (free application) and extract system.img and boot.img. Now flash those in twrp and you're done
done it with Odin on Virtualbox. Thanks!
I am having some issues with flashing stock firmware to my Galaxy S9 the Model is a SM-G960F and I have been able to pull a version of the stock formware from the sammobile site. I can flash TWRP and then a custom OS however I need to update the current device to Android 10 Q for the OS I want. I use a Linux system and I have ADB and Fastboot installed and I have no issue sideloading or flashing firmware onto the device. However, the stock firmware comes with a number of .tar.md5 files that I am unsure how to use in order to flash the device back to stock in using Fastboot and ADB. If anyone can provide some assistance. I am running into a wall when it comes to completing this install from Linux
Any assistance is appriciated.
EDIT: Alternativley, If anyone can tell me how to install the Vendors on the S9 SM-G960F without stock update that should work as well.
TIA!
Hi, just went through the process of flashing stock on my S9 too. It was rather a pain in the a**.
First of all, you will not be able to flash full stock to a Samsung device (in download mode) using fastboot/adb, those don't work with Samsung devices.
In general fastboot is useless for Samsung.
You can just go ahead and extract all those .tar.md5 files with tar -xvf filename.tar.md5.
(Use CSC if you want to wipe data, otherwise HOME_CSC. Although I'm not totally sure in which cases you would have to wipe data manually anyway.)
There should be a vendor.img file somewhere, I think you can just flash this via TWRP by selecting Install > Install image > (choose vendor.img) > (select vendor as target partition).
That would be by far the easiest way.
But I have never tried this way! (At least, all that could possibly happen is a soft brick that can be fixed by going full stock.)
I don't get why you do not want to use heimdall in the first place, as the only way I'm aware of to flash via bootloader/download onto a Samsung device is heimdall or odin and heimdall is natively supported on Linux.
When you would use heimdall, after extracting the .tar.md5 files, you would find a .pit file somewhere, which shows a mapping of the extracted files to the partitions. You can view this mapping with heimdall --print-pit --file filename.pit.
After this, build your heimdall command like heimdall --BOOT boot.img --SYSTEM system.img ... for each of the extracted files. DO IT ALL IN ONE COMMAND!
Although the version of heimdall I tried to use had a problem. Aparently some versions of heimdall are unable to flash a system.img larger than 4GB.
So I had to overcome my pride and use Windows with Odin for the flashing. (Normally I use Arch btw )
Hope I could help you a bit on your quest with this little booklet.
Best Regards!
Hello,
Thank you very much for this exchange, because I am in a case very near from the Arcticstagmedia's description.
I'm on the same device SM-G960F, looking to flash a stock ROM on Android 10 (Q) before to install /e/ OS (Q) on it.
I did the :
Code:
heimdall print-pit --file STARLTE_EUR_OPEN.pit
It returned me :
Code:
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/
Entry Count: 32
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 14665
Unknown 5: 12600
Unknown 6: 48
Unknown 7: 5
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 1
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 81
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1024
File Offset (Obsolete): 2
File Size (Obsolete): 0
Partition Name: BOOTLOADER2
Flash Filename: -
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 90
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1792
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: CM
Flash Filename: cm.bin
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 91
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1792
Partition Block Count: 256
File Offset (Obsolete): 4
File Size (Obsolete): 0
Partition Name: ECT
Flash Filename: ect.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 1536
File Offset (Obsolete): 3
File Size (Obsolete): 0
Partition Name: CPEFS
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 2048
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4096
Partition Block Count: 5120
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UP_PARAM
Flash Filename: up_param.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13312
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KEYSTORAGE
Flash Filename: keystorage.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13314
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA2
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 15362
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTB
Flash Filename: dtb.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 17410
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DTBO
Flash Filename: dtbo.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 19458
Partition Block Count: 14080
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 33538
Partition Block Count: 16638
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50176
Partition Block Count: 12800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 62976
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NAD_REFER
Flash Filename: nad_refer.bin
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 63232
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSISTENT
Flash Filename:
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 63360
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MISC
Flash Filename:
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 63616
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEADY
Flash Filename: steady.bin
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 64640
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DQMDBG
Flash Filename: dqmdbg.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 68736
Partition Block Count: 1126400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1195136
Partition Block Count: 166400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: VENDOR
Flash Filename: vendor.img
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1361536
Partition Block Count: 165376
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ODM
Flash Filename: odm.img
FOTA Filename:
--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1526912
Partition Block Count: 153600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1680512
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1683072
Partition Block Count: 12800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OMR
Flash Filename: omr.img
FOTA Filename:
--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1695872
Partition Block Count: 1280
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_DEBUG
Flash Filename: modem_debug.bin
FOTA Filename:
--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 8 (Unknown)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 1697152
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
Then I tried the command
Code:
heimdall --BOOTLOADER sboot.bin --BOOTLOADER2 - --CM cm.bin --ECT ect.bin --CPEFS --PIT - --MD5HDR md5.img --BOTA0 - --BOTA1 - --EFS efs.img --PARAM param.bin --UP_PARAM up_param.bin --KEYSTORAGE keystorage.bin --BOTA2 - --DTB dtb.img --DTBO dtbo.img --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --NAD_REFER nad_refer.bin --PERSISTENT --MISC --STEADY steady.bin --DQMDBG dqmdbg.img --SYSTEM system.img --VENDOR vendor.img --ODM odm.img --CACHE cache.img --HIDDEN hidden.img --OMR omr.img --CP_DEBUG modem_debug.bin --USERDATA userdata.img
And it failed.
I'm a very newbie on Heimdall and Android. I'm not at all a developer, I'm just wishing to learn a bit, to become step by step a more advanced user, and to be more aware of the stuff I'm using everyday.
I'm using NixOS, so I would like to avoid the Odin option. Only if the Heimdall variant fail despite your help, I'll have to do it with Odin through a VM.
Thanks again for this topic, and maybe it could help other people if I can then confirm I did 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...