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
Before you follow all this steps, remember:
THIS IS NOT A HOW TO...!!!!!!!!!!!
Remember, that i'm asking to other more experienced users if this method should work, so, i haven't tried it yet
Hi, im trying to change the ROM of my galaxy s3 mini from Linux using heimdall, and i've doubts.
My current ROM:
build number: JR003H.I8190XXALL2
kernel version: 3.0.31-639956
android version: 4.1.1
baseband version: I8190XXALL2
New ROM:
http://forum.xda-developers.com/showthread.php?t=2104638
build number: JZO54K.I8190XXAMA1
kernel version: 3.0.31 - 790526
baseband version: XAAMA1 [EUROPE]
android version: 4.1.2
ROM STATUS: NON-WIPE
FIRMWARE STATUS AFTER FLASH: OFFICIAL
BINARY COUNT AFTER FLASH: NONE
In this thread, the user arturaz explained how to change the ROM using heimdall:
http://forum.xda-developers.com/showthread.php?t=2066668
But, he used a ROM with the same baseband than the old one. As you see, I have an issue: my current baseband version is different than the new one. So, i'll have to flash more files, and thats my trouble. Because I'm not sure about that, and I need someone to tell me if my reasoning is ok.
Lets go!
1. Decompress all files of my ROM. I've stored then in my home:
/home/ali3n//galaxys3/I8190XXAMA1_I8190OXAAMA1_4.1.2_rooted_by_infected_/
Code:
[COLOR="Blue"]$ cd /home/ali3n//galaxys3/I8190XXAMA1_I8190OXAAMA1_4.1.2_rooted_by_infected_/[/COLOR]
Code:
[COLOR="Blue"]$ ls -1a[/COLOR]
boot.img
cache.img
hidden.img
modem.bin
STE_boot1.img
STE_boot2.img
system.img
So, those are the files that I've to look for in my current pit file.
I put my phone in download mode, connect to my pc and:
2. ¿Does heimdall detect my device?
Code:
[COLOR="Blue"]$ sudo heimdall detect[/COLOR]
Device detected
3. Lets see my pit file to look for the files needed in the new ROM version and which partitions are used for each of them:
Code:
[COLOR="Blue"]$ sudo heimdall print-pit[/COLOR]
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...
Claiming interface...
Attempt failed. Detaching driver... -----> (i'm not sure about if should I continue)
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: 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 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 0
Partition Block Count: 256
Unknown 2: 0
Unknown 3: 0
Partition Name: MBR,GPT
Filename:
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 256
Partition Block Count: 768
Unknown 2: 0
Unknown 3: 0
Partition Name: MasterTOC
Filename: STE_boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 70
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 1024
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: goldenxx.pit
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 71
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 6144
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: MD5HDR
Filename: md5.img
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 8192
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot1
Filename: STE_boot1.img
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 9216
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot2
Filename: STE_boot2.img
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 10240
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: Dnt
Filename: dnt.ssw
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 11264
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: reserved
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 16384
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS
Filename: cspsa.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 18432
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS2
Filename: cspsa2.img
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 20480
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: EFS.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 53248
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS
Filename: modemfs.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 86016
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS2
Filename: modemfs2.img
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 118784
Partition Block Count: 102400
Unknown 2: 0
Unknown 3: 0
Partition Name: Fota
Filename: ssgtest.img
--- Entry #14 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 380928
Partition Block Count: 128
Unknown 2: 0
Unknown 3: 0
Partition Name: IPL Modem
Filename: ipl.bin
--- Entry #15 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 14
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 385024
Partition Block Count: 28672
Unknown 2: 0
Unknown 3: 0
Partition Name: Modem
Filename: modem.bin
--- Entry #16 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 15
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 417792
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: Loke4
Filename: normal.bin
--- Entry #17 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 16
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 421888
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: 2ndLoke4
Filename: normal2.bin
--- Entry #18 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 17
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 425984
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #19 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 18
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 458752
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel
Filename: boot.img
--- Entry #20 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 19
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 491520
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel2
Filename: recovery.img
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
--- Entry #22 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 21
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 2981888
Partition Block Count: 1720320
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHEFS
Filename: cache.img
--- Entry #23 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 22
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 4702208
Partition Block Count: 655360
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #24 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 23
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 5357568
Partition Block Count: 9891840
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: userdata.img
Ending session...
Rebooting device...
Re-attaching kernel driver...
4. flashing the device and installing the rooted ROM
Once I've located which Partition Identifier is associated to each of the new ROM files:
Code:
[COLOR="Blue"]$ sudo heimdall flash --3 STE_boot1.img --4 STE_boot2.img --14 modem.bin --18 boot.img --20 system.img --21 cache.img --22 hidden.img[/COLOR]
I think thats all. ¿It's all right? ¿Does anybody do it before? I don't know if should i do anything else before flashing the device, and i wanna know your opinion about if this is the right way.
Thank you!
In Linux, Heimdall doesn't read download mode but ADB reads normally. In Win7, ADB doesn't read but Odin reads download mode.
Sent from Spaceball One.
blackknightavalon said:
In Linux, Heimdall doesn't read download mode but ADB reads normally. In Win7, ADB doesn't read but Odin reads download mode.
Sent from Spaceball One.
Click to expand...
Click to collapse
Thank you for your answer, but I don't know what you mean blackknightavalon. In this thread a user explains how to change the ROM using heimdall in linux:
http://forum.xda-developers.com/showthread.php?t=2066668
My issue, is that the new ROM uses a different baseband version than the current one. So I don't know if the procedure that I've described, based on the experience of arturaz could work.
Thank you!
nslookup said:
In this thread a user explains how to change the ROM using heimdall in linux:
http://forum.xda-developers.com/showthread.php?t=2066668
My issue, is that the new ROM uses a different baseband version than the current one.
Click to expand...
Click to collapse
Probably too late for you, but maybe still useful for further heimdall users...
I guess what arturaz meant, was: Since he had a "XXALJL" build on his phone before he explicitly chose the same build but rooted. And further, since the baseband was the same, all he needed to re-flash was the system partition in order to get the "su" binary where it belongs. That's a Linux habitat: Only change the least that's needed when everything else is already there.
Maybe arturaz is willing to confirm my interpretation.
However, after reading his posting I went the same lane. My Mini had the same build and I've rooted it exactly as described. Then I installed ROM-manager and with the help of su (aka "root"), CWM. Using this I installed BenzROM, which has a different build. But since the entire image was replaced, the baseband fits to it.
And it works
Hope that helps.
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
================================================== ====
Sending AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE AMSS CERTIFICATE SUCCESS
Sending AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : AMSS WRITE SUCCESS
Sending ADSP Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE ADSP CERTIFICATE SUCCESS
Sending ADSP Data Blocks
(Please Wait for 25 Seconds...)
Status : ADSP WRITE SUCCESS
Sending MDM AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM AMSS CERTIFICATE SUCCESS
Sending MDM AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM AMSS WRITE SUCCESS
Sending MDM DSP1 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP1 CERTIFICATE SUCCESS
Sending MDM DSP1 Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM DSP1 WRITE SUCCESS
Sending MDM DSP2 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP2 CERTIFICATE SUCCESS
Sending MDM DSP2 Data Blocks
(Please Wait for 100 Seconds...)
Status : MDM DSP2 WRITE SUCCESS
Sending WPOS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 1652 Bytes
Status : WRITE WPOS CERTIFICATE SUCCESS
Sending WPOS Data Blocks
[BLOCK 1 0x00000000~0x00FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8D9F6A1AF69045EC0339C2EFFC2527D
---------- : D1CAECCFCFC39F1F44C67A5AD3F6C050
Status : WPOS WRITE SUCCESS
[BLOCK 2 0x01000000~0x016573FF]
Data Size: 0x00657400 Bytes
SHA-256 : 98D712C48E828E9816D3F7E84CFDE5DB
---------- : 2C32011C24D4615234D0F613F4EF7B52
Status : WPOS WRITE SUCCESS
[BLOCK 3 0x01697400~0x01FFFFFF]
Data Size: 0x00968C00 Bytes
SHA-256 : 80EB94E3FB5AE03E9091361275A3138E
---------- : 2D0370E5C2A497C74BEA6BEAA43A9E21
Status : WPOS WRITE SUCCESS
[BLOCK 4 0x02000000~0x02FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 07BE87B2AF4D1386F4C6CA136F3E5A57
---------- : 71DC6DDB330A07AAB4493C8AA329BB58
Status : WPOS WRITE SUCCESS
[BLOCK 5 0x03000000~0x03FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2A3DE5C7CB693B00E257A4E7FB03E834
---------- : 11FAA597F94B220E69E25BD4653BE9B5
Status : WPOS WRITE SUCCESS
[BLOCK 6 0x04000000~0x04FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 16A3B764DD2CCBE5D144B504A919A847
---------- : 2F5DDCBBE2506ACEF6A39800E4DC5124
Status : WPOS WRITE SUCCESS
[BLOCK 7 0x05000000~0x05FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 4A508131A19FC499F19529C55D5D69B8
---------- : D85FA016F8CADE240FA88FA175159699
Status : WPOS WRITE SUCCESS
[BLOCK 8 0x06000000~0x06FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 9E494B017FB7E00D9245C8AEF0F01467
---------- : F3A10341E7441CBEBDE04399AFDD8C5E
Status : WPOS WRITE SUCCESS
[BLOCK 9 0x07000000~0x07FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2AA1C1C01BA5F8825796F134753C7651
---------- : ABAC4C024CF30CE60B624C4E6C8CD665
Status : WPOS WRITE SUCCESS
[BLOCK 10 0x08000000~0x08FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 6F6EA7A66C4AE1A05CF643378A07E1A8
---------- : 523B29D66201C2FBD4053B19E785DE14
Status : WPOS WRITE SUCCESS
[BLOCK 11 0x09000000~0x09FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 017C4DB9A69575E684BADB7515DBBF59
---------- : 67A6F0DA20F034470D6148B12A1013F4
Status : WPOS WRITE SUCCESS
[BLOCK 12 0x0A000000~0x0AFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 1EFE884A458C910A768D6A60FF74BA8B
---------- : 58F546EB92737ACD1A59169E583CD407
Status : WPOS WRITE SUCCESS
[BLOCK 13 0x0B000000~0x0BFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 713CF0944BA46C6820DCEB7A210C365A
---------- : 7F8A1B0C3E168DE07B46E14907F511FC
Status : WPOS WRITE SUCCESS
[BLOCK 14 0x0C000000~0x0CFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 425A9ED14D4A78F21CDD261AB87F2CF1
---------- : 37080DD8E63F6A9BBBC4E9181AF7B9D2
Status : WPOS WRITE SUCCESS
[BLOCK 15 0x0D000000~0x0DFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 0C09DA5584E22D2709C548F2E5CD05F5
---------- : CFB62CE93C7DAF202A4B92299072B4FB
Status : WPOS WRITE SUCCESS
[BLOCK 16 0x0E000000~0x0EFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CC14545EF5F62DA50EFADEC5E077FA15
---------- : FE6723E61D703468E0F2B88A3A77008E
Status : WPOS WRITE SUCCESS
[BLOCK 17 0x0F000000~0x0FFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 75D352196D46AC4FED27B84844D89D27
---------- : A8E6C4BD07D46537FA1D66BC533BF017
Status : WPOS WRITE SUCCESS
[BLOCK 18 0x10000000~0x10FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D6847541FEB0C828C7BE18F045FD2602
---------- : D31D627E75BAA24AD9EBE13E111DCD96
Status : WPOS WRITE SUCCESS
[BLOCK 19 0x11000000~0x11FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 3512321DD2C8349BF40BF6ACD45B82A8
---------- : 970E7902252853F1C75FD6DA3B07416C
Status : WPOS WRITE SUCCESS
[BLOCK 20 0x12000000~0x12FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 970B38B361801866AEB1F9D0E2A6E5FB
---------- : 28066FD1BCF0EF794B57E56439B29152
Status : WPOS WRITE SUCCESS
[BLOCK 21 0x13000000~0x13FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8E0BAEDBCFC0A13A125FF17A9DDDA0E
---------- : 91AC3DD74B6E738F3AD53D269F12CFFD
Status : WPOS WRITE SUCCESS
[BLOCK 22 0x14000000~0x14FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D786A1406E5AF5D0B5354003197BCE87
---------- : F34053A66DF8375001E2DB59D528B21D
Status : WPOS WRITE SUCCESS
[BLOCK 23 0x15000000~0x15FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 47A2B984B6D9C39AF4131C9ED8DB949A
---------- : 82CBC84E0019ECB0E1BABB61E0F47790
Status : WPOS WRITE SUCCESS
[BLOCK 24 0x16000000~0x16FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D4CEA61B44087F662387735C6AF3F626
---------- : D0A782BCFC893D7CD19A1895A2503AE8
Status : WPOS WRITE SUCCESS
[BLOCK 25 0x17000000~0x17FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 93D0DB4DA824CE4660B96A99A1F65989
---------- : CA45F500E83FC9A53D1D8330B150A80E
Status : WPOS WRITE SUCCESS
[BLOCK 26 0x18000000~0x184A17FF]
Data Size: 0x004A1800 Bytes
SHA-256 : 0CE0CCDE41E4E40B170207CABCE6AA18
---------- : 8FD44C00E21833E6B5926A1F0CDFA40A
Status : WPOS WRITE SUCCESS
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
otchere said:
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
Click to expand...
Click to collapse
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
thals1992 said:
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
Click to expand...
Click to collapse
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
otchere said:
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
Click to expand...
Click to collapse
Did you first try the hard reset method with the VolDown + Power first? The only other method I'd recommend is using the Nokia Care Suite instead of what you are using. Its much simpler. Just remember to download the latest edition with the CareSuite External cfg file.
One other thing: what phone are you flashing this *onto*? If you tried flashing a Lumia 900 ROM onto a Lumia 920, for example, there is no possible way it will work (although the flashing tool should detect the discrepancy).
By the way, to get to appropriate forums for the Lumia 900, you should go to the WP7 forums (not WP8, such as this) or possibly to a device-specific forum
Oh, and title your thread properly! Seriously, people... if somebody posts a thread with a title like "plz help me" my default response is "No. Go read the forum rules and come back when you can make posts distinguishable from spam."
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