Wifi don't work? Flash this! /Persist Repair

Search This thread
By:
Advanced…
Boss442

Boss442

Senior Member
Jul 19, 2012
428
551
28
Mar Del Plata
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).

Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.

:highfive:

Download from:
MEDIAFIRE!
MEGA!
 
Last edited:
  • Like
Reactions: NoobByn-tek, Bhaskara Rao, Fedroid and 3 others
P

pushkaraj_d

Senior Member
Jan 16, 2013
105
5
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).

Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.

:highfive:

Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Bro how to flash it ?
I flashed with twrp v3.0
it gave an error at the end. unable to mount something.
wifi is not working on my mot g2013. I have tried 5-6 roms.
Pls help
 
P

pushkaraj_d

Senior Member
Jan 16, 2013
105
5
No it dint.

Twrp gave error. Also the file whicg have to copy in that persist folder gets deleted automatically.
 
D

Deleted member 7332069

Guest
This works

OK, this works but not exactly by flashing.

First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.

Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code: 
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code: 
adb shell
7.
Code: 
mount -o rw,remount /persist
8.
Code: 
exit
- we are exiting shell now
9.
Code: 
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code: 
adb shell
12.
Code: 
mount -o ro,remount /persist
13.
Code: 
exit
14. Reboot your phone

If you have unsufficient permissions or something, try
Code: 
chmod 777 /persist
after point 7 and
Code: 
chmod 771 /persist
after point 11

Tell me if it works, was ok for me.
 
  • Like
Reactions: Bhaskara Rao and norte112
N

norte112

New member
Apr 26, 2014
4
0
Tucuman
zyzioziom said:
OK, this works but not exactly by flashing.

First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.

Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code: 
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code: 
adb shell
7.
Code: 
mount -o rw,remount /persist
8.
Code: 
exit
- we are exiting shell now
9.
Code: 
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code: 
adb shell
12.
Code: 
mount -o ro,remount /persist
13.
Code: 
exit
14. Reboot your phone

If you have unsufficient permissions or something, try
Code: 
chmod 777 /persist
after point 7 and
Code: 
chmod 771 /persist
after point 11

Tell me if it works, was ok for me.
Click to expand...
Click to collapse

Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.

I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "

Would you help me please?
 
D

Deleted member 7332069

Guest
norte112 said:
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.

I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "

Would you help me please?
Click to expand...
Click to collapse

norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
 
  • Like
Reactions: norte112
N

norte112

New member
Apr 26, 2014
4
0
Tucuman
zyzioziom said:
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
Click to expand...
Click to collapse

The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
 
D

Deleted member 7332069

Guest
norte112 said:
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
Click to expand...
Click to collapse

Code: 
adb shell
ls -al

And paste the results here

Also, try whole process again but after each "adb shell" add another command: "su"
 
  • Like
Reactions: norte112
N

norte112

New member
Apr 26, 2014
4
0
Tucuman
zyzioziom said:
Code: 
adb shell
ls -al

And paste the results here

Also, try whole process again but after each "adb shell" add another command: "su"
Click to expand...
Click to collapse

Deputy results:

D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←8shell@falcon:/ $

I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):

D:\xt1032\ABD-fastboot>adb root
adbd is already running as root

D:\xt1032\ABD-fastboot>adb shell su
root@falcon:/ #
 
D

Deleted member 7332069

Guest
norte112 said:
Deputy results:

D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←8shell@falcon:/ $

I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):

D:\xt1032\ABD-fastboot>adb root
adbd is already running as root

D:\xt1032\ABD-fastboot>adb shell su
root@falcon:/ #
Click to expand...
Click to collapse

