Related
Have searched around for partition info on the skyrocket, didn't find anything specific to our device so decided to do some investigation by dumping all of the block devices listed under /dev/block. Most of the partition info lives in mmcblk0p1 and mmcblk0p11 (PIT).
Might be useful info to someone in the future, so posting for reference.
Code:
Device Name Size Part Name ODIN tar file Mount Point
mmcblk0boot0 512KB (empty) n/a (empty partition)
mmcblk0boot1 512KB (empty) n/a (empty partition)
mmcblk0p1 100MB SMD_HDR (partition info)
mmcblk0p2 500KB SBL1 sbl1.mbn
mmcblk0p3 1500KB SBL2 sbl2.mbn
mmcblk0p4 1KB (unnamed partition with '55 AA' MBR signature)
mmcblk0p5 500KB RPM rpm.mbn
mmcblk0p6 2MB SBL3 sbl3.mbn
mmcblk0p7 2500KB ABOOT aboot.mbn
mmcblk0p8 10MB BOOT boot.img
mmcblk0p9 500KB TZ tz.mbn
mmcblk0p10 500KB SSD n/a (empty partition)
mmcblk0p11 500KB PIT celox.pit
mmcblk0p12 10MB PARAM param.lfs
mmcblk0p13 98MB MODEM amss.bin /system/etc/firmware/misc
mmcblk0p14 3MB MSM_ST1 efs.img
mmcblk0p15 3MB MSM_ST2 n/a
mmcblk0p16 3MB MSM_FSG n/a
mmcblk0p17 98MB MDM mdm.bin /system/etc/firmware/misc_mdm
mmcblk0p18 3MB M9K_EFS1 efsclear1.bin
mmcblk0p19 3MB M9K_EFS2 efsclear2.bin
mmcblk0p20 3MB M9K_FSG n/a
mmcblk0p21 10MB DEVENC enc.img.ext4 /efs
mmcblk0p22 10MB RECOVERY recovery.img
mmcblk0p23 3MB FOTA n/a
mmcblk0p24 598MB SYSTEM system.img.ext4 /system
mmcblk0p25 2GB USERDATA userdata.img.ext4 /data
mmcblk0p26 302MB CACHE cache.img.ext4 /cache
mmcblk0p27 129MB TOMBSTONES tomb.img.ext4 /tombstones
mmcblk0p28 11.2GB UMS ums.rfs /mnt/sdcard
Great post, these partitions will be the same for T989 people as well. just a FYI
Any chance you could pull the celox.pit file out and upload to somewhere for me to download?
lunchbox201 said:
Any chance you could pull the celox.pit file out and upload to somewhere for me to download?
Click to expand...
Click to collapse
Dump of PIT file (mmcblk0p11.bin) from SGH-I727 attached.
cschmitt said:
Dump of PIT file (mmcblk0p11.bin) from SGH-I727 attached.
Click to expand...
Click to collapse
So can I just rename this file (Once it is extracted) to skyrocket.pit and use it in ODIN?
tjsooley said:
So can I just rename this file (Once it is extracted) to skyrocket.pit and use it in ODIN?
Click to expand...
Click to collapse
That's a partition dump, lots of trailing empty space that probably needs to be trimmed.
Attached is a copy that's trimmed down to 4KB.
As far as flashing the pit in ODIN, if you're comfortable in your knowledge and wish to proceed you obviously have a good reason for doing so.
cschmitt said:
Have searched around for partition info on the skyrocket, didn't find anything specific to our device so decided to do some investigation by dumping all of the block devices listed under /dev/block. Most of the partition info lives in mmcblk0p1 and mmcblk0p11 (PIT).
Might be useful info to someone in the future, so posting for reference.
Code:
Device Name Size Part Name ODIN tar file Mount Point
mmcblk0boot0 512KB (empty) n/a (empty partition)
mmcblk0boot1 512KB (empty) n/a (empty partition)
mmcblk0p1 100MB SMD_HDR (partition info)
mmcblk0p2 500KB SBL1 sbl1.mbn
mmcblk0p3 1500KB SBL2 sbl2.mbn
mmcblk0p4 1KB (unnamed partition with '55 AA' MBR signature)
mmcblk0p5 500KB RPM rpm.mbn
mmcblk0p6 2MB SBL3 sbl3.mbn
mmcblk0p7 2500KB ABOOT aboot.mbn
mmcblk0p8 10MB BOOT boot.img
mmcblk0p9 500KB TZ tz.mbn
mmcblk0p10 500KB SSD n/a (empty partition)
mmcblk0p11 500KB PIT celox.pit
mmcblk0p12 10MB PARAM param.lfs
mmcblk0p13 98MB MODEM amss.bin /system/etc/firmware/misc
mmcblk0p14 3MB MSM_ST1 efs.img
mmcblk0p15 3MB MSM_ST2 n/a
mmcblk0p16 3MB MSM_FSG n/a
mmcblk0p17 98MB MDM mdm.bin /system/etc/firmware/misc_mdm
mmcblk0p18 3MB M9K_EFS1 efsclear1.bin
mmcblk0p19 3MB M9K_EFS2 efsclear2.bin
mmcblk0p20 3MB M9K_FSG n/a
mmcblk0p21 10MB DEVENC enc.img.ext4 /efs
mmcblk0p22 10MB RECOVERY recovery.img
mmcblk0p23 3MB FOTA n/a
mmcblk0p24 598MB SYSTEM system.img.ext4 /system
mmcblk0p25 2GB USERDATA userdata.img.ext4 /data
mmcblk0p26 302MB CACHE cache.img.ext4 /cache
mmcblk0p27 129MB TOMBSTONES tomb.img.ext4 /tombstones
mmcblk0p28 11.2GB UMS ums.rfs /mnt/sdcard
Click to expand...
Click to collapse
What command did you type in to view the dump?
KillaT21 said:
What command did you type in to view the dump?
Click to expand...
Click to collapse
There is no single command. Most of it was collected from the celox.pit and looking at the mount points.
Reported
Sent from my SGH-I727 using xda premium
jamesc760 said:
Reported
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Reported what?
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesc760 said:
Reported
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Do us a favor and get off xda if you're going to be a scumbag pls. No need to be abusing the report button.
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm a bit confused. Can I make EFS backup with
Code:
dd if=/dev/block/mmcblk0p21 of=/sdcard/efs.rfs
from ADB shell?
It gives me
Code:
/dev/block/mmcblk0p21: cannot open for read: Permission denied
under SU.
Sorry if it's stupid question.
That command should work, but appears that you don't have root. What rom are you on?
cschmitt said:
That command should work, but appears that you don't have root. What rom are you on?
Click to expand...
Click to collapse
I'm rooted and I have Paranoid Android Tried this in airplane mode as well
blazedj said:
I'm rooted and I have Paranoid Android Tried this in airplane mode as well
Click to expand...
Click to collapse
Try typing the command:
Su
Then hit enter. THEN run the above referenced commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Try typing the command:
Su
Then hit enter. THEN run the above referenced commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I did so but it didn't work first time. Maybe permissions were not set up correctly until I connected again. Should have tried twice before complaining here
Thanks for your time!
Now it works both through ADB and terminal emulator. Got 10mb image. I wonder if it's fastboot or Odin flashable?
System dump script
Attached is a batch file that uses ADB to perform a binary dump of every partition on the Skyrocket to the local hard drive. It requires that ADB and the Skyrocket drivers are already installed and working on the computer, and requires a rooted device.
It does not dump /system or /data, partitions due to their size, although this can be enabled by un-commenting the appropriate line(s) in the script. It also does not backup /sdcard because the sdcard is used for the temporary dump files on the device.
After doing this you will have a backup of the PIT, EFS, bootloaders, modems, etc. --everything.
As always, proceed at your own risk.
delete pls.
Hi guys.
My story is here. http://forum.xda-developers.com/showthread.php?t=2033458&page=2 , post#12
I couldn't use adb on Windows as there was some error while driver installation.
So I used Linux-machine.
Command adb devices -l gave me this:
~$ adb devices -l
List of devices attached
4305228e offline usb:1-1
Only when I connect phone swithed on (if I can say that because nothing on screen).
Other USB-ports showed the same, changing only port-number.
All other modes: Download mode, tried to enter Recovery, this command showed:
~$ adb devices -l
List of devices attached
Does any1 have any ideas if my phone is really dead? Or, maybe, I still have hope to recover it.
Well let me tell you that first off adb won't do anything in that state second run lsusb to see if its recognized on the computer third it may not always be necessary but check your rules.d folder to add 99android.rules.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Where can I get a complete list of what each partition is? There's a list for the HTC Amaze at http://forum.xda-developers.com/showthread.php?t=1545911 but that list isn't correct for the Desire S.
I've worked out the following, but would like a complete list:
mmcblk0p17 misc_version
mmcblk0p18 hboot
mmcblk0p22 boot
mmcblk0p25 system
mmcblk0p26 data
mmcblk0p27 cache
mmcblk0p28 devlog
The command “cat /proc/partitions" lists all partitions, but not their name/function.
Sent from my Desire S
you can try to use command “cat /proc/emmc”
Here are my findings if you stil need the info:
Code:
mmcblk0p1 qcsbl_cfg part of radio.img
mmcblk0p2 qcsbl <empty>
mmcblk0p3 osbl part of radio.img
mmcblk0p4 extended part of radio.img elf-header of rex/amss
--------- --------- -------
mmcblk0p5 modem part of radio.img
mmcblk0p6 adsp part of radio.img
mmcblk0p7 htc rcdata.img Radio settings (IMEI,CID,S-OFF)
mmcblk0p8 rf_nv <empty>
mmcblk0p9 nv_mfg <empty>
mmcblk0p10 cdma_user_data <empty>
mmcblk0p11 rf_delta <empty>
mmcblk0p12 reserved <empty>
mmcblk0p13 modem_fs1
mmcblk0p14 modem_fs2
mmcblk0p15 htc_data <empty>
mmcblk0p16 htc_reserved <empty>
mmcblk0p17 misc device info
mmcblk0p18 appsbl hboot
mmcblk0p19 splash1
mmcblk0p20 wifi WiFi module
mmcblk0p21 recovery
mmcblk0p22 boot kernel & ramdisk
mmcblk0p23 mfg device config ?, contains WiFi MAC-address and Serial number
mmcblk0p24 splash2 <empty>
mmcblk0p25 system
mmcblk0p26 data userdata
mmcblk0p27 cache
mmcblk0p28 devlog
This is 0.98.x partition layout, on 2.00.x it has more partitions, but I believe that the first 27 are the same
Brilliant! Thanks.
Would you mind sharing how you found out all of this?
Sent from my HTC Desire S
How can you get this info? I need it ,Thanks.
BillGoss said:
Brilliant! Thanks.
Would you mind sharing how you found out all of this?
Sent from my HTC Desire S
Click to expand...
Click to collapse
A lot of searching through the Net, dumping partitions, hex analyzing, comparing to rom.zip images...
EDIT: some of the names are pure guess, such as mfg, but the content is 100 % verified. The names can be verified checking the hboot string if somebody is interested...
Thanks!
Sent from my Desire S
Need this for gt-i8150
amidabuddha said:
A lot of searching through the Net, dumping partitions, hex analyzing, comparing to rom.zip images...
EDIT: some of the names are pure guess, such as mfg, but the content is 100 % verified. The names can be verified checking the hboot string if somebody is interested...
Click to expand...
Click to collapse
Hey, I really need this for my model of phone (try to get a network unlock code from phone), but I'm really noob at hacking at using linux. What command would allow me to check the 'hboot' string of a given mmcblkXpXX file?
Thanks heaps,
Foxy
GrayedFox said:
Hey, I really need this for my model of phone (try to get a network unlock code from phone), but I'm really noob at hacking at using linux. What command would allow me to check the 'hboot' string of a given mmcblkXpXX file?
Thanks heaps,
Foxy
Click to expand...
Click to collapse
You have to dump the partition to the SD card via the dd command (you can use terminal emulator on your device) then copy the image to PC, open it with some HEX editor and look through the file
Sent from my HTC Desire S using Tapatalk
DD onto Mac
amidabuddha said:
You have to dump the partition to the SD card via the dd command (you can use terminal emulator on your device) then copy the image to PC, open it with some HEX editor and look through the file
Click to expand...
Click to collapse
Thanks. I've been using the strings command and piping to egrep for binary files, pulling only lines that have at least one 8 digit number present.I don't have very large SD cards on my phone - is there any way I could data dump directly to my mac, or alternatively (this would be much faster too) get my mac to do the work? Like... somehow open a terminal on the mac that had super user and root access to the phone?
Again, sorry for being a noob. I've been googling the above problem :S
EDIT: never mind. Downloading ADK now and will use ADB... pretty sure that will do it.
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
EDIT:
Problem solved: See post#57
Bump
Sent from my SCH-I535 using xda app-developers app
letinsh said:
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
Click to expand...
Click to collapse
do you have a pit from the 16 gb version
man that would be great if somebody would post a pitfile for both versions...I know that would help a few folks that corrupted thier emmc internal memory and get the "e cant mount" errors in recovery.
I am game ... how would I extract the PIT file?
Sent from my SCH-I535 using xda premium
Standby. Getting confirmation, then I'll post instructions.
Sent from my SCH-I535 using xda app-developers app
bump...
il gladly dump my 32gb blue if there's instructions.
here is some info from the i9300 forum
http://forum.xda-developers.com/showthread.php?t=1742668
What I'm trying to get confirmation on is using darkyy's dd command from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=960946
Just trying to verify that's the correct place to get it for the SGS3 and that that would produce a flashable .pit file.
Sent from my SCH-I535 using xda app-developers app
please post as soon as you get the ok because i think then we would also be able to use heimdall but i might be wrong.
Bump
Sent from my SCH-I535 using xda premium
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.
letinsh said:
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.[/QUOTE\]
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
joka10 said:
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
letinsh said:
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
Click to expand...
Click to collapse
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
joka10 said:
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
Click to expand...
Click to collapse
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
Heimdall has never been able to recognize my phone...and I was looking somewhere and the developer said it wasn't working and to try 1.3.1 which was not successful either. I had to borrow a computer to use Odin...I know this isn't a solution for getting heimdall to work but I personally don't think it will...if you do get it to work the steps you took would be appreciated
Sent from my SCH-I535 using xda premium
letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
We can use either or I thin for odin you flash using repartition checked and placing it in the pda field but it will allow us to flash with heimdall using that pit since it can't find the one on the phone. Lastly internal flash /dev/block/mmcblk0 becomes /dev/block/mmcblk1 is what i have found so it looks like either im wrong or it has to be one of the 24 blocks.
Can someone with a working 32 run this in a Terminal? It should pull the PIT from your phone and place it in the SD card. I'm sure those with a 16gb would love to have their PIT file as well.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/pit.bin bs=4096 count=1 skip=4
Info from HERE (International device, but the blocks should be the same)
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Try this. https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Irwenzhao said:
Try this. nandroid PM me if u have any problems.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Click to expand...
Click to collapse
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?
trelozakinthinos said:
Thank you for your reply... I have used already this app and I have some questions...
a) When it asks me for select device it says
"Your device code is arubaslimss. Please select the path that corresponds to your device!
If device is nit in list please click the Get Identified button"
So my phone is not on the list and I clicked the get identified button and it sends an email
Code:
Android version: REL 4.1.2
onandroid script version: 9.2
Device: arubaslimss samsung samsung GT-I8260
Contents of: /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20 mmcblk0p1
179 2 175 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 12288 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 12288 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 512 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 1331200 mmcblk0p21
179 22 737280 mmcblk0p22
179 23 327680 mmcblk0p23
179 24 5115488 mmcblk0p24
179 32 3870720 mmcblk1
179 33 3869696 mmcblk1p1
I din't get any response yet...
b) Without identifying my phone I pressed the backup and it did a 2GB backup.
Although I don't know how to check if this works. I mean I can't my phone restore this backup. Any help?
Click to expand...
Click to collapse
Guess the phone's not supported yet then. But if u already made a backup, backup all your apps using helium (backup to sd) and try restoring using the backup u have. (wipe data first)
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
trelozakinthinos said:
Hello
I want to make an image Back-up of my Core and I cannot find something!
I tried the search but I couldn't.
I tried also the rom manager but it does not support my Core.
I want to make this image back up so I can go back if i install an other ROM.
How can I do this?
I hope you can help me!!
(I have already succesfully rooted my phone)
Thank you for your time and help!
Click to expand...
Click to collapse
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card
sawan.aware.1 said:
Use CWM to backup the phone. It's way easier. Preferably backup to external sd card
Click to expand...
Click to collapse
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!
trelozakinthinos said:
CWM does not work with my phone! Not in the list! That's why I was searching for nandroid!
Click to expand...
Click to collapse
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.
sawan.aware.1 said:
Dude follow guide in forum of galaxy core. Cwm is ported for galaxy core amd I am using cwm. It's yet not available in list.
Click to expand...
Click to collapse
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you
trelozakinthinos said:
Sorry my friend but I do not understant this. What it means ported?
I downloaded but when i try to find my phone on the list i can't! so I can't use it. Right?
Where exavtly in the galaxy core forum? Give me a link please!
Thank you
Click to expand...
Click to collapse
Here is the link where you can find cwm for galaxy core and its working. The issues are also discussed.
http://forum.xda-developers.com/showthread.php?t=2517850
1) Remove SD card
2) Boot into CWM Recovery by pressing Power + Volume Up + Home button.
3) Choose "Backup and Restore" and then choose "Backup".
Wait for few minutes and you will get your Nandroid backup in phone's internal memory.
NOTE : You should have enough memory(around 1.8GB - it was in my case) and yup i have got BLACK screen when i did it without removing SD card so i have said remove SD card in the very first step.
I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.
MirXas said:
I have succesfully backed up my phone's ROM without removing the SD CARD, many times. I haven't got any error's afterall.
Personally, I don't recommend backing up to the internal memory, because it's the /data partition, wich oftenly gets wiped (or you wipe it yourself) when flashing a new ROM.
Just some thought.
Click to expand...
Click to collapse
You are right friend but i just told him how to take nandroid backup and that is just a matter of common sense that anyone will transfer the backup either to PC or external SD card.
How big is nandroid backup for Core? (Stock rom)
friendfriend said:
How big is nandroid backup for Core? (Stock rom)
Click to expand...
Click to collapse
Depends on what you have. Mine was over 2GB
1 gb
Sent from my GT-I8260 using XDA Premium 4 mobile app
Depends on how much tada you have in your /data and /system partitions, 'cause all of that is backed up. Mine was from 1 to about 1,5 GB.
Sent from my Lenovo A3000-H using xda app-developers app
mine was 1.8 gb on stock odexed rom
Sent from my GT-I8262 using XDA Premium 4 mobile app
Mine iz 1.7gb.
Hello!
I need enlightenment and help from all of you, I spent hours looking for information and solutions but I wasn't able to find a situation similar to mine, rather small pieces from different scenarios.
Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.
I will try my best to describe the current situation and the solutions that I tried...
Currently, I am able to access fastboot and ADB sideload., even able to flash the recovery. The problem lies with not being able to install a ROM properly. What I can't do is access TWRP after a reboot, I must first flash it via fastboot in order to be able to access it, then of course it will reset after a reboot. TWRP will just keep being stuck in a loop if I don't go to fastboot. Whenever I try to install a ROM, it will fail not long after due to errors like : "Unable to mount data, system,cache etc."
I tried the following:
-The 'Repair' option in the advanced menu.
-Formatting using the 'ADB shell..." commands (I'm trying to find the correct command, as soon I arrive to my desktop, I'll update this post). What I did noticed is after entering that command, it would return strange characters. According to some posts, it could be some color formatting but I'm not sure.
-'sideloading' recoveries and ROMs.
INFO:
-Bootloader is 10.6.1.14.10
-Recovery is TWRP 2.8.6.0
From what I read, my guess is to correct the partition errors. Any tips on how to achieve this?
Could this be fixed by flashing a new bootloader or would it make it worse? I don't want to risk it further until I get some professional advice
Any assistance is greatly appreciated, Thank you all!
razgrizpr said:
Hello!
Here's my situation:
After installing lj50036's pre-nightly OmniROM and setting it up, I decided to reboot and "clean" it. My BIG mistake was that for some reason (probably sleep-deprivation effects) I thought that doing a format in TWRP was a good idea...yeah, messed up.
Click to expand...
Click to collapse
Why was doing a format a BIG mistake ???
Thx Josh
lj50036 said:
Why was doing a format a BIG mistake ???
Thx Josh
Click to expand...
Click to collapse
Doesn't formatting via TWRP erase all the data including the OS?
razgrizpr said:
Doesn't formatting via TWRP erase all the data including the OS?
Click to expand...
Click to collapse
Depends what partitions you formatted. The OS is in /system; your data is in /data.
_that said:
Depends what partitions you formatted. The OS is in /system; your data is in /data.
Click to expand...
Click to collapse
Makes sense. So I guess I erased them all? I honestly don't know since I left it formatting and returned a few hours later only to find it turned off. When I booted it, I experienced the mentioned issues. Battery was full as well. So maybe something went wrong during the formatting?
Is there a way to diagnose the partitions?
Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
berndblb said:
Did you try this?
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.
Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.
razgrizpr said:
Yes, I tried that. Upon entering 'make_ext4fs /dev/block/mmcblk0p8' I get the message 'Need size of file system'.
Found a similar thread where the issue was not being able to mount /data. It appears that for some people 'this' helped them although I'm not sure if I should try it. Others have mentioned 'downgrading' the bootloader and then go through all the process again with success.
Click to expand...
Click to collapse
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
lj50036 said:
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
Click to expand...
Click to collapse
Thank you lj50036, I'm at work at the moment so I will try that as soon I get home and report back.
lj50036 said:
From recovery run this and post the output ....
Code:
adb pull /proc/partitions
You will get a file called 'partitions' in the current directory.....
Thx Josh
Click to expand...
Click to collapse
Here are the results:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 24901600 mmcblk1p1
razgrizpr said:
Here are the results:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 24901600 mmcblk1p1
Click to expand...
Click to collapse
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
That is what it should look like ....
So if you still have fastboot flash the pt.blob will give you these partition back ....
After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...
Thx Josh
lj50036 said:
Code:
major minor #blocks name
179 0 31039488 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 28924416 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
That is what it should look like ....
So if you still have fastboot flash the pt.blob will give you these partition back ....
After you flash the pt.blob boot back into recovery and run the same command and see it matches mine ...
Thx Josh
Click to expand...
Click to collapse
Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!
razgrizpr said:
Thank you so much lj50036!
Looks like correcting the partitions did the trick. After flashing the file, I managed to flash the ROM successfully.
All is good now, thank you all!
Click to expand...
Click to collapse
Great to see you up and running ....
Can you add 'SOLVED' to the thread tittle ...... :good:
Thx Josh