Database Develop

Problem with efs folder content

Hi,
I bought a brand new samsung galaxy s plus GT-I9001 in Poland (locked to Orange network) and I 'm trying to unlock the phone, but I can't because my phone does not contain the nv_data.bin file in the efs folder.
I have rooted the phone using the tutorial posted in
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Rooting
I got root access and found that in efs folder I got these files
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# pwd
pwd
/
# ls -l -a
ls -l -a
drwxrwx--x system system 2012-10-09 15:39 efs
dr-x------ root root 2012-10-10 13:27 config
drwxrwx--- system cache 2012-10-10 13:29 cache
drwxrwx--x system system 1980-01-06 01:00 persist
lrwxrwxrwx root root 2012-10-10 13:27 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:27 acct
drwxrwxr-x root system 2012-10-10 13:27 mnt
lrwxrwxrwx root root 2012-10-10 13:27 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:27 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:27 etc -> /system/etc
-rw-r--r-- root root 5610 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 01:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-10-10 12:15 system
drwxr-xr-x root root 2012-10-10 13:27 sys
drwxr-x--- root root 1970-01-01 01:00 sbin
-rw-r--r-- root root 339852 1970-01-01 01:00 recovery
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2011 1970-01-01 01:00 lpm.rc
drwxr-xr-x root root 1970-01-01 01:00 lib
-rwxr-x--- root root 24620 1970-01-01 01:00 initlogo.rle
-rwxr-x--- root root 30518 1970-01-01 01:00 init.rc
-rwxr-x--- root root 6900 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 8590 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 1677 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 106780 1970-01-01 01:00 init
-rw-r--r-- root root 118 1970-01-01 01:00 default.prop
drwxrwx--x system system 2012-10-10 13:27 data
-rw-r--r-- root root 38528 1970-01-01 01:00 charging.rle
-rw-r--r-- root root 22268 1970-01-01 01:00 ARIESVE.rle
drwx------ root root 2011-12-19 08:31 root
drwxr-xr-x root root 2012-10-10 13:35 dev
# cd efs
cd efs
# ls -l -a
ls -l -a
-rw-r--r-- system system 9 2012-10-09 15:39 cryptprop_applied_result
-rw-r--r-- root root 5 2012-10-10 10:51 cryptprop_onetimeboot
-rw-r--r-- system system 1 2012-10-09 15:39 cryptprop_essiv
drwx------ root root 1980-01-06 01:01 lost+found
drwxrwxr-x root root 1980-01-06 01:09 .files
-rw-r--r-- root root 3 2012-10-10 10:51 cryptprop_securewipedata
# cd .files
cd .files
# ls -l -a
ls -l -a
drwxrwxr-x media system 1980-01-06 01:01 .ssh01
-rw-rw-rw- radio radio 2 1980-01-06 01:09 keystr
drwxrwxr-x media system 1980-01-06 01:01 .jck12
drwxrwxr-x media system 1980-01-06 01:01 .dj550
as you can see the efs folder contain cryptprop files which are very small.
The phone works normally, it has its IMEI and connects to GSM network and WiFi network as well. (*#06# returns value 352377055840629)
I'm trying to unlock the phone myself but without nv_data.bin I'm getting nowhere...
Could someone please help me?
PS:
I have changed the stock rom (orange) to XEO rom (I9001XXKPU 2.3.6 and I9001XXKI2 2.3.4) but efs folder is the same each time.

I have checked the init.rc file in the root... ht file looks like this:
Line 56:
mkdir /efs 0771 system system
Line 131 - 135:
mount ext4 /dev/block/mmcblk0p27 /efs nosuid nodev barrier=0
insmod /lib/modules/sec_param.ko
Line 160 - 165:
#efs
chown system system /efs
chmod 0771 /efs
mkdir /efs/.files 0775
# Added for testing DIVX DRM
mkdir /efs/.files/.ssh01 0775
mkdir /efs/.files/.jck12 0775
mkdir /efs/.files/.dj550 0775
chown media system /efs/.files/.ssh01
chown media system /efs/.files/.jck12
chown media system /efs/.files/.dj550
chmod 0775 /efs/.files/.ssh01
chmod 0775 /efs/.files/.jck12
chmod 0775 /efs/.files/.dj550
This init.rc does not create the folders WiFi or Bluetooth like in other device (I checked in a galaxy SII)
The init.rc file is attached.

fcornejo said:
I 'm trying to unlock the phone,
Click to expand...
Click to collapse
It might be easier to use an app or tool from My Android Collections to unlock phone

xsenman said:
It might be easier to use an app or tool from My Android Collections to unlock phone
Click to expand...
Click to collapse
Well thanx, but all the aps and methods require the nv_data.bin file...

fcornejo said:
Well thanx, but all the aps and methods require the nv_data.bin file...
Click to expand...
Click to collapse
have a look at /persist folder.

xsenman said:
have a look at /persist folder.
Click to expand...
Click to collapse
There are files:
Code:
#
# cd persist
cd persist
# ls -l -a
ls -l -a
-rw-r--r-- root root 3468 2011-08-29 00:40 WCN1314_qcom_wlan_nv.bi
-rw-r--r-- root root 3 2011-08-29 00:40 efs_info.bin
drwxr-xr-x root root 2011-09-08 10:14 qcom
-rw-r--r-- root root 1656 2011-08-29 00:40 qcom_wlan_nv.bin
-rw-rw-rw- root root 2 2012-10-10 13:27 sd_det.bin
-rw-rw-rw- root root 1 2012-10-10 12:08 usb_sel.bin
drwxrwxr-x root root 1980-01-06 01:00 .files
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_pass
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_done

How can I (we) contribute to dev, rooting, roms, etc?

I apologize if this is a newbie question, but now that my kindle fire 2 updated itself to 10.2.3, I have lost root. I've also noticed that no roms or bootloader workaround has been done for the kindle fire 2.
So my question is: if I have some experience with linux systems (although maybe not with android specifically), how can I get started contributing to the rom community? I ask this in the context of kindle fire 2 of course.
I found a few docs like this: dubdubdub sourceconference dot com slash publications/bos12pubs/android-modding-source.pdf
I noticed that /data is now under group perm rwx :system , and maybe there's an existing path towards getting system group perm from standard adb shell
Code:
127|[email protected]:/sys $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4 ro,relatime,ba
rrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4 rw,nosuid,node
v,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4 rw,nosuid,nodev,
noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /efs ext4 rw,relatime,barrier=
1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
[email protected]:/sys $ ls -al /
ls -al /
drwxr-xr-x root root 2012-12-06 10:04 acct
drwxrwx--- system cache 2012-12-06 12:23 cache
dr-x------ root root 2012-12-06 10:04 config
lrwxrwxrwx root root 2012-12-06 10:04 d -> /sys/kernel/debug
drwxrwx--x system system 2012-12-05 11:54 data
-rw-r--r-- root root 89 1969-12-31 18:00 default.prop
drwxr-xr-x root root 2012-12-06 10:04 dev
drwxr-xr-x root root 2012-11-22 01:59 efs
lrwxrwxrwx root root 2012-12-06 10:04 etc -> /system/etc
-rwxr-x--- root root 98608 1969-12-31 18:00 init
-rwxr-x--- root root 2344 1969-12-31 18:00 init.goldfish.rc
-rwxr-x--- root root 9053 1969-12-31 18:00 init.omap4blazeboard.rc
-rwxr-x--- root root 4204 1969-12-31 18:00 init.omap4blazeboard.usb.
rc
-rwxr-x--- root root 17463 1969-12-31 18:00 init.rc
lrwxrwxrwx root root 2012-12-06 10:04 misc -> /dev/block/platfo
rm/omap/omap_hsmmc.1/by-name/misc
drwxrwxr-x root system 2012-12-06 10:04 mnt
dr-xr-xr-x root root 1969-12-31 18:00 proc
drwx------ root root 2012-11-28 01:23 root
drwxr-x--- root root 1969-12-31 18:00 sbin
lrwxrwxrwx root root 2012-12-06 10:04 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-12-06 10:04 sys
drwxr-xr-x root root 2012-12-06 06:33 system
-rw-r--r-- root root 272 1969-12-31 18:00 ueventd.goldfish.rc
-rw-r--r-- root root 1289 1969-12-31 18:00 ueventd.omap4blazeboard.r
c
-rw-r--r-- root root 4267 1969-12-31 18:00 ueventd.rc
lrwxrwxrwx root root 2012-12-06 10:04 vendor -> /system/vendor

re: contributing, and not moaning..
..respect to you, Sir, refreshing attitude - guess you can best help by doing..
for my own part, currently have a 'half-root' KF2, root read / ftp access, Google Music (only thing I need personally) etc. all working fine under 10.2.3, I cannot change folder permissions (/data, etc.) at all tho, either under adb or ftp (does ftp chmod work *at all*? on Fire? - I have zero android/Fire experience, unfortunately), any and all further ideas appreciated tho..
either that, or I guess we just wait on the 10.2.3 Youtube crack walkthrough

My impression so far is there are three categories of workaround for root:
file permissions exploits, which take advantage of log writing or other scripts that already have root, and hijack them to modify system perms (e.g. the qemu root method)
bootloader over-writing (e.g. cwm). KF2 uses a locked bootloader unlike KF1, but KF2 ("otter2" builds) share a lot of similarity with the kindle HD, and that bootloader has reportedly been successfully worked around by some people.
other exploits, e.g. the typical modifying of binary assembly files or overflow bugs that are totally outside of my purview
any others?
If there was a repository of ideas for #1, perhaps we can see if there's crossover of another vendor exploit with KF2.
Also, I'd love links that outline the boot, recovery, and OTA scripts for KF2
Ideas for trying #2 without bricking would be nice too

Reboot loop after upgrading from CM 10.0 stable to CM 10.1 nightly

Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks

transact said:
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
Click to expand...
Click to collapse
Have you tried wiping data again from recovery and then boot?

ishangoyal said:
Have you tried wiping data again from recovery and then boot?
Click to expand...
Click to collapse
Yeah, multiple times.
I tried to flash stock firmware back but I think system is read only now.
When I flashed stockfirmware from samfirmware also with odin and pit file, I was able to go to stock recovery but phone never booted to stock firmware. Then I flashed semaphore . this time I could see semaphore logo and then cyanogenmod animation. Seeing cyanogen animation was a surprise as it should have been wiped when i flashed stockfirmare.
I went to recovery mode again did factory reset, cache wipe, dalvik cache. Then mounted usb and copied latest nightly of 10.1 and gapps to customroms folder on my sdcard.
After copying I rebooted into recovery mode again and selected install from zip on sdcard but to my surprise the new files I copied were not there but the files I deleted were still there.
It seems like phone didn't allow me to alter content of sdcard. To test I mounted the usb storage again and created some dummy files like default.txt, default.ini and default.zip in root of sdcard and deleted some files from my backup files of fuellog folder. After unmounting and going through files on phone I discovered that new files are not there and old files are still present.
Another thing is that I have factory reset multiple times, wiped cache partition and cleared dalvik cache as well but every time I mount usb from recovery I have .android_secure folder filled with my previous apps from CM 10.0, which I think shouldn't be there after factory reset.
So I guess it is something to do with permissions. I have done 'fix permissions' multiple times but that also didn't helped.
One more thing I noticed is that after I flash CM10.1 from old file still in my sdcard, on first boot I get com.phone.android error but then on second boot I saw option to complete action using apex, nova or trebuchet laucnher behing the com.android.phone error. I think I shouldn't see that message as it is suppose to be new install with factory reset.
after I click ok on the error message, the phone reboots again but this time it stuck on cyanogen animation. it never goes past animation on 3rd boot.
I have really no idea what is happening.
Is there a way to reset everything through adb? or reset file permissions? I could access my device using adb but had no idea what I could do or not do.
File system view when phone is booting and stuck at cyanogen animation
Code:
drwxr-xr-x root root 2013-01-15 10:29 acct
-rw-r--r-- root root 614 2013-01-15 10:29 boot.txt
drwxrwx--x system cache 2013-01-15 10:29 cache
-rwxr-x--- root root 264080 2013-01-15 10:29 charger
dr-x------ root root 2013-01-15 10:29 config
lrwxrwxrwx root root 2013-01-15 10:29 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-11 17:08 data
drwxrwx--x system system 2013-01-15 10:29 datadata
-rw-r--r-- root root 163 2013-01-15 10:29 default.prop
drwxr-xr-x root root 2013-01-15 10:29 dev
drwxr-xr-x radio radio 2013-01-14 21:30 efs
lrwxrwxrwx root root 2013-01-15 10:29 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2013-01-15 10:29 etc -> /system/etc
-rw-r----- root root 568 2013-01-15 10:29 fstab.aries
-rwxr-x--- root root 109484 2013-01-15 10:29 init
-rwxr-x--- root root 555 2013-01-15 10:29 init.aries.gps.rc
-rwxr-x--- root root 5375 2013-01-15 10:29 init.aries.rc
-rwxr-x--- root root 3899 2013-01-15 10:29 init.aries.usb.rc
-rwxr-x--- root root 1238 2013-01-15 10:29 init.cm.rc
-rwxr-x--- root root 2487 2013-01-15 10:29 init.goldfish.rc
-rwxr-x--- root root 18768 2013-01-15 10:29 init.rc
-rwxr-x--- root root 1795 2013-01-15 10:29 init.trace.rc
-rwxr-x--- root root 3915 2013-01-15 10:29 init.usb.rc
-rw-r--r-- root root 340 2013-01-15 10:29 lpm.rc
drwxr-xr-x root root 2013-01-14 22:02 lvm
drwxrwxr-x root system 2013-01-15 10:29 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwxr-xr-x root root 2013-01-14 21:28 radio
drwxr-xr-x root root 2013-01-15 10:29 res
drwxr-x--- root root 2013-01-15 10:29 sbin
lrwxrwxrwx root root 2013-01-15 10:29 sdcard -> /storage/sdcard0
d---r-x--- root sdcard_r 2013-01-15 10:29 storage
drwxr-xr-x root root 2013-01-15 10:29 sys
drwxr-xr-x root root 2013-01-11 17:01 system
-rw-r--r-- root root 1489 2013-01-15 10:29 ueventd.aries.rc
-rw-r--r-- root root 272 2013-01-15 10:29 ueventd.goldfish.rc
-rw-r--r-- root root 5220 2013-01-15 10:29 ueventd.rc
lrwxrwxrwx root root 2013-01-15 10:29 vendor -> /system/vendor
file system view when in recovery
Code:
drwxr-xr-x 18 root root 0 Jan 15 00:12 .
drwxr-xr-x 18 root root 0 Jan 15 00:12 ..
drwxr-xr-x 3 root root 0 Jan 15 00:12 acct
-rw-r--r-- 1 root root 586 Jan 15 00:12 boot.txt
drwxrwx--x 1 system cache 4096 Jan 14 23:29 cache
-rwxr-x--- 1 root root 264080 Jan 15 00:12 charger
dr-x------ 2 root root 0 Jan 15 00:12 config
lrwxrwxrwx 1 root root 17 Jan 15 00:12 d -> /sys/kernel/debug
drwxrwx--x 12 system system 0 Jan 15 00:12 data
-rw-r--r-- 1 root root 2887 Jan 15 00:12 default.prop
drwxr-xr-x 13 root root 3040 Jan 15 00:12 dev
drwxr-xr-x 2 root root 0 Jan 15 00:12 efs
d--------- 2 system system 0 Jan 15 00:12 emmc
drwxr-xr-x 2 root root 0 Jan 15 00:12 etc
-rw-r----- 1 root root 568 Jan 15 00:12 fstab.aries
-rwxr-x--- 1 root root 109484 Jan 15 00:12 init
-rwxr-x--- 1 root root 10349 Jan 15 00:12 init.rc
-rw-r--r-- 1 root root 340 Jan 15 00:12 lpm.rc
drwxr-xr-x 4 root root 0 Jan 14 11:02 lvm
dr-xr-xr-x 73 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 15 00:12 res
drwxr-x--- 2 root root 0 Jan 15 00:12 sbin
d--------- 2 system system 0 Jan 15 00:12 sdcard
drwxr-xr-x 12 root root 0 Jan 15 00:12 sys
drwxr-xr-x 3 root root 0 Jan 15 00:12 system
drwxr-xr-x 2 root root 0 Jan 15 00:12 tmp
-rw-r--r-- 1 root root 1489 Jan 15 00:12 ueventd.aries.rc
-rw-r--r-- 1 root root 272 Jan 15 00:12 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5220 Jan 15 00:12 ueventd.rc
-rw-r--r-- 1 root root 3899 Jan 15 00:12 usb.rc
lrwxrwxrwx 1 root root 14 Jan 15 00:12 vendor -> /system/vendor
I hope they give some kind of clue.
please help.
thanks

transact said:
Yeah, multiple times.
I hope they give some kind of clue.
please help.
thanks
Click to expand...
Click to collapse
That's a really weird and detailed explanation .. however I am unable to explain the behaviour of your phone.. what I can suggest is formating the sd card too (if you have backup of data that is) and format /system too manually along with wiping data, cache and dalvik cache.. after that flash CM10.1 nightly twice.. don't flash gapps atm.. after that reboot recovery.. wipe data, cache again (not /system this time) and flash nightly again.. fix permissions and then reboot..
I know repetition like this doesn't make much sense but nor does your problem..
Hope this will help.

if you are comeing from cm10.0 ant flashing cm10.1 it is recommend to wipe /system befor flashing

my note has no service after trying to install cwm recovery using terminal emulator

hello guys .. i dont know if this is the right place to post this since this is my first post .. sorry .
my phone has no service .. i think some of the /dev blocks is corrupted .. tried restoring /efc using twrp but no luck .. i tried installing cwm using terminal emulator after downloading a marshmallow rom with a faulty recovery ..
so i want to ask .. does installing a stock rom reset the /dev blocks values ? or is there any other way that i can get my service back ? i searched threads but no luck finding any solution .. any help will be appreciated .. if you need any more info to help me just ask please .. and i tried doing so because i had no access to a pc at that time .. thank you

Can you check in settings>phone and see if your baseband/imei is written?

AutumQueen92 said:
Can you check in settings>phone and see if your baseband/imei is written?
Click to expand...
Click to collapse
Baseband version, imei, network, mobile network type, imei sv, Bluetooth address... All unknown...
Running biftor slimkat v11.0 if that helps

N00b... said:
Baseband version, imei, network, mobile network type, imei sv, Bluetooth address... All unknown...
Running biftor slimkat v11.0 if that helps
Click to expand...
Click to collapse
Ahhh, I see the problem. Your IMEI got erased, I do not have the solution for that sorry. Maybe try googling around?

AutumQueen92 said:
Ahhh, I see the problem. Your IMEI got erased, I do not have the solution for that sorry. Maybe try googling around?
Click to expand...
Click to collapse
No luck... Been searching since I woke up... I have backed up /efs... Restoring it was supposed to do the trick. But it doesn't work... Nothing changes when I restore it... Tried flashing different kk roms but none of them work... Will try to flash stock rom once I get back home... Not in a hurry for a solution since this is not the phone I use everyday... Got a nexus 6p 2 weeks ago

N00b... said:
No luck... Been searching since I woke up... I have backed up /efs... Restoring it was supposed to do the trick. But it doesn't work... Nothing changes when I restore it... Tried flashing different kk roms but none of them work... Will try to flash stock rom once I get back home... Not in a hurry for a solution since this is not the phone I use everyday... Got a nexus 6p 2 weeks ago
Click to expand...
Click to collapse
Have you tried setting the permissions of the folder for the efs backup? the phone will not accept folders placed without the proper permission.

You should change permission of efs backup folder as AutumQueen92 mentioned above.

AutumQueen92 said:
Have you tried setting the permissions of the folder for the efs backup? the phone will not accept folders placed without the proper permission.
Click to expand...
Click to collapse
It already has full permissions rwxrwxrwx

N00b... said:
It already has full permissions rwxrwxrwx
Click to expand...
Click to collapse
I don't think that's the right permission. Try rwx --- --- ? I'm not sure of the actual config but google should find some answers. Other than that, I can't help much.
Edit: I was curious myself since I'm re-using my Note.
Code:
permissions / owners / timestamp / file
-rw-r--r-- root root 1 2010-12-31 16:00 cryptprop_rebootMode
-rw-r--r-- root root 0 2011-07-18 15:16 cryptprop_onetimeboot
-rw-r--r-- root root 3 2011-07-17 11:56 cryptprop_securewipedata
drwxrwxr-x root root 2000-01-01 01:03 .files
-rwx------ radioradio 2097152 2011-07-17 12:29 nv_data.bin
-rw-rw-rw- radio radio 1065 2010-12-31 16:00 nv.log
-rwx------ radio radio 32 2011-07-17 12:29 nv_data.bin.md5
drwx------ system system 2010-12-31 16:01 dmp
-rw-r--r-- system system 9 2010-12-31 16:01 cryptprop_applied_result
drwxrwxr-x radio radio 2011-05-21 04:10 imei
-rw-rw-rw- system system 6 2000-01-01 01:04 calibration_data
-rwx------ radio radio 1048576 2010-12-31 16:00 .nv_core.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_core.bak.md5
-rwx------ radio radio 2097152 2010-12-31 16:00 .nv_data.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_data.bak.md5
-rw-rw-rw- radio radio 1 2010-12-31 16:00 .nv_state
-rw-r--r-- system system 3 2011-07-17 03:00 cryptprop_persist.sys.language
-rwxrwxr-- radio radio 880 2010-12-31 16:02 redata.bin
-rw-rw-rw- system system 256 2010-12-31 16:00 edk_p
-rw-r--r-- system system 18 2011-07-17 03:00 cryptprop_persist.sys.timezone
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lock_pattern_autolock
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lockscreen.password_type
-rw-r--r-- system system 5 2011-07-09 22:41 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- system system 5 2011-06-19 09:09 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- system system 6 2011-06-05 00:53 cryptprop_lock_pattern_tactile_feedback_enabled

AutumQueen92 said:
I don't think that's the right permission. Try rwx --- --- ? I'm not sure of the actual config but google should find some answers. Other than that, I can't help much.
Edit: I was curious myself since I'm re-using my Note.
Code:
permissions / owners / timestamp / file
-rw-r--r-- root root 1 2010-12-31 16:00 cryptprop_rebootMode
-rw-r--r-- root root 0 2011-07-18 15:16 cryptprop_onetimeboot
-rw-r--r-- root root 3 2011-07-17 11:56 cryptprop_securewipedata
drwxrwxr-x root root 2000-01-01 01:03 .files
-rwx------ radioradio 2097152 2011-07-17 12:29 nv_data.bin
-rw-rw-rw- radio radio 1065 2010-12-31 16:00 nv.log
-rwx------ radio radio 32 2011-07-17 12:29 nv_data.bin.md5
drwx------ system system 2010-12-31 16:01 dmp
-rw-r--r-- system system 9 2010-12-31 16:01 cryptprop_applied_result
drwxrwxr-x radio radio 2011-05-21 04:10 imei
-rw-rw-rw- system system 6 2000-01-01 01:04 calibration_data
-rwx------ radio radio 1048576 2010-12-31 16:00 .nv_core.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_core.bak.md5
-rwx------ radio radio 2097152 2010-12-31 16:00 .nv_data.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_data.bak.md5
-rw-rw-rw- radio radio 1 2010-12-31 16:00 .nv_state
-rw-r--r-- system system 3 2011-07-17 03:00 cryptprop_persist.sys.language
-rwxrwxr-- radio radio 880 2010-12-31 16:02 redata.bin
-rw-rw-rw- system system 256 2010-12-31 16:00 edk_p
-rw-r--r-- system system 18 2011-07-17 03:00 cryptprop_persist.sys.timezone
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lock_pattern_autolock
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lockscreen.password_type
-rw-r--r-- system system 5 2011-07-09 22:41 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- system system 5 2011-06-19 09:09 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- system system 6 2011-06-05 00:53 cryptprop_lock_pattern_tactile_feedback_enabled
Click to expand...
Click to collapse
My efs folder was corrupted .. Same goes for my dev folder .. Tried the first approach that any sane person would do .. Flash a stock ROM .. After lots of searching I found the n7000xxlso stock ROM and flashed it .. Everything worked like a charm .. Then I installed philz and flashed slimkat again .. Now everything is working

No CSC folder in stock MM?

In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?

SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?

pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018

SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.

pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes

SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.

pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!

Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.

Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!

SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.

pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468

pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!

You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.