You have strange results here :/
Here is my console:
Code: 
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1	device

Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
root@falcon:/ # ls -al
total 2382
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 .
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 ..
drwxr-xr-x  44 root   root        0 1970-06-28 19:00 acct
drwxrwx---   6 system cache    4096 2016-03-05 03:28 cache
lrwxrwxrwx   1 root   root       13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------   2 root   root        0 1970-06-28 19:00 config
lrwxrwxrwx   1 root   root       17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x  35 system system   4096 2016-03-09 18:37 data
-rw-r--r--   1 root   root      555 1970-01-01 01:00 default.prop
drwxr-xr-x  15 root   root    15300 1970-06-28 19:00 dev
lrwxrwxrwx   1 root   root       11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r--   1 root   root    53465 1970-01-01 01:00 file_contexts
drwxr-xr-x   4 root   root     4096 1970-01-01 01:00 firmware
drwxr-xr-x   3 root   root     1024 1970-01-01 01:00 fsg
-rw-r-----   1 root   root     2468 1970-01-01 01:00 fstab.qcom
-rwxr-x---   1 root   root   639808 1970-01-01 01:00 init
-rwxr-x---   1 root   root     8581 1970-01-01 01:00 init.cm.rc
-rwxr-x---   1 root   root      983 1970-01-01 01:00 init.environ.rc
-rwxr-x---   1 root   root     3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x---   1 root   root     4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x---   1 root   root    29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x---   1 root   root     4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x---   1 root   root    11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x---   1 root   root    26983 1970-01-01 01:00 init.rc
-rwxr-x---   1 root   root     1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x---   1 root   root      319 1970-01-01 01:00 init.superuser.rc
-rwxr-x---   1 root   root     2764 1970-01-01 01:00 init.target.rc
-rwxr-x---   1 root   root     1921 1970-01-01 01:00 init.trace.rc
-rwxr-x---   1 root   root     9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x---   1 root   root     5339 1970-01-01 01:00 init.usb.rc
-rwxr-x---   1 root   root      342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x   9 root   system    200 1970-06-28 19:00 mnt
drwxr-xr-x   2 root   root        0 1970-01-01 01:00 oem
drwxr-xr-x  12 root   root     1024 1970-01-01 01:01 pds
drwxrwx--x   4 system system   4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root   root        0 1970-01-01 01:00 proc
-rw-r--r--   1 root   root     6049 1970-01-01 01:00 property_contexts
drwx------   2 root   root        0 2016-03-05 03:29 root
drwxr-x---   2 root   root        0 1970-01-01 01:00 sbin
lrwxrwxrwx   1 root   root       21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r--   1 root   root     2182 1970-01-01 01:00 seapp_contexts
-rw-r--r--   1 root   root       69 1970-01-01 01:00 selinux_version
-rw-r--r--   1 root   root   258562 1970-01-01 01:00 sepolicy
-rw-r--r--   1 root   root    14812 1970-01-01 01:00 service_contexts
drwxr-xr-x   4 root   root       80 2016-03-09 11:57 storage
dr-xr-xr-x  14 root   root        0 1970-06-28 19:00 sys
drwxr-xr-x  16 root   root     4096 2016-03-08 21:09 system
lrwxrwxrwx   1 root   root       16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r--   1 root   root    12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r--   1 root   root     7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx   1 root   root       14 1970-06-28 19:00 vendor -> /system/vendor

Your "ls -al" displayed nothing, am I right?
 
  • Like
Reactions: norte112
N

norte112

New member
Apr 26, 2014
4
0
Tucuman
zyzioziom said:
You have strange results here :/
Here is my console:
Code: 
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1	device

Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
root@falcon:/ # ls -al
total 2382
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 .
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 ..
drwxr-xr-x  44 root   root        0 1970-06-28 19:00 acct
drwxrwx---   6 system cache    4096 2016-03-05 03:28 cache
lrwxrwxrwx   1 root   root       13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------   2 root   root        0 1970-06-28 19:00 config
lrwxrwxrwx   1 root   root       17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x  35 system system   4096 2016-03-09 18:37 data
-rw-r--r--   1 root   root      555 1970-01-01 01:00 default.prop
drwxr-xr-x  15 root   root    15300 1970-06-28 19:00 dev
lrwxrwxrwx   1 root   root       11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r--   1 root   root    53465 1970-01-01 01:00 file_contexts
drwxr-xr-x   4 root   root     4096 1970-01-01 01:00 firmware
drwxr-xr-x   3 root   root     1024 1970-01-01 01:00 fsg
-rw-r-----   1 root   root     2468 1970-01-01 01:00 fstab.qcom
-rwxr-x---   1 root   root   639808 1970-01-01 01:00 init
-rwxr-x---   1 root   root     8581 1970-01-01 01:00 init.cm.rc
-rwxr-x---   1 root   root      983 1970-01-01 01:00 init.environ.rc
-rwxr-x---   1 root   root     3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x---   1 root   root     4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x---   1 root   root    29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x---   1 root   root     4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x---   1 root   root    11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x---   1 root   root    26983 1970-01-01 01:00 init.rc
-rwxr-x---   1 root   root     1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x---   1 root   root      319 1970-01-01 01:00 init.superuser.rc
-rwxr-x---   1 root   root     2764 1970-01-01 01:00 init.target.rc
-rwxr-x---   1 root   root     1921 1970-01-01 01:00 init.trace.rc
-rwxr-x---   1 root   root     9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x---   1 root   root     5339 1970-01-01 01:00 init.usb.rc
-rwxr-x---   1 root   root      342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x   9 root   system    200 1970-06-28 19:00 mnt
drwxr-xr-x   2 root   root        0 1970-01-01 01:00 oem
drwxr-xr-x  12 root   root     1024 1970-01-01 01:01 pds
drwxrwx--x   4 system system   4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root   root        0 1970-01-01 01:00 proc
-rw-r--r--   1 root   root     6049 1970-01-01 01:00 property_contexts
drwx------   2 root   root        0 2016-03-05 03:29 root
drwxr-x---   2 root   root        0 1970-01-01 01:00 sbin
lrwxrwxrwx   1 root   root       21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r--   1 root   root     2182 1970-01-01 01:00 seapp_contexts
-rw-r--r--   1 root   root       69 1970-01-01 01:00 selinux_version
-rw-r--r--   1 root   root   258562 1970-01-01 01:00 sepolicy
-rw-r--r--   1 root   root    14812 1970-01-01 01:00 service_contexts
drwxr-xr-x   4 root   root       80 2016-03-09 11:57 storage
dr-xr-xr-x  14 root   root        0 1970-06-28 19:00 sys
drwxr-xr-x  16 root   root     4096 2016-03-08 21:09 system
lrwxrwxrwx   1 root   root       16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r--   1 root   root    12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r--   1 root   root     7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx   1 root   root       14 1970-06-28 19:00 vendor -> /system/vendor

