Database Develop

wpa_supplicant.conf resets permission after boot

I have modified wpa_supplicant.conf and after every reboot of the phone, the permissions are reset:
# cd /data/misc/wifi
# ls -ltr
drwxrwx--- 1 1010 1010 2048 Sep 2 18:27 sockets
-rw-rw---- 1 0 0 744 Sep 3 06:15 wpa_supplicant.conf
In order for wireless to work I need to reset perms to 666 as Wifi does not switch on:
/SettingsWifiEnabler( 3196): Received wifi state changed from Unknown to Enabling
E/WifiHW ( 1422): Cannot access "/data/misc/wifi/wpa_supplicant.conf": Permission denied
E/WifiHW ( 1422): Wi-Fi will not be enabled
How can I make the permissions stick?

try to booting into recovery go to console ,then
mount /data
chmod 666 /data/misc/wifi/wpa_supplicant.conf
may or may not work

ubernicholi said:
try to booting into recovery go to console ,then
mount /data
chmod 666 /data/misc/wifi/wpa_supplicant.conf
may or may not work
Click to expand...
Click to collapse
I did that a number of times. in recovery mode after chmoding to 666 permissions show as
-rw-rw-rw- 1 0 0 744 Sep 3 06:15 wpa_supplicant.conf
after reboot it shows as
-rw-rw---- 1 0 0 744 Sep 3 06:15 wpa_supplicant.conf
Not sure how to overcome this as it appears that the reboot process changes the permissions back (perhaps a Cyanogen problem - running on 4.0.4??)

if your running cyanogen's rom couldn't you just put the chmod command in the userinit.sh. welll that is if you have a ext partition

Please read stickies before posting. This should be in the Q&A forum.

problem solved by placing the following into userinit.sh. still strange that something changes the permissions and ownership of that file during boot-process.
if [ -d /data/misc/wifi ];
then
busybox chown 1000:1000 /data/misc/wifi/wpa_supplicant.conf;
busybox chmod 666 /data/misc/wifi/wpa_supplicant.conf;
echo "Changed permissions for wpa_supplicant.conf"
fi;

I found this to be working permanently:
The solution was to simply change ownership back to system:wifi
$ adb root
$ adb -d shell
# cd /data/misc/wifi
# chown system.wifi wpa_supplicant.conf
# reboot
Click to expand...
Click to collapse
Found somewhere. Sorry, I've not bookmarked the link.

thank you!

clean copy of wpa_supplicant.conf
Hey all. New to the forum. was wondering if any has an original copy of the wpa_supplicant.conf file for the flytouch2. i was doing some experimenting and fudged it up real good. thanks in advancd

Hey just wanted to thank you for this thread.. saved me a lot of time on a project
stupid ownership.

Thanks. This post helped me too...

Me too. Thanks

Thanks!
I can't believe I never did a search on the XDA forums for this issue, which has been plaguing me for months.
Well actually "plaguing" is probably too strong a word, but it is usually the little annoyances that drive me up the wall way more than the large problems!
that is all
pam

another way to solve
hello,
I've had similar issues after modifiying the file with ES Explorer. The problem is that the app not only rewrites the permissions of the file but also the owner and group. Fortunately the app stores a .bak file so i could "ls-l" the correct file settings.
U should use
chmod 660 wpa_supplicant.conf (by default and not 666!)
and
chown system.wifi wpa_supplicant.conf (sets owner to system and group to wifi)
Good luck!

I've been having simmular problem:
While back I have edited the same file (using ES file explorer app) and ever since then everytime i reboot my wifi wont switch on (instead it just shows an error in status field)
So far solution i had to use is to open the wpa_supplicant.conf file in ES and "edit and save" it... So pretty much even if i type in and erase a random character, and then try to exit ES asks if i want to save. Click yes and go to settings and wifi is switching on no prob...
Does this seem like I should use one of the solutions posted above, or is there some other resolution to my problem?
Im running Gingerbread on HTC doubleshot.
I appreciate any help given!
Thanks in advance.

thank you!

Just wanted to say thank you,

can anybody help me with this command line

