Third, what does this have to do with partitions in a thread that is two years old?
[REF] Skyrocket Partition Info
- Thread starter cschmitt
- Start date
Third, what does this have to do with partitions in a thread that is two years old?
I gave up hope that society would become intelligent enough to find relevant topics, now I'm just answering sometime with questions.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Sorry for posting in this topic. I know that this thread is not about bricked phones. But I really don't know where to write about my problem and if it's even worth to write. I'll try to make separate question about my issue.
There are lots of threads that *are* about bricked phones, you might want to try there, or start a new one.
This partition info would help in creating a pit. with more storage space for apps and rom espercially since lollipop is just around the corner and uses art runtime, which means less app compared to dalvik runtime........would look into it when i have the time. I personally do not own this phone but my elder brother does.
Actually thinking of getting this phone.
Actually thinking of getting this phone.
Phatboyj420
Senior Member
@cschmitt
Dear sir,
Can You please clarify the following for me
Here
You say to properly b-up/restore EFS You need " mmcblk0p18 --Through-- mmcblk0p21 "
where above it shows " mmcblk0p14 " as being the EFS.img
Also in another post of yours I read something about finding efs1-3.bin files in a nandroid Backup to restore EFS how do these correlate to the above partition table
I only ask all of this because one of my two SkyRockets has a Zeroed out IMEI on the latest SlimRom
and I'm doing my research in preparation to fix it.
I do have a 10mb efs.img I found in my Clockworkmod folder in a subfolder called .efsbackup but I want to make sure I flash it to the proper location before I proceed
In a worst case scenario is it safe to copy partitions from one SkyRocket to another if so what Partitions are/aren't safe to copy I would assume the EFS partition is one that is not safe as it contains IMEI but thats only my assumption
That being said a list of partitions that can be safely transferred device-to-device "given they are the same device" would be very helpful also
Sorry I know there are several ?'s Here I hope I made it clear what it is I'm asking
Any assistance is greatly appreciated
Last edited:
@raptorddd I used the new reparation pit file in t989 site and decided to try sultans cm12.1 ROM on it, it work perfectly. Thought you might like to know.
Similar threads
- Sticky
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
21Have 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/sdcard5System 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.11
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.1