Your "ls -al" displayed nothing, am I right?
Click to expand...
Click to collapse

I found the problem, after writing the adb shell command, the console brings me the following result: ← 7 ← [r ← [999; ← 999H [6n

I just click on INTRO and I recently enabled the line: ← 8root @ falcon: / #

After that, I entered the commands and could properly install the drivers !!!

Problem solved.

Thank you very much for the support, help and above all, patience.
 
Fedroid

Fedroid

Senior Member
Jan 19, 2011
363
94
Barcelona
Moto G
Huawei P8lite/P8 Lite
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).

Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.

:highfive:

Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Worked perfect with flashify and twrp (copy first to a safe location)

Many thanks!
 
  • Like
Reactions: Bhaskara Rao
zack1175

zack1175

Senior Member
Feb 19, 2014
91
32
My wifi bug is kinda weird.
When I turn on and off my wifi 2-3times,the wifi I connected previously disappear.
Solution is to wipe everything including internal storage to have it working.But still I don't know what's the problem...
 
N

NoobByn-tek

Member
Dec 6, 2014
6
1
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.

1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033

2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)

3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)

4. Restart your phone and its wifi should resume functioning

Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
 
  • Like
Reactions: bsa12
B

bsa12

New member
Jun 9, 2013
1
0
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.

1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033

2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)

3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)

4. Restart your phone and its wifi should resume functioning

Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse

I faced same problem after flashed custom rom; searching high and low, tried many method, and finally, bumped this thread, and specifically NoobByn-tek post. I followed exactly what your have done (but with different version CM13 [cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon] because could not find the version you used), and multiple flashed with TWRP 3.0.2. With only one attempt, wifi connection is back.:victory:

Big thank you all.:good::good::rolleyes:
 
poran123

poran123

Senior Member
Aug 12, 2012
1,139
122
30
Shillong
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.

1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033

2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)

3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)

4. Restart your phone and its wifi should resume functioning

Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse

tried this still no luck...:crying::crying:
 
brchickery

brchickery

Senior Member
Dec 17, 2011
117
14
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).

Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.

:highfive:

Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse



Holy cow!!! After 2 weeks of trying everything under the sun this actually worked!!! I really really appreciate you posting this. Thank you so much!!!

My mac address was 00:00:00:00:02 or whatever it was and nothing would work. I simply flashed this and was back up and running. THANK YOU!
 
You must log in or register to reply here.

Similar threads

T
[GUIDE] Moto G - Restore stock firmware
Replies
2K
Views
1M
sd_shadow
sd_shadow
pfufle
  • Poll
[updated] THE ULTIMATE GUIDE TO FLASH GPE LOLLIPOP 5.1 on XT1032/33/34 WITH ROOT
Replies
611
Views
199K
S
sharath_babu
lost101
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images
Replies
552
Views
364K
sd_shadow
sd_shadow
Aashish-kkhckr
[root] [recovery] moto g [working]
Replies
317
Views
232K
S
Syed.sahil.haider
xtrs84zk
Bootloader Upgrader Tool [Falcon] [Peregrine] [41.18] [41.19] [41.1A]
Replies
349
Views
188K
X
XpeRiAdikTo

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    Boss442
    Boss442
    Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).

    Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
    But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.

    :highfive:

    Download from:
    MEDIAFIRE!
    MEGA!
    View
    2
    D
    Deleted member 7332069
    This works

    OK, this works but not exactly by flashing.

    First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.

    Step by step:
    1. Enable root for ADB in developer settings in your phone
    2. Connect your phone with USB
    3.
    Code: 
    adb root
    4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
    5. /persist is not accessible by default (read-only) so we must mount it as writable partition
    6.
    Code: 
    adb shell
    7.
    Code: 
    mount -o rw,remount /persist
    8.
    Code: 
    exit
    - we are exiting shell now
    9.
    Code: 
    adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
    - we are copying driver to phone
    10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
    11.
    Code: 
    adb shell
    12.
    Code: 
    mount -o ro,remount /persist
    13.
    Code: 
    exit
    14. Reboot your phone

    If you have unsufficient permissions or something, try
    Code: 
    chmod 777 /persist
    after point 7 and
    Code: 
    chmod 771 /persist
    after point 11

    Tell me if it works, was ok for me.
    View
    1
    D
    Deleted member 7332069
    norte112 said:
    Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.

    I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "

    Would you help me please?
    Click to expand...
    Click to collapse

    norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
    The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
    View
    1
    D
    Deleted member 7332069
    norte112 said:
    The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
    Click to expand...
    Click to collapse

    Code: 
    adb shell