this used to work when i did on my mytouch
cd /data/app-private/
ls
cp */sdcard
when i enter the command on my nexus i get error
cp: cant stat '*': no such file or directory
can some body please tell me how properly write the comand for a nexus one

What exactly are you trying to accomplish with the command? Are you trying to copy everything from /data/app-private/ onto your microSDHC card? If so, I would just (as root), do:
cp /data/app-private/* /sdcard
Make sure that you su to root before issuing the command, or you will get a permission denied error.

doesnt work either

What are you trying to do?
Can you link the place where you originally saw this command?

napoleontheruler said:
cd /data/app-private/
ls
cp */sdcard
Click to expand...
Click to collapse
so from the command and the errors you get using your and nathanzachary's version it looks like
a) your missing a space between * and /
b) you need root access to read anything in /data
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.

FloOGB said:
so from the command and the errors you get using your and nathanzachary's version it looks like
a) your missing a space between * and /
b) you need root access to read anything in /data
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.
Click to expand...
Click to collapse
i know about the space typo. "ls" shows all of the protected apps on your device. this command line would basically let you save any protected app to the devices sdcard. in a nut shell paid apps for free but it wont work on my nexus. can anyone figure out what the command line should be for a nexus.
i am running cm 5.0.5.3 if it helps any

"ls" is the same as "dir" in windows. it just lists the content of the directory you changed into with "cd". thats why we need to see the complete output of your console session. that includes your input, the output and the error messages. this is the reason i wanted to see an "ls -al" to see the access rights of that directory. if you dont want us to see the aps than please cut out the names, but leave all dots
this is up till know a purley "linux" problem, we just need the right data.
EDIT: and do an "id" please, just after the ls -al, copy that output as well.

FloOGB said:
"ls" is the same as "dir" in windows. it just lists the content of the directory you changed into with "cd". thats why we need to see the complete output of your console session. that includes your input, the output and the error messages. this is the reason i wanted to see an "ls -al" to see the access rights of that directory. if you dont want us to see the aps than please cut out the names, but leave all dots
this is up till know a purley "linux" problem, we just need the right data.
EDIT: and do an "id" please, just after the ls -al, copy that output as well.
Click to expand...
Click to collapse
drwxrwx--x 1 system system 2048 Mar 22 21:51
drwxrwx--x 1 system system 2048 Mar 25 18:04
i dont know if that will help

FloOGB said:
we need to see the complete output of your console session
Click to expand...
Click to collapse
something like
Code:
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
I just want to see which user you are on the shell and if the access rights match. Because if you are not root you don't even have list rights on that directory, which causes the "cant stat *" message
Did you root you N1? How do you access the shell? ADB? SSH? App? This is getting pointless

FloOGB said:
This is getting pointless
Click to expand...
Click to collapse
that's a little harsh on him...
he is having problems. be understanding. everyone has to start somewhere.
but, flo is correct, we need more detail on how you're commanding, and you'll definitely need root access

FloOGB said:
something like
Code:
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
I just want to see which user you are on the shell and if the access rights match. Because if you are not root you don't even have list rights on that directory, which causes the "cant stat *" message
Did you root you N1? How do you access the shell? ADB? SSH? App? This is getting pointless
Click to expand...
Click to collapse
ok first of all how would it be possible to run cm 5.0.5.3 witch i posted my n1 is currently running if i didnt have root. i am using this coomand as i have been through better terminal emulator. if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so. besides what is the point of terminal emulator, adb, or fastboot without root.

napoleontheruler said:
ok first of all how would it be possible to run cm 5.0.5.3 witch i posted my n1 is currently running if i didnt have root. i am using this coomand as i have been through better terminal emulator. if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so. besides what is the point of terminal emulator, adb, or fastboot without root.
Click to expand...
Click to collapse
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
Click to expand...
Click to collapse
1) adb shell
2) bash
3) id
4) cd /data/app-private/
5) ls -al
6) cp * /sdcard
Basically anything after bash-4.1# is a command.

