[Q] Phone does not boot after symbolic link fonts files - Huawei Ideos X5 U8800

When I symbolic linked /system/fonts/DroidSans-Bold.ttf and /system/fonts/DroidSans.ttf to /HWUserData/fonts/simsun.ttc, the phone can reboot successfully, and I can see the default fonts are changed as expected:
Code:
# This one is still working
sh-4.2# ls -l
ls -l
total 5536
-rw-r--r-- 1 0 0 6880 Dec 3 10:11 Clockopia.ttf
lrwxrwxrwx 1 0 0 28 Dec 22 01:48 DroidSans-Bold.ttf -> /HWUserData/fonts/simsun.ttc
-rw-r--r-- 1 0 0 194488 Dec 3 10:11 DroidSans-Bold.ttf.bak
lrwxrwxrwx 1 0 0 28 Dec 22 01:43 DroidSans.ttf -> /HWUserData/fonts/simsun.ttc
-rw-r--r-- 1 0 0 190776 Dec 3 10:11 DroidSans.ttf.bak
-rw-r--r-- 1 0 0 622280 Dec 3 10:11 DroidSansArabic.ttf
-rw-r--r-- 1 0 0 3725920 Dec 3 10:11 DroidSansFallback.ttf
-rw-r--r-- 1 0 0 23076 Dec 3 10:11 DroidSansHebrew.ttf
-rw-r--r-- 1 0 0 119380 Dec 3 10:11 DroidSansMono.ttf
-rw-r--r-- 1 0 0 36028 Dec 3 10:11 DroidSansThai.ttf
-rw-r--r-- 1 0 0 185228 Dec 3 10:11 DroidSerif-Bold.ttf
-rw-r--r-- 1 0 0 190304 Dec 3 10:11 DroidSerif-BoldItalic.ttf
-rw-r--r-- 1 0 0 177560 Dec 3 10:11 DroidSerif-Italic.ttf
-rw-r--r-- 1 0 0 172916 Dec 3 10:11 DroidSerif-Regular.ttf
lrwxrwxrwx 1 0 0 26 Dec 21 10:31 msyh.ttc -> /HWUserData/fonts/msyh.ttc
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 msyhbd.ttc -> /HWUserData/fonts/msyhbd.ttc
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 simhei.ttf -> /HWUserData/fonts/simhei.ttf
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 simsun.ttc -> /HWUserData/fonts/simsun.ttc
Then, I symbolic linked all fonts to /HWUserData/fonts/***, reboot, phone is stucked at Huawei logo screen:
Code:
sh-4.2# ls -l
# This one make the phone can't boot
ls -l
total 5536
-rw-r--r-- 1 0 0 6880 Dec 3 10:11 Clockopia.ttf
lrwxrwxrwx 1 0 0 10 Dec 22 02:16 DroidSans-Bold.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 194488 Dec 3 10:11 DroidSans-Bold.ttf.bak
lrwxrwxrwx 1 0 0 10 Dec 22 02:16 DroidSans.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 190776 Dec 3 10:11 DroidSans.ttf.bak
lrwxrwxrwx 1 0 0 8 Dec 22 02:17 DroidSansArabic.ttf -> msyh.ttc
-rw-r--r-- 1 0 0 622280 Dec 3 10:11 DroidSansArabic.ttf.bak
lrwxrwxrwx 1 0 0 8 Dec 22 02:19 DroidSansFallback.ttf -> msyh.ttc
-rw-r--r-- 1 0 0 3725920 Dec 3 10:11 DroidSansFallback.ttf.bak
lrwxrwxrwx 1 0 0 8 Dec 22 02:19 DroidSansHebrew.ttf -> msyh.ttc
-rw-r--r-- 1 0 0 23076 Dec 3 10:11 DroidSansHebrew.ttf.bak
lrwxrwxrwx 1 0 0 8 Dec 22 02:19 DroidSansMono.ttf -> msyh.ttc
-rw-r--r-- 1 0 0 119380 Dec 3 10:11 DroidSansMono.ttf.bak
lrwxrwxrwx 1 0 0 8 Dec 22 02:19 DroidSansThai.ttf -> msyh.ttc
-rw-r--r-- 1 0 0 36028 Dec 3 10:11 DroidSansThai.ttf.bak
lrwxrwxrwx 1 0 0 10 Dec 22 02:14 DroidSerif-Bold.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 185228 Dec 3 10:11 DroidSerif-Bold.ttf.bak
lrwxrwxrwx 1 0 0 10 Dec 22 02:14 DroidSerif-BoldItalic.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 190304 Dec 3 10:11 DroidSerif-BoldItalic.ttf.bak
lrwxrwxrwx 1 0 0 10 Dec 22 02:15 DroidSerif-Italic.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 177560 Dec 3 10:11 DroidSerif-Italic.ttf.bak
lrwxrwxrwx 1 0 0 10 Dec 22 02:13 DroidSerif-Regular.ttf -> simsun.ttc
-rw-r--r-- 1 0 0 172916 Dec 3 10:11 DroidSerif-Regular.ttf.bak
lrwxrwxrwx 1 0 0 26 Dec 21 10:31 msyh.ttc -> /HWUserData/fonts/msyh.ttc
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 msyhbd.ttc -> /HWUserData/fonts/msyhbd.ttc
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 simhei.ttf -> /HWUserData/fonts/simhei.ttf
lrwxrwxrwx 1 0 0 28 Dec 21 10:31 simsun.ttc -> /HWUserData/fonts/simsun.ttc
I can use 'adb' to get shell, but 'su' command failed with "Segmentation fault", so I can't undo these symbolic links.
'adb logcat' show a lot of logs which I don't understand it: pastebin.com/a3Ar1XvK
Any chance to revive this phone?

well,i have to reupgrade ROM to bring it back, some data are lost
Sent from my U8800 using XDA App

You should make backup before you do something major to your device.
Recovery backup saves your time.

Related

[help] 32A cant mount SD card

Hi Guys
I recently tried to upgrade my radio and SPL to use Cursors32A rom. It update failed and cannot seem to get the SD card to mount in recovery mode again
When i try to mount/use the card it come up with the following error
Code:
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or director
y
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
Now ive been going through the forums over the last two days trying to fix it. The one method that stands out to me is the gold card method..but i cant seem to obtain the CID.
Now my knowledge of the andriod/unix enviroment is limited(i was brain washed my M$)
anyway please help a n00b
Thanks
Kyle
Hi,
What is your current SPL?
Does fastboot works ?
a command like fastboot boot recovery-RA-sapphire-v1.5.2H.img works ?
Cedric
Fastboot won't work for him, no eng spl. Did you try another SD card? I know it's a simple question but double check if it's working. I remember another command available that helps mount your SD card but I forgot the command. Try searching the forums more, I'm sure you'll be able to find it.
If I remember correctly, your SPL + Radio don't match up. I've never seen that together before. Lucky it isn't bricked yet
The command is fastboot oem enableqxdm 0
the prompt returns 'OKAY'.
Hey guys
i tried 6 different sdcards
d_ced, when i run the below command i get
Code:
c:\android\android-sdk-windows\tools>fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
ill post my ls -l for reference
Code:
drwxrwxrwx 1 0 0 2048 Sep 6 1980 cache
drwxr-xr-x 2 1000 1000 0 Jan 1 1970 data
-rwxr-xr-x 1 1000 1000 2733 Jan 1 1970 default.prop
drwxr-xr-x 11 0 0 1300 Jan 6 00:07 dev
drwxr-xr-x 2 1000 1000 0 Jan 1 1970 etc
-rwxr-xr-x 1 1000 1000 106764 Jan 1 1970 init
-rwxr-xr-x 1 1000 1000 1677 Jan 1 1970 init.goldfish.rc
-rwxr-xr-x 1 1000 1000 2781 Jan 1 1970 init.hero.rc
-rwxr-xr-x 1 1000 1000 598 Jan 1 1970 init.rc
dr-xr-xr-x 42 0 0 0 Jan 1 1970 proc
drwxr-xr-x 3 1000 1000 0 Jan 1 1970 res
drwx------ 2 0 0 0 Jan 1 1970 root
drwxr-x--- 2 1000 1000 0 Jan 6 00:07 sbin
drwxr-xr-x 2 0 0 0 Jan 6 00:07 sdcard
drwxr-xr-x 15 0 0 0 Jan 1 1970 sys
drwxr-xr-x 3 1000 1000 0 Jan 1 1970 system
drwxr-xr-x 2 1000 1000 0 Jan 6 00:07 tmp/CODE]
also i have not tried the goldcard method but i cannot get the CID of the device
thanks in advance guys!
Thanks
Kyle
well guys i tried following the instructions of /forum.xda-developers.com/showthread.php?t=639107&page=5 and i bricked it...it just sits at the HTC magic screen :/
oh well thanks in advance!

[help neded] I need a dump of a /dev/ on a stock captivate rooted

Hello guys,
Can you please post a ls -al /dev/block/
and if you can provide a .tar.gz of the entire thing.
Thanks!
how do I do this on droid explorer, I tried opening the folder with usb debug on, but it won't open.
Hello,
You need root.
Code:
adb shell
su
cd /dev/block/
ls -al
I already did this somewhere around the forum, likely in one of the lagfix threads...
max_warheads said:
I already did this somewhere around the forum, likely in one of the lagfix threads...
Click to expand...
Click to collapse
I did a quick search. Please post here.
Thanks!
Code:
bash-4.1# ls -al /dev/block
total 0
drwxr-xr-x 3 0 0 1360 Aug 21 06:48 .
drwxr-xr-x 10 0 0 13580 Aug 21 06:48 ..
brw------- 1 0 0 137, 0 Aug 21 06:48 bml0!c
brw------- 1 0 0 137, 1 Aug 21 06:48 bml1
brw------- 1 0 0 137, 10 Aug 21 06:48 bml10
brw------- 1 0 0 137, 11 Aug 21 06:48 bml11
brw-r--r-- 1 0 0 137, 12 Aug 21 06:48 bml12
brw------- 1 0 0 137, 2 Aug 21 06:48 bml2
brw------- 1 0 0 137, 3 Aug 21 06:48 bml3
brw------- 1 0 0 137, 4 Aug 21 06:48 bml4
brw------- 1 0 0 137, 5 Aug 21 06:48 bml5
brw------- 1 0 0 137, 6 Aug 21 06:48 bml6
brw------- 1 0 0 137, 7 Aug 21 06:48 bml7
brw------- 1 0 0 137, 8 Aug 21 06:48 bml8
brw------- 1 0 0 137, 9 Aug 21 06:48 bml9
brw------- 1 0 0 7, 0 Aug 21 06:48 loop0
brw------- 1 0 0 7, 1 Aug 21 06:48 loop1
brw------- 1 0 0 7, 2 Aug 21 06:48 loop2
brw------- 1 0 0 7, 3 Aug 21 06:48 loop3
brw------- 1 0 0 7, 4 Aug 21 06:48 loop4
brw------- 1 0 0 7, 5 Aug 21 06:48 loop5
brw------- 1 0 0 7, 6 Aug 21 06:48 loop6
brw------- 1 0 0 7, 7 Aug 21 06:48 loop7
brw------- 1 0 0 179, 0 Aug 21 06:48 mmcblk0
brw------- 1 0 0 179, 1 Aug 21 06:48 mmcblk0p1
brw------- 1 0 0 179, 2 Aug 21 06:48 mmcblk0p2
brw------- 1 0 0 1, 0 Aug 21 06:48 ram0
brw------- 1 0 0 1, 1 Aug 21 06:48 ram1
brw------- 1 0 0 1, 10 Aug 21 06:48 ram10
brw------- 1 0 0 1, 11 Aug 21 06:48 ram11
brw------- 1 0 0 1, 12 Aug 21 06:48 ram12
brw------- 1 0 0 1, 13 Aug 21 06:48 ram13
brw------- 1 0 0 1, 14 Aug 21 06:48 ram14
brw------- 1 0 0 1, 15 Aug 21 06:48 ram15
brw------- 1 0 0 1, 2 Aug 21 06:48 ram2
brw------- 1 0 0 1, 3 Aug 21 06:48 ram3
brw------- 1 0 0 1, 4 Aug 21 06:48 ram4
brw------- 1 0 0 1, 5 Aug 21 06:48 ram5
brw------- 1 0 0 1, 6 Aug 21 06:48 ram6
brw------- 1 0 0 1, 7 Aug 21 06:48 ram7
brw------- 1 0 0 1, 8 Aug 21 06:48 ram8
brw------- 1 0 0 1, 9 Aug 21 06:48 ram9
brw------- 1 0 0 138, 1 Aug 21 06:48 stl1
brw------- 1 0 0 138, 10 Aug 21 06:48 stl10
brw------- 1 0 0 138, 11 Aug 21 06:48 stl11
brw------- 1 0 0 138, 12 Aug 21 06:48 stl12
brw------- 1 0 0 138, 2 Aug 21 06:48 stl2
brw------- 1 0 0 138, 3 Aug 21 06:48 stl3
brw------- 1 0 0 138, 4 Aug 21 06:48 stl4
brw------- 1 0 0 138, 5 Aug 21 06:48 stl5
brw------- 1 0 0 138, 6 Aug 21 06:48 stl6
brw------- 1 0 0 138, 7 Aug 21 06:48 stl7
brw------- 1 0 0 138, 8 Aug 21 06:48 stl8
brw------- 1 0 0 138, 9 Aug 21 06:48 stl9
brw------- 1 0 0 139, 0 Aug 21 06:48 tfsr0!c
brw------- 1 0 0 139, 1 Aug 21 06:48 tfsr1
brw------- 1 0 0 139, 10 Aug 21 06:48 tfsr10
brw------- 1 0 0 139, 11 Aug 21 06:48 tfsr11
brw------- 1 0 0 139, 12 Aug 21 06:48 tfsr12
brw------- 1 0 0 139, 2 Aug 21 06:48 tfsr2
brw------- 1 0 0 139, 3 Aug 21 06:48 tfsr3
brw------- 1 0 0 139, 4 Aug 21 06:48 tfsr4
brw------- 1 0 0 139, 5 Aug 21 06:48 tfsr5
brw------- 1 0 0 139, 6 Aug 21 06:48 tfsr6
brw------- 1 0 0 139, 7 Aug 21 06:48 tfsr7
brw------- 1 0 0 139, 8 Aug 21 06:48 tfsr8
brw------- 1 0 0 139, 9 Aug 21 06:48 tfsr9
drwxr-xr-x 2 0 0 100 Aug 21 06:48 vold
bash-4.1#
Actually, sorry, that was for the JH2 ROM.

[Q] multiboot: whats happening?

It happened to me twice now... not sure what the heck is happening here...
I have CM7.2 installed as primary and CM9 as secondary with multiboot.
Things were running just fine in both ROMs. But one fine day, when I was booting into CM9, for no apparent reason, I get the welcome to Android thing - the screen you get when you first boot into any ROM. Finding it weird I reboot and go to my primary ROM. There again, I am greeted with the green android.
Thinking that it must be some mistake I did, I promptly restore my backup (generated by my daily backup script - Thank god for that!!). This corrects both the ROMs alright...
Today again, I faced the same thing. Only difference in previous experience and today is that I just resized CM9 images (data/cache and system). Not sure why this would have any impact on the primary ROM...
Does this happen because both ROMs share same .android_secure or something like that? If so, why does this occur randomly and not every time I switch between ROMs?
PS: I know this question really belongs here but can't post it there because of the 10 post rule
the same thing happened to me, many times. I was not able to express it the way you did.
I am posting this thread's link on the concerned thread. Thanx.
P.S.: Enjoy your 1st 'Thanks' on XDA.
brajesh.sharma87 said:
P.s.: Enjoy your 1st 'thanks' on xda.
Click to expand...
Click to collapse
whooohooooooooooooo!!!!!!!!! :d:d:d:d
It looks like multiboot randomly mount real data partition instead of virtual one in fsimages. I have real cm7 and virtual cm9 and when this happened data restore real partition is needed.
Virtual partitions mount
There's script /system/bootmenu/2nd-boot/fshook.edit_devtree.sh in the bootmenu, which replaces real devices with virtual ones from fsimages on sdcard. This script is running twice: from init.hook.rc and 2nd-boot.sh.
I change fshook.edit_devtree.sh to write log on sdcard:
Code:
#### SYSTEM
# setup virtual image as device
losetup /dev/block/loop4 /fshook/mounts/imageSrc/fsimages/system.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p21 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p21 b 7 4 2>> /fshook/mounts/imageSrc/dev.log
######## DATA
# setup virtual image as device
losetup /dev/block/loop6 /fshook/mounts/imageSrc/fsimages/data.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p25 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p25 b 7 6 2>> /fshook/mounts/imageSrc/dev.log
######## CACHE
# setup virtual image as device
losetup /dev/block/loop5 /fshook/mounts/imageSrc/fsimages/cache.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p24 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p24 b 7 5 2>> /fshook/mounts/imageSrc/dev.log
######## PDS
# setup virtual image as device
losetup /dev/block/loop2 /fshook/mounts/imageSrc/fsimages/pds.img 2>> /fshook/mounts/imageSrc/dev.log
rm /dev/block/mmcblk1p7 2>> /fshook/mounts/imageSrc/dev.log
mknod -m 0600 /dev/block/mmcblk1p7 b 7 2 2>> /fshook/mounts/imageSrc/dev.log
ls -l /dev/block/mmcblk1p* >> /fshook/mounts/imageSrc/dev.log
When some of virtual partitions (in this case it was cache) isn't mounted correctly, log file is following:
Code:
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p1
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p10
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p11
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p12
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p13
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p14
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p15
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p16
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p17
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p18
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p19
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p2
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p20
brw------- 1 root root 7, 4 Feb 15 10:10 /dev/block/mmcblk1p21
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p22
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p23
brw------- 1 root root 7, 5 Feb 15 10:10 /dev/block/mmcblk1p24
brw------- 1 root root 7, 6 Feb 15 10:10 /dev/block/mmcblk1p25
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p3
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p4
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p5
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p6
brw------- 1 root root 7, 2 Feb 15 10:10 /dev/block/mmcblk1p7
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p8
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p9
losetup: /dev/block/loop4: No such file or directory
losetup: /dev/block/loop6: No such file or directory
losetup: /dev/block/loop5: No such file or directory
mknod: /dev/block/mmcblk1p24: File exists
losetup: /dev/block/loop2: No such file or directory
brw-rw---- 1 root system 179, 33 Feb 15 10:10 /dev/block/mmcblk1p1
brw------- 1 root root 179, 42 Feb 15 10:10 /dev/block/mmcblk1p10
brw------- 1 root root 179, 43 Feb 15 10:10 /dev/block/mmcblk1p11
brw------- 1 root root 179, 44 Feb 15 10:10 /dev/block/mmcblk1p12
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p13
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p14
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p15
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p16
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p17
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p18
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p19
brw------- 1 root root 179, 34 Feb 15 10:10 /dev/block/mmcblk1p2
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p20
brw------- 1 root root 7, 4 Feb 15 10:10 /dev/block/mmcblk1p21
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p22
brw------- 1 root root 7, 3 Feb 15 10:10 /dev/block/mmcblk1p23
brw------- 1 root root 179, 56 Feb 15 10:10 /dev/block/mmcblk1p24
brw------- 1 root root 7, 6 Feb 15 10:10 /dev/block/mmcblk1p25
brw------- 1 root root 179, 35 Feb 15 10:10 /dev/block/mmcblk1p3
brw------- 1 root root 179, 36 Feb 15 10:10 /dev/block/mmcblk1p4
brw------- 1 root root 179, 37 Feb 15 10:10 /dev/block/mmcblk1p5
brw-rw---- 1 root system 179, 38 Feb 15 10:10 /dev/block/mmcblk1p6
brw------- 1 root root 7, 2 Feb 15 10:10 /dev/block/mmcblk1p7
brw------- 1 root root 179, 40 Feb 15 10:10 /dev/block/mmcblk1p8
brw------- 1 root root 179, 41 Feb 15 10:10 /dev/block/mmcblk1p9
mknod couldn't create mmcblk1p24 device, although it looks like removed without warning before. And in the first run of this script mknod was create mmcblk1p24 correctly.
Most people got problem in multiboot when using CM7.2 as nandroid. You might want to revert back to CM7.1 stable. I'm using it smoothly without any single problem

[HELP] I need pds.img Backup

Hello Everyone,
I found the way to make adb run on a Defy with screwed /pds partition. But of course the OS is not booting. Can somebody help me uploading a backup of your /pds partiton?. I can't found it anywhere Thanks in advance to anyone
EDIT: I don't need anymore ALL the /pds file content, but only the content of opprof folder
TheElix said:
Hello Everyone,
I found the way to make adb run on a Defy with screwed /pds partition. But of course the OS is not booting. Can somebody help me uploading a backup of your /pds partiton?. I can't found it anywhere Thanks in advance to anyone
Click to expand...
Click to collapse
Do you have a reference for what is contained in the /pds partition? Doesn't the /pds partition contain device specific information, maybe including the IMEI which we certainly don't want to share.
See this thread: http://forum.xda-developers.com/showthread.php?t=2675326
craig_comstock said:
Do you have a reference for what is contained in the /pds partition? Doesn't the /pds partition contain device specific information, maybe including the IMEI which we certainly don't want to share.
See this thread: http://forum.xda-developers.com/showthread.php?t=2675326
Click to expand...
Click to collapse
I looked at that thread but I didn't found anything useful.
BTW I found a backup online and now my Defy is booting :laugh: But, of course, the IMEI shows as 0000000000000000000 and doesn't connect to the network
There's the content of my /pds
Code:
[email protected]:/ # ls -lR /pds
/pds:
drwxrwx--- radio radio 2015-10-30 05:17 bp_nvm
drwxrwx--- radio radio 2015-10-28 06:26 comm_drv
drwxr-xr-x root root 1981-12-31 13:00 config
drwxr----- root root 2012-08-29 07:51 factory
-rw-r--r-- root root 507504 2015-10-27 06:11 hijack
drwxrwx--- root root 2015-07-05 05:41 lost+found
drwxr-xr-x root root 2015-10-28 04:21 opprof
drwxrwxr-x system shell 2015-10-27 04:42 public
drwxr-xr-x root radio 2015-07-05 05:41 scim
drwxrwx--- 9007 9007 2015-10-27 06:15 security
-rw-r--r-- root root 260184 2015-10-27 06:11 update-binary
-rw-r--r-- root root 1335532 2015-10-27 06:11 update-recovery.zip
drwxrwx--x wifi wifi 2015-10-27 06:15 wifi
drwxrwxr-x 9003 9003 2015-10-27 06:15 wmdrm
/pds/bp_nvm:
-rw-r--r-- root root 3604 2015-10-27 06:11 FILE_PDS5
-rw-r--r-- root root 1970 2015-10-27 06:11 FILE_PDS_SUBSIDY_LOCK_DBK_1
-rw-r--r-- root root 2406 2015-10-27 06:11 FILE_PDS_SUBSIDY_LOCK_DBK_2
-rw-r--r-- root root 3197 2015-10-28 04:21 File_PDS1
-rw-r--r-- root root 2276 2015-10-27 06:11 File_PDS2
-rw-r--r-- root root 4387 2015-10-28 04:21 File_PDS3
-rw-r--r-- root root 4032 2015-10-28 04:21 File_PDS4
-rw-r--r-- root root 2602 2015-10-27 06:11 File_PDS_IMEI
-rw-r--r-- root root 4482 2015-10-27 06:11 File_PDS_LTE1
-rw-r--r-- root root 6722 2015-10-27 06:11 File_PDS_LTE2
-rw-r--r-- root root 320 2015-10-28 04:21 File_PDS_SBCM
-rw-r--r-- root root 1330 2015-10-30 05:18 File_PDS_Subsidy_Lock
-rw-r--r-- root root 312 2015-10-27 06:11 NVM_Daemon_Log.txt
-rw-rw-rw- root radio 1512 2015-10-28 06:21 NVM_Daemon_MD5
-rw------- root root 32 2012-12-06 08:42 md5
/pds/comm_drv:
-rw-r--r-- root root 1 2015-10-27 06:11 cat_log_control.cfg
-rw-r--r-- root root 1 2015-10-27 06:11 cat_routing_path_control.cfg
-rw-rw-rw- root radio 2704 2015-10-28 06:26 mmins_settings.cfg
-rw-r--r-- root root 1 2015-10-27 06:11 ms_log_control.cfg
-rw-r--r-- root root 61 2015-10-27 06:11 opprof.txt
/pds/config:
-rw-r----- root root 0 1981-12-31 13:00 barcode
-rw-r----- root root 0 1981-12-31 13:00 baseband
-rw-r----- root root 0 2012-12-06 08:41 bootmode
-rw-r----- root root 1 1981-12-31 13:00 boslogcat
-rw-r----- root root 0 1981-12-31 13:00 carrier
-rw-r----- root root 0 1981-12-31 13:00 console
-rw-r----- root root 0 1981-12-31 13:00 display
-rw-r----- root root 0 1981-12-31 13:00 dtname
-rw-r----- root root 0 1981-12-31 13:00 fti
-rw-r----- root root 0 1981-12-31 13:00 hwrev
-rw-r----- root root 0 1981-12-31 13:00 model
-rw-r----- root root 0 1981-12-31 13:00 msn
/pds/factory:
-rw-r----- root root 128 2012-08-29 08:55 fti
/pds/lost+found:
/pds/opprof:
/pds/public:
drwxrwxr-x root root 1981-12-31 13:04 atvc
drwxr-x--- 9000 9000 2015-10-27 06:15 battd
-rw------- root root 5 2012-12-06 08:13 cur.locale
-rw-r--r-- root root 2 2012-08-29 07:58 tcxo.bin
/pds/public/atvc:
/pds/public/battd:
-rw-rw---- root root 10 2015-10-27 06:11 batt_offset_data
-rw-rw---- root root 12 2015-10-27 06:11 batt_phasing_data
-rw-rw---- root root 256 2015-10-27 06:11 batt_tuning_data
/pds/scim:
/pds/security:
-rw-r--r-- root 9007 4096 2015-10-27 06:11 counter.bin
-rw-r--r-- root 9007 5086 2015-10-27 06:11 janusDeviceCert.dat
-rw-rw-r-- root 9007 608 2012-09-24 17:14 keymaptable.dat
-rw-rw-r-- root 9007 110 1981-12-31 13:04 keyring.dat
-rw-r--r-- root 9007 22528 2015-10-27 06:11 system.bin
/pds/wifi:
-rw-r--r-- root root 468 2015-10-27 06:11 nvs_map.bin
-rw-rw---- root root 1113 2012-09-19 07:33 nvs_map_mac80211.bin
/pds/wmdrm:
-rw-r--r-- root root 32 2015-10-27 06:11 hashsdidmap.dat
Are some files missing?
TheElix said:
I looked at that thread but I didn't found anything useful.
BTW I found a backup online and now my Defy is booting :laugh: But, of course, the IMEI shows as 0000000000000000000 and doesn't connect to the network
There's the content of my /pds
Code:
[email protected]:/ # ls -lR /pds
/pds:
drwxrwx--- radio radio 2015-10-30 05:17 bp_nvm
drwxrwx--- radio radio 2015-10-28 06:26 comm_drv
drwxr-xr-x root root 1981-12-31 13:00 config
drwxr----- root root 2012-08-29 07:51 factory
-rw-r--r-- root root 507504 2015-10-27 06:11 hijack
drwxrwx--- root root 2015-07-05 05:41 lost+found
drwxr-xr-x root root 2015-10-28 04:21 opprof
drwxrwxr-x system shell 2015-10-27 04:42 public
drwxr-xr-x root radio 2015-07-05 05:41 scim
drwxrwx--- 9007 9007 2015-10-27 06:15 security
-rw-r--r-- root root 260184 2015-10-27 06:11 update-binary
-rw-r--r-- root root 1335532 2015-10-27 06:11 update-recovery.zip
drwxrwx--x wifi wifi 2015-10-27 06:15 wifi
drwxrwxr-x 9003 9003 2015-10-27 06:15 wmdrm
/pds/bp_nvm:
-rw-r--r-- root root 3604 2015-10-27 06:11 FILE_PDS5
-rw-r--r-- root root 1970 2015-10-27 06:11 FILE_PDS_SUBSIDY_LOCK_DBK_1
-rw-r--r-- root root 2406 2015-10-27 06:11 FILE_PDS_SUBSIDY_LOCK_DBK_2
-rw-r--r-- root root 3197 2015-10-28 04:21 File_PDS1
-rw-r--r-- root root 2276 2015-10-27 06:11 File_PDS2
-rw-r--r-- root root 4387 2015-10-28 04:21 File_PDS3
-rw-r--r-- root root 4032 2015-10-28 04:21 File_PDS4
-rw-r--r-- root root 2602 2015-10-27 06:11 File_PDS_IMEI
-rw-r--r-- root root 4482 2015-10-27 06:11 File_PDS_LTE1
-rw-r--r-- root root 6722 2015-10-27 06:11 File_PDS_LTE2
-rw-r--r-- root root 320 2015-10-28 04:21 File_PDS_SBCM
-rw-r--r-- root root 1330 2015-10-30 05:18 File_PDS_Subsidy_Lock
-rw-r--r-- root root 312 2015-10-27 06:11 NVM_Daemon_Log.txt
-rw-rw-rw- root radio 1512 2015-10-28 06:21 NVM_Daemon_MD5
-rw------- root root 32 2012-12-06 08:42 md5
/pds/comm_drv:
-rw-r--r-- root root 1 2015-10-27 06:11 cat_log_control.cfg
-rw-r--r-- root root 1 2015-10-27 06:11 cat_routing_path_control.cfg
-rw-rw-rw- root radio 2704 2015-10-28 06:26 mmins_settings.cfg
-rw-r--r-- root root 1 2015-10-27 06:11 ms_log_control.cfg
-rw-r--r-- root root 61 2015-10-27 06:11 opprof.txt
/pds/config:
-rw-r----- root root 0 1981-12-31 13:00 barcode
-rw-r----- root root 0 1981-12-31 13:00 baseband
-rw-r----- root root 0 2012-12-06 08:41 bootmode
-rw-r----- root root 1 1981-12-31 13:00 boslogcat
-rw-r----- root root 0 1981-12-31 13:00 carrier
-rw-r----- root root 0 1981-12-31 13:00 console
-rw-r----- root root 0 1981-12-31 13:00 display
-rw-r----- root root 0 1981-12-31 13:00 dtname
-rw-r----- root root 0 1981-12-31 13:00 fti
-rw-r----- root root 0 1981-12-31 13:00 hwrev
-rw-r----- root root 0 1981-12-31 13:00 model
-rw-r----- root root 0 1981-12-31 13:00 msn
/pds/factory:
-rw-r----- root root 128 2012-08-29 08:55 fti
/pds/lost+found:
/pds/opprof:
/pds/public:
drwxrwxr-x root root 1981-12-31 13:04 atvc
drwxr-x--- 9000 9000 2015-10-27 06:15 battd
-rw------- root root 5 2012-12-06 08:13 cur.locale
-rw-r--r-- root root 2 2012-08-29 07:58 tcxo.bin
/pds/public/atvc:
/pds/public/battd:
-rw-rw---- root root 10 2015-10-27 06:11 batt_offset_data
-rw-rw---- root root 12 2015-10-27 06:11 batt_phasing_data
-rw-rw---- root root 256 2015-10-27 06:11 batt_tuning_data
/pds/scim:
/pds/security:
-rw-r--r-- root 9007 4096 2015-10-27 06:11 counter.bin
-rw-r--r-- root 9007 5086 2015-10-27 06:11 janusDeviceCert.dat
-rw-rw-r-- root 9007 608 2012-09-24 17:14 keymaptable.dat
-rw-rw-r-- root 9007 110 1981-12-31 13:04 keyring.dat
-rw-r--r-- root 9007 22528 2015-10-27 06:11 system.bin
/pds/wifi:
-rw-r--r-- root root 468 2015-10-27 06:11 nvs_map.bin
-rw-rw---- root root 1113 2012-09-19 07:33 nvs_map_mac80211.bin
/pds/wmdrm:
-rw-r--r-- root root 32 2015-10-27 06:11 hashsdidmap.dat
Are some files missing?
Click to expand...
Click to collapse
This is what I have
Code:
# cd /pds
# ls -lR
.:
drwxrwx--- 2 radio radio 1024 Oct 30 09:09 bp_nvm
drwxrwx--- 2 radio radio 1024 Oct 30 08:35 comm_drv
drwxrwx--- 2 root root 1024 Sep 22 2010 lost+found
drwxrwx--- 2 radio shell 1024 Dec 26 2012 opprof
drwxrwxr-x 3 system shell 1024 Dec 31 1969 public
drwxrwx--- 2 root radio 1024 Dec 31 1969 scim
drwxrws--- 2 system system 1024 Nov 10 2010 security
drwxrwx--x 2 wifi wifi 1024 Dec 31 1969 wifi
drwxrwxr-x 2 9003 9003 1024 Jan 16 2011 wmdrm
./bp_nvm:
-rw-rw---- 1 radio radio 3604 Dec 31 1969 FILE_PDS5
-rw-rw---- 1 radio radio 1970 Dec 31 1969 FILE_PDS_SUBSIDY_LOCK_DBK_1
-rw-rw---- 1 radio radio 2406 Dec 31 1969 FILE_PDS_SUBSIDY_LOCK_DBK_2
-rw-rw---- 1 radio radio 3197 Oct 28 16:44 File_PDS1
-rw-rw---- 1 radio radio 2276 Dec 31 1969 File_PDS2
-rw-rw---- 1 radio radio 4387 Dec 25 2012 File_PDS3
-rw-rw---- 1 radio radio 4032 Dec 25 2012 File_PDS4
-rw-rw---- 1 radio radio 2602 Dec 31 1969 File_PDS_IMEI
-rw-rw---- 1 radio radio 4482 Dec 31 1969 File_PDS_LTE1
-rw-rw---- 1 radio radio 6722 Dec 31 1969 File_PDS_LTE2
-rw-rw---- 1 radio radio 320 Dec 25 2012 File_PDS_SBCM
-rw------- 1 radio radio 1330 Oct 30 11:09 File_PDS_Subsidy_Lock
-rw-rw-rw- 1 radio radio 1599 Dec 25 2012 NVM_Daemon_MD5
./comm_drv:
-rw-rw-rw- 1 root radio 1 Dec 31 1969 cat_log_control.cfg
-rw-rw-rw- 1 root radio 1 Dec 31 1969 cat_routing_path_control.cfg
-rw-rw-rw- 1 root radio 2990 Oct 30 08:35 mmins_settings.cfg
-rw-rw-rw- 1 root radio 1 Dec 31 1969 ms_log_control.cfg
-rw-rw-rw- 1 root radio 61 Oct 29 17:38 opprof.txt
./lost+found:
./opprof:
-rw-rw-r-- 1 root radio 15996 Oct 30 06:36 2G_CALL_DROP_2g_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_csd_t_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_csv_nt_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_psd_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 MMINS_cc_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 304 Oct 30 06:36 MMINS_count_file.bin
-rw-rw-r-- 1 root radio 228 Oct 30 06:36 MMINS_timer_file.bin
-rw-rw-r-- 1 root radio 588 Oct 30 06:36 RRC_MM_CM_count_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 STACK_PROFILING_stack_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 STACK_RECOVERY_engine_recovery_debug_info_generic_file.bin
-rw-rw-r-- 1 root radio 2016 Oct 30 06:36 opprof_error_log.bin
-rw-rw-r-- 1 root radio 208 Oct 30 06:36 opprof_info_file.bin
./public:
drwxr-x--- 2 9000 9000 1024 Dec 31 1969 battd
-rw-r--r-- 1 root radio 2 Dec 31 1969 tcxo.bin
./public/battd:
-rw-rw---- 1 9000 9000 10 Dec 31 1969 batt_offset_data
-rw-rw---- 1 9000 9000 12 Dec 31 1969 batt_phasing_data
-rw-rw---- 1 9000 9000 256 Dec 31 1969 batt_tuning_data
./scim:
./security:
-rw------- 1 root 9007 4096 Nov 10 2010 counter.bin
-rw-rw-r-- 1 9004 9007 5086 Nov 10 2010 janusDeviceCert.dat
-rw-rw-r-- 1 root 9007 333 Nov 10 2010 keymaptable.dat
-rw------- 1 root 9007 22528 Nov 10 2010 system.bin
./wifi:
-rw-rw-rw- 1 9004 9004 468 Dec 31 1969 nvs_map.bin
./wmdrm:
-rw-rw-rw- 1 app_46 9003 32 Sep 5 2012 hashsdidmap.dat
---------- Post added at 11:49 AM ---------- Previous post was at 11:33 AM ----------
There is some info about pds and IMEI here:
http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
and here:
http://forum.xda-developers.com/showthread.php?p=52648789#post52648789
working solution from that last one is this... have you tried something like it?
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and your IMEI should be back!
Click to expand...
Click to collapse
craig_comstock said:
This is what I have
Code:
# cd /pds
# ls -lR
.:
drwxrwx--- 2 radio radio 1024 Oct 30 09:09 bp_nvm
drwxrwx--- 2 radio radio 1024 Oct 30 08:35 comm_drv
drwxrwx--- 2 root root 1024 Sep 22 2010 lost+found
drwxrwx--- 2 radio shell 1024 Dec 26 2012 opprof
drwxrwxr-x 3 system shell 1024 Dec 31 1969 public
drwxrwx--- 2 root radio 1024 Dec 31 1969 scim
drwxrws--- 2 system system 1024 Nov 10 2010 security
drwxrwx--x 2 wifi wifi 1024 Dec 31 1969 wifi
drwxrwxr-x 2 9003 9003 1024 Jan 16 2011 wmdrm
./bp_nvm:
-rw-rw---- 1 radio radio 3604 Dec 31 1969 FILE_PDS5
-rw-rw---- 1 radio radio 1970 Dec 31 1969 FILE_PDS_SUBSIDY_LOCK_DBK_1
-rw-rw---- 1 radio radio 2406 Dec 31 1969 FILE_PDS_SUBSIDY_LOCK_DBK_2
-rw-rw---- 1 radio radio 3197 Oct 28 16:44 File_PDS1
-rw-rw---- 1 radio radio 2276 Dec 31 1969 File_PDS2
-rw-rw---- 1 radio radio 4387 Dec 25 2012 File_PDS3
-rw-rw---- 1 radio radio 4032 Dec 25 2012 File_PDS4
-rw-rw---- 1 radio radio 2602 Dec 31 1969 File_PDS_IMEI
-rw-rw---- 1 radio radio 4482 Dec 31 1969 File_PDS_LTE1
-rw-rw---- 1 radio radio 6722 Dec 31 1969 File_PDS_LTE2
-rw-rw---- 1 radio radio 320 Dec 25 2012 File_PDS_SBCM
-rw------- 1 radio radio 1330 Oct 30 11:09 File_PDS_Subsidy_Lock
-rw-rw-rw- 1 radio radio 1599 Dec 25 2012 NVM_Daemon_MD5
./comm_drv:
-rw-rw-rw- 1 root radio 1 Dec 31 1969 cat_log_control.cfg
-rw-rw-rw- 1 root radio 1 Dec 31 1969 cat_routing_path_control.cfg
-rw-rw-rw- 1 root radio 2990 Oct 30 08:35 mmins_settings.cfg
-rw-rw-rw- 1 root radio 1 Dec 31 1969 ms_log_control.cfg
-rw-rw-rw- 1 root radio 61 Oct 29 17:38 opprof.txt
./lost+found:
./opprof:
-rw-rw-r-- 1 root radio 15996 Oct 30 06:36 2G_CALL_DROP_2g_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_csd_t_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_csv_nt_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 3G_CALL_DROP_3g_psd_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 MMINS_cc_call_drop_generic_file.bin
-rw-rw-r-- 1 root radio 304 Oct 30 06:36 MMINS_count_file.bin
-rw-rw-r-- 1 root radio 228 Oct 30 06:36 MMINS_timer_file.bin
-rw-rw-r-- 1 root radio 588 Oct 30 06:36 RRC_MM_CM_count_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 STACK_PROFILING_stack_generic_file.bin
-rw-rw-r-- 1 root radio 224 Oct 30 06:36 STACK_RECOVERY_engine_recovery_debug_info_generic_file.bin
-rw-rw-r-- 1 root radio 2016 Oct 30 06:36 opprof_error_log.bin
-rw-rw-r-- 1 root radio 208 Oct 30 06:36 opprof_info_file.bin
./public:
drwxr-x--- 2 9000 9000 1024 Dec 31 1969 battd
-rw-r--r-- 1 root radio 2 Dec 31 1969 tcxo.bin
./public/battd:
-rw-rw---- 1 9000 9000 10 Dec 31 1969 batt_offset_data
-rw-rw---- 1 9000 9000 12 Dec 31 1969 batt_phasing_data
-rw-rw---- 1 9000 9000 256 Dec 31 1969 batt_tuning_data
./scim:
./security:
-rw------- 1 root 9007 4096 Nov 10 2010 counter.bin
-rw-rw-r-- 1 9004 9007 5086 Nov 10 2010 janusDeviceCert.dat
-rw-rw-r-- 1 root 9007 333 Nov 10 2010 keymaptable.dat
-rw------- 1 root 9007 22528 Nov 10 2010 system.bin
./wifi:
-rw-rw-rw- 1 9004 9004 468 Dec 31 1969 nvs_map.bin
./wmdrm:
-rw-rw-rw- 1 app_46 9003 32 Sep 5 2012 hashsdidmap.dat
---------- Post added at 11:49 AM ---------- Previous post was at 11:33 AM ----------
There is some info about pds and IMEI here:
http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
and here:
http://forum.xda-developers.com/showthread.php?p=52648789#post52648789
working solution from that last one is this... have you tried something like it?
Click to expand...
Click to collapse
I tried it but it didn't worked BTW I think that the problem may be the missing opprof folder....

LG G5 partition scheme

look at the txt file below for the info. i tried putting in on the main post, but it didn't edit right. it is the complete partition scheme for the LGLS922, but i am pretty sure it applies to other G5s.
Nice one! Thanks for sharing!
How did You get the List? I can provide a H850 one for comparsion if You want. Just want to make sure that there are no diffrences :angel:
used adb shell and inputed "cat /proc/partitions" and installed this app and went into settings on the app and enables everything in it
schizoidd said:
used adb shell and inputed "cat /proc/partitions" and installed this app and went into settings on the app and enables everything in it
Click to expand...
Click to collapse
Perfect, i will share it here asap
Thanks again!
Miustone said:
Perfect, i will share it here asap
Thanks again!
Click to expand...
Click to collapse
not a problem, i am kinda curious about the partition scheme on these devices
can anyone else plz put in their input on their G5. I'd like to know.
Here is the H850 scheme:
Code:
[email protected]:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name
total 0
drwxr-xr-x 2 0 0 1400 Jan 1 17:33 .
drwxr-xr-x 4 0 0 1580 Jan 1 17:33 ..
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 OP -> /dev/block/sda16
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 aboot -> /dev/block/sde6
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 apdp -> /dev/block/sde26
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 boot -> /dev/block/sde1
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cache -> /dev/block/sda14
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 cust -> /dev/block/sda15
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 devinfo -> /dev/block/sdb7
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 dip -> /dev/block/sdb6
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 dpo -> /dev/block/sde28
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 drm -> /dev/block/sda3
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 eksst -> /dev/block/sda8
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 encrypt -> /dev/block/sda7
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 factory -> /dev/block/sda6
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 fota -> /dev/block/sdb3
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 fsg -> /dev/block/sdb5
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 grow -> /dev/block/sda18
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 grow2 -> /dev/block/sdb8
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 grow4 -> /dev/block/sdd4
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 grow6 -> /dev/block/sdf4
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 hyp -> /dev/block/sde12
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 keystore -> /dev/block/sda11
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 laf -> /dev/block/sda1
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 misc -> /dev/block/sda5
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 modem -> /dev/block/sde18
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 mpt -> /dev/block/sda2
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 msadp -> /dev/block/sde27
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 persist -> /dev/block/sda12
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 pmic -> /dev/block/sde14
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 rct -> /dev/block/sda9
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 recovery -> /dev/block/sde2
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 rpm -> /dev/block/sde10
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 sec -> /dev/block/sde19
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 sns -> /dev/block/sda4
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 spare1 -> /dev/block/sdb4
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 ssd -> /dev/block/sda10
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 system -> /dev/block/sda13
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 tz -> /dev/block/sde4
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 0 0 16 Jan 1 17:33 userdata -> /dev/block/sda17
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 0 0 15 Jan 1 17:33 xblbak -> /dev/block/sdb2
any have file PrimaryGPT.bin G5 correctly for QPST ?

Categories

Resources