I've seen a lot of stuff using 'dd' but nothing that uses that for backuping the entire phone.
When I connect my phone I see both the external SDcard and the internal and just to be sure to take the correct one I pull the external out,
unless you know by its size, can I use this: (this assumes that /dev/sdb is the internal SDcard)
Code:
dd if=/dev/sdb of=/some/place/phone.image bs=4096 conv=notrunc,noerror
and later use that for a total recovery?
I've done this for lots of my Linux systems even just to backup some partitions (but then sdbN...)
but never on a phone and since it's Linux based....
//B52
Of course you can backup using dd, I suggest though that you do partitions seperately since restoring a single image be problematic if possible since some partitions are hidden and writing to the bootloader partitions is not a good idea incase of problems
Here is a list of the partitions with names.
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
The ones I suggest backing up are:
EFS this is a must and the most important without it your phone could be unusable if the files become corrupt and you don't have a backup
DATAFS is user data
FACTORYFS is the system partition
HIDDEN if you are on Jelly Bean this adds to and extends the system partition
UMS is your internal sdcard (probably better ways to backup then a dd)
Even if you backup don't restore the SBL partitions since if something goes wrong it will screw your phone and they are not damaged if your phone boots at all if they get damaged you will be paying to get your phone jtaged
One thing though, since this is not under /dev/sdX, is it possible to use dd on these /dev/block/ ?
Never done that before and what is the difference between a block and a device?
Related
I flashed a I9100 firmware on my I9100M on bell and now I don't have the M on the bootlogo anymore. Also, the bell stock download mode start directly to downloading, but now it ask for downloading or cancel with volume up/down.
Does anybody have a way to fix this (like have the original boot.bin, sbl.bin and param.lfs from bell firmware I9100MUGKG2) because I downloaded the original firmware and these files are not included.
If you have a rooted I9100M running stock firmware, use this step and upload me the file please:
adb shell
$ su
# dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
But if you have all the file I ask (if you did a nandroid backup with CWM before upgrading or modding the phone), please upload for me.
I need warranty and now my phone isn't stock.
Thankx
Download full stock rom from Samfirmware.com & extract the files yourself.
NLSGS2beast said:
I flashed a I9100 firmware on my I9100M on bell and now I don't have the M on the bootlogo anymore. Also, the bell stock download mode start directly to downloading, but now it ask for downloading or cancel with volume up/down.
Does anybody have a way to fix this (like have the original boot.bin, sbl.bin and param.lfs from bell firmware I9100MUGKG2) because I downloaded the original firmware and these files are not included.
If you have a rooted I9100M running stock firmware, use this step and upload me the file please:
adb shell
$ su
# dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
But if you have all the file I ask (if you did a nandroid backup with CWM before upgrading or modding the phone), please upload for me.
I need warranty and now my phone isn't stock.
Thankx
Click to expand...
Click to collapse
I too have a simular problem, I dont need to send it in for warranty but am wanting to get the Sbl.bin file and param.lfs for Bell Canada's GT-i9100M phone, I downloaded the old GB KG2 FM and also have the new ICS LD3 FM and none contain the Sbl.bin file or the param.lfs that Bell uses.
I have access to another i9100M that has not been changed with anything custom, does anyone know of a way that I can get the Sbl.bin data and how to get the param.lfs off of another phone?.
Thank you.
OK I think I figured this out, I found out the partitions to backup by listing them by name
Code:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Then I just did a dd on partitions 2 and 3 I didn't do the param because I have modified my boot logo and know enough from changing it before Hellcats easy app to know it is not specific to the phone since it has all variant logos at the same time and it shows the correct one by file name.
shadowofdarkness said:
OK I think I figured this out, I found out the partitions to backup by listing them by name
Code:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Then I just did a dd on partitions 2 and 3 I didn't do the param because I have modified my boot logo and know enough from changing it before Hellcats easy app to know it is not specific to the phone since it has all variant logos at the same time and it shows the correct one by file name.
Click to expand...
Click to collapse
Lol I was on the toliet and found the directory too, I already found out that the MMCBLK's where the data to dump and was cross refernceing from PIT file information, but then low and behold looking by name confirmed for sure which one, however how did you extract the exact data from those mmcblocks? , when I do a data partition dump, it dumps the whole partition so for example the param.lfs partition is 8MBs, how were you able to access the specific data and convert it/get it out of those blocks?, I will need to repeat this process on my family members phone so that I can get the param file, also how did you tar them up so that they are Odin flash-able?.
Also will it be fine to flash both sbl 1 and 2 bins just as they are and will Odin properly flash them in the correct sections? or should I just use sbl1 to be safe and rename it to sbl.bin ?(since that is how it comes in firmware packages etc)
In my picture here I was using Yaffs Explorer app but the options are very limiting.
dbzgod said:
Lol I was on the toliet and found the directory too, I already found out that the MMCBLK's where the data to dump and was cross refernceing from PIT file information, but then low and behold looking by name confirmed for sure which one, however how did you extract the exact data from those mmcblocks? , when I do a data partition dump, it dumps the whole partition so for example the param.lfs partition is 8MBs, how were you able to access the specific data and convert it/get it out of those blocks?, I will need to repeat this process on my family members phone so that I can get the param file, also how did you tar them up so that they are Odin flash-able?.
Also will it be fine to flash both sbl 1 and 2 bins just as they are and will Odin properly flash them in the correct sections? or should I just use sbl1 to be safe and rename it to sbl.bin ?(since that is how it comes in firmware packages etc)
In my picture here I was using Yaffs Explorer app but the options are very limiting.
Click to expand...
Click to collapse
I didn't do anything special and those should be entire partition images. I doubt that tar is Odin flashable since the filenames will be off. I just put them in a tar.bz2 by right clicking the files on my Desktop and selecting compress since xda wouldn't allow me to attach bin files
shadowofdarkness said:
I didn't do anything special and those should be entire partition images. I doubt that tar is Odin flashable since the filenames will be off. I just put them in a tar.bz2 by right clicking the files on my Desktop and selecting compress since xda wouldn't allow me to attach bin files
Click to expand...
Click to collapse
Ah okay, yeah thats what I was able to do as well just got copys of the partitions from 2 ways, one was using the partition raw dump that makes a .raw file from within Yaffs Explorer, and the second was just using the shell cmds
dd if=/dev/block/mmcblk0p4 of=/sdcard/param.lfs
dd if=/dev/block/mmcblk0p2 of=/sdcard/Sb1l.bin
dd if=/dev/block/mmcblk0p3 of=/sdcard/Sbl2.bin
So now im thinking that they probably arnt Odin flash-able and what I will half to do is just:
dd if=/sdcard/param.lfs of=/dev/block/mmcblk0p4 to copy them over? or would that be bad/corrupt the the mmc partitions?
The raw data dumps from Yaffs Explorer makes them just to be their names mmcblk0p4.raw so would it be better to just use those raw dumps instead when copying over to the dev/block section?
My intention is to list all physical partitions of /dev/block/mmcblk0 but outputs the following:
Code:
# fdisk -l /dev/block/mmcblk0
sh: fdisk: not found
Any idea about how to install such fdisk, cfdisk, parted or alternative command? Apparently it is not shipped by default.
Note: Superuser is installed.
{
"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"
}
Hey! At least you made it on the right for part of the site!
Sent from my GT-I9100 using xda premium
Use busybox.
scandiun said:
My intention is to list all physical partitions of /dev/block/mmcblk0 but outputs the following:
Code:
# fdisk -l /dev/block/mmcblk0
sh: fdisk: not found
Any idea about how to install such fdisk, cfdisk, parted or alternative command? Apparently it is not shipped by default.
Note: Superuser is installed.
Click to expand...
Click to collapse
Do you have busybox installed?
EDIT: WAIT.
You said above:
My intention is to list all physical partitions of /dev/block/mmcblk0
Click to expand...
Click to collapse
Are you sure you want to use fdisk? Maybe you should read what fdisk does...
ctomgee said:
Do you have busybox installed?
EDIT: WAIT.
You said above:
Are you sure you want to use fdisk? Maybe you should read what fdisk does...
Click to expand...
Click to collapse
I had fdisk installed, but was version 1.17.1 which hadn't the fdisk applet. now I've got the BusyBox Pro 1.20.0 from market and does have it, just what I needed.
However, I haven't found what I am looking for. There seems to be only one partition, while I am looking for all the ones corresponding to efs, data, system, misc, boot, recovery and so on. Any ideas on that?
And yes, I used fdisk before on linux and cfdisk on freebsd so I feel quite comfortable with it.
scandiun said:
I had fdisk installed, but was version 1.17.1 which hadn't the fdisk applet. now I've got the BusyBox Pro 1.20.0 from market and does have it, just what I needed.
However, I haven't found what I am looking for. There seems to be only one partition, while I am looking for all the ones corresponding to efs, data, system, misc, boot, recovery and so on. Any ideas on that?
And yes, I used fdisk before on linux and cfdisk on freebsd so I feel quite comfortable with it.
Click to expand...
Click to collapse
Sorry, I missed the -l flag in your image, and for some reason I didn't process what you were looking for exactly.
Use the "df" command.
What are you trying to figure out exactly? Just a list of the partitions or sizes or something else...
Here is a list of the partitions and what they are used for
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
shadowofdarkness said:
What are you trying to figure out exactly? Just a list of the partitions or sizes or something else...
Here is a list of the partitions and what they are used for
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
That is what I was looking for. As i see, there is no such /misc partition.
scandiun said:
That is what I was looking for. As i see, there is no such /misc partition.
Click to expand...
Click to collapse
I have seen people using the normally unused partition 12 on /misc to hide files or just as extra space.
shadowofdarkness said:
I have seen people using the normally unused partition 12 on /misc to hide files or just as extra space.
Click to expand...
Click to collapse
Is there where linux/ubuntu is installed with some market installers?
How to get the size (dynamic, I mean kB, MB, etc) of all partitions? Why partitions won't shop up in mmcblk0 directly?
scandiun said:
How to get the size (dynamic, I mean kB, MB, etc) of all partitions? Why partitions won't shop up in mmcblk0 directly?
Click to expand...
Click to collapse
Use df:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
Is it possible to restore a damaged device partition (eg. from below list) (eg : /dev/block/mmcblk0p8) using a backup from another working phone ?
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
is the content of the partition different on each s2 phone ?
If we create a backup with following command :
[dd if=/dev/block/mmcblk0p8 of=/sdcard/phonebackup/mmcblk0p8.img bs=4096]
and restore in similar way,is there a risk of bricking the phone ?
This partition apparently holds the IMEI (well on the Moto G 2013 it does) but I don't even see that it exists on this phone (xt1527). I can't seem to make a backup of it but the phone works so, is it even there or have they changed how it works?
bump, same issue
seems a bunch of us have this issue.
sad there seems to be no answer anywhere..
edit:
here is what i got listing partitions.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-06-10 11:47 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-10 11:47 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-10 11:47 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-10 11:47 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-10 11:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-10 11:47 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-10 11:47 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-10 11:47 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-10 11:47 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-10 11:47 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-10 11:47 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-10 11:47 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-10 11:47 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-10 11:47 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-10 11:47 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-10 11:47 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-10 11:47 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-10 11:47 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-10 11:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-10 11:47 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-10 11:47 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-10 11:47 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-10 11:47 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-10 11:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-10 11:47 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-10 11:47 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-10 11:47 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-10 11:47 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-10 11:47 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-10 11:47 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-10 11:47 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-10 11:47 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-10 11:47 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-10 11:47 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-10 11:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-10 11:47 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-10 11:47 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-10 11:47 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-10 11:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-10 11:47 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-10 11:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-10 11:47 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-10 11:47 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-10 11:47 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_umts:/ #
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
conductive said:
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
Click to expand...
Click to collapse
on another phone it's mmcblk12 (i have been doing a LOT of searching on this)
i looked at the root folder on my phone and i see a shortcut to "pds"
when i open it it's empty.
i have some experience with Linux but i am no pro and it's been a while for my nix activity.
and i have almost no experience with Android.
i am good with computer stuff though. cracking, coding reversing, graphics etc.
i love modding everything i can.
i say that to give a bit of context to this..
if anyone else has any idea or leads on what i can do or where to look i am all ears.
i posted that partition command because i found it on Google
and i remember using it (ls) before trouble shooting driver issues on Linux in the past.
you guys will notice the console log i posted does not list a pds partition by-name..
is it because it's not mounted maybe ? or is it using a different name on this phone ?
i'd love to try and update to 5.1 (from 5.0..2) on my Telus XT1527 but i think it's time i make a PDS backup before i carry on any further.. so far i have installed a custom kernel and TWRP + root.
So i can't continue until i figure out a way to back that stuff up (irresponsible otherwise i think)
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
conductive said:
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
Click to expand...
Click to collapse
That says Atrix though and on another posting i found it was mmcblk0p12
If you look at the log i posted earlier that number mmcblk0p3 is mapped to DDR
I have been dumping the partitions and checking them (if the file size is roughly correct)
I heard it was suppose to be about 8mb as an .img on another device.
and i have one downloaded as an image and extracted (some other guys data)
so if i find the files on my phone i think i can match them to my downloaded files.
i also got a windows tool to extract the images ready..
One last thing i said i seen a shortcut to "pds" on the filesystem of my Telus XT1527
so i take it that it's there just that i can't see it or something.
I'm basically poking around in the dark LOL
edit:
oh and i seen on other phones that pds partition can be backed up with TWRP.
The TWRP i have installed does not show it for me (i am using Squid's TWRP)
The partitions are probably associated with the OS version and not the hardware so you should probably compare your version to a similar version.
If you can find fstab file you should be able to (cat fstab) and see what the partitions are mounted as.
The partition should be mounted or else your device will not work.
I've modded fstab on linux before but i am not finding it i think on the XT1527
found a couple with "fstab" in the title and it don't say much..
just one line about mounting the sdcard.
Thanks but i am lost.. i wonder how it's created because it's prob not files in the Firmware package right ?
So then i'd have to assume the contents of PDS would be created on the phones first boot maybe.
i don't know what else to do really i am going around in circles ..i might just say screw it and give up.
too bad guys here who DO have the ability to find it can't help
100% of Moto-E users seem to carry on flashing their phones with out it
so i take it backing up the PDS is pointless ?
Just kind of dumb i see tutorials on how to do it all over but no one can claim it actually works LOL
If you google it you will see what i am saying (people tell you to you to do it becuase it's sooooo important..
then it doesn't work ahahaha
thanks for your help conductive.
edit:
Oh and guys.. i tried to do this because... Q13:
http://forum.xda-developers.com/moto-e-2015/help/faq-frequently-questions-moto-e-2015-t3044929
The stickied topic here tells us all how to do it.
..but did anyone at all bother to verify it actually works ?
Ok so i think i got it.. sort of.
I installed "Root Explorer Pro" and when i opened it this time it showed files/folders.
I then selected .zip it up and copied it manually to my sdcard then to my PC.
I have been hex viewing the contents with UltraEdit and the files contain data.
I also compared to a pds dump from an Atrix and they are some what similar.
I did see a reference in one of the root config files about the pds partition though..
I can't recall which file it was but it said something about
setting the dummy directory "pds" as persistent.
I don't know what is going on but i got the content off the phone i think.
edit:
Here is what the root of that folder looked like (folder names)
Code:
.bt_nv.bin
batt_health
bt
camera
data
factory
lost+found
public
security
WCNSS_wlan_dictionary.dat
wifi
wmdrm
Hello!
I have an off-brand (PumpkinX) Android 5.1 tablet that freezes at the Intel logo screen during boot. I can still get into Fastboot and recovery. The tablet identifies itself in fastboot as inet_w I101B. The serial number starts with Baytrail. When booting, the PumpkinX logo appears, then the Intel logo, at which point the tablet freezes.
Long story short...after several months of operation, some kind of corruption happens, and the tablet will not boot. The first one was replaced by the vendor. And the second one has now done the same thing. I have a logcat (attached) of what happens. In summary, the tablet starts throwing
Code:
E/EM FG ALGO Iface:(xxx): Failed to get File Descriptor
errors shortly after boot, and does this until it is turned off. I am trying to understand what is going on, so I can fix the problem myself.
When I got the second tablet, I made images of all the partitions, so if a partition is bad, I can restore it. What I am trying to figure out is which partition might be corrupted, and I am hoping that someone could look at the logcat and make a guess as to what point in the boot process this happens and what has been corrupted. The partition layout is as follows:
Code:
[email protected]_w:/ # ls -l /dev/block/platform/80860F14:00/by-name
lrwxrwxrwx root root 2016-09-10 17:12 ESP -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-09-10 17:12 boot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-09-10 17:12 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-09-10 17:12 config -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-09-10 17:12 data -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-09-10 17:12 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-09-10 17:12 fastboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-09-10 17:12 logs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-09-10 17:12 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-09-10 17:12 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-09-10 17:12 persistent -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-09-10 17:12 recovery -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-09-10 17:12 system -> /dev/block/mmcblk0p12
Thanks for any help!
Bump...still looking for some insight/help! Thanks!