napoleontheruler said:
if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so.
Click to expand...
Click to collapse
I did? Multiple times?
FloOGB said:
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.
Click to expand...
Click to collapse
FloOGB said:
EDIT: and do an "id" please, just after the ls -al, copy that output as well.
Click to expand...
Click to collapse
Thats the reason why i got a bit frustrated, sorry. archangelugp posted the command sequence.

archangelugp said:
1) adb shell
2) bash
3) id
4) cd /data/app-private/
5) ls -al
6) cp * /sdcard
Basically anything after bash-4.1# is a command.
Click to expand...
Click to collapse
do i run in terminal emulator or adb connect

napoleontheruler said:
do i run in terminal emulator or adb connect
Click to expand...
Click to collapse
Whichever method you use you'll have to use the su command to get root access first.
Connect your phone to your computer via USB cable, and make sure USB debugging is enabled on your phone (Settings > Applications > Development)
Enter adb shell to fire up Debug Bridge and enter shell mode
Enter su to become superuser
Enter cat /data/app-private/filename.apk > /sdcard/filename.apk to copy the file to the SD card.
exit
exit
Click to expand...
Click to collapse
I didn't want to reinvent the wheel so I pasted this from here. Both methods are shown.

wind0zer said:
Whichever method you use you'll have to use the su command to get root access first.
I didn't want to reinvent the wheel so I pasted this from here. Both methods are shown.
Click to expand...
Click to collapse
i was talking about what command line to find the output info and if i should run that though terminal emulator or adb.the link is were i got the command line from. so r u telling me that the termial emulator method will not work on the nexus.

Yes you can use the terminal in the phone to back up your paid apps.
Which part of the steps (in the link) do you not understand?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

Why so troublesome.
By using below two apps, you can simply copy out your purchase & install apps:
- Root Explorer
- Titanium Backup

Yeah, my guess was that he isn't logged in as root, thats why I need the output of "id".
I think it doesn't matter how you access the phone, trough a terminal emulator on the phone or though adb.
Just write us down the uid and gid value from "id", that should be little enough text to copy manually
for example, write down the red part:
bash-4.1# id
uid=0(root) gid=0(root)

Optimus 4x bootloader / bct / flash.cfg dump from kdz

This is the Optimus 4x bootloader / bct / flash.cfg dump from kdz
http://cafe.naver.com/androidhacker/487 (in Korean)
kdz file can be extracted with LGExtract.exe
The extracted *.dz file is very similar with the old style dz file.
So I can extract it manually (please see the above link)
the old style dz file format: http://www.frenchcoder.com/dzextract-lg-dz-file-format-and-extract-tool-lg-ks20/
Im not sure It is worth for Optimus 4x
(I don't have Optimus 4x and I can't test it)
but you can try the following recent nvflash crack~
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
happy hacking~
Changes
●dzextract script added
●flash.bct.encrypt file added
-----
EDIT:
SBK Detector for Transformer by [email protected]
http://forum.xda-developers.com/showthread.php?t=1232612 v1
http://forum.xda-developers.com/showthread.php?t=1290503 v2
See also http://www.xda-developers.com/android/sbk-detection-tool-for-the-asus-transformer/
SBK is leaked for Transformer...

nice, someone is testing it? cause i don't have a linux (downloading now, lol)
@down nah, f*ck.

wkpark said:
This is the Optimus 4x bootloader / bct / flash.cfg dump from kdz
http://cafe.naver.com/androidhacker/487 (in Korean)
Click to expand...
Click to collapse
so now we just need the secret SBK key, which is somewhere in the kdz or in the upgrade modem firmware as well.
otherwise those files are worthless, since you cannot boot without a SBK.
and that is IF you get the sbk extracted and they got the device open and you got the driver in place.

Dexter_nlb said:
so now we just need the secret SBK key, which is somewhere in the kdz or in the upgrade modem firmware as well.
otherwise those files are worthless, since you cannot boot without a SBK.
and that is IF you get the sbk extracted and they got the device open and you got the driver in place.
Click to expand...
Click to collapse
Yes the hardest part! already mentioned at androidroot.mobi
http://androidroot.mobi/technical/tf-secure-boot-key/

