Related
Hi all
I am using a Galaxy Note GT-N7000 2.3.6 N7000XXKK5 (Hungerian) 2.6.35.7-N7000XXKKA-...
I was wondring if there is a way to view the device list in the partition table and there mount points.
I understand in older versions of android "cat /proc/mtd" would produce a table like this:
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 093a0000 00020000 "userdata"
I see now the mount points have moved to "/dev/block" but I can not get there names.
I have seen many assesments of some of the "mmcblk0p0-13" names, but nothing looked like an orgenized list of the "Partition Information Table".
Can anyone tell me how I can printout a table like above on SGN.
I would like to use the "dd" command to create images of all the partitions before I start messing with my phone.
If anyone could help me with these commands I would mostly appreciate it.
"dd if=/dev/block/mmcblk0p? of=/sdcard/???.img bs=4096"
(for all mmcblk0p? and there names ???.img)
and if possible to printout the partition table using "cat /dev/block/???" or anything else.
I fund ths on the "[INFO][DEV]SGS2 Epic 4G Touch Partition Structure"
http://forum.xda-developers.com/showthread.php?t=1278281
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.bin
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 614400
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 720896
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 753664
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1802240
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5996544
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 30130176
Partition Block Count: 638976
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
I was wondering if i could find something like that for SGN
Best Regards & Thanks
Yishai
+1
yes it would be nice to know that. Then if it possible to use dd commands, then we will can flash custom kernels much easier and maybe make linux running nativeky if we get kernek source. Sorry for bad english.
Well, you can get the basic partitions from /proc/mounts :
Code:
-> adb shell cat /proc/mounts | grep /dev/block
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /preload ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/259:3 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
..............
cat /proc/mounts and partitions doesn't show where is recovery.img. and no cat/proc/mtd in /proc. So how to know where is recovery.img?
using adb
Code:
adb shell parted /dev/block/mmcblk0
using terminal emulator on the phone
Code:
su
parted /dev/block/mmcblk0
and then command: print
N7000 ................
dev: size erasesize name
mmcblk0p1: 001500000 000000 "efs"
mmcblk0p2: 000147c00 000000 "sbl1"
mmcblk0p3: 000147c00 000000 "sbl2"
mmcblk0p4: 000831400 000000 "param"
mmcblk0p5: 000831400 000000 "boot"
mmcblk0p6: 000831400 000000 "recovery"
mmcblk0p7: 00d200000 000000 "cache"
mmcblk0p8: 0010ccccd 000000 "modem"
mmcblk0p9: 037d00000 000000 "system"
mmcblk0p10: 086300000 000000 "userdata"
mmcblk0p11: 2f999999a 000000 "emmc"
mmcblk0p12: 021900000 000000 "hidden"
---------- Post added at 12:18 PM ---------- Previous post was at 11:53 AM ----------
please ask where bs = 4096 ?????????????????/
thinh182009 said:
N7000 ................
---------- Post added at 12:18 PM ---------- Previous post was at 11:53 AM ----------
[please ask where bs = 4096 ?????????????????/
Click to expand...
Click to collapse
Since your question is off-topic, I'll keep it short -
bs (block size) in the 'dd' command is actually the cpu buffer size used during data transport between devices. If not specified, default is 512 bytes. Each respective hardware driver then buffers I/O data between the cpu and its dependent device. 4096 is probably a good number for Android.
on Nexus 7 flo and maybe other devices:
/dev/block/mmcblk0p14 boot.img
/dev/block/mmcblk0p22 system.img
Hiya,
Can somebody post the output of "sudo heimdall print-pit --verbose" from linux with a fully working 16gb galaxy note?
Thanks!
clarkk said:
Hiya,
Can somebody post the output of "sudo heimdall print-pit --verbose" from linux with a fully working 16gb galaxy note?
Thanks!
Click to expand...
Click to collapse
I can do it if you do the same with none working Note
Can I do it from Windows?
Heimdall doesn't recognize my note, Odin does, When I tried installing heimdall drivers, i run zadig.exe, it won't show me any Samsung device in the list (yes i pressed show all and phone is connected in download mode.)
So i can't do what you want from this computer, i'll try again at home.
Here is the output from my Note :
Code:
Heimdall v1.3 (beta), Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
Serial No: "?"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 409600
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 516096
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 548864
Partition Block Count: 1744896
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 2293760
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 6488064
Partition Block Count: 23232512
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: ums.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Re-attaching kernel driver...
I don't know if it worth mentioning it, but at the end I got some libusb errors -7.
Maybe its because the permission is denied.
Pls try it with this:
sudo chmod 666 /dev/bus/usb/001/00*
* stands for the port.
e.g.
If you have a "USB -7" error, so pls type this:
sudo chmod 666 /dev/bus/usb/001/007
or
If you have a "USB -3" error, so pls type this:
sudo chmod 666 /dev/bus/usb/001/003
and so on...
Thanks guys, i dont have the file near me from a broken note but i believe it looks the same still, i was trying to make sense of the heimdall readout. Its odd that doing a dump of the pit file from it produces a different binary file than the one that everybody is using with odin.
Chris X.,
I did it from Windows and here is the result
Code:
c:\Temp\Heimdall>heimdall.exe print-pit --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is initialised.
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 409600
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 516096
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 548864
Partition Block Count: 1744896
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 2293760
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 6488064
Partition Block Count: 23232512
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: ums.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
Hope it helps...
By the way, is it possible to do a bit by bit (in other words a RAW) ROM extraction/flash (many people including me would do it considered the work you already did for the community and the fact that we would learn a bit more on Note internals) so afterwards, an simple EFS restore would restore you Note original hardware information?
Thats mine from a stock note with stock firmware LB1.
Code:
[email protected]:~$ adb reboot download
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ sudo heimdall print-pit --verbose
[sudo] password for chris:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
Serial No: "?"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 409600
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 516096
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 548864
Partition Block Count: 1744896
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 2293760
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 6488064
Partition Block Count: 23232512
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: ums.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
Re-attaching kernel driver...
[email protected]:~$
Chris X.,
Regarding a raw ROM copy, do you think it is possible?
Chris X. said:
Maybe its because the permission is denied.
Pls try it with this:
sudo chmod 666 /dev/bus/usb/001/00*
* stands for the port.
e.g.
If you have a "USB -7" error, so pls type this:
sudo chmod 666 /dev/bus/usb/001/007
or
If you have a "USB -3" error, so pls type this:
sudo chmod 666 /dev/bus/usb/001/003
and so on...
Click to expand...
Click to collapse
Sadly i'm on Windows.
Chris X. said:
Maybe its because the permission is denied.
Pls try it with this:
[...]
If you have a "USB -7" error, so pls type this:
sudo chmod 666 /dev/bus/usb/001/007
[...]
Click to expand...
Click to collapse
Thanks for the suggestion, but (sadly?) it doesn't work : "No files or folders of this type"
I've got 001, 002, 003, 006 and 014 in /dev/bus/usb/001/, and 001, 002, 003, 004 and 005 in /dev/bus/usb/002/, but no 007.
The error I've got after Re-attaching kernel driver... is ERROR: libusb error -7 whilst receiving packet. Retrying...
Sine. said:
Thanks for the suggestion, but (sadly?) it doesn't work : "No files or folders of this type"
I've got 001, 002, 003, 006 and 014 in /dev/bus/usb/001/, and 001, 002, 003, 004 and 005 in /dev/bus/usb/002/, but no 007.
The error I've got after Re-attaching kernel driver... is ERROR: libusb error -7 whilst receiving packet. Retrying...
Click to expand...
Click to collapse
I think I got this error when I used my USBtoRS232 converter.. Needed a newer Linux kernel to get rid of the error or updated libusb package..
Sine. said:
Thanks for the suggestion, but (sadly?) it doesn't work : "No files or folders of this type"
I've got 001, 002, 003, 006 and 014 in /dev/bus/usb/001/, and 001, 002, 003, 004 and 005 in /dev/bus/usb/002/, but no 007.
The error I've got after Re-attaching kernel driver... is ERROR: libusb error -7 whilst receiving packet. Retrying...
Click to expand...
Click to collapse
Which version of Ubuntu do you have?
Pls try this:
Code:
sudo apt-get install libusb-dev
if you need an upgrade, so pls try this:
Code:
sudo bash -c "apt-get update && apt-get upgrade"
btw --> http://forum.xda-developers.com/showpost.php?p=23187465&postcount=1486
like title, which are the condition to use repartion + pit to flash a firmware?
same pakage content only 5 partition (file), for example
hidden.img = i don't know what do this
factoryfs.img = system partition
modem.bin = radio compart
cache.img = sec_csc.zip
zImage = kernel
can i use this package with repartition (+pit) flagged?
i extract the partition from .pit using heimdall, and the log is this
Code:
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 409600
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 516096
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 548864
Partition Block Count: 1744896
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 2293760
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 6488064
Partition Block Count: 23232512
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: ums.rfs
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (` )
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Chip Identifier: 1 (` )
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
which of these partitions are required to use repartition?
thank's guy!
Never use pit file OR Re-partition option in Odin, except you are well expertise in modding N flashing, any wrong pit can brick your device.
routinely pit not require to flash any GB/ICS ROM, it needed only if you have did somthing wrong (e.g. flashed wrong firmware on note, which is not meant for Note)
N yes dont extract tar file (e.g factoryfs,hidden,cache)
Find my thread 'all stock ROM....' in sticky of development N refer to post#2 for installation guide)
dr.ketan said:
Never use pit file OR Re-partition option in Odin, except you are well expertise in modding N flashing, any wrong pit can brick your device.
routinely pit not require to flash any GB/ICS ROM, it needed only if you have did somthing wrong (e.g. flashed wrong firmware on note, which is not meant for Note)
N yes dont extract tar file (e.g factoryfs,hidden,cache)
Find my thread 'all stock ROM....' in sticky of development N refer to post#2 for installation guide)
Click to expand...
Click to collapse
I know that you only use file.tar.md5 with odin, but this is not the question.
I would like to create packages for use with repartition in a safe manner (for example, to go back from a flash of CM9), how does [Ramad] for galaxy S.
i'm not noob, but i don't know everything!
do u know the utility of hiddem.img and data.img?
have an other question about data.img:
in gingerbread is the partion of /data/app
but in ICS?
ICS should be different from GB, because the partition DATA is not limited to only 2 gb but is variable.
but, in this case, why ICS and GB have the same PIT?
Partition shud b same in both gb n ics, b'coz u can safely flash without repartitionung too
Sent from my GT-N7000 using xda premium
dr.ketan said:
Partition shud b same in both gb n ics, b'coz u can safely flash without repartitionung too
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i know, but:
IF i wont buid a package that work well with repartition flagged, which partition i must tu use to repack PDA.tar.md5??
Reference/Information/Development.
==================================================
This is a development thread. Do not ask for help with this or that,
this is not a support thread! Make sure that any question you might
have, is directly related to the benefit of this thread and on-topic.
==================================================
Click to expand...
Click to collapse
The goal here is to obtain as detailed information about the device i9506 partitions as possible.
So i post here 3 different results obtained by using different ways
Click to expand...
Click to collapse
- Terminal Tool Parted
- Heimdall i9506.pit file printed ([email protected] Dobell)
- Mobile Odin Pro dump file ([email protected])
Click to expand...
Click to collapse
---- General Device Info ----
Device Name:
Samsung Galaxy S4 LTE+
Manufacturer Product Name:
GT-i9506
Processor:
Qualcomm Snapdragon 800 MSM8974
OS version:
Android 4.2.2
Click to expand...
Click to collapse
Read out by Terminal (Tool Parted)
Code:
[B][email protected]:~$ sudo adb shell
[sudo] password for xenix96:
[email protected]:/ $ su
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 016G94 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 19.9MB 15.7MB apnhlos
2 19.9MB 80.2MB 60.2MB modem
3 80.2MB 80.7MB 524kB sbl1
4 80.7MB 80.7MB 32.8kB dbi
5 80.7MB 80.7MB 32.8kB ddr
6 80.7MB 82.8MB 2097kB aboot
7 82.8MB 83.4MB 524kB rpm
8 83.4MB 83.9MB 524kB tz
9 83.9MB 94.4MB 10.5MB pad
10 94.4MB 105MB 10.5MB param
11 105MB 120MB 14.7MB ext4 efs
12 120MB 123MB 3146kB modemst1
13 123MB 126MB 3146kB modemst2
14 126MB 147MB 21.0MB boot
15 147MB 168MB 21.0MB recovery
16 168MB 178MB 10.5MB fota
17 178MB 186MB 7331kB backup
18 186MB 189MB 3146kB fsg
19 189MB 189MB 1024B fsc
20 189MB 189MB 8192B ssd
21 189MB 197MB 8389kB persist
22 197MB 210MB 12.6MB ext4 persdata
23 210MB 2600MB 2391MB ext4 system
24 2600MB 2967MB 367MB ext4 cache
25 2967MB 3177MB 210MB ext4 hidden
26 3177MB 15.8GB 12.6GB ext4 userdata
(parted)
quit
[email protected]:/ $ exit
[email protected]:/ $ exit
[email protected]:~$[/B]
=================================================================================
Printed out from I9506.pit file by Heimdall
Code:
[B][SIZE="4"]Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Entry Count: 30
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14137
Unknown 6: 52
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: 8192
Partition Block Count: 30720
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: 38912
Partition Block Count: 117632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
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: 156544
Partition Block Count: 1024
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: 157568
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DBI
Flash Filename: sdi.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: 157632
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DDR
Flash Filename:
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: 157696
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: 161792
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: 162816
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: 163840
Partition Block Count: 20480
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: 1 (FOTA)
Partition Block Size: 184320
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 204800
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
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: 233472
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.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: 239616
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.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: 245760
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
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: 286720
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 327680
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 348160
Partition Block Count: 14318
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 362478
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
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: 368622
Partition Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSC
Flash Filename:
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: 368624
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 368640
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename: persist.img.ext4
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 385024
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 409600
Partition Block Count: 4669440
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5079040
Partition Block Count: 716800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5795840
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
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: 6205440
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8974.pit
FOTA Filename:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
[/SIZE][/B]
=================================================================================
Read out of Mobile Odin pro Dump file
Code:
[B][SIZE="4"]
lrwxrwxrwx root root 1970-01-17 13:37 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-17 13:37 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-17 13:37 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-17 13:37 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-17 13:37 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-17 13:37 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-17 13:37 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-17 13:37 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-17 13:37 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-17 13:37 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-17 13:37 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-17 13:37 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-17 13:37 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-17 13:37 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-17 13:37 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-17 13:37 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-17 13:37 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-17 13:37 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-17 13:37 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-17 13:37 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-17 13:37 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-17 13:37 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-17 13:37 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-17 13:37 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-17 13:37 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-17 13:37 userdata -> /dev/block/mmcblk0p26[/SIZE][/B]
Click to expand...
Click to collapse
for op....
another one...
last one...
Partition table info/help I9506 badly needed
(When/if reading "we" mean Xenix and me that are working with this. Not my voices that some claim .)
@Dear Phil,
(I respect no PM since it's better then just ignoring (F-OFF is better then ignore!). But I hope you see this and answer.)
We need your help and your vast knowledge.
We have so little to work with. No "pre-Knox". Quite rough situation here since we can't get past the locks and blocks.
Also the damage to the hardware and the software to it. Make us wonder if there was an erase of data?
We don't even know if just reading/dumping the whole phone will trigger this "hidden efuse-data" that hard-bricks the phone...
I have it confirmed from SS that it's the same hardware as N9005 so "theoretically" it should just work using that.
But they have another partition table since they have crammed in more space so it's same same not same.
The "/system" is way too small. I want to repartition the phone but again, E-fuse?
You know the layout of the EEPROMS. You know the layout of every single damn device on earth! :good:
They have damn many block-partitions! Can you provide us with some info or point in some direction?
What they really are and the size they "usually" have?
You have seen the pre/post Knox partitions. What changed?
Is that discrepancy of partition size vs the stated size something that always existed or is it after Knox?
We have and use. Any new version?
If you read and feel for it, can you please get in touch and push us forward? Pliiiize, Christmas? haha
Happy holidays!
Did someone have contact? Mess me in that case.
/Abs
can you give me pit file for i9506? im searching for it cant find it. need to flash another region rom but i get fai after hidden and stating invalid ext4 image
mezo91 said:
can you give me pit file for i9506? im searching for it cant find it. need to flash another region rom but i get fai after hidden and stating invalid ext4 image
Click to expand...
Click to collapse
Then you didnt searched well my friend.... http://forum.xda-developers.com/showthread.php?p=49731942
Cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
xenix96 said:
Then you didnt searched well my friend.... http://forum.xda-developers.com/showthread.php?p=49731942
Cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
im trying to flash latest australia rom. but it dont let me. at the end after hidden i get fail ext4 and on mobile invalid ext4 image. so i reflash Singapore rom. i want to flash the aust one as this one doesnt seem to have lte connectivity due to the csc i guess as i read on the web.
Mobile Odin dump
Mobile Odin dump
Android 4.3
mezo91 said:
ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
im trying to flash latest australia rom. but it dont let me. at the end after hidden i get fail ext4 and on mobile invalid ext4 image. so i reflash Singapore rom. i want to flash the aust one as this one doesnt seem to have lte connectivity due to the csc i guess as i read on the web.
Click to expand...
Click to collapse
As you can read here in DeHAWK post http://forum.xda-developers.com/showpost.php?p=51891913&postcount=516
DeHAWK said:
Time for a little update.
.....
...
..
More about the 4.4.2 aboot.mbn; both the phone model and carrier e.g SKT is listed in here. Hope you guys can see what this means...if active, it might prevent us from flashing anything else than firmware from our own carrier.
.....
....
....
Stay tuned.
Regards.
Click to expand...
Click to collapse
And i made the same experiance with 4.3 I9506 France orange firmware from December ....i was no more able to flash any othere carrier specific firmware....
So this means the knoxed Bootloader also prevent us from flashing(Official Samsung Firmware) anything else than firmware from our own carrier!!!
If someone who had same issue can confirm this would be fine.... since i can no more test it cause i am back on 4.2.2 after i get replaced my device
If this assumption is wrong please correct me!!
Cheers
xenix96 said:
As you can read here in DeHAWK post http://forum.xda-developers.com/showpost.php?p=51891913&postcount=516
And i made the same experiance with 4.3 I9506 France orange firmware from December ....i was no more able to flash any othere carrier specific firmware....
So this means the knoxed Bootloader also prevent us from flashing(Official Samsung Firmware) anything else than firmware from our own carrier!!!
If someone who had same issue can confirm this would be fine.... since i can no more test it cause i am back on 4.2.2 after i get replaced my device
If this assumption is wrong please correct me!!
Cheers
Click to expand...
Click to collapse
I flashed my knox Germany (T-Mobile) 4.3 i9506 with the unbranded Nordic 4.3 and the warranty 0x0 was retained.
I've also done the same with an EE i9505 4.3 that I bought recently directly from them in UK with UK unbranded BTU 4.4.2 firmware and did not void warranty bit.
Bear in mind both of the aforementioned phones were carrier unlocked from factory. I do not know what could happen to a carrier locked phone.
Here is PIT from my GT-I9506 (ks01lte):
View attachment MSM8974.zip
Hey
Just to let you know. I have been contacted several times by PM from people who can't flash other carriers firmware. It always stops after the hidden image. Just got one PM about this only 15 minutes ago.
So my prediction about the this is right. First time I heard about this, was back in January. It was a guy in Germany who had flashed the french 4.3 and now he couldn't get back to 4.2.2. We managed to get it back to 4.2.2 quite easy, but it wouldn't let him flash his german CSC/Hidden. But he actually found the solution himself here on XDA.
So carriers CAN lock the phone to a specific CSC, even on 4.3. Not said that they do, at least not all of them.
Regards.
Sent from my GT-I9305 using XDA Premium 4 mobile app
INFO
Hello guys!
I contacted the moderators to clean and close this thread.
Cause i sell my device so i cant maintain this thread in future.
Thanks for the nice time with you guys with this phone!
Cheers
Mod Edit
Thread closed at the request of the [OP]
malybru
Forum Moderator
Hello,
since 2 weeks i try to get root together with encryption (Settings > Security > encrypt Phone ) running.
But i allready get stuck at the encryption
While testing several CustomROMs (see below) , i was (somewhere in between) able to encrypt OmniROM. (I don't no why it worked neither why it doesnot works anymore.)
Recoverys it used * TWRP 2.8.7.0 from golden-guy
* TWRP 2.8.0.0 from Novafusion
* TWRP 2.8.7.3 from Android-andi
Custom ROMs I used * SlimKAT 4.4.4 from Android-Andi
* CM12.1 from Novafusion
* CM 11.0 from Novafusion
* RR1 5.1.1 from Novafusion
* OmniROM 5.1.1 from golden-guy
(erverything in the latest version. (Date today 21. May .2016)
ATM I am not able to encrypt any of the above ROMs
The last 2 days i followed the instructions from android-andis thread :
http://forum.xda-developers.com/showthread.php?t=2548257
android-andis Instructions (date: 22 May 2016)
Backup all important stuff! We need to format the device!
Make sure using latest TWRP
Wipe -> Advanced Wipe:
Cache
Dalvic
System
Data
Wipe -> Format Data -> Type yes to confirm
This is the most important step! It will keep some space for the footer! Without that encryption is not possible!
Flash Rom
Reboot
Set a Pin for Lockscreen
Encrypt your device
Point by Point severaly times. (Just to make clear: Yes, I did "Format Data" and typed yes to perform it.)
It just didn't work.
----------------------------------------------------------------------------------------
Here are some Infos from the last try with the combination of:
TWRP 2.7.8.3 from android-andi &
SlimKAT 4.4.4 from android-andi April 2016 release
just in case someone needs it. The heimdall print of the PIT.
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
...
Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 28519
Unknown 4: 25708
Unknown 5: 28261
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MBR,GPT
Flash Filename:
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 256
Partition Block Count: 768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MasterTOC
Flash Filename: STE_boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: goldenxx.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6144
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot1
Flash Filename: STE_boot1.img
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot2
Flash Filename: STE_boot2.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Dnt
Flash Filename: dnt.ssw
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: reserved
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS
Flash Filename: cspsa.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 18432
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS2
Flash Filename: cspsa2.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: EFS.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 53248
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS
Flash Filename: modemfs.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 86016
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS2
Flash Filename: modemfs2.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 118784
Partition Block Count: 102400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Fota
Flash Filename: ssgtest.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 380928
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IPL Modem
Flash Filename: ipl.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 385024
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Modem
Flash Filename: modem.bin
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 417792
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Loke4
Flash Filename: normal.bin
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 421888
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: 2ndLoke4
Flash Filename: normal2.bin
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 425984
Partition Block Count: 32768
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: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 458752
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel
Flash Filename: boot.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 491520
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel2
Flash Filename: recovery.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 524288
Partition Block Count: 2457600
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: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2981888
Partition Block Count: 1720320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHEFS
Flash Filename: cache.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4702208
Partition Block Count: 655360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5357568
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: userdata.img
FOTA Filename: remained
And also the output of fdisk /dev/block/mmcblk0 (taken while adb into recovery)
# fdisk -ul /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 15269888 sectors, 3360M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15269854
Number Start (sector) End (sector) Size Code Name
2 256 1023 384K 0700 MasterTOC
3 1024 3071 1024K 0700 PIT
4 6144 8191 1024K 0700 MD5HDR
5 8192 9215 512K 0700 STEboot1
6 9216 10239 512K 0700 STEboot2
7 10240 11263 512K 0700 Dnt
8 11264 12287 512K 0700 reserved
9 16384 18431 1024K 0700 CSPSAFS
10 18432 20479 1024K 0700 CSPSAFS2
11 20480 53247 16.0M 0700 EFS
12 53248 86015 16.0M 0700 ModemFS
13 86016 118783 16.0M 0700 ModemFS2
14 118784 221183 50.0M 0700 Fota
15 380928 381055 65536 0700 IPL Modem
16 385024 413695 14.0M 0700 Modem
17 417792 421887 2048K 0700 Loke4
18 421888 425983 2048K 0700 2ndLoke4
19 425984 458751 16.0M 0700 PARAM
20 458752 491519 16.0M 0700 Kernel
21 491520 524287 16.0M 0700 Kernel2
22 524288 2981887 1200M 0700 SYSTEM
23 2981888 4702207 840M 0700 CACHEFS
24 4702208 5357567 320M 0700 HIDDEN
25 5357568 15269854 4839M 0700 DATAFS
cat fstab.samsunggolden from recovery:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p12 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache f2fs nodiratime,noatime,nosuid,nodev,discard,background_gc=off,inline_xattr,active_logs=2 wait
/dev/block/mmcblk0p11 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/mmcblk0p25 /data f2fs nodiratime,noatime,nosuid,nodev,discard,background_gc=off,inline_xattr,active_logs=2 wait,encryptable=footer
# Vold managed volumes (External SDCard)
/devices/sdi0/mmc_host/mmc1/mmc1* auto vfat defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
# Recovery
/dev/block/mmcblk0p20 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p21 /recovery emmc defaults recoveryonly
Trying encryption (Settings > Security > encrypt Phone) the adb logcat presented:
E/Cryptfs ( 1687): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------------------------------------------------------------------------------------
Here are some Infos from the last try with the combination of:
TWRP 2.7.8.0 from golden-guy &
OmniROM 5.1.1 from golden-guy (20160505 release)
cat fstab.samsunggolden from recovery:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p12 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p23 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p11 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
# Vold managed volumes (External SDCard)
/devices/sdi0/mmc_host/mmc1/mmc1* auto vfat defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
# Recovery
/dev/block/mmcblk0p20 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p21 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p22 /system ext4 defaults recoveryonly
/dev/block/mmcblk0p23 /cache ext4 defaults recoveryonly
/dev/block/mmcblk0p25 /data ext4 defaults recoveryonly
/dev/block/mmcblk0p11 /efs ext4 defaults recoveryonly
When trying encryption (Settings > Security > encrypt Phone) the adb logcat presented:
E/Cryptfs ( 1686): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1686): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
--------------------------------------------
I am willing to serve further Information if needed, or for example to:
* resize the /dev/block/mmcblk0p25 via adb or
* change the PIT via "PIT Magic" / "EFS Professional"
if someone is going to guide me.
If the adb solution needs the parted command, please direct me to a recovery which got it.
I couldn't find any
Just found some obscure Download-Links for parted to put it barehand into /system . But i an not willing to use this.
Any help is welcome.
Greeting
Follow http://andi34.github.io/faq_twrp.html
After that flash your rom and gapps.
Enjoy encryption (SlimLP and CM12.1 need a different kernel to use it because of CAF based vold, i don't think i have added needed changes to my latest SlimLP build).
Hello Android-Andi,
Android-Andi said:
Follow http://andi34.github.io/faq_twrp.html
After that flash your rom and gapps.
Enjoy encryption (SlimLP and CM12.1 need a different kernel to use it because of CAF based vold, i don't think i have added needed changes to my latest SlimLP build).
Click to expand...
Click to collapse
thanx for taking time to help. :good: Unfortunatly it didn't work.
First of all i Flashed your TWRP 2.8.7.3 build via recovery.
After a reboot into your recovery i followed exactly the steps from your URL.
Then i Installed your latest SlimKAT 4.4.4 (11042016) via Recovery . (NO gapps)
(I also checked the MD5 of the downloaded files)
After a direct boot into system & setting up a 8 digit PIN i tried to encrypt the phone.
The result of cat abd_logcat_of_encrypting_SlimKAT.txt | grep Cryptfs was still:
E/Cryptfs ( 1682): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Just to be sure i did it exactly the same way with the OmniROM 5.1.1. golden-guy (20160505 release) and golden-guy latest TWRP 2.8.7.0
the result of adb logcat was:
E/Cryptfs ( 1681): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1681): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
....
Just a thought:
I am kinda confused. About a week ago it worked to encrypt only with OmniROM. (I am not sure if i ever did a Format Data befor that time.) And after i tried several other ROMs it does not work anymore to encrypt any ROM.
....
I searched a lot around this problem.
As far as i understand the "encryptable=footer" in the fstab indicates that the filesystem should be able to be encyrpted
AND
the /data partition on /dev/block/mmcblk0p25 has to be at the end of /mmcblk0
AND
/mmcblk0 has to have some free sectors at the end.
As far as i manage to read the fdisk output from the first Post: There are some "unusable"/unused sectors at the end of mmcblk0 .
Is it possible that this sectors are not for the encryption ?
Do i just have to resize (shrink) /dev/block/mmcblk0p25 a little ?
Or do i have to resize (shrink) the ext4 filesystem (which contains /data and ist "lying" on /dev/block/mmcblk0p25?
Or are these both the same ? :silly:
Greetings
You could try the twrp somewhere on last pages of my twrp thread, It's attached as flashable zip.
Atm i don't own a golden and can't test myself.
Some roms need 2 kernel commits to have working encryption because some roms use CAF based vold source (cm12.1 and newer, SlimLP)
https://github.com/andi34/android_k...mmit/514595570f2f542f55576946d913a9b17e6664e7
https://github.com/andi34/android_k...mmit/6c80b864ff6458ed8643c9b2f9bca9f11c63fabd
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
You could try the twrp somewhere on last pages of my twrp thread, It's attached as flashable zip.
Atm i don't own a golden and can't test myself.
Some roms need 2 kernel commits to have working encryption because some roms use CAF based vold source (cm12.1 and newer, SlimLP)
Click to expand...
Click to collapse
Hallo Android-Andi,
thanks for your time !!
i wasn't sure which TWRP you meant exactly. So i did a couple of tests
I allways worked in the following order:
1. flashed the TWRP-Recovery via Recovery
2. rebooted into the "downgraded" Recovery
3. wiped the dalvic, system, cache
4. formated Data
5. rebooted into recovery
6. flashed the mentioned ROM
First try:
TWRP_test4 (?) from yourt TWRP Thread(wich turned out to be a TWRP 2.8.7.0) & Slim KAT 4.4.4
adb logcat
E/Cryptfs ( 1684): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
all following TWRPs are from "your" AFH site.(/I]
Second try:
TWRP 2.8.7.0 F2FS & SlimKAT 4.4.4
adb logcat
E/Cryptfs ( 1681): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
Third try:
TWRP 2.8.7.0 f2fs & SlimLP (from android-andi) because you mentioned several times that there has to be some fixes for SlimLP & Cm12.1
adb logcat
Far Up in the logcat...
I/Cryptfs ( 1668): Check if PFE is activated on Boot
E/Cryptfs ( 1668): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1668): Error getting crypt footer and key
and later on the typical (but now with "Bad magic ..." line
E/Cryptfs ( 1668): Bad magic for real block device /dev/block/mmcblk0p25
E/Cryptfs ( 1668): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
Forth try:
TWPR 2.8.6.4 & SlimKAT 4.4.4
adb logcat
E/Cryptfs ( 1682): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
-----------------------------------
I hope you have another idea for me......
Greetings
Hello Everybody !
I managed to encrypt from Settings :victory:
I "just" resized (shrinked) the /data partition a little bit.
To Perform this i used the TWRP 2.8.7.3 version from Android-Andi
because it was the one which got all the commands i needed for it.
@ android-andi (would it make sense to change the TWRP setup, so that his tweak is done automatically ?)
at least some people semmed to have similar Problems like me.
I did a adb root / adb shell into the Recovery and followed a Tipp from over Here:
http://android.stackexchange.com/questions/117405/how-do-you-encrypt-your-device-running-cyanogenmod-12-1
Just because the www is sometimes full of dead ends i post the Instructions here, as I used them on MY device.
So i changed them a little bit from the originalpost.
If you wanna try something similar you should NOT just copy & paste the Commands.
Make shure which "/dev/block/..." is your /data partition
In Linux i did: (don't know what do to in Windows, sorry)
$ adb root
$ adb shell
within the adb Shell YOU should
~ # mount | grep data
to find the actual block device of the data partition.
For ME it is /dev/block/mmcblk0p25
so i did the following:
~ # umount /data
& i had also to do
~ # umount /sdcard
~ # e2fsck -f /dev/block/mmcblk0p25
everything was fine otherwise i could do e2fsck -f -p /dev/block/mmcblk0p25 to repair the stuff
~ # tune2fs -l /dev/block/mmcblk0p25 to obtain the "Block count" from the output.
~ # tune2fs -l /dev/block/mmcblk0p25
tune2fs 1.42.9 (28-Dec-2013)
Filesystem volume name: <none>
Last mounted on: /data
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 310080
Block count: 1239035
Reserved block count: 0
Free blocks: 1174719
Free inodes: 309535
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 303
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8160
Inode blocks per group: 510
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Last mount time: Tue Jan 3 14:00:32 2012
Last write time: Tue Jan 3 14:05:19 2012
Mount count: 0
Maximum mount count: -1
Last checked: Tue Jan 3 14:05:19 2012
Check interval: 0 (<none>)
Lifetime writes: 213 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
For me it was : 1239035
~ # resize2fs /dev/block/mmcblk0p25 1239015 , i.e. substract a sufficient amount like 20 from the original block count. As far as i read 8 should be the exact amonunt. But I am not fighting for the last Byte.
~ # resize2fs /dev/block/mmcblk0p25 1239015
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /dev/block/mmcblk0p25 to 1239015 (4k) blocks.
The filesystem on /dev/block/mmcblk0p25 is now 1239015 blocks long.
to check if everything is okay:
~ # e2fsck -f -p /dev/block/mmcblk0p25 found a minor problem which got fixed
~ # e2fsck -f -p /dev/block/mmcblk0p25
/dev/block/mmcblk0p25: Inode 7, i_size is 1270947840, should be 1275146240. FIXED.
/dev/block/mmcblk0p25: 545/310080 files (8.3% non-contiguous), 64316/1239015 blocks
After that i just did a reboot into recovery.
I Just wiped dalvic, system, cache & DATA ( NO FORMAT TO MESS THINGS UP AGAIN !!!)
Then I flashed SlimKAT 4.4.4. from Android-Andi April 2016 build.
Rebooted into System.
In System in Settings > Interface > Lockscreen i set up PIN
Than in Settings > Security > encrypt Phone EVERYTHING went fine. Finally after a couple of weeks !!
adb Logcat "tells" now:
D/Cryptfs ( 1686): Just asked init to shut down class main
D/Cryptfs ( 1686): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 1686): unmounting /data/data succeeded
D/Cryptfs ( 1686): unmounting /data succeeded
D/Cryptfs ( 1686): Just triggered post_fs_data
D/Cryptfs ( 1686): post_fs_data done
D/Cryptfs ( 1686): Just triggered restart_min_framework
E/Cryptfs ( 1686): Crypt_ftr version doesn't support persistent data
I/Cryptfs ( 1686): Enabling support for allow_discards in dmcrypt.
E/Cryptfs ( 1686): Encrypting filesystem in place...
After first root app installation (root browser) the system did a crash.
Since thea i installed 3 more root apps. so far (about since an hour) the system is running stable.
Greetings
P.S.
I Suppose this trick should at least work with any KiTKat ROM.....
I gonna try Lollipop , but not tonight ....
Update
to anybody how may it concern.
I installed successfully OmniRom 5.1.1. on the device. encryption still working.
Recovery was still: TWRP 2.8.7.3 by Android-andi
OmniROM 5.1.1. by golden-guy (build 05052016)
I just booted into Recovery & entered the choosen encryption PIN & wiped:
system
cache
dalvic
data !!
I did NOT format data.
Next step was to flash the OmniROM image.
Booted back into System.
Everything worked fine. data was still encrypted !
-----
Next try was to flash CM12.1 by Novafusion (bulid 24 05 2016)
The same TWRP a above.
I had no errors flashing the same way as above.
But booting into system ended with a "corrupted" encrypted Filesystem.
A factory Reset didn't help.
----
Even flashing the promary SlimKAT 4.4.4 by Android-andi didn't changed the problem.
I don't know the reason why the corruption happend (perhaps because i didn't used the "novafusion TWRP Recovery" , perhaps for another reason.
So i did a "classic" Flash with "wipe of dalvic, system, cache" and a "format data".
after flashing SlimKAT again, i got the same old error from all the postings above.
----
Im not gonna dig deeper into this Stuff. I now gonna do the "/Data shrink" again and gonna be happy with what i managed to fullfill.
Greeting