Database Develop

[Q] Partition Table & Mount Point List

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

[Q] pda's condition to use repartition + pit

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

flashing gt-i8190 from linux using heimdall. ¿How to?

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.

[Q] Need Help Unbricking i9000M - Tried All Suggestions

I've probably read everything currently available for unbricking a Galaxy S (i9000)g and Galaxy S Vibrant (i9000M), but I'm open to more suggestions!
Here's my current situation:
Bricked GT-i9000M - can't do anything except go into download mode
Odin doesn't detect the phone at all (obviously driver-related, but hang on)
Heimdall works fine, but the flashing just doesn't seem to complete (I've added my current PIT at the end of the post)
Can't boot into recovery (partly because I keep overwriting the recovery trying to install ROMs so right now it might not even be properly installed)
Tools available at my disposal:
Linux laptop running Kubuntu 14.04
Windows 8.1 Desktop
Windows 7 Laptop (not too accessible but can use if necessary)
Heimdall 1.4 frontend and command line
An ODIN flashable stock i9000M ROM that I extracted the files for flashing with Heimdall (although it was missing a boot.bin so I used one from another ROM, probably not the best idea, but I'm trying everything) obtained from here (it's bolded under "Android Rescue, Recovery Kits -> Upgrade or Downgrade or for Recovery": http://forum.xda-developers.com/showthread.php?p=29331775#post29331775
Issues
- It's been so long since I had this phone working that I forgot what ROM, kernel, etc. it was originally running and I know there's supposed to be an "upgrade" procedure for GB to ICS/JB, but I just want the phone bootable into a ROM right now.
- I can't seem to find a proper i9000M stock ROM (I apologize if I've missed it, but would greatly appreciate a link)
- Speaking of links, most "recovery kits" I've come across have dead links
- Most unbricking guides and the aforementioned recovery kits specifically state "ONLY for use with i9000" so I've stayed away from them for the most part just in case I end up with a perma-brick (not likely, but a possibility nonetheless)
With all that being said, I would appreciate ANY help you guys can give as I'm honestly all out of ideas. It seems like it's so close to working, I just need a proper, stock i9000M heimdall-flashable ROM.
Here's my most recent flash attempt (stock i9000M ROM from "Rescue kit" with files extracted into Heimdall flashable format, and using boot.bin from stock i9000 recovery kit)
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Releasing device interface...
Here's my PIT output:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 13
Unknown 1: 1
Unknown 2: 0
Unknown 3: 7508
Unknown 4: 65
Unknown 5: 64224
Unknown 6: 18
Unknown 7: 55304
Unknown 8: 67
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 6684783
File Size (Obsolete): 2097268
Partition Name: IBL+PBL
Flash Filename: boot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename:
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 20
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 40
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.rfs
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 4
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 21
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: zImage
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 22
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1146
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.rfs
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 23
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DBDATAFS
Flash Filename: dbdata.rfs
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 24
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 140
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.rfs
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 11
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 50
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 11
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
Ending session...
Releasing device interface...
Re-attaching kernel driver...
EDIT: Just wanted to add that I've been using the 512 PIT, I've read mixed things on ROMs working with various PITs so I've just always been using whatever a guide tells me to use, which has always been the 512 for me since I've pretty much just been flashing stock ROMs.

Working ROM but Infamous Battery Boot Loop
Ok, I can successfully flash ROMs now! I followed this guide: http://forum.xda-developers.com/showthread.php?t=1886393 and pretty much just gave up with the i9000M part especially since I don't plan on using this device with a SIM card anyway.
I had to flash the ROM in that guide twice - the first time WITHOUT the root zImage, and the second time WITH the rooted zImage. Then I flash CM9.1.0 twice (as per recommended in the guide) and from that point on my phone is almost fully functioning again - I can flash ROMs in recovery, I can reboot into recovery, and can use the ROMs perfectly. HOWEVER, I can't do anything if I shut off the phone. I can reboot no problem, but as soon as I power off the device, it's back to the battery boot loop. From that point I have to go into download mode and repeat the aforementioned steps.
So, I want to try fixing this battery boot loop so that I can actually power off my device when I want to. I've wanted to try some of the suggestions here http://forum.xda-developers.com/showthread.php?t=1923225&page=4, but as soon as I shut off the device I get the battery boot loop, so I can't possibly know when it's at 100%.
The other thing is that my battery seems to be at ~3.95/3.92V so it almost seems like it's overcharging since it's rated at 3.7V.
I've also tried wiping the battery stats via CWM but that doesn't seem to help.
Any suggestions would be greatly appreciated.

Can this Galaxy tab 7 be saved?

Hi, Any chance in resurrecting this galaxy tab 7? I think the partition table is messed up.
Model: Verizon Mobile SCH-I800
Issue: many;
failed to mount's
can't mount's
format fails
can't open
unknown rom
history unknown
*Can boot into recovery and download mode *can't apply update.zip from sdcard, can't even mount sdcard.
I have tried heimdall with stock roms and PITs etc but with no luck, Could not get the full file off The Collective helper package (stops mid download so could not go further with that; http://forum.xda-developers.com/showthread.php?t=2383201
About to try adb with parted etc but have found little info on this and wouldn't know where to start.
Any help would be greatly appreciated thanks, happy to try anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
**Thread moved from XDA Assist section**

A little better from flashing the files from unbricking post, but still having troubles
Tab will boot and be stuck at Verizon screen.
If someone could help out and go to here and try to download The collective helper package (direct link) and re-up it to another mirror, I'd be very grateful. I can only get through at most half of the download before it stalls but it looks like some people can get the whole thing.
Or if you could post a link to stock firmware tar.gz file for this that would be great, I cannot find it at sammobile or live.samsung-updates or pretty much anywhere...
Thanks!

Also check
ORIGINAL NON ROOTED Galaxy Tab stock ROM for Verizon.
and
[Tutorial] How To Restore Verizon Galaxy Tab Back To Stock
Looks like Heimdall is the flasher for your tablet, not ODIN as I had mentioned earlier, but you already know that.

Tried a complete flash with your first link you posted, Thanks a proper tar.gz! used heimdall.exe rather than frontend as I was getting libusb errors. command;
heimdall.exe flash --repartition --pit sch-i800.pit --CACHE cache.rfs --FACTORYFS system.rfs --PARAM param.lfs --KERNEL zImage --RECOVERY recovery.bin
everything appeared to work fine & 100% successful except I'm still at the same screen above...
The errors I get are;
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmblk0p2
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
While i'm a little further, i'm at a loss what is still wrong, will try adb into partitions later and see if any are fat32 or something as I've seen on a post somewhere. Thanks for your help
update;
Flashed CWM with Odin.. attempting to flash cyanogenmod via a guide, got nowhere, reflashed back to where I was...
Here's my partition table if anyone can spot anything wrong.. ;
Downloading device's PIT file...
PIT file download successful.
Entry Count: 13
Unknown 1: 4380672
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 64
Unknown 7: 63496
Unknown 8: 20
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IBL+PBL
Flash Filename: boot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename:
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 20
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 40
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.rfs
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 4
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 21
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 22
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.rfs
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 23
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 348
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DBDATAFS
Flash Filename: dbdata.rfs
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 24
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 140
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.rfs
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 8
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 64
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MOVINAND
Flash Filename: movinand.bin
FOTA Filename:

Full Restock
Just try Full Restock again via GB-Stock Safe :fingers-crossed:
---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------
http://postimg.org/image/jplw65lvb/

NO! GB stock safe v5 is for P1000 only.
Sent from my GT-N7100 using XDA Free mobile app