wkpark said:
This is the Optimus 4x bootloader / bct / flash.cfg dump from kdz
http://cafe.naver.com/androidhacker/487 (in Korean)
kdz file can be extracted with LGExtract.exe
The extracted *.dz file is very similar with the old style dz file.
So I can extract it manually (please see the above link)
the old style dz file format: http://www.frenchcoder.com/dzextract-lg-dz-file-format-and-extract-tool-lg-ks20/
Im not sure It is worth for Optimus 4x
(I don't have Optimus 4x and I can't test it)
but you can try the following recent nvflash crack~
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
happy hacking~
Click to expand...
Click to collapse
Thanks for the info. I will start doing some hacking

_RSAobj said:
Thanks for the info. I will start doing some hacking
Click to expand...
Click to collapse
the bootloader do seem to contain "unlock" functionality, and it does also seem to support blob files , so one of the partitions should be able to contain a flashable blob like on prime. but still without unlocking mechanism, those blob's need signing too.

Dexter_nlb said:
the bootloader do seem to contain "unlock" functionality, and it does also seem to support blob files , so one of the partitions should be able to contain a flashable blob like on prime. but still without unlocking mechanism, those blob's need signing too.
Click to expand...
Click to collapse
thanks to all of you guys for your passion and for your help in trying to make the 4x an even better phone!

Hm, i hope we'll get the early christmas present soon
It's really good that we've a clue
@The Troll Like u see, it works, but it needs sth to work, like Dexter said
Sent from my LG-P880 using xda premium

did anyone extract and confirm?
i tried dz-extract loonnnggg ago but didnt seem to work
too sleepy atm to check..
temme what to do in the morning
i got ubuntu installed and v10c and f downloaded aleady

The Troll said:
did anyone extract and confirm?
i tried dz-extract loonnnggg ago but didnt seem to work
too sleepy atm to check..
temme what to do in the morning
i got ubuntu installed and v10c and f downloaded aleady
Click to expand...
Click to collapse
Yes, I managed to extract it. Thanks to the hint above.
For the first, got the flash.cfg and bootloader.bin. Will continue tomorrow.

I love this community!!!

so we got the bootloader..
what are the chances of it being unlocked?
i mean suppose we find the sbk keys in there..
what else will we need? and how do we get it?

The Troll said:
did anyone extract and confirm?
i tried dz-extract loonnnggg ago but didnt seem to work
too sleepy atm to check..
temme what to do in the morning
i got ubuntu installed and v10c and f downloaded aleady
Click to expand...
Click to collapse
ok Ive just added my dzextact script
and dump "flash.bct.encrypt" file found at the BCT_ENCRYPT subfile entry.
The Troll said:
so we got the bootloader..
what are the chances of it being unlocked?
i mean suppose we find the sbk keys in there..
what else will we need? and how do we get it?
Click to expand...
Click to collapse
I guess P880 have "fused" SBK that's why the flash.bct.encrypt found in the kdz.
See also http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf

LG's old tegra2 devices have no SBK (P990/P999/SU660)
and some fuse information can be obtained via sysfs
(for kernel 2.6.39)
arch/arm/mach-tegra/tegra_odm_fuses.c
http://nv-tegra.nvidia.com/gitweb/?...62fd10ddbae8bed780ca80204efe11ee8;hb=rel-14r7
for SU660(P990 variant)
Code:
# busybox uname -a
Linux localhost 2.6.39.4-gb348b1e #1 SMP PREEMPT Sun Oct 28 01:37:22 KST 2012 armv7l unknown
# ls /sys/firmware/fuse
device_key
ignore_dev_sel_straps
jtag_disable
odm_production_mode
odm_reserved
sec_boot_dev_cfg
sec_boot_dev_sel
secure_boot_key
sw_reserved
Code:
[email protected]:/sys/firmware/fuse # cat secure_boot_key
0x00000000000000000000000000000000
How about P880 ?
----
Edit:
See also http://forum.xda-developers.com/showthread.php?t=1847950
I guess the fuse information work correctly only for a developer version

is fused a good news or bad?
what are the chances of this being unlocked? :/
should i sell it off or not? :/