ls -al

    And paste the results here

    Also, try whole process again but after each "adb shell" add another command: "su"
    View
    1
    D
    Deleted member 7332069
    norte112 said:
    Deputy results:

    D:\xt1032\ABD-fastboot>adb shell
    ←7←[r←[999;999H←[6nls -al
    ←8shell@falcon:/ $

    I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):

    D:\xt1032\ABD-fastboot>adb root
    adbd is already running as root

    D:\xt1032\ABD-fastboot>adb shell su
    root@falcon:/ #
    Click to expand...
    Click to collapse

    You have strange results here :/
    Here is my console:
    Code: 
    Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1	device

Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
root@falcon:/ # ls -al
total 2382
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 .
drwxr-xr-x  19 root   root        0 1970-06-28 19:00 ..
drwxr-xr-x  44 root   root        0 1970-06-28 19:00 acct
drwxrwx---   6 system cache    4096 2016-03-05 03:28 cache
lrwxrwxrwx   1 root   root       13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------   2 root   root        0 1970-06-28 19:00 config
lrwxrwxrwx   1 root   root       17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x  35 system system   4096 2016-03-09 18:37 data
-rw-r--r--   1 root   root      555 1970-01-01 01:00 default.prop
drwxr-xr-x  15 root   root    15300 1970-06-28 19:00 dev
lrwxrwxrwx   1 root   root       11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r--   1 root   root    53465 1970-01-01 01:00 file_contexts
drwxr-xr-x   4 root   root     4096 1970-01-01 01:00 firmware
drwxr-xr-x   3 root   root     1024 1970-01-01 01:00 fsg
-rw-r-----   1 root   root     2468 1970-01-01 01:00 fstab.qcom
-rwxr-x---   1 root   root   639808 1970-01-01 01:00 init
-rwxr-x---   1 root   root     8581 1970-01-01 01:00 init.cm.rc
-rwxr-x---   1 root   root      983 1970-01-01 01:00 init.environ.rc
-rwxr-x---   1 root   root     3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x---   1 root   root     4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x---   1 root   root    29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x---   1 root   root     4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x---   1 root   root    11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x---   1 root   root    26983 1970-01-01 01:00 init.rc
-rwxr-x---   1 root   root     1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x---   1 root   root      319 1970-01-01 01:00 init.superuser.rc
-rwxr-x---   1 root   root     2764 1970-01-01 01:00 init.target.rc
-rwxr-x---   1 root   root     1921 1970-01-01 01:00 init.trace.rc
-rwxr-x---   1 root   root     9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x---   1 root   root     5339 1970-01-01 01:00 init.usb.rc
-rwxr-x---   1 root   root      342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x   9 root   system    200 1970-06-28 19:00 mnt
drwxr-xr-x   2 root   root        0 1970-01-01 01:00 oem
drwxr-xr-x  12 root   root     1024 1970-01-01 01:01 pds
drwxrwx--x   4 system system   4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root   root        0 1970-01-01 01:00 proc
-rw-r--r--   1 root   root     6049 1970-01-01 01:00 property_contexts
drwx------   2 root   root        0 2016-03-05 03:29 root
drwxr-x---   2 root   root        0 1970-01-01 01:00 sbin
lrwxrwxrwx   1 root   root       21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r--   1 root   root     2182 1970-01-01 01:00 seapp_contexts
-rw-r--r--   1 root   root       69 1970-01-01 01:00 selinux_version
-rw-r--r--   1 root   root   258562 1970-01-01 01:00 sepolicy
-rw-r--r--   1 root   root    14812 1970-01-01 01:00 service_contexts
drwxr-xr-x   4 root   root       80 2016-03-09 11:57 storage
dr-xr-xr-x  14 root   root        0 1970-06-28 19:00 sys
drwxr-xr-x  16 root   root     4096 2016-03-08 21:09 system
lrwxrwxrwx   1 root   root       16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r--   1 root   root    12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r--   1 root   root     7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx   1 root   root       14 1970-06-28 19:00 vendor -> /system/vendor

    Your "ls -al" displayed nothing, am I right?
    View

New posts