Related
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!
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
does it work?
No it dint.
Twrp gave error. Also the file whicg have to copy in that persist folder gets deleted automatically.
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.
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?
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
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.
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"
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
←[email protected]:/ $
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
[email protected]:/ #
norte112 said:
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
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
[email protected]:/ #
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
[email protected]:/ # 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?
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
[email protected]:/ # 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.
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!
Didn't work for me
I tried flashing the zip, copying manually in CM file explorer and twrp and adb.
The driver is present in /persist but my Mac is stil 02:00:00:00:00
edit:
it's working after doing this:
http://forum.xda-developers.com/showpost.php?p=64771901&postcount=6
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...
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
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:
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:
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!
update link please
Hi,
Do you know how to backup boot image?
I read that its in param partition but when I open it was nothing inside
I found the param by this:
ls -l /dev/block/platform/msm_sdcc.1/by-name
Code:
lrwxrwxrwx root root 2014-01-11 04:52 aboot -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 2014-01-11 04:52 apnhlos -> /dev/block/mmc
blk0p1
lrwxrwxrwx root root 2014-01-11 04:52 backup -> /dev/block/mmcb
lk0p17
lrwxrwxrwx root root 2014-01-11 04:52 boot -> /dev/block/mmcblk
0p14
lrwxrwxrwx root root 2014-01-11 04:52 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 2014-01-11 04:52 dbi -> /dev/block/mmcblk0
p4
lrwxrwxrwx root root 2014-01-11 04:52 ddr -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 2014-01-11 04:52 efs -> /dev/block/mmcblk0
p11
lrwxrwxrwx root root 2014-01-11 04:52 fota -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 2014-01-11 04:52 fsc -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 2014-01-11 04:52 fsg -> /dev/block/mmcblk0
p18
lrwxrwxrwx root root 2014-01-11 04:52 hidden -> /dev/block/mmcb
lk0p25
lrwxrwxrwx root root 2014-01-11 04:52 modem -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2014-01-11 04:52 modemst1 -> /dev/block/mm
cblk0p12
lrwxrwxrwx root root 2014-01-11 04:52 modemst2 -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 2014-01-11 04:52 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 2014-01-11 04:52 param -> /dev/block/mmcbl
k0p10
lrwxrwxrwx root root 2014-01-11 04:52 persdata -> /dev/block/mm
cblk0p22
lrwxrwxrwx root root 2014-01-11 04:52 persist -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 2014-01-11 04:52 recovery -> /dev/block/mm
cblk0p15
lrwxrwxrwx root root 2014-01-11 04:52 rpm -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 2014-01-11 04:52 sbl1 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 2014-01-11 04:52 ssd -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 2014-01-11 04:52 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 2014-01-11 04:52 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 2014-01-11 04:52 userdata -> /dev/block/mm
cblk0p26
And I backup with :
dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p10 of=/storage/extSdCard/param.bin bs=4096
But when I opened param.bin with tar was empty.
Any idea?
You obviously don't know what you're doing, and are going to wind up in Bricktown.
That aside, dd creates images, NOT tar files. You need to know what format the binary image is in to mount and/or extract it to inspect contents.
Again, tar won't help you here.
Sent from my leanKernel 3.17 powered stock 4.4.2 SM-N900T
On Galaxy S I was able to open image with tar!
But this image contains only zeros.
I just got my Pure and started right off by unlocking it and getting it ready for use. Wifi worked originally.
* I unlocked the bootloader (wifi still working),
* allowed system update to Marshmallow
* applied root using the instructions in this thread,
* applied the fix for unlocked logo from this thread (the file linked to by the "Marshmallow logo" link)
Of those steps, probably the logo fix was the most risky, as it says that it's for Lollipop.
So here's the problem. My system boots just fine, but the wifi will not turn on. When I look at the wifi MAC address it says it's 02:00:00:00:00:00, which is obviously not right. When I turn on wifi, logcat says this:
Code:
WifiStateMachine: Failed to load driver
WifiStateMachine: setWifiState: unknown state
I'm guessing something got overwritten in a persistent partition I wasn't supposed to touch. It may be similar to the problem talked about in this thread.
Any ideas what I should do to recover? I'm guessing I've lost some persistent data and I'll need some help from someone who can get me a valid version of that data.
Try using the return to stock tool? It'll put you back to lollipop, but it should fix it.
That's probably worth a try, downloading stock image right now.
Additional info: all other radios (LTE, Bluetooth) seem to work okay.
Could someone do the following and see if it looks the same as mine?
Code:
[email protected]:/ $ su
[email protected]:/ # ls -lR /persist/
/persist/:
drwxr-xr-x mot_tcmd mot_tcmd 1969-12-31 17:03 antcap
drwxr-xr-x mot_pwric mot_pwric 1969-12-31 17:03 batt_health
drwxr-xr-x mot_tcmd bluetooth 1969-12-31 17:03 bt
drwxr-sr-x mot_tcmd mot_tcmd 1969-12-31 17:03 camera
drwx------ system system 2015-07-30 12:20 data
drwxrwx--- system graphics 1969-12-31 17:03 display
drwxr-xr-x mot_tcmd mot_tcmd 1969-12-31 17:03 factory
drwx------ root root 1969-12-31 17:00 lost+found
drwxrwx--- radio radio 2015-09-09 20:11 mdm
drwxr-xr-x mot_tcmd mot_tcmd 1969-12-31 17:03 public
drwxrws--- mot_tpapi mot_tpapi 2015-08-24 07:18 security
drwxrwxr-x root root 2015-07-29 11:05 sensors
drwxr-xr-x mot_tcmd mot_tcmd 1969-12-31 17:03 wifi
-rw------- wifi system 7 1969-12-31 17:03 wlan_mac_serial.bin
drwxrwxr-x mot_drm mot_drm 1969-12-31 17:03 wmdrm
/persist//antcap:
/persist//batt_health:
/persist//bt:
/persist//camera:
drwxr-xr-x camera mot_tcmd 1969-12-31 17:01 ledcal
/persist//camera/ledcal:
-rw-rw---- camera camera 77 1969-12-31 17:01 front
-rw-rw---- camera camera 229 1969-12-31 17:01 rear
/persist//data:
drwx------ system system 2015-08-24 07:19 sfs
drwx------ system system 2015-07-30 12:20 tz
/persist//data/sfs:
-rwx------ system system 1336 2015-08-24 07:18 4EZQjbOGb1W-1552WQ33osdXIck_
-rwx------ system system 1336 2015-08-24 07:19 BlnxQBesIFWbwNCK2OMEGP-wOkg_
-rwx------ system system 1336 2015-08-24 07:18 DsmAfAWBFCJVlmQUsgNSwY12M+E_
-rwx------ system system 1336 2015-08-24 07:18 FvF0SaGbFseVknwwKwP2Pknp7KQ_
-rwx------ system system 1336 2015-08-24 07:19 S184ZMCBpOaKXnKHFMVZu2KUkTY_
-rwx------ system system 1336 2015-08-24 07:19 S3TZEnsT9XVFFU2I2lWugTOYodo_
-rwx------ system system 1336 2015-08-24 07:19 bT7VGR2tDnBydb1IJmFjNDdBaU8_
-rwx------ system system 1336 2015-08-24 07:18 guy+4YDd1pve+q2qkHB6MDV1xDQ_
-rwx------ system system 1336 2015-08-24 07:18 iV4mGrgUcC10F1SsXzWV6jTaSQw_
-rwx------ system system 1336 2015-08-24 07:18 nmD18nOVg-hJSoABl8Jk6ugi0Ns_
-rwx------ system system 1336 2015-08-24 07:19 oQUrZKLiEwq4QuUfUhM7PmBq714_
-rwx------ system system 1336 2015-08-24 07:18 ouH--IhHfo3YeuC7fV5HOm64N8o_
/persist//data/tz:
-rwx------ system system 272 2015-08-24 07:19 tz_counter
-rwx------ system system 272 2015-08-24 07:19 tz_counter.bak
/persist//display:
/persist//factory:
-rw-rw---- mot_tcmd mot_tcmd 128 1969-12-31 17:01 fti
/persist//lost+found:
/persist//mdm:
-rw------- radio radio 5 2015-12-18 11:22 oma_dm_update
/persist//public:
drwxrwx--- mot_atvc shell 1969-12-31 17:03 atvc
drwxr-xr-x mot_accy mot_tcmd 1969-12-31 17:03 battd
drwxr-xr-x system mot_tcmd 2015-09-10 09:45 hiddenmenu
drwx------ system system 1969-12-31 17:03 locale
drwx------ radio radio 1969-12-31 17:03 omadm
drwxrwx--- system system 1969-12-31 17:03 svcs
/persist//public/atvc:
/persist//public/battd:
/persist//public/hiddenmenu:
drwxrwxr-x system mot_tcmd 2015-08-24 07:51 data
-rw-rw-r-- system mot_tcmd 4 2015-12-18 11:24 life_calls
-rw-rw-r-- system mot_tcmd 8 2015-12-18 11:24 life_timer
/persist//public/hiddenmenu/data:
-rw-rw-r-- system mot_tcmd 8 2015-12-18 10:23 mobile_data_rx
-rw-rw-r-- system mot_tcmd 8 2015-12-18 10:23 mobile_data_tx
-rw-rw-r-- system mot_tcmd 8 2015-12-18 10:23 wifi_data_rx
-rw-rw-r-- system mot_tcmd 8 2015-12-18 10:23 wifi_data_tx
/persist//public/locale:
/persist//public/omadm:
/persist//public/svcs:
/persist//security:
-rw------- mot_tcmd mot_tpapi 1954 2015-08-24 07:18 18.bin
/persist//sensors:
-rw-rw-r-- system root 2 2015-07-29 11:05 sensors_settings
/persist//wifi:
/persist//wmdrm:
Looks like system restore did it. I wish I knew what happened but it seems to be working now.
I downloaded the stock Marshmallow image from this thread, specifically the 6.0 Stock Unrooted.zip file and then I restored it in TWRP (restore, not install zip, be sure to read the instructions in the thread). I only restored boot and system, not data.
Edit:
Okay, last update. I flashed the boot.img from the root method linked above and the problem is back. I'll take my issue over there.
Hello,
I went back to lolipop, because I had problems that I will make in another post (different from yours). When I lost my wifi when I returned to the clark stock rom, I had to restore the modem by itself (NON-HLOS.bin) because for some reason it was skipping it. Can't remember if I did TWRP or bootloaded it on though.
Had the same problem. A clean wipe \install of TruPureX MM rom fixed it for me.
Mismatch between modem and android version broke my wifi.
I tried to downgrade to clark_retus stock image on Motorola's website, which included flashing the modem (NON-HLOS.bin) meant for android 5. For some reason I had a boot loop, so I restored my 6.0 nandroid. All was working except wifi. I downloaded the 6.0 firmware from the firmware thread (XT1575_CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip), extracted the 6.0 modem file (NON-HLOS.bin) and flash that with fastboot; now things are fine.
Hi to all!
So this is my case, right now IM really desperate.
My phone is a SM-G900H I installed this ROM: https://forum.xda-developers.com/ga...-exynos/rom-resurrection-remix-5-7-4-t3526192 (that BTW is a great proyect)
This works the first time until I reboot the phone, then I get stuck in a bootloop.
So from Sammobile I downloaded 3 different firmware and I flashed to my phone, this is what happens in all cases:
When Odin set on green and the phone reboots after the Samsung logo I see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the progress bar always stops on "40%" and then change to this:
So what is that make me think there is something in the phone that is stopping the process..
This is what I tried to do:
- I flashed 3 different firmware including the Bl,AP,CP,PIT variation.
- I flashed TWRP, CWM and I used the recovery stock
- I try to recover my phone with OTA.
- I tried to change the kernel.
- I tried to recover a friend stock backup with twrp.
- Finally I used nand erase all
- Tried to flash STOCK ROM DEODEX of @yash92duster
- Tried the two PIT.
Data that maybe is useful:
- When I go to TWRP and I mount EFS then I go to filemanager and I click to the EFS folder, the phone reboots.
- I can't use ADB SHELL (with TWRP), if I type adb devices I don't see it, but if I use the stock recovery and I choose adb sideload I see the id and I can do sideload very well.
I have access to:
Download Mode.
ADB (Only if I flash philz recovery).
Recovery.
Folders an disk data:
drwxr-xr-x root root 2017-01-10 16:12 boot
drwxr-xr-x root root 2017-01-10 11:29 cache
drwxr-xr-x root root 2017-01-10 10:39 data
drwxr-xr-x root root 2017-01-10 16:12 datadata
-rw-r--r— root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-10 16:12 dev
drwxr-xr-x root root 2017-01-10 16:12 emmc
drwxr-xr-x root root 2017-01-10 16:12 etc
drwxr-xr-x root root 2017-01-10 16:12 external_sd
-rw-r--r— root root 10976 1970-01-01 00:00 file_contexts
-rw-r---— root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-10 16:12 internal_sd
-rw-r--r— root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-10 16:12 mnt
drwxr-xr-x root root 2017-01-10 11:29 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r— root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-10 16:12 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-10 16:12 sd-ext
lrwxrwxrwx root root 2017-01-10 16:12 sdcard -> /data/media
-rw-r--r— root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r— root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-10 16:12 storage
dr-xr-xr-x root root 2017-01-10 16:12 sys
drwxr-xr-x root root 2017-01-10 11:32 system
drwxrwxr-x root shell 2017-01-10 16:12 tmp
-rw-r--r— root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r— root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
Click to expand...
Click to collapse
---
Filesystem Size Used Free Blksize
/dev 933.0M 128.0K 932.9M 4.0K
/tmp 933.0M 12.0K 933.0M 4.0K
/storage 933.0M 0.0K 933.0M 4.0K
/mnt/secure 933.0M 0.0K 933.0M 4.0K
/mnt/fuse 933.0M 0.0K 933.0M 4.0K
/cache 192.8M 472.0K 192.4M 4.0K
/data 11.6G 2.8M 11.6G 4.0K
/system 2.4G 2.2G 191.6M 4.0K
/preload 15.7M 40.0K 15.6M 4.0K
Click to expand...
Click to collapse
---
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,
journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p18 /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /preload ext4 rw,seclabel,relatime,discard,journal_checksu
m,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
Click to expand...
Click to collapse
What I think:
There is something that in the "updating" process make stop the progress so android finish erasing o reverting the process.
Thanks in advance!
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
youdoofus said:
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
Click to expand...
Click to collapse
I will try this, is safe remove all folders?
Thanks
maardobal said:
I will try this, is safe remove all folders?
Thanks
Click to expand...
Click to collapse
all of the folders called "android". Just those folders.
youdoofus said:
all of the folders called "android". Just those folders.
Click to expand...
Click to collapse
I cant find any "android" folder on my device. Any suggestion?
Code:
drwxr-xr-x root root 2017-01-11 01:06 boot
drwxr-xr-x root root 2017-01-10 19:43 cache
drwxr-xr-x root root 2017-01-10 19:43 data
drwxr-xr-x root root 2017-01-11 01:06 datadata
-rw-r--r-- root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-11 01:06 dev
drwxr-xr-x root root 2017-01-11 01:06 emmc
drwxr-xr-x root root 2017-01-11 01:06 etc
drwxr-xr-x root root 2017-01-11 01:06 external_sd
-rw-r--r-- root root 10976 1970-01-01 00:00 file_contexts
-rw-r----- root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-11 01:06 internal_sd
-rw-r--r-- root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-11 01:06 mnt
drwxr-xr-x root root 2016-03-14 17:26 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r-- root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-11 01:06 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-11 01:06 sd-ext
lrwxrwxrwx root root 2017-01-11 01:06 sdcard -> /data/media
-rw-r--r-- root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r-- root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-11 01:06 storage
dr-xr-xr-x root root 2017-01-11 01:06 sys
drwxr-xr-x root root 2017-01-10 19:43 system
drwxrwxr-x root shell 2017-01-11 01:06 tmp
-rw-r--r-- root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r-- root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
maardobal said:
I cant find any "android" folder on my device. Any suggestion?
Code:
drwxr-xr-x root root 2017-01-11 01:06 boot
drwxr-xr-x root root 2017-01-10 19:43 cache
drwxr-xr-x root root 2017-01-10 19:43 data
drwxr-xr-x root root 2017-01-11 01:06 datadata
-rw-r--r-- root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-11 01:06 dev
drwxr-xr-x root root 2017-01-11 01:06 emmc
drwxr-xr-x root root 2017-01-11 01:06 etc
drwxr-xr-x root root 2017-01-11 01:06 external_sd
-rw-r--r-- root root 10976 1970-01-01 00:00 file_contexts
-rw-r----- root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-11 01:06 internal_sd
-rw-r--r-- root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-11 01:06 mnt
drwxr-xr-x root root 2016-03-14 17:26 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r-- root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-11 01:06 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-11 01:06 sd-ext
lrwxrwxrwx root root 2017-01-11 01:06 sdcard -> /data/media
-rw-r--r-- root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r-- root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-11 01:06 storage
dr-xr-xr-x root root 2017-01-11 01:06 sys
drwxr-xr-x root root 2017-01-10 19:43 system
drwxrwxr-x root shell 2017-01-11 01:06 tmp
-rw-r--r-- root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r-- root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
Click to expand...
Click to collapse
itll be in the external or sdccard folders
maardobal said:
Hi to all!
So this is my case, right now IM really desperate.
My phone is a SM-G900H I installed this ROM: https://forum.xda-developers.com/ga...-exynos/rom-resurrection-remix-5-7-4-t3526192 (that BTW is a great proyect)
This works the first time until I reboot the phone, then I get stuck in a bootloop.
So from Sammobile I downloaded 3 different firmware and I flashed to my phone, this is what happens in all cases:
When Odin set on green and the phone reboots after the Samsung logo I see this:
But the progress bar always stops on "40%" and then change to this:
So what is that make me think there is something in the phone that is stopping the process..
This is what I tried to do:
- I flashed 3 different firmware including the Bl,AP,CP,PIT variation.
- I flashed TWRP, CWM and I used the recovery stock
- I try to recover my phone with OTA.
- I tried to change the kernel.
- I tried to recover a friend stock backup with twrp.
- Finally I used nand erase all
- Tried to flash STOCK ROM DEODEX of @yash92duster
- Tried the two PIT.
Data that maybe is useful:
- When I go to TWRP and I mount EFS then I go to filemanager and I click to the EFS folder, the phone reboots.
- I can't use ADB SHELL (with TWRP), if I type adb devices I don't see it, but if I use the stock recovery and I choose adb sideload I see the id and I can do sideload very well.
I have access to:
Download Mode.
ADB (Only if I flash philz recovery).
Recovery.
Folders an disk data:
---
---
What I think:
There is something that in the "updating" process make stop the progress so android finish erasing o reverting the process.
in advance!
Click to expand...
Click to collapse
Change battery simple and try different data cable
youdoofus said:
itll be in the external or sdccard folders
Click to expand...
Click to collapse
Only on external sd i have .android-secure and Android folder...
But only on sdcard, my problem happend even if sdcard is not on the device.
Any idea?
maardobal said:
Only on external sd i have .android-secure and Android folder...
But only on sdcard, my problem happend even if sdcard is not on the device.
Any idea?
Click to expand...
Click to collapse
the folder is just called "android", and if youve wiped your internal and its never fully booted since, it might not have the android folder on the internal as it gets created during the initial boot process
youdoofus said:
the folder is just called "android", and if youve wiped your internal and its never fully booted since, it might not have the android folder on the internal as it gets created during the initial boot process
Click to expand...
Click to collapse
I will try that idea then.. I keep you updated.
youdoofus said:
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
Click to expand...
Click to collapse
I tried this, doesnt work, is still on bootloop :crying::crying::crying::crying:
maardobal said:
I tried this, doesnt work, is still on bootloop :crying::crying::crying::crying:
Click to expand...
Click to collapse
where did you get your tar file from?
This is my GF's phone, it's running stock OOS 4.7.15, rooted.
She freaked out earlier today as she noticed a bunch of random images in the gallery app, they seemed to be mostly profile pictures, so I figured this was a case of creating a .nomedia file for some badly written app, but on further investigation they were in the root of the SD card. I'm fairly sure apps can't even write there without root and the only root apps she has are AdAway and All in one Gestures.
They all have names like the following:
Code:
OnePlus5:/sdcard $ ls -la
total 6864
...
-rw-rw---- 1 root sdcard_rw 332685 2017-12-29 04:37 cache_02f9bfd9b03bd154f0cae12e56251bff.png
-rw-rw---- 1 root sdcard_rw 67313 2017-12-29 04:36 cache_16f225a9c1ee0d2e68cb0ce439fa3dd0.png
-rw-rw---- 1 root sdcard_rw 264347 2017-12-29 04:36 cache_30d6ec140be77b6a78f87ec3c5557c72.png
-rw-rw---- 1 root sdcard_rw 243801 2017-12-29 05:12 cache_3b5075e23d5b7a63f058ebc3462fc582.png
-rw-rw---- 1 root sdcard_rw 30350 2017-12-29 04:37 cache_3e2b796c13dc712d676e6349b7f58872.png
-rw-rw---- 1 root sdcard_rw 287502 2017-12-29 05:12 cache_478775ee042a66ac56b82fe10b1fa49b.png
-rw-rw---- 1 root sdcard_rw 184855 2017-12-29 04:36 cache_4be7cf38c02b6fdb36f99b7021b79f8c.png
-rw-rw---- 1 root sdcard_rw 213460 2017-12-29 04:37 cache_4edebfec6a046879ce95d736380e04f5.png
-rw-rw---- 1 root sdcard_rw 32960 2017-12-29 04:38 cache_5710370294b4c4ae37a56985a2aad917.png
-rw-rw---- 1 root sdcard_rw 216642 2017-12-29 04:35 cache_58a3d26dd5db8b72ae326487f86cd7c0.png
-rw-rw---- 1 root sdcard_rw 232544 2017-12-29 04:36 cache_5cb96b0090e810e751c82f8fd0c7e355.png
-rw-rw---- 1 root sdcard_rw 61329 2017-12-29 04:38 cache_60f8f4e24d424b2eb983c54b43956258.png
-rw-rw---- 1 root sdcard_rw 258607 2017-12-29 04:38 cache_99271ac67958c10bc73a08e82fe43fa5.png
-rw-rw---- 1 root sdcard_rw 130454 2017-12-29 04:38 cache_c471e2fcbf7cfabaf945b74af8aab0e4.png
-rw-rw---- 1 root sdcard_rw 163615 2017-12-29 04:37 cache_d2c7343280c34a509e747ae10b565ae2.png
-rw-rw---- 1 root sdcard_rw 194348 2017-12-29 04:36 cache_e194a087da69e8efd2217b70aab7fd6d.png
-rw-rw---- 1 root sdcard_rw 178388 2017-12-29 05:12 cache_e2b9d87cadb0b438804e2bc484a43e6b.png
Not exactly helpful as che can't remember what apps she was using 5 days ago at 5 in the morning!
Any idea where they might've come from?
Lum_UK said:
This is my GF's phone, it's running stock OOS 4.7.15, rooted.
She freaked out earlier today as she noticed a bunch of random images in the gallery app, they seemed to be mostly profile pictures, so I figured this was a case of creating a .nomedia file for some badly written app, but on further investigation they were in the root of the SD card. I'm fairly sure apps can't even write there without root and the only root apps she has are AdAway and All in one Gestures.
They all have names like the following:
Code:
OnePlus5:/sdcard $ ls -la
total 6864
...
-rw-rw---- 1 root sdcard_rw 332685 2017-12-29 04:37 cache_02f9bfd9b03bd154f0cae12e56251bff.png
-rw-rw---- 1 root sdcard_rw 67313 2017-12-29 04:36 cache_16f225a9c1ee0d2e68cb0ce439fa3dd0.png
-rw-rw---- 1 root sdcard_rw 264347 2017-12-29 04:36 cache_30d6ec140be77b6a78f87ec3c5557c72.png
-rw-rw---- 1 root sdcard_rw 243801 2017-12-29 05:12 cache_3b5075e23d5b7a63f058ebc3462fc582.png
-rw-rw---- 1 root sdcard_rw 30350 2017-12-29 04:37 cache_3e2b796c13dc712d676e6349b7f58872.png
-rw-rw---- 1 root sdcard_rw 287502 2017-12-29 05:12 cache_478775ee042a66ac56b82fe10b1fa49b.png
-rw-rw---- 1 root sdcard_rw 184855 2017-12-29 04:36 cache_4be7cf38c02b6fdb36f99b7021b79f8c.png
-rw-rw---- 1 root sdcard_rw 213460 2017-12-29 04:37 cache_4edebfec6a046879ce95d736380e04f5.png
-rw-rw---- 1 root sdcard_rw 32960 2017-12-29 04:38 cache_5710370294b4c4ae37a56985a2aad917.png
-rw-rw---- 1 root sdcard_rw 216642 2017-12-29 04:35 cache_58a3d26dd5db8b72ae326487f86cd7c0.png
-rw-rw---- 1 root sdcard_rw 232544 2017-12-29 04:36 cache_5cb96b0090e810e751c82f8fd0c7e355.png
-rw-rw---- 1 root sdcard_rw 61329 2017-12-29 04:38 cache_60f8f4e24d424b2eb983c54b43956258.png
-rw-rw---- 1 root sdcard_rw 258607 2017-12-29 04:38 cache_99271ac67958c10bc73a08e82fe43fa5.png
-rw-rw---- 1 root sdcard_rw 130454 2017-12-29 04:38 cache_c471e2fcbf7cfabaf945b74af8aab0e4.png
-rw-rw---- 1 root sdcard_rw 163615 2017-12-29 04:37 cache_d2c7343280c34a509e747ae10b565ae2.png
-rw-rw---- 1 root sdcard_rw 194348 2017-12-29 04:36 cache_e194a087da69e8efd2217b70aab7fd6d.png
-rw-rw---- 1 root sdcard_rw 178388 2017-12-29 05:12 cache_e2b9d87cadb0b438804e2bc484a43e6b.png
Not exactly helpful as che can't remember what apps she was using 5 days ago at 5 in the morning!
Any idea where they might've come from?
Click to expand...
Click to collapse
Yeah Bro, It's your GF's Phone? It's nude pictures of her other boyfriend.... Root the phone and recover the images. There are plenty of root apps that will recover that. Just don't be upset when you recover them ROFL.
Atlantian said:
Yeah Bro, It's your GF's Phone? It's nude pictures of her other boyfriend.... Root the phone and recover the images. There are plenty of root apps that will recover that. Just don't be upset when you recover them ROFL.
Click to expand...
Click to collapse
Yeah no. We're both lesbians and polyamorous so it isn't that, and I wouldn't really care even if it was. I already looked at the images, and they're just random profile pictures from who knows where. The phone is already rooted.
Was hoping to figure out what app decided to store that crap on the root of the bloody SD card, since you can't really put a .nomedia file there. I thought apps couldn't write to the root of the SD card anyway?