wkpark said:
LG's old tegra2 devices have no SBK (P990/P999/SU660)
and some fuse information can be obtained via sysfs
(for kernel 2.6.39)
arch/arm/mach-tegra/tegra_odm_fuses.c
http://nv-tegra.nvidia.com/gitweb/?...62fd10ddbae8bed780ca80204efe11ee8;hb=rel-14r7
for SU660(P990 variant)
Code:
# busybox uname -a
Linux localhost 2.6.39.4-gb348b1e #1 SMP PREEMPT Sun Oct 28 01:37:22 KST 2012 armv7l unknown
# ls /sys/firmware/fuse
device_key
ignore_dev_sel_straps
jtag_disable
odm_production_mode
odm_reserved
sec_boot_dev_cfg
sec_boot_dev_sel
secure_boot_key
sw_reserved
Code:
[email protected]:/sys/firmware/fuse # cat secure_boot_key
0x00000000000000000000000000000000
How about P880 ?
----
Edit:
See also http://forum.xda-developers.com/showthread.php?t=1847950
I guess the fuse information work correctly only for a developer version
Click to expand...
Click to collapse
Code:
[email protected]:/sys/firmware/fuse # ls -la
-rw-rw-r-- radio system 4096 2012-10-29 07:21 device_key
-rw-rw-r-- radio system 4096 2012-10-29 07:21 ignore_dev_sel_straps
-rw-rw-r-- radio system 4096 2012-10-29 07:21 jtag_disable
-rw-rw-r-- radio system 4096 2012-10-29 07:21 odm_production_mode
-rw-rw-r-- radio system 4096 2012-10-29 07:21 odm_reserved
-rw-rw-r-- radio system 4096 2012-10-29 07:21 sec_boot_dev_cfg
-rw-rw-r-- radio system 4096 2012-10-29 07:21 sec_boot_dev_sel
-rw-rw-r-- radio system 4096 2012-10-29 07:21 secure_boot_key
-rw-rw-r-- radio system 4096 2012-10-29 07:21 sw_reserved
Code:
[email protected]:/sys/firmware/fuse $ su
[email protected]:/sys/firmware/fuse # cat secure_boot_key
[email protected]:/sys/firmware/fuse #
Code:
[email protected]:/sys/firmware/fuse # cat device_key
0xffffffff
[email protected]:/sys/firmware/fuse # cat ignore_dev_sel_straps
0x00000001
[email protected]:/sys/firmware/fuse # cat jtag_disable
0x00000000
[email protected]:/sys/firmware/fuse # cat odm_production_mode
0x00000001
[email protected]:/sys/firmware/fuse # cat odm_reserved
0x0000000000000000000000000000000000000000000000000000000000000000
[email protected]:/sys/firmware/fuse # cat sec_boot_dev_cfg
0x00000011
[email protected]:/sys/firmware/fuse # cat sec_boot_dev_sel
0x00000000
[email protected]:/sys/firmware/fuse # cat secure_boot_key
[email protected]:/sys/firmware/fuse # cat sw_reserved
0x00000000

wkpark said:
Code:
[email protected]:/sys/firmware/fuse # cat secure_boot_key
0x00000000000000000000000000000000
How about P880 ?
Click to expand...
Click to collapse
i believe life is not that simple. secret are to remain secrets until revealed by improper handling , this would have been plain stupid to enable if it was shown here.

Dexter_nlb said:
i believe life is not that simple. secret are to remain secrets until revealed by improper handling , this would have been plain stupid to enable if it was shown here.
Click to expand...
Click to collapse
I just make it clear
anyway LG sometime do stupid things like as leaking their RSA keys for some locked omap4 devices

so.. can someone temme whats with the fused sbk?
and if its even possible to get it?

Hi there.
I want to buy this phone and was just around on this forum for some weeks. Now i have an optimus black and in our forum an user made a tool for extracting al tables and content from kdz files. I dont know if it will work for 4x hd but have a look here and maybe dexter or other devs will come with some ideas.
http://forum.xda-developers.com/showthread.php?t=1566532
And here for an attemp to boot from sdcard http://forum.xda-developers.com/showthread.php?t=1960047.
Sorry for my awfull english.

