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
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?
My samsung A205 fails to initialize FMP, the smatphone with the bootloader unlocked.
I tried various kernels like Rippler, Eureka and physwizz versions in TWRP.
And several Roms
I can always see the same error in dmesg:
Code:
[ 2560.206443] [2: mmc-cmdqd/0: 1799] exynos-fmp fmp: exynos_fmp_config: Fail to work fmp config due to fips in error.
[ 2560.206474] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_prep_tran_desc: failed to configure crypto engine. ret(-1)
[ 2560.206485] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_request: failed to setup tx desc: -1
[ 2560.206535] I[2: ksoftirqd/2: 22] mmc0: mmc_blk_cmdq_complete_rq: txfr error: -1
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612] =============== CQ RECOVERY START ======================
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206784] [2: kworker/2:2: 3612] [CQ] mmc0: SW RESET: 250
[ 2560.206794] [2: kworker/2:2: 3612] ----- cnt_recovery: 2743
[ 2560.206803] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_pass: 2743
[ 2560.206812] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_fail: 0
[ 2560.207055] [2: kworker/2:2: 3612] [CQ] mmc0:----- REQUEUE: tag 0 sector 32770, nr 2, retries 1
[ 2560.207181] [2: kworker/2:2: 3612] [CQ] mmc0: Enable after SW RESET
[ 2560.207198] [2: kworker/2:2: 3612]
While a well-functioning team shows:
Code:
[ 2.047718] [7: swapper/0: 1] exynos-fmp fmp: Exynos FMP Version: 1.3.2
[ 2.048316] [7: swapper/0: 1] exynos-fmp fmp: Found partno 32 for FMP test
[ 2.053900] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-xts passed
[ 2.058193] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-cbc passed
[ 2.058212] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP sha256 passed
[ 2.058246] [6: kworker/u16:3: 251] [SENSOR] stk3x3x_prox_cal: read_value = 10, (0xc0)
[ 2.058263] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for UFSFMP hmac(sha256) passed
[ 2.058269] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: self-tests for FMP passed
[ 2.058751] [7: swapper/0: 1] FIPS(do_fmp_integrity_check): Integrity Check Passed
[ 2.058758] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: integrity check for FMP passed
[ 2.058868] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_probe: Exynos FMP driver is proved
Documentation about FMP and FIPS:
Document 2016
Document 2020
What could i try?
because of that mistake cannot access the flash memory properly so it cannot start a full android system just start in TWRP.
tried compiling a kernel with FIPS options disabled, and it works I can see the capabilities of all partitions by starting TWRP in read-only mode. when I do it in read write mode it works unstable and restarts.
Exploring in the kernel source code I could see
arch/arm64/boot/dts/exynos/dtbo/exynos7885.dts
Code:
fmp_0: fmp {
compatible = "samsung,exynos-fmp";
exynos,host-type = "mmc";
exynos-host = <&dwmmc_0>;
exynos,block-type = "mmcblk0p";
exynos,fips-block_offset = <5>;
Mount the partition mmcblk0p5 (CPEFS) and I found it to be of type ext4 and empty.
Could someone give me a copy of that partition or show me what files it originally has inside?
Upgrade:
I discovered that the partition mmcblk0p4 (SEC EFS) is corrupt.
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
In mmcblk0p4 (SEC EFS) I have:
Code:
Battery
FactoryApp
TEE
adp_token
afc
cpk
imei
lost+found
lpm
lpm_boot.log
nfc
nxp
pfw_data
prov
prov_data
recovery
sec_efs
ssm
tee
umc
wv.keys
./Battery:
batt_capacity_max
./FactoryApp:
Sensorinfo
asoc
batt_after_manufactured
batt_cable_count
batt_discharge_level
batt_temp_charge
cisd_data
cisd_wc_data
factorymode
fdata
gyro_cal_data
hist_nv
keystr
max_current
max_temp
rtc_status
test_nv
./FactoryApp/Sensorinfo:
Accelerometer
Barometer
Gyroscope
Light
Magnetometer
Proximity
./TEE:
./adp_token:
./afc:
./cpk:
./imei:
factory.prop
mps_code.dat
omcnw_code.dat
./lost+found:
#27
#28
#29
#30
#31
#32
#33
#35
#36
#39
#40
#41
#42
#43
#44
#45
#46
#48
#49
#50
#51
#52
#53
#54
#55
#56
#57
#58
#59
#60
#61
#62
#63
#64
#65
#66
#67
#72
#74
#75
#76
#81
#82
#92
#93
#94
#95
#98
./lost+found/#40:
./lpm:
./nfc:
./nxp:
./pfw_data:
./prov:
issued.log
libdevkm.lock
./prov_data:
./recovery:
extra_history
history
prev_tmp_recovery.log
./sec_efs:
!SVC
SVC
SettingsBackup.json
nfc
skpm_FACTORY_OCF_ECC_P256
skpm_OTA_WB_TA_Downloader_RSA_2048
skpm_sk.dat
skpm_supported_list
ucm_ca_cert
./sec_efs/nfc:
./sec_efs/ucm_ca_cert:
./ssm:
./tee:
./umc:
BulkEnrollmentProfile
From what I see in lost+found I know I have lost files.
Unfortunately e2fsck does not repair my partition. I made a copy using dd and tried to repair that image from my Salckware on my desktop pc but without success.
It would be great if someone published a complete backup of the partitions obviously without MAC, IMEI, Serial Number, and Bluethoo address.
Who can help me:
I need a copy of the sec_efs partition
To do this, I had to run:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img bs=4096
or at least the listing
Code:
ls -R -l > /external_sd/secefs.lst
I've been looking for a backup on the web for days but I haven't been successful so far. If you see any dumps of that paticion on the web, the download link will do me good.
Thanks
Cant you just install stock firmware using odin
physwizz said:
Cant you just install stock firmware using odin
Click to expand...
Click to collapse
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it was on screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of testing with different roms. On February 4, immediately took advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I am able to mount some partitions.
After that I started to read the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
Checking the other partitions I discover broken SEC_EFS.
I made a backup of what I could using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
format it with the same original parameters and restore the files you rescue from backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
sercari said:
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it showed on the screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of trying different roms. on february 4 it turned on immediately take advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I managed to mount some partitions.
After that I started reading the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
checking the other partitions I discover broken SEC_EFS.
I made a backup of what I pure using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
Format it with the same original parameters and restore the files you rescue from the backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
Click to expand...
Click to collapse
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
physwizz said:
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you, this guide is very good, unfortunately it does not solve my case. Disable_Dm-Verity_ForceEncrypt didn't work either.
The problem of my phone is with FMP = Flash Memory Protector
It fails to start FIPS because a file is probably missing or corrupt. I think that what would help me would be to see the list of files of those partitions to know their name and weight.
It would help me if you can create a text file on your external memory card and paste this content inside:
Code:
mkdir /secefs
mount /dev/block/mmcblk0p4 /secefs -o ro
cd /secefs
ls -a -R -l > /external_sd/secefs.lst
mkdir /efs
mount /dev/block/mmcblk0p3 /efs -o ro
cd /efs
ls -a -R -l > /external_sd/efs.lst
mkdir /cpefs
mount /dev/block/mmcblk0p5 /cpefs -o ro
cd /cpefs
ls -a -R -l > /external_sd/cpefs.lst
Or with this other you can make a backup:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img
dd if=/dev/block/mmcblk0p3 of=/external_sd/efs.img
dd if=/dev/block/mmcblk0p5 of=/external_sd/cpefs.img
(suppose the file is called mkbl.txt)
finally run it from the TWRP terminal:
Code:
/external_sd/mkbl.txt
with that I would generate files in /external_sd/
NOTE: If you generate backup files, keep in mind that they contain IMEIs and addresses that are private to you. You could make a copy of the .img file, mount it from linux in a folder and edit the files that contain personal information. Or you can trust me and I can erase that personal information to make the files public.
On the other hand, in the case of the lists with ls, it does not include any personal information, only file names and weights
sercari said:
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
Click to expand...
Click to collapse
Confirmed cpefs that is mounted in / vendor / cpefs contains only these two files normally.
Code:
-rwx------ 1 radio radio 546304 feb 4 20:51 .nv_core.bak
-rwx------ 1 radio radio 32 feb 4 20:51 .nv_core.bak.md5
drwx------ 2 radio radio 4096 ene 1 2019 lost+found
I would only need to find out the content of the partition /dev/mccblk0p4 (sec_efs) which I think is not mounted anywhere when the system is running. for which it is necessary to mount it to be able to list its content. I wait if someone can help me.
Thanks to TBM13 from the telegram @Galaxy_A20_official group who shared with me the list of files and directories on their sec_efs partition.
Thanks to TOP who shared the list of files on his cpefs partition. Thanks to this I can continue investigating.
mmcblk0p4 (sec_efs):
Code:
.:
total 180
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 .
drwxr-xr-x 30 root root 0 2021-02-24 17:24 ..
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 Battery
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 FactoryApp
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 TEE
drwxr--r-- 2 system system 4096 2019-01-01 12:00 adp_token
drwx------ 2 system system 4096 2019-01-01 12:00 afc
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 cpk
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 imei
drwx------ 2 root root 16384 2008-12-31 15:00 lost+found
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 lpm
-rw-rw---- 1 root system 256 2020-12-15 23:19 lpm_boot.log
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 nxp
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 pfw_data
drwxrwx--- 2 system system 4096 2019-06-29 17:22 prov
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 prov_data
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 recovery
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 sec_efs
drwxrwx--- 2 system system 4096 2019-01-01 12:00 ssm
drwx------ 2 system system 4096 2019-01-01 12:00 tee
drwx------ 2 system system 4096 2019-08-31 01:46 umc
-rw-r--r-- 1 system system 168 2019-06-29 17:22 wv.keys
./Battery:
total 20
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 system system 4 2021-02-21 02:58 batt_capacity_max
./FactoryApp:
total 132
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 28 2019-06-29 08:37 HwParamBattQR
-rw------- 1 system system 4876 2019-06-29 17:22 HwParamData
-rw------- 1 system system 824 2019-06-29 17:22 HwPartInform
drwx------ 2 system system 4096 2019-01-01 12:00 Sensorinfo
-rw-r----- 1 system log 3 2019-01-01 12:00 asoc
-rwxr--r-- 1 system system 1 2019-01-01 12:00 baro_delta
-rw-r----- 1 system system 2 2020-12-15 22:43 batt_after_manufactured
-rw------- 1 system system 4 2021-02-23 14:39 batt_cable_count
-rw-r----- 1 system system 6 2020-12-15 22:57 batt_discharge_level
-rw------- 1 system system 62 2021-02-24 17:10 batt_temp_charge
-rw------- 1 system system 1 2019-01-01 12:00 cable_detect_count_octa
-rw-rw---- 1 system system 195 2021-02-23 15:31 cisd_data
-rw-rw---- 1 system system 20 2019-01-01 12:00 cisd_wc_data
-rwxr--r-- 1 system system 13 2019-01-01 12:00 control_no
-rw------- 1 system system 2 2020-11-28 14:37 earjack_count
-rwxr--r-- 1 system system 2 2019-06-29 17:22 factorymode
-rwxrwxr-x 1 system radio 4 2019-01-01 12:00 fdata
-rw------- 1 system system 30 2021-02-24 13:06 gyro_cal_data
-rwxrwxr-x 1 system radio 0 2018-12-31 17:00 hist_nv
-rwxr--r-- 1 system system 2 2019-06-29 17:22 keystr
-rw------- 1 system system 5 2019-10-12 21:38 max_current
-rw------- 1 system system 4 2020-01-19 20:53 max_temp
-rwxr--r-- 1 system system 5 2019-06-29 17:29 mdnie
-rw------- 1 system system 1 2019-06-29 17:29 mdnie_ver
-rwxr--r-- 1 system system 5 2019-01-01 12:00 prepay
-rw------- 1 system system 1 2019-06-29 17:22 rtc_status
-rwxr--r-- 1 system system 11 2019-06-29 17:22 serial_no
-rwxrwxr-x 1 system radio 2000 2018-12-31 17:00 test_nv
./FactoryApp/Sensorinfo:
total 40
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 ..
-rw------- 1 system system 21 2019-01-01 12:00 Accelerometer
-rw------- 1 system system 4 2019-01-01 12:00 Barometer
-rw------- 1 system system 17 2019-01-01 12:00 Gyroscope
-rw------- 1 system system 4 2019-01-01 12:00 Light
-rw------- 1 system system 19 2019-01-01 12:00 Magnetometer
-rw------- 1 system system 31 2019-01-01 12:00 Proximity
./TEE:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./adp_token:
total 16
drwxr--r-- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./afc:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./cpk:
total 20
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-r--r-- 1 radio radio 920 2019-06-29 17:29 h2k.dat
./imei:
total 40
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 96 2021-02-21 03:41 factory.prop
-rwxrwxr-x 1 radio system 3 2020-12-15 23:26 mps_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code2.dat
-rwxrwxr-x 1 system radio 14 2019-06-29 17:22 prodcode.dat
-rw-rw-r-- 1 system system 4 2019-12-29 20:07 total_call_time
./lost+found:
total 28
drwx------ 2 root root 16384 2008-12-31 15:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./lpm:
total 20
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 root system 85 2020-12-15 23:19 lpm_info.log
./nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./nxp:
total 16
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./pfw_data:
total 16
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./prov:
total 20
drwxrwx--- 2 system system 4096 2019-06-29 17:22 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw----r-- 1 system system 559 2019-09-01 00:28 issued.log
-rw-rw---- 1 system system 0 2019-01-01 12:00 libdevkm.lock
./prov_data:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./recovery:
total 24
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 257 2020-12-15 23:25 extra_history
-rw------- 1 root root 2529 2020-12-15 23:25 history
./sec_efs:
total 76
-rw------- 1 system system 569 2020-12-15 23:12 !SVC
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rwx------ 1 root radio 0 2019-06-29 17:07 .ffw
-rw------- 1 system system 569 2020-12-15 23:12 SVC
-rw------- 1 system system 6655 2020-12-15 23:32 SettingsBackup.json
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
-rw------- 1 system system 1517 2019-06-29 17:22 skpm_FACTORY_OCF_ECC_P256
-rw------- 1 system system 983 2019-09-01 00:29 skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
-rw------- 1 system system 4104 2019-08-31 02:43 skpm_OTA_WB_TA_Downloader_RSA_2048
-rw------- 1 system system 3941 2019-08-31 02:43 skpm_sk.dat
-rw------- 1 system system 4711 2019-09-01 00:29 skpm_supported_list
drwx------ 2 system system 4096 2019-01-01 12:00 ucm_ca_cert
./sec_efs/nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./sec_efs/ucm_ca_cert:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./ssm:
total 16
drwxrwx--- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./tee:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./umc:
total 20
drwx------ 2 system system 4096 2019-08-31 01:46 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 1 2019-08-31 01:46 BulkEnrollmentProfile
Observing the list compare weight, permissions, owner and group of each file in /lost+found and I was able to deduce which file was and give it the corresponding location and name.
The only file I am missing is: /sec_efs/skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
Someone has any idea about this file, apparently it is a key but I don't know if the phone should generate it automatically or how to get it.
I add that you do not know that the skpm_sk.dat file is blank. if I have it with a hex editor it is full of zeros
Thanks
Finally and mysteriously I boot into twrp allowing me to see all the partitions. (Only TWRP with full memory access would not start the system) Take advantage and I made a copy from partition 1 to 25 to and 31. Unfortunately I discovered that I have the partitions boot0, boot1, boot3, m9kefs, m9kefs2, m9kefs3, nad_fw, nad_refer blank.
UPDATE:
1- Get a copy of m9kefs1, 2 and 3 and I have them ok.