Database Users

[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

[Q] Dalvik-cache ?

Hi.
Where is Dalvik-cache placed here ?:
Code:
# ls -al
total 256
drwxr-xr-x 23 root root 4096 Jun 24 10:08 .
drwxr-xr-x 23 root root 4096 Jun 24 10:08 ..
drwxr-xr-x 2 root root 4096 Nov 20 2011 .config
-rw-r--r-- 1 root root 147816 Jun 24 10:08 .readahead
drwxr-xr-x 2 root root 4096 Jan 5 08:16 bin
drwxr-xr-x 3 root root 4096 Nov 20 2011 boot
drwxr-xr-x 18 root root 4400 Jun 24 10:10 dev
drwxr-xr-x 118 root root 12288 Jun 24 10:08 etc
drwxr-xr-x 4 root root 4096 Nov 20 2011 home
drwxr-xr-x 22 root root 12288 Jan 5 08:16 lib
drwx------ 2 root root 16384 Nov 20 2011 lost+found
drwxr-xr-x 3 root root 60 Jun 24 10:10 media
drwxr-xr-x 2 root root 4096 Oct 25 2011 mnt
drwxr-xr-x 4 root root 4096 Dec 27 17:24 opt
dr-xr-xr-x 164 root root 0 Jun 24 2012 proc
drwx------ 27 root root 4096 Jun 24 10:25 root
drwxr-xr-x 21 root root 680 Jun 24 10:27 run
drwxr-xr-x 3 root root 12288 Jan 5 08:17 sbin
drwxr-xr-x 2 root root 4096 Oct 25 2011 selinux
drwxr-xr-x 4 root root 4096 Nov 10 2011 srv
drwxr-xr-x 12 root root 0 Jun 24 10:07 sys
drwxrwxrwt 18 root root 4096 Jun 24 10:25 tmp
drwxr-xr-x 12 root root 4096 Nov 10 2011 usr
drwxr-xr-x 15 root root 4096 Oct 1 2011 var

It is normally /data/cache/dalvik-cache
You have no data on there though....

I'm sure you are right.
Many thanks for your reply
# ls -al data/
total 96
drwx------ 3 Lajka users 32768 Jun 23 08:37 .
drwx------ 17 Lajka users 32768 Jan 1 1970 ..
drwx------ 2 Lajka users 32768 Jun 23 18:24 com.keramidas.TitaniumBackup
Click to expand...
Click to collapse

Its /data/dalvik-cache/
Send from my LG GT540 Android 4.0.3 Polishblood PreRC CM9

Thanks, and means, that I have no dalvik-cache ?.
Why?

hmm where did you get this and what are you trying to do? You dont have a recovery?

Hi.
What do you mean ?.
I have accessed the GT540 from my linux box, and can't see it.
I would delete the dalvik-cache.
No recovery available.
What's a way to get it ?.

Maybe there is a way but ... get a recovery

Please advice me to make a recovery, thanks!

aalested said:
Please advice me to make a recovery, thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1224747 just follow this

Indeed this was a nice link. Many many thanks :laugh:

Does this mean to be done when the telephone starts up ?
Next put your phone in Fastboot mode by rebooting then holding Camera+Power
Click to expand...
Click to collapse

aalested said:
Does this mean to be done when the telephone starts up ?
Click to expand...
Click to collapse
to go in fastboot mode turn your phone off. then press power on and at the same time hold the camera button

@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
From this thread:
http://http://forum.xda-developers.com/showthread.php?t=1224747
There stands:
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Click to expand...
Click to collapse
Which one can I use for my GT540 with Android 2.1 ?

aalested said:
@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
Which one can I use for my GT540 with Android 2.1 ?
Click to expand...
Click to collapse
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.

Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow

andreas__ said:
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.
Click to expand...
Click to collapse
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you

-Grift- said:
Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow
Click to expand...
Click to collapse
Ok, but where is the "the tool get the original version" ?
Link ?.

aalested said:
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you
Click to expand...
Click to collapse
as -Grift- gave full instructions for the fastboot tool you now should have android 2.3 installed on your GT540.
IF you REALLY want back to 2.1 (maybe because of battery life)
check this:
http://forum.xda-developers.com/showthread.php?t=1368013

@andreas__
Manny thanks, great!

Galaxy Note 8 - GT-N5110 Update 4/22/2013...

The Note 8 model GT-N5110 has been updated in the U.S.
As of yesterday, the device is running a new kernel & the build number is now JZO54K.N5510UEDMD1.
Not sure what has changed, just said stability improvements, but as soon as I am finished building my dev environment on the new machine, I will grab the update & pot it here, unless someone beats me to it.

FYI... After applying the update I had to re-root my device.
Sent from my GT-N5110 using Tapatalk 2

Using SuperSU Pro's "survival mode" setting, I maintained root.
If anybody is interested in looking closer, here's the .zip for the update. I renamed it to the version name. It was named update.zip in the /cache/fota directory.
https://www.dropbox.com/s/qbcmt2lpb6o72po/UEDMD1.zip

MSHampton said:
FYI... After applying the update I had to re-root my device.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
Using VooDoo & Koush's SuperUser, I was able to restore root with a single click! Same probably goes for others as well.

Since my 5110 is rooted, trying to force the update gives me the stock "Your device has been modified" message, so I assume I have to unroot to get this update? Any recommendations on doing just that, or is there another way around this?

Juvenall said:
Since my 5110 is rooted, trying to force the update gives me the stock "Your device has been modified" message, so I assume I have to unroot to get this update? Any recommendations on doing just that, or is there another way around this?
Click to expand...
Click to collapse
It's actually not about being rooted or not rooted. It's what you changed with that root access. If there are any system modifications, apps frozen, etc, those have to be reverted back in order for the OTA to work, but you can remain rooted and even keep root with the apps mentioned above.

I did nothing besides the root itself and I'm still getting that message. Can't update.

I too am unable to update the device due to the same Message. All I did was root and install busy box. I'm thinking the only way to be able to install the OTA at this point is to either factory reset or install the zip from recovery.
I've tried to uninstall busybox to see if that was the problem but it won't proceed with the uninstall.
Sent from my GT-N5110 using Tapatalk HD

are y'all using any apps to keep root?

What I Did to Update/Keep Root
Download/install Voodoo OTA Rootkeeper from the market and use it to make a backup su. Then download the file referenced earlier in this thread, rename it update.zip, and place it in the root directory of your external SD card.
Then unroot using Voodoo OTA Rootkeeper and boot into recovery. Install the update and reboot.
Then reroot via OTA Rootkeeper.
Viola! Updated

docfreed said:
Download/install Voodoo OTA Rootkeeper from the market and use it to make a backup su. Then download the file referenced earlier in this thread, rename it update.zip, and place it in the root directory of your external SD card.
Then unroot using Voodoo OTA Rootkeeper and boot into recovery. Install the update and reboot.
Then reroot via OTA Rootkeeper.
Viola! Updated
Click to expand...
Click to collapse
I was getting the error message like some others say they got so;
I followed these instructions except instead of downloading the file in the thread, I rebooted after unrooting and checked for software update through the about device>software update>check for updates. I did it and updated, rebooted and did it again and there was another update just a wee bit larger than the first. Cycled through both updates, rebooted, rerooted, rebooted again and I am updated with root.
Now if I can just figure out what the updates actually did.

Personally I like Koush's Superuser. No funky permissions, no paid "donation" version, just SuperUser access that works.
What I do to keep my system OTA updatable:
1. Install & launch Framaroot.
2. select "Install SuperSu", but do not reset device.
3. Install CWM's SuperUser by Koush. (This way the SU app is not in the "/system/app" folder, it is in "/data/app", which saves you some DRM headaches
4. Launch the new SuperUser & follow prompts to "Install" the new SU binary.
5. Make Backup with VooDoo
6. Open Framaroot again & select "Unroot"
7. Restore your new CWM SuperUser binary with the backup you took using VooDoo in step #5.
8. Reset device & rock & roll.
It is okay to have SU in the /System/* folder, but I find it causes issues with apps that are DRM strict, like many of the cable/dish/streaming apps, so I prefer to install it normally thru Play Store, or via file browser.

What am I missing? I updated but don't have the same build as JZO54K.N5510UEDMD1. I am using the .zip in a post on the 1st page. This is what I have...
Edit: I think I'm fine, I was getting mixed up in the original post stating its JZO54k.N5510, not N5110 as it should be. Can someone still confirm for me?
Also, the method right above mine works wonderful.

I'm waiting to hear that I'm hotter with the ladies or something else good after applying the update to want to.
From the file list, they did patch quite a bit of stuff.
ls -lR
.:
total 888
drwxr-xr-x 3 root root 4096 Apr 23 09:37 META-INF
drwxr-xr-x 3 root root 4096 Apr 23 09:37 patch
drwxr-xr-x 3 root root 4096 Apr 23 09:37 recovery
-rw-r--r-- 1 root root 887040 Jun 22 2011 sboot.bin
drwxr-xr-x 3 root root 4096 Apr 23 09:37 system
./META-INF:
total 40
-rw-r--r-- 1 root root 1772 Jun 22 2011 CERT.RSA
-rw-r--r-- 1 root root 15412 Jun 22 2011 CERT.SF
-rw-r--r-- 1 root root 15359 Jun 22 2011 MANIFEST.MF
drwxr-xr-x 4 root root 4096 Apr 23 09:37 com
./META-INF/com:
total 8
drwxr-xr-x 2 root root 4096 Apr 23 09:37 android
drwxr-xr-x 3 root root 4096 Apr 23 09:37 google
./META-INF/com/android:
total 8
-rw-r--r-- 1 root root 209 Jun 22 2011 metadata
-rw-r--r-- 1 root root 1736 Jun 22 2011 otacert
./META-INF/com/google:
total 4
drwxr-xr-x 2 root root 4096 Apr 23 09:37 android
./META-INF/com/google/android:
total 300
-rw-r--r-- 1 root root 221760 Jun 22 2011 update-binary
-rw-r--r-- 1 root root 72624 Jun 22 2011 updater-script
./patch:
total 4564
-rw-r--r-- 1 root root 4655574 Jun 22 2011 boot.img.p
drwxr-xr-x 7 root root 4096 Apr 23 09:37 system
./patch/system:
total 28
-rw-r--r-- 1 root root 142 Jun 22 2011 SW_Configuration.xml.p
drwxr-xr-x 2 root root 4096 Apr 23 09:37 app
drwxr-xr-x 2 root root 4096 Apr 23 09:37 bin
-rw-r--r-- 1 root root 204 Jun 22 2011 build.prop.p
drwxr-xr-x 3 root root 4096 Apr 23 09:37 etc
drwxr-xr-x 2 root root 4096 Apr 23 09:37 framework
drwxr-xr-x 2 root root 4096 Apr 23 09:37 lib
./patch/system/app:
total 972
-rw-r--r-- 1 root root 2046 Jun 22 2011 ApplicationsProvider.apk.p
-rw-r--r-- 1 root root 2044 Jun 22 2011 BackupRestoreConfirmation.apk.p
-rw-r--r-- 1 root root 2055 Jun 22 2011 BluetoothAvrcp.apk.p
-rw-r--r-- 1 root root 2033 Jun 22 2011 BluetoothMap.apk.p
-rw-r--r-- 1 root root 2027 Jun 22 2011 CSC.apk.p
-rw-r--r-- 1 root root 2057 Jun 22 2011 CertInstaller.apk.p
-rw-r--r-- 1 root root 2050 Jun 22 2011 DSMForwarding.apk.p
-rw-r--r-- 1 root root 2025 Jun 22 2011 DefaultContainerService.apk.p
-rw-r--r-- 1 root root 2046 Jun 22 2011 DrmProvider.apk.p
-rw-r--r-- 1 root root 2021 Jun 22 2011 EdmSysScopeService.apk.p
-rw-r--r-- 1 root root 2063 Jun 22 2011 EdmVpnServices.apk.p
-rw-r--r-- 1 root root 74275 Jun 22 2011 FactoryTest.apk.p
-rw-r--r-- 1 root root 2110 Jun 22 2011 HiddenMenu.apk.p
-rw-r--r-- 1 root root 2048 Jun 22 2011 InputDevices.apk.p
-rw-r--r-- 1 root root 2065 Jun 22 2011 KeyChain.apk.p
-rw-r--r-- 1 root root 2052 Jun 22 2011 PackageInstaller.apk.p
-rw-r--r-- 1 root root 2037 Jun 22 2011 PartnerBookmarksProvider.apk.p
-rw-r--r-- 1 root root 2072 Jun 22 2011 Personalization.apk.p
-rw-r--r-- 1 root root 2073 Jun 22 2011 PickUpTutorial.apk.p
-rw-r--r-- 1 root root 2076 Jun 22 2011 Preconfig.apk.p
-rw-r--r-- 1 root root 2118 Jun 22 2011 PreloadInstaller.apk.p
-rw-r--r-- 1 root root 308 Jun 22 2011 PreloadInstaller.odex.p
-rw-r--r-- 1 root root 540182 Jun 22 2011 SamsungApps_Tablet.apk.p
-rw-r--r-- 1 root root 162779 Jun 22 2011 SamsungIME.odex.p
-rw-r--r-- 1 root root 2133 Jun 22 2011 SecBluetooth.apk.p
-rw-r--r-- 1 root root 3423 Jun 22 2011 SecBrowser.apk.p
-rw-r--r-- 1 root root 2259 Jun 22 2011 SecCalendarProvider_Kona_Tablet.apk.p
-rw-r--r-- 1 root root 2115 Jun 22 2011 SecCalendar_Kona_SPen.apk.p
-rw-r--r-- 1 root root 3843 Jun 22 2011 SecContacts.apk.p
-rw-r--r-- 1 root root 2043 Jun 22 2011 SecContactsProvider.apk.p
-rw-r--r-- 1 root root 2058 Jun 22 2011 SecDownloadProvider.apk.p
-rw-r--r-- 1 root root 2083 Jun 22 2011 SecDownloadProviderUi.apk.p
-rw-r--r-- 1 root root 2059 Jun 22 2011 SecHTMLViewer.apk.p
-rw-r--r-- 1 root root 2652 Jun 22 2011 SecLauncher2.apk.p
-rw-r--r-- 1 root root 2062 Jun 22 2011 SecLiveWallpapersPicker.apk.p
-rw-r--r-- 1 root root 2056 Jun 22 2011 SecMediaProvider.apk.p
-rw-r--r-- 1 root root 2059 Jun 22 2011 SecOmaDownloadProvider.apk.p
-rw-r--r-- 1 root root 2112 Jun 22 2011 SecPhone.apk.p
-rw-r--r-- 1 root root 2108 Jun 22 2011 SecSettings.apk.p
-rw-r--r-- 1 root root 2038 Jun 22 2011 SecSettingsProvider.apk.p
-rw-r--r-- 1 root root 2057 Jun 22 2011 SecSoundRecorder.apk.p
-rw-r--r-- 1 root root 2078 Jun 22 2011 SecWallpaperChooser.apk.p
-rw-r--r-- 1 root root 2060 Jun 22 2011 SecurityProvider.apk.p
-rw-r--r-- 1 root root 1922 Jun 22 2011 SharedStorageBackup.apk.p
-rw-r--r-- 1 root root 2079 Jun 22 2011 Stk.apk.p
-rw-r--r-- 1 root root 2171 Jun 22 2011 SystemUI.apk.p
-rw-r--r-- 1 root root 2072 Jun 22 2011 TasksProvider.apk.p
-rw-r--r-- 1 root root 2069 Jun 22 2011 TelephonyProvider.apk.p
-rw-r--r-- 1 root root 2045 Jun 22 2011 UserDictionaryProvider.apk.p
-rw-r--r-- 1 root root 2027 Jun 22 2011 VpnDialogs.apk.p
-rw-r--r-- 1 root root 2060 Jun 22 2011 minimode-res.apk.p
-rw-r--r-- 1 root root 2116 Jun 22 2011 serviceModeApp.apk.p
./patch/system/bin:
total 12
-rw-r--r-- 1 root root 171 Jun 22 2011 debuggerd.p
-rw-r--r-- 1 root root 171 Jun 22 2011 mdnsd.p
-rw-r--r-- 1 root root 185 Jun 22 2011 wpa_supplicant.p
./patch/system/etc:
total 12
-rw-r--r-- 1 root root 151 Jun 22 2011 apks_count_list.txt.p
drwxr-xr-x 2 root root 4096 Apr 23 09:37 security
-rw-r--r-- 1 root root 556 Jun 22 2011 security_profile.dat.p
./patch/system/etc/security:
total 4
-rw-r--r-- 1 root root 203 Jun 22 2011 otacerts.zip.p
./patch/system/framework:
total 352
-rw-r--r-- 1 root root 194 Jun 22 2011 CustFeature.jar.p
-rw-r--r-- 1 root root 166 Jun 22 2011 CustFeature.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 GlobalConfig.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 GlobalConfig.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 access.control.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 access.control.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 allshare.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 allshare.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 allsharelib.jar.p
-rw-r--r-- 1 root root 181 Jun 22 2011 allsharelib.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 am.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 am.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 android.policy.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 android.policy.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 android.test.runner.jar.p
-rw-r--r-- 1 root root 176 Jun 22 2011 android.test.runner.odex.p
-rw-r--r-- 1 root root 264 Jun 22 2011 apache-xml.jar.p
-rw-r--r-- 1 root root 184 Jun 22 2011 apache-xml.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bmgr.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 bmgr.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bouncycastle.jar.p
-rw-r--r-- 1 root root 182 Jun 22 2011 bouncycastle.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bu.jar.p
-rw-r--r-- 1 root root 169 Jun 22 2011 bu.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.android.future.usb.accessory.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 com.android.future.usb.accessory.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.android.location.provider.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 com.android.location.provider.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.google.widevine.software.drm.jar.p
-rw-r--r-- 1 root root 161 Jun 22 2011 com.google.widevine.software.drm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 content.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 content.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 core-junit.jar.p
-rw-r--r-- 1 root root 167 Jun 22 2011 core-junit.odex.p
-rw-r--r-- 1 root root 235 Jun 22 2011 core.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 core.odex.p
-rw-r--r-- 1 root root 1617 Jun 22 2011 ext.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 ext.odex.p
-rw-r--r-- 1 root root 2118 Jun 22 2011 framework-res.apk.p
-rw-r--r-- 1 root root 209 Jun 22 2011 framework.jar.p
-rw-r--r-- 1 root root 183 Jun 22 2011 framework.odex.p
-rw-r--r-- 1 root root 193 Jun 22 2011 framework2.jar.p
-rw-r--r-- 1 root root 179 Jun 22 2011 framework2.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 ime.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 ime.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 input.jar.p
-rw-r--r-- 1 root root 167 Jun 22 2011 input.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 javax.obex.jar.p
-rw-r--r-- 1 root root 164 Jun 22 2011 javax.obex.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 kies_feature.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 kies_feature.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 libvtmanagerjar.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 libvtmanagerjar.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 minimode.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 minimode.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 monkey.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 monkey.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 multiwindow.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 multiwindow.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 org.simalliance.openmobileapi.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 org.simalliance.openmobileapi.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 pm.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 pm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 requestsync.jar.p
-rw-r--r-- 1 root root 166 Jun 22 2011 requestsync.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sec_edm.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 sec_edm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sec_feature.jar.p
-rw-r--r-- 1 root root 160 Jun 22 2011 sec_feature.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 sec_platform_library.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 sec_platform_library.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 seccamera.jar.p
-rw-r--r-- 1 root root 176 Jun 22 2011 seccamera.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 secface.jar.p
-rw-r--r-- 1 root root 170 Jun 22 2011 secface.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sechardware.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 sechardware.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 secmediarecorder.jar.p
-rw-r--r-- 1 root root 169 Jun 22 2011 secmediarecorder.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 services.jar.p
-rw-r--r-- 1 root root 184 Jun 22 2011 services.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 svc.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 svc.odex.p
-rw-r--r-- 1 root root 2110 Jun 22 2011 twframework-res.apk.p
-rw-r--r-- 1 root root 196 Jun 22 2011 twframework.jar.p
-rw-r--r-- 1 root root 178 Jun 22 2011 twframework.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 uiautomator.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 uiautomator.odex.p
./patch/system/lib:
total 112
-rw-r--r-- 1 root root 43641 Jun 22 2011 libSamsungVoiceEngine.so.p
-rw-r--r-- 1 root root 251 Jun 22 2011 libbcc.so.p
-rw-r--r-- 1 root root 178 Jun 22 2011 libbcinfo.so.p
-rw-r--r-- 1 root root 184 Jun 22 2011 libchromium_net.so.p
-rw-r--r-- 1 root root 164 Jun 22 2011 libmdnssd.so.p
-rw-r--r-- 1 root root 584 Jun 22 2011 libstagefright_soft_aacdec.so.p
-rw-r--r-- 1 root root 677 Jun 22 2011 libstagefright_soft_aacenc.so.p
-rw-r--r-- 1 root root 38271 Jun 22 2011 libwebcore.so.p
-rw-r--r-- 1 root root 168 Jun 22 2011 libwebrtc_audio_preprocessing.so.p
./recovery:
total 1200
drwxr-xr-x 2 root root 4096 Apr 23 09:37 etc
-rw-r--r-- 1 root root 1217002 Jun 22 2011 recovery-from-boot.p
./recovery/etc:
total 4
-rw-r--r-- 1 root root 535 Jun 22 2011 install-recovery.sh
./system:
total 8
-rw-r--r-- 1 root root 13 Jun 22 2011 CSCVersion.txt
drwxr-xr-x 2 root root 4096 Apr 23 09:37 lib
./system/lib:
total 4
-rw-r--r-- 1 root root 20 Jun 22 2011 libbcc.so.sha1

Two Updates?
I see some folks referring to JZO54K.N5510UEDMD1 - we have of course the GT-N5110 (WiFi only) Tablets. Are these typo's? Or is there a second update?
After the first update, I have a build number of JZO54K.N5110UEDMD1. I have not seen a second update.

UEDMD1 is the latest one, just started today, or yesterday.
Sent from my SCH-I535 using Tapatalk 2

johnnyvol said:
I followed these instructions except instead of downloading the file in the thread, I rebooted after unrooting and checked for software update through the about device>software update>check for updates. I did it and updated, rebooted and did it again and there was another update just a wee bit larger than the first. Cycled through both updates, rebooted, rerooted, rebooted again and I am updated with root.
Click to expand...
Click to collapse
This is the way I ended up getting the update. Worked like a charm.
Sent from my GT-N5110 using xda premium

jntdroid said:
UEDMD1 is the latest one, just started today, or yesterday.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Actually I was referring to the "N5510" part that was stated above - I assume it should read N5110. We should all have a UEDMD1 part

Is anyone else seeing a performance hit after applying this?
I haven't gotten rid of all the junkware in /system yet (required to restore to apply the update - maybe not 100%, but as I don't have a phone I'd gotten rid of the phone stuff, so the update gacked) and that may be the cause, but I was surprised that Antutu was reporting a 3-5% performance hit after the update.

GSLEON3 said:
Personally I like Koush's Superuser. No funky permissions, no paid "donation" version, just SuperUser access that works.
What I do to keep my system OTA updatable:
1. Install & launch Framaroot.
2. select "Install SuperSu", but do not reset device.
3. Install CWM's SuperUser by Koush. (This way the SU app is not in the "/system/app" folder, it is in "/data/app", which saves you some DRM headaches
4. Launch the new SuperUser & follow prompts to "Install" the new SU binary.
5. Make Backup with VooDoo
6. Open Framaroot again & select "Unroot"
7. Restore your new CWM SuperUser binary with the backup you took using VooDoo in step #5.
8. Reset device & rock & roll.
It is okay to have SU in the /System/* folder, but I find it causes issues with apps that are DRM strict, like many of the cable/dish/streaming apps, so I prefer to install it normally thru Play Store, or via file browser.
Click to expand...
Click to collapse
Worked great now rooted. Had the update in place before so good to go.

[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....