DDMS: Unable to open log device

I am currently on PA2.57, some kind of CM10.1 version. I try to connect with Eclipse DDMS to check something in the logcat, but there it mentions:
Unable to open log device '/dev/log/main': No such file or directory.
[email protected]:/dev # pwd
pwd
/dev
[email protected]:/dev # ls l*
ls l*
light link_pm
[email protected]d:/dev # cd /system/bin
cd /system/bin
[email protected]:/system/bin # ls -l log*
ls -l log*
lrwxrwxrwx 1 root root 7 Jan 23 15:43 log -> toolbox
-rwxr-xr-x 1 root shell 13672 Aug 1 2008 logcat
-rwxr-xr-x 1 root shell 9592 Aug 1 2008 logwrapper
[email protected]:/system/bin #
Click to expand...
Click to collapse
I am confused, cause the logcat is there, but why is there no proper dir? Can anybody help how to set up the dirs properly? Is this related with CM? or..

Roland_SGN said:
I am currently on PA2.57, some kind of CM10.1 version. I try to connect with Eclipse DDMS to check something in the logcat, but there it mentions:
Unable to open log device '/dev/log/main': No such file or directory.
I am confused, cause the logcat is there, but why is there no proper dir? Can anybody help how to set up the dirs properly? Is this related with CM? or..
Click to expand...
Click to collapse
Your kernel or an app that controls the kernel has the logging disabled. You need to enable logging in order for /dev/log/main to be created and be viewed with Eclipse or a log app. Look for the disable/enable log in the kernel app. If there isn't one then you need to consult the dev responsible for the custom ROM with his/her preferred kernel or consult the creator of that specific kernel.

[Q] Wifi not working

My wiifi is not working, it's a XT1056 , software 4.4.2.
<6>[ 34.137372,1] wlan: loading driver v3.2.6.114.1220.3
<3>[ 34.137494,1] wlan: [960:F :HDD] hdd_driver_init: WLAN device not found!!
<3>[ 34.137616,1] wlan: driver load failure
Click to expand...
Click to collapse

bean1975 said:
My wiifi is not working, it's a XT1056 , software 4.4.2.
Click to expand...
Click to collapse
Please see the post I directed you to in the sim-unlock thread.

This is what I have in my persist directory:
ls /persist/*bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Click to expand...
Click to collapse

bean1975 said:
Code:
ls /persist/*bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Click to expand...
Click to collapse
Yep, you are missing the factory file: WCNSS_qcom_wlan_nv.bin
Download it! It's linked here: http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
Post # 7. Then put only the missing file in /persist, and change the permissions (they might be set correctly already). Reboot and wifi should be back up

No, it's right there, look at my post.
-rw-r--r-- root root 29776 2013-09-21 18:40 WCNSS_qcom_wlan_nv.bin

bean1975 said:
No, it's right there, look at my post.
-rw-r--r-- root root 29776 2013-09-21 18:40 WCNSS_qcom_wlan_nv.bin
Click to expand...
Click to collapse
Ohhhh my bad! So it looks like you are missing this one: .bt_nv.bin
Is that correct?

adb shell su -c 'ls -la' /persist
-rw-rw---- bluetooth bluetooth 9 2013-09-21 18:35 .bt_nv.bin
that's there too. I just didnt hunt for hidden files.

bean1975 said:
adb shell su -c 'ls -la' /persist
-rw-rw---- bluetooth bluetooth 9 2013-09-21 18:35 .bt_nv.bin
that's there too. I just didnt hunt for hidden files.
Click to expand...
Click to collapse
Bummer. Then based on your original post:
hdd_driver_init: WLAN device not found!!
I would have to assume an actual hardware failure. That's too bad....
I really don't have any further advice or suggestions for you -- except for to maybe consider trying to flash the entire 4.4.2 SBF and return to 100% stock and see if it might fix the issue (assuming you haven't tried this already). I'm wondering if the seller didn't sell you a bad unit...

Yeah, probably hw fail, oh well, not a big deal.