hey everyone,
i reflashed the stock 5.1.1 image today, but after booting (in recovery it works just fine) my /sdcard is read-only:
Code:
p backup-2015-09-22-1442949879837.kiikb ./kii-kb <
cp: ./kii-kb/backup-2015-09-22-1442949879837.kiikb: Permission denied
1|[email protected]:/sdcard #
here are the outputs of ls -l and mount
Code:
1|[B][email protected]:/sdcard # ls -l[/B]
drwxrwx--- root sdcard_r 2015-09-23 13:14 !ReadyToFlash
drwxrwx--- root sdcard_r 2015-09-23 13:15 Alarms
drwxrwx--x root sdcard_r 2015-09-23 13:16 Android
drwxrwx--- root sdcard_r 2015-09-23 13:25 DCIM
drwxrwx--- root sdcard_r 2015-09-23 13:26 Documents
drwxrwx--- root sdcard_r 2015-09-23 21:08 Download
drwxrwx--- root sdcard_r 2015-09-23 13:28 Files
drwxrwx--- root sdcard_r 2015-09-23 12:46 Movies
drwxrwx--- root sdcard_r 2015-09-23 13:42 Music
drwxrwx--- root sdcard_r 2015-09-23 13:42 Notifications
drwxrwx--- root sdcard_r 2015-09-23 13:46 Pictures
drwxrwx--- root sdcard_r 2015-09-23 12:46 Podcasts
drwxrwx--- root sdcard_r 2015-09-23 13:46 Ringtones
drwxrwx--- root sdcard_r 2015-09-23 13:46 TWRP
drwxrwx--- root sdcard_r 2015-09-23 13:16 backup
-rwxrwx--- root sdcard_r 1626 2015-09-22 21:32 backup-2015-09-22-1442949879837.kiikb
drwxrwx--- root sdcard_r 2015-09-23 13:16 com.facebook.katana
drwxrwx--- root sdcard_r 2015-09-23 13:16 com.facebook.orca
drwxrwx--- root sdcard_r 2015-09-23 13:16 data
drwxrwx--- root sdcard_r 2015-09-23 12:54 flash
drwxrwx--- root sdcard_r 2015-09-23 13:28 kii-kb
drwxrwx--- root sdcard_r 2015-09-23 13:28 media
drwxrwx--- root sdcard_r 2015-09-23 13:46 runtasticPRO
-rwxrwx--- root sdcard_r 54859 2015-09-22 21:32 sms-20150922212654.xml
-rwxrwx--- root sdcard_r 2929 2015-09-22 21:32 sms.xsl
drwxrwx--- root sdcard_r 2015-09-23 13:47 viber
[B][email protected]:/ # ls -l[/B]
drwxr-xr-x root root 2015-09-23 20:56 acct
drwxrwx--- system cache 2015-09-23 20:31 cache
lrwxrwxrwx root root 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ root root 2015-09-23 20:56 config
lrwxrwxrwx root root 2015-09-23 20:56 d -> /sys/kernel/debug
drwxrwx--x system system 2015-09-23 20:56 data
-rw-r--r-- root root 341 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2015-09-23 20:56 dev
lrwxrwxrwx root root 2015-09-23 20:56 etc -> /system/etc
-rw-r--r-- root root 18941 1970-01-01 01:00 file_contexts
dr-xr-x--- system system 1970-01-01 01:00 firmware
-rw-r----- root root 2625 1970-01-01 01:00 fstab.mako
-rwxr-x--- root root 227652 1970-01-01 01:00 init
-rwxr-x--- root root 944 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 15680 1970-01-01 01:00 init.mako.rc
-rwxr-x--- root root 5957 1970-01-01 01:00 init.mako.usb.rc
-rwxr-x--- root root 1945 1970-01-01 01:00 init.performance_profiles.rc
-rwxr-x--- root root 22022 1970-01-01 01:00 init.rc
-rwxr-x--- root root 1927 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3885 1970-01-01 01:00 init.usb.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.zygote32.rc
drwxrwxr-x root system 2015-09-23 20:56 mnt
drwxrwx--x system system 2015-09-16 10:15 persist
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2870 1970-01-01 01:00 property_contexts
drwxr-xr-x root root 1970-01-01 01:00 res
drwx------ root root 2015-04-14 23:26 root
drwxr-x--- root root 2015-09-23 21:09 sbin
lrwxrwxrwx root root 2015-09-23 20:56 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 826 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 50 1970-01-01 01:00 selinux_version
-rw-r--r-- root root 129888 1970-01-01 01:00 sepolicy
-rw-r--r-- root root 129294 1970-01-01 01:00 sepolicy_bk
-rw-r--r-- root root 9854 1970-01-01 01:00 service_contexts
drwxr-x--x root sdcard_r 2015-09-23 20:56 storage
dr-xr-xr-x root root 2015-09-23 20:56 sys
drwxr-xr-x root root 2015-09-23 13:48 system
drwxr-xr-x root root 2015-09-23 20:56 tmp-mksh
-rw-r--r-- root root 2342 1970-01-01 01:00 ueventd.mako.rc
-rw-r--r-- root root 4464 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 2015-09-23 20:56 vendor -> /system/vendor
[B][email protected]:/ # mount[/B]
rootfs / rootfs ro,seclabel,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:radio_efs_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
i tried the following:
Code:
adb root
adb remount
#mount -o remount,rw /sdcard
#mount -o remount,rw rootfs /
#chmod 755 /sdcard/*
nothing did the trick, even tried to fix permissions via twrp.
can anyone help me get this solved please without a fw reflash?
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 have an inactived SH306, i can not run the app from sdcard after i copy UICCUnlock_305SH.apk to the sdcard,the icon of this apk file is gray. So i check the status from adb shell,the apk file attribute is 770，that means i have not any permission. And i put the apk on the directory /storage/sdcard1 /Android,it still failed.
How can i do to fix this issue.
[email protected]:/storage/sdcard1 $ ls -al
ls -al
-rwxrwx--- root sdcard_r 46360 2015-01-21 18:18 306sh_RUIM
drwxrwx--x root sdcard_r 2015-03-12 04:35 Android
drwxrwx--- root sdcard_r 2015-03-12 04:35 LOST.DIR
-rwxrwx--- root sdcard_r 379833 2015-01-21 18:18 UICCUnlock_305SH.apk
Hi,
Unrooted phone fell in the water and failed to power on.
I send it to a lab (not an LG lab). Laboratory cleaned of corrosion but didn't change any part.
The phone works now, but without Baseband and IMEI.
I tried to root/flash (KDZ and TOT)/erase (data/dalvik etc) but nothing works. Obviously I don't have a backup since the phone was unrooted.
Tried with Qualcomm NV tool and EFS professional, but I'm unable to change IMEI (I know it).
Please advise.
I'm attaching some details about the file system and the mounts:
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ls -l
lrwxrwxrwx root root 1970-01-01 02:00 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 02:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 02:00 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 02:00 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 02:00 cust -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 02:00 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 02:00 dbibak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 02:00 drm -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 02:00 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 02:00 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 02:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 02:00 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 02:00 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 02:00 laf -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 02:00 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 02:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 02:00 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 02:00 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 02:00 mpt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 02:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 02:00 pad1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 02:00 pad2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 02:00 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 02:00 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 02:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 02:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 02:00 rpmbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 02:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 02:00 sns -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 02:00 spare -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 02:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 02:00 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 02:00 tombstones -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 02:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 02:00 tzbak -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 02:00 userdata -> /dev/block/mmcblk0p35
Code:
[email protected]:/ $ls -l
drwxr-xr-x root root 1970-01-01 02:00 acct
drwxrwx--- system cache 2015-09-29 19:39 cache
-rwxr-x--- root root 271856 2014-04-25 14:39 charger
dr-x------ root root 1970-01-01 02:00 config
drwxr-xr-x root root 1970-01-01 02:00 cust
lrwxrwxrwx root root 1970-01-01 02:00 d -> /sys/kernel/debug
drwxrwx--x system system 2009-01-02 15:00 data
-rw-r--r-- root root 133 2014-04-25 13:58 default.prop
drwxr-xr-x root root 2009-01-02 13:00 dev
lrwxrwxrwx root root 1970-01-01 02:00 etc -> /system/etc
-rw-r--r-- root root 9471 2014-04-25 14:36 file_contexts
dr-xr-x--- system system 1970-01-01 02:00 firmware
-rw-r----- root root 1944 2014-04-25 14:18 fstab.g2
-rwxr-x--- root root 202260 2014-04-25 14:39 init
-rwxr-x--- root root 1041 2014-04-25 14:18 init.environ.rc
-rwxr-x--- root root 6097 2014-04-25 14:18 init.g2.rc
-rwxr-x--- root root 3184 2014-04-25 14:18 init.g2_product.rc
-rwxr-x--- root root 2344 2014-04-25 14:18 init.galbi-sensor.sh
-rwxr-x--- root root 6847 2014-04-25 14:18 init.galbi.class_core.sh
-rwxr-x--- root root 2518 2014-04-25 14:18 init.galbi.class_main.sh
-rwxr-x--- root root 2687 2014-04-25 14:18 init.galbi.crash.sh
-rwxr-x--- root root 6466 2014-04-25 14:18 init.galbi.early_boot.sh
-rwxr-x--- root root 37883 2014-04-25 14:18 init.galbi.rc
-rwxr-x--- root root 5914 2014-04-25 14:18 init.galbi.sh
-rwxr-x--- root root 3206 2014-04-25 14:18 init.galbi.syspart_fixup.sh
-rwxr-x--- root root 29210 2014-04-25 14:18 init.galbi.usb.rc
-rwxr-x--- root root 6120 2014-04-25 14:18 init.galbi.usb.sh
-rwxr-x--- root root 2063 2014-04-25 14:18 init.lge.cmm.usb.sh
-rwxr-x--- root root 664 2014-04-25 14:18 init.lge.early.rc
-rwxr-x--- root root 3588 2014-04-25 14:18 init.lge.log.rc
-rwxr-x--- root root 2795 2014-04-25 14:18 init.lge.rc
-rwxr-x--- root root 22330 2014-04-25 14:18 init.lge.usb.rc
-rwxr-x--- root root 3029 2014-04-25 14:18 init.lge.usb.sh
-rwxr-x--- root root 21154 2014-04-25 14:19 init.rc
-rwxr-x--- root root 0 2014-04-25 14:18 init.recovery.galbi.rc
-rwxr-x--- root root 9173 2014-04-25 14:18 init.target.rc
-rwxr-x--- root root 1795 2014-04-25 14:18 init.trace.rc
-rwxr-x--- root root 5397 2014-04-25 14:18 init.usb.rc
-rwxr-x--- root root 67824 2014-04-25 14:18 initlogo_fhd.rle
-rw-r--r-- root root 506 2014-04-25 14:19 lgdms.fota.rc
-rw-r--r-- root root 1463 2014-04-25 14:19 lgdms.fota_update.rc
drwxrwxr-x root system 1970-01-01 02:00 mnt
drwxrwxr-x system system 2015-09-30 16:28 mpt
drwxrwx--x system system 2015-09-30 12:50 persist
drwxrwx--x system system 1970-01-02 08:48 persist-lg
lrwxrwxrwx root root 1970-01-01 02:00 pkg -> /storage/sdcard0
-rw-r--r-- root root 1702 2014-04-25 14:18 preload_sl.sh
dr-xr-xr-x root root 1970-01-01 02:00 proc
-rw-r--r-- root root 2324 2014-04-25 14:36 property_contexts
drwxr-xr-x root root 2014-04-25 14:18 res
drwx------ root root 2014-04-25 14:20 root
drwxr-x--- root root 2014-04-25 14:39 sbin
lrwxrwxrwx root root 1970-01-01 02:00 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 774 2014-04-25 14:36 seapp_contexts
-rw-r--r-- root root 82342 2014-04-25 14:19 sepolicy
-rw-r--r-- root root 1 1970-01-01 02:00 smpl_boot
drwxr-xr-x root root 1970-01-01 02:00 sns
drwxr-x--x system sdcard_r 1970-01-01 02:00 storage
dr-xr-xr-x root root 1970-01-01 02:00 sys
drwxr-xr-x root root 1970-01-01 02:00 system
drwxr-xr-x root root 1970-01-01 02:00 tmp-mksh
lrwxrwxrwx root root 1970-01-01 02:00 tombstones -> /data/tombstones
-rw-r--r-- root root 9098 2014-04-25 14:18 ueventd.g2.rc
-rw-r--r-- root root 4083 2014-04-25 14:18 ueventd.rc
lrwxrwxrwx root root 1970-01-01 02:00 vendor -> /system/vendor
All files became INVISIBLE/encrypted after Rand. Restart & Prompted a "New Phone"..
Image: i.imgur dot com/Puonis8.jpg
When the phone restarted, it suddenly showed a "New Phone" wizard as if you're setting up the phone for the first time. It's trying to install stuff on top of the already occupied internal storage (gray colored bar in graph)
The files still seem to be there but are invisible, as depicted by the gray bar marked "Others" (img link above)
It didn't ask for my existing fingerprint scan. All my phone settings have reset as if it's a new phone but with the latest OS firmware available. No fingerprint scan, no password, nothing.
I never did a reset on the phone. It had an existing random spontaneous restart problem going on for a month now.
It's 5.0.1 T-Mobile. No recent firmware upgrades. I had it upgraded last August
It seems to be trying to setup a new version of the phone, trying to "update" apps, on top of the already existing phone with my files (that are invisible, depicted as gray in the image), but of course it triggered an "Insufficient Storage" error.
My video and image files were never private, only a handful of PDF legal document files. The long gray bar in the 31/32GB portion of the image is that set of missing files
Samsung Kies, SmartSwitch can't access them. Samsung+ rep doesn't know what to do either
Does anyone know what I can do to restore them?
travisgp19 said:
Image: i.imgur dot com/Puonis8.jpg
When the phone restarted, it suddenly showed a "New Phone" wizard as if you're setting up the phone for the first time. It's trying to install stuff on top of the already occupied internal storage (gray colored bar in graph)
The files still seem to be there but are invisible, as depicted by the gray bar marked "Others" (img link above)
It didn't ask for my existing fingerprint scan. All my phone settings have reset as if it's a new phone but with the latest OS firmware available. No fingerprint scan, no password, nothing.
I never did a reset on the phone. It had an existing random spontaneous restart problem going on for a month now.
It's 5.0.1 T-Mobile. No recent firmware upgrades. I had it upgraded last August
It seems to be trying to setup a new version of the phone, trying to "update" apps, on top of the already existing phone with my files (that are invisible, depicted as gray in the image), but of course it triggered an "Insufficient Storage" error.
My video and image files were never private, only a handful of PDF legal document files. The long gray bar in the 31/32GB portion of the image is that set of missing files
Samsung Kies, SmartSwitch can't access them. Samsung+ rep doesn't know what to do either
Does anyone know what I can do to restore them?
Click to expand...
Click to collapse
Have you installed Samsung USB drivers on a PC and see if it mounts the phone and is viewable there?
dicksteele said:
Have you installed Samsung USB drivers on a PC and see if it mounts the phone and is viewable there?
Click to expand...
Click to collapse
Is there a data recovery software / app I can buy somewhere to make them visible? When I mounted the phone and used Kies, SmartSwitch and Windows Explorer, they all showed that the internal memory is pretty fully occupied, but when I go through every folders, they are empty - it's accessing the "new" system on top of my already existing system that had my media files which seem to have been encrypted / invisible... Thank you sir for your message. I should have backed up my videos I really apologize for my irresponsibility
travisgp19 said:
Is there a data recovery software / app I can buy somewhere to make them visible? When I mounted the phone and used Kies, SmartSwitch and Windows Explorer, they all showed that the internal memory is pretty fully occupied, but when I go through every folders, they are empty - it's accessing the "new" system on top of my already existing system that had my media files which seem to have been encrypted / invisible... Thank you sir for your message. I should have backed up my videos I really apologize for my irresponsibility
Click to expand...
Click to collapse
Ok, so you have adb loaded on your Windows PC?
If not got grab this
http://forum.xda-developers.com/showthread.php?p=48915118
I just checked the Google Drive and it is available.
After installing it go to a windows command window
Type adb devices. Hopefully you will see your device. Obviously it needs to be plugged in. Just saying, I've done it myself wondering WTF and the cable is dangling on the floor.
If you see it, type :
C:\(whatvever directory you are in)>adb shell
You should get this
[email protected]:/ $
Then do this
[email protected]:/ $ cd /sdcard
cd /sdcard
[email protected]:/sdcard $ ls -la
ls -la
drwxrwx--- root sdcard_r 2015-11-26 19:05 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 18:03 .face
drwxrwx--- root sdcard_r 2015-11-26 19:05 Alarms
drwxrwx--x root sdcard_r 2015-11-27 05:37 Android
drwxrwx--- root sdcard_r 2015-11-26 19:05 DCIM
drwxrwx--- root sdcard_r 2015-11-26 19:05 Download
drwxrwx--- root sdcard_r 2015-11-26 19:05 Movies
drwxrwx--- root sdcard_r 2015-11-26 19:05 Music
drwxrwx--- root sdcard_r 2015-11-26 19:05 Notifications
drwxrwx--- root sdcard_r 2015-11-26 19:05 Pictures
drwxrwx--- root sdcard_r 2015-11-26 19:10 Playlists
drwxrwx--- root sdcard_r 2015-11-26 19:05 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 19:05 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 19:03 Samsung
drwxrwx--- root sdcard_r 2015-11-27 05:25 TitaniumBackup
drwxrwx--- root sdcard_r 2015-11-26 20:48 clockworkmod
[email protected]:/sdcard $ cd Movies
cd Movies
[email protected]:/sdcard/Movies $ ls -la
ls -la
-rwxrwx--- root sdcard_r 34779759 2015-11-27 18:35 VX 5 Radar Love - YouTube.wmv
[email protected]:/sdcard/Movies $
I'm curious if you can see them and what the permissions are
dicksteele said:
Ok, so you have adb loaded on your Windows PC?
If not got grab this
http://forum.xda-developers.com/showthread.php?p=48915118
I just checked the Google Drive and it is available.
After installing it go to a windows command window
Type adb devices. Hopefully you will see your device. Obviously it needs to be plugged in. Just saying, I've done it myself wondering WTF and the cable is dangling on the floor.
If you see it, type :
C:\(whatvever directory you are in)>adb shell
You should get this
[email protected]:/ $
Then do this
[email protected]:/ $ cd /sdcard
cd /sdcard
[email protected]:/sdcard $ ls -la
ls -la
drwxrwx--- root sdcard_r 2015-11-26 19:05 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 18:03 .face
drwxrwx--- root sdcard_r 2015-11-26 19:05 Alarms
drwxrwx--x root sdcard_r 2015-11-27 05:37 Android
drwxrwx--- root sdcard_r 2015-11-26 19:05 DCIM
drwxrwx--- root sdcard_r 2015-11-26 19:05 Download
drwxrwx--- root sdcard_r 2015-11-26 19:05 Movies
drwxrwx--- root sdcard_r 2015-11-26 19:05 Music
drwxrwx--- root sdcard_r 2015-11-26 19:05 Notifications
drwxrwx--- root sdcard_r 2015-11-26 19:05 Pictures
drwxrwx--- root sdcard_r 2015-11-26 19:10 Playlists
drwxrwx--- root sdcard_r 2015-11-26 19:05 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 19:05 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 19:03 Samsung
drwxrwx--- root sdcard_r 2015-11-27 05:25 TitaniumBackup
drwxrwx--- root sdcard_r 2015-11-26 20:48 clockworkmod
[email protected]:/sdcard $ cd Movies
cd Movies
[email protected]:/sdcard/Movies $ ls -la
ls -la
-rwxrwx--- root sdcard_r 34779759 2015-11-27 18:35 VX 5 Radar Love - YouTube.wmv
[email protected]:/sdcard/Movies $
I'm curious if you can see them and what the permissions are
Click to expand...
Click to collapse
Hello, sir. I don't think it showed any movie file, but I can actually see files found in the SD card just fine, the Internal Memory is what I could not see, sorry if I got confused but here:
C:\Users\B570>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ ls -la
drwxrwx--- root sdcard_r 2015-11-27 16:02 .DataStorage
drwxrwx--- root sdcard_r 2015-11-26 20:45 .Hnc
drwxrwx--- root sdcard_r 2015-11-26 20:07 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 16:02 .UTSystemConfig
drwxrwx--- root sdcard_r 2015-11-26 20:07 .face
drwxrwx--- root sdcard_r 2013-12-31 16:02 Alarms
drwxrwx--x root sdcard_r 2013-12-31 16:02 Android
drwxrwx--- root sdcard_r 2015-11-26 20:46 DCIM
drwxrwx--- root sdcard_r 2013-12-31 16:02 Download
drwxrwx--- root sdcard_r 2013-12-31 16:02 Movies
drwxrwx--- root sdcard_r 2013-12-31 16:02 Music
drwxrwx--- root sdcard_r 2015-11-26 20:45 My Documents
drwxrwx--- root sdcard_r 2013-12-31 16:02 Notifications
drwxrwx--- root sdcard_r 2015-11-26 20:07 Pictures
drwxrwx--- root sdcard_r 2015-11-26 20:57 Playlists
drwxrwx--- root sdcard_r 2013-12-31 16:02 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 20:07 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 21:35 SnoteData
drwxrwx--- root sdcard_r 2015-11-26 20:23 media
drwxrwx--- root sdcard_r 2015-11-26 20:07 yahoo
[email protected]:/sdcard $ cd Movies
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $
travisgp19 said:
Hello, sir. I don't think it showed any movie file, but I can actually see files found in the SD card just fine, the Internal Memory is what I could not see, sorry if I got confused but here:
C:\Users\B570>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ ls -la
drwxrwx--- root sdcard_r 2015-11-27 16:02 .DataStorage
drwxrwx--- root sdcard_r 2015-11-26 20:45 .Hnc
drwxrwx--- root sdcard_r 2015-11-26 20:07 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 16:02 .UTSystemConfig
drwxrwx--- root sdcard_r 2015-11-26 20:07 .face
drwxrwx--- root sdcard_r 2013-12-31 16:02 Alarms
drwxrwx--x root sdcard_r 2013-12-31 16:02 Android
drwxrwx--- root sdcard_r 2015-11-26 20:46 DCIM
drwxrwx--- root sdcard_r 2013-12-31 16:02 Download
drwxrwx--- root sdcard_r 2013-12-31 16:02 Movies
drwxrwx--- root sdcard_r 2013-12-31 16:02 Music
drwxrwx--- root sdcard_r 2015-11-26 20:45 My Documents
drwxrwx--- root sdcard_r 2013-12-31 16:02 Notifications
drwxrwx--- root sdcard_r 2015-11-26 20:07 Pictures
drwxrwx--- root sdcard_r 2015-11-26 20:57 Playlists
drwxrwx--- root sdcard_r 2013-12-31 16:02 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 20:07 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 21:35 SnoteData
drwxrwx--- root sdcard_r 2015-11-26 20:23 media
drwxrwx--- root sdcard_r 2015-11-26 20:07 yahoo
[email protected]:/sdcard $ cd Movies
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $ ls -la
[email protected]:/sdcard/Movies $
Click to expand...
Click to collapse
That's is the internal memory we are looking at. It's called /sdcard in the system. It is confusing.
The "add-on" Sdcard (the mirco-sdcard you added) is called extSdCard in system.
[email protected]:/
2|[email protected]:/ $ cd storage
cd storage
2|[email protected]:/storage $ ls -la
ls -la
d--------- system system 2015-11-27 19:21 Private
drwx------ root root 2015-11-27 19:21 UsbDriveA
drwx------ root root 2015-11-27 19:21 UsbDriveB
drwx------ root root 2015-11-27 19:21 UsbDriveC
drwx------ root root 2015-11-27 19:21 UsbDriveD
drwx------ root root 2015-11-27 19:21 UsbDriveE
drwx------ root root 2015-11-27 19:21 UsbDriveF
dr-xr-xr-x root root 2015-11-27 19:21 emulated
drwx--x--x system system 2015-11-27 19:21 enc_emulated
drwxrwx--x root sdcard_r 2015-11-27 19:21 extSdCard ADD-ON CARD
lrwxrwxrwx root root 2015-11-27 19:21 knox-emulated -> /mnt/shell/knox-emulated
lrwxrwxrwx root root 2015-11-27 19:21 sdcard0 -> /storage/emulated/legacy Internal Memory
[email protected]:/storage $ cd extSdCard
[email protected]:/storage/extSdCard $ ls -la
ls -la
drwxrwx--- root sdcard_r 2015-11-03 11:58 .SIc-yJMAhEcjs6wmSi9Uhdeyr_M=
lstat './.android_secure' failed: Permission denied
-rwxrwx--- root sdcard_r 33 2015-08-15 09:08 .tcookieid
drwxrwx--x root sdcard_r 2015-09-20 11:52 Android
-rwxrwx--- root sdcard_r 212060 2015-11-27 11:18 Contacts.vcf
drwxrwx--- root sdcard_r 2015-10-11 11:02 DCIM
drwxrwx--- root sdcard_r 2015-10-31 14:43 Documents
drwxrwx--- root sdcard_r 2015-10-30 13:19 Download
drwxrwx--- root sdcard_r 2015-08-15 09:08 LOST.DIR
drwxrwx--- root sdcard_r 2015-08-18 22:30 Media
-rwxrwx--- root sdcard_r 39664801 2015-11-09 15:39 N910C_COI6_Modem.zip
drwxrwx--- root sdcard_r 2015-11-02 10:08 Pictures
-rwxrwx--- root sdcard_r 8052986 2015-11-08 23:50 SamsungCamera3_Mod_N910C.zip
-rwxrwx--- root sdcard_r 8044211 2015-11-25 22:44 SamsungCamera3_Mod_N910C_v1.2.zip
drwxrwx--- root sdcard_r 2015-10-19 12:27 SamsungCamera4-V3.1
drwxrwx--- root sdcard_r 2015-08-15 09:08 System Volume Information
drwxrwx--- root sdcard_r 2015-08-15 09:08 TWRP
-rwxrwx--- root sdcard_r 11392327 2015-11-23 22:59 TouchWizHome_ZERO_6dock.zip
drwxrwx--- root sdcard_r 2015-11-26 14:14 backup
-rwxrwx--- root sdcard_r 12398592 2015-11-09 21:17 boot.img
drwxrwx--- root sdcard_r 2015-11-27 19:57 clockworkmod
drwxrwx--- root sdcard_r 2015-08-15 09:08 data
drwxrwx--- root sdcard_r 2015-09-04 18:47 doubleTwist
drwxrwx--- root sdcard_r 2015-11-25 22:48 files
drwxrwx--- root sdcard_r 2015-09-29 21:34 sms
drwxrwx--- root sdcard_r 2015-11-27 05:26 tibu
-rwxrwx--- root sdcard_r 5430 2015-10-26 01:22 tk_gapps_log.txt
-rwxrwx--- root sdcard_r 14770457 2015-11-23 17:57 twrp-2.8.5.0-trltexx.zip
-rwxrwx--- root sdcard_r 13646793 2015-11-23 17:57 twrp-2.8.6.0-trltexx.zip
[email protected]:/storage/extSdCard $
That shows what is on your micro-sdcard you added in.
So I'm confused as to which one you are looking for files.
dicksteele said:
That's is the internal memory we are looking at. It's called /sdcard in the system. It is confusing.
The "add-on" Sdcard (the mirco-sdcard you added) is called extSdCard in system.
[email protected]:/
2|[email protected]:/ $ cd storage
cd storage
2|[email protected]:/storage $ ls -la
ls -la
d--------- system system 2015-11-27 19:21 Private
drwx------ root root 2015-11-27 19:21 UsbDriveA
drwx------ root root 2015-11-27 19:21 UsbDriveB
drwx------ root root 2015-11-27 19:21 UsbDriveC
drwx------ root root 2015-11-27 19:21 UsbDriveD
drwx------ root root 2015-11-27 19:21 UsbDriveE
drwx------ root root 2015-11-27 19:21 UsbDriveF
dr-xr-xr-x root root 2015-11-27 19:21 emulated
drwx--x--x system system 2015-11-27 19:21 enc_emulated
drwxrwx--x root sdcard_r 2015-11-27 19:21 extSdCard ADD-ON CARD
lrwxrwxrwx root root 2015-11-27 19:21 knox-emulated -> /mnt/shell/knox-emulated
lrwxrwxrwx root root 2015-11-27 19:21 sdcard0 -> /storage/emulated/legacy Internal Memory
[email protected]:/storage $ cd extSdCard
[email protected]:/storage/extSdCard $ ls -la
ls -la
drwxrwx--- root sdcard_r 2015-11-03 11:58 .SIc-yJMAhEcjs6wmSi9Uhdeyr_M=
lstat './.android_secure' failed: Permission denied
-rwxrwx--- root sdcard_r 33 2015-08-15 09:08 .tcookieid
drwxrwx--x root sdcard_r 2015-09-20 11:52 Android
-rwxrwx--- root sdcard_r 212060 2015-11-27 11:18 Contacts.vcf
drwxrwx--- root sdcard_r 2015-10-11 11:02 DCIM
drwxrwx--- root sdcard_r 2015-10-31 14:43 Documents
drwxrwx--- root sdcard_r 2015-10-30 13:19 Download
drwxrwx--- root sdcard_r 2015-08-15 09:08 LOST.DIR
drwxrwx--- root sdcard_r 2015-08-18 22:30 Media
-rwxrwx--- root sdcard_r 39664801 2015-11-09 15:39 N910C_COI6_Modem.zip
drwxrwx--- root sdcard_r 2015-11-02 10:08 Pictures
-rwxrwx--- root sdcard_r 8052986 2015-11-08 23:50 SamsungCamera3_Mod_N910C.zip
-rwxrwx--- root sdcard_r 8044211 2015-11-25 22:44 SamsungCamera3_Mod_N910C_v1.2.zip
drwxrwx--- root sdcard_r 2015-10-19 12:27 SamsungCamera4-V3.1
drwxrwx--- root sdcard_r 2015-08-15 09:08 System Volume Information
drwxrwx--- root sdcard_r 2015-08-15 09:08 TWRP
-rwxrwx--- root sdcard_r 11392327 2015-11-23 22:59 TouchWizHome_ZERO_6dock.zip
drwxrwx--- root sdcard_r 2015-11-26 14:14 backup
-rwxrwx--- root sdcard_r 12398592 2015-11-09 21:17 boot.img
drwxrwx--- root sdcard_r 2015-11-27 19:57 clockworkmod
drwxrwx--- root sdcard_r 2015-08-15 09:08 data
drwxrwx--- root sdcard_r 2015-09-04 18:47 doubleTwist
drwxrwx--- root sdcard_r 2015-11-25 22:48 files
drwxrwx--- root sdcard_r 2015-09-29 21:34 sms
drwxrwx--- root sdcard_r 2015-11-27 05:26 tibu
-rwxrwx--- root sdcard_r 5430 2015-10-26 01:22 tk_gapps_log.txt
-rwxrwx--- root sdcard_r 14770457 2015-11-23 17:57 twrp-2.8.5.0-trltexx.zip
-rwxrwx--- root sdcard_r 13646793 2015-11-23 17:57 twrp-2.8.6.0-trltexx.zip
[email protected]:/storage/extSdCard $
That shows what is on your micro-sdcard you added in.
So I'm confused as to which one you are looking for files.
Click to expand...
Click to collapse
I remember now, I'm sorry. Yes it's the SDCARD (internal memory) I could not access. The CMD lines I pasted also reflected what I get if I access it via the Kies/Explorer GUIs. Is there a software that can recover my files that seem to be encrypted now? Thanks, sir
travisgp19 said:
I remember now, I'm sorry. Yes it's the SDCARD (internal memory) I could not access. The CMD lines I pasted also reflected what I get if I access it via the Kies/Explorer GUIs. Is there a software that can recover my files that seem to be encrypted now? Thanks, sir
Click to expand...
Click to collapse
Not sure how they got encrypted. I am tripping on the date differences
Everything you are looking for looks to be probably original phone date. Everything else is recent.
C:\Users\B570>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ ls -la
drwxrwx--- root sdcard_r 2015-11-27 16:02 .DataStorage
drwxrwx--- root sdcard_r 2015-11-26 20:45 .Hnc
drwxrwx--- root sdcard_r 2015-11-26 20:07 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 16:02 .UTSystemConfig
drwxrwx--- root sdcard_r 2015-11-26 20:07 .face
drwxrwx--- root sdcard_r 2013-12-31 16:02 Alarms
drwxrwx--x root sdcard_r 2013-12-31 16:02 Android
drwxrwx--- root sdcard_r 2015-11-26 20:46 DCIM
drwxrwx--- root sdcard_r 2013-12-31 16:02 Download
drwxrwx--- root sdcard_r 2013-12-31 16:02 Movies
drwxrwx--- root sdcard_r 2013-12-31 16:02 Music
drwxrwx--- root sdcard_r 2015-11-26 20:45 My Documents
drwxrwx--- root sdcard_r 2013-12-31 16:02 Notifications
drwxrwx--- root sdcard_r 2015-11-26 20:07 Pictures
drwxrwx--- root sdcard_r 2015-11-26 20:57 Playlists
drwxrwx--- root sdcard_r 2013-12-31 16:02 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 20:07 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 21:35 SnoteData
drwxrwx--- root sdcard_r 2015-11-26 20:23 media
drwxrwx--- root sdcard_r 2015-11-26 20:07 yahoo
You can try Dr Fone from Wondershare. See what it sees.... There's a trial version, I think you may be able to recover a few files as a limit, then you need to purchase to do more. Its been awhile since I've used it.
dicksteele said:
Not sure how they got encrypted. I am tripping on the date differences
Everything you are looking for looks to be probably original phone date. Everything else is recent.
C:\Users\B570>adb shell
[email protected]:/ $ cd /sdcard
[email protected]:/sdcard $ ls -la
drwxrwx--- root sdcard_r 2015-11-27 16:02 .DataStorage
drwxrwx--- root sdcard_r 2015-11-26 20:45 .Hnc
drwxrwx--- root sdcard_r 2015-11-26 20:07 .SPenSDK30
drwxrwx--- root sdcard_r 2015-11-27 16:02 .UTSystemConfig
drwxrwx--- root sdcard_r 2015-11-26 20:07 .face
drwxrwx--- root sdcard_r 2013-12-31 16:02 Alarms
drwxrwx--x root sdcard_r 2013-12-31 16:02 Android
drwxrwx--- root sdcard_r 2015-11-26 20:46 DCIM
drwxrwx--- root sdcard_r 2013-12-31 16:02 Download
drwxrwx--- root sdcard_r 2013-12-31 16:02 Movies
drwxrwx--- root sdcard_r 2013-12-31 16:02 Music
drwxrwx--- root sdcard_r 2015-11-26 20:45 My Documents
drwxrwx--- root sdcard_r 2013-12-31 16:02 Notifications
drwxrwx--- root sdcard_r 2015-11-26 20:07 Pictures
drwxrwx--- root sdcard_r 2015-11-26 20:57 Playlists
drwxrwx--- root sdcard_r 2013-12-31 16:02 Podcasts
drwxrwx--- root sdcard_r 2015-11-26 20:07 Ringtones
drwxrwx--- root sdcard_r 2015-11-26 21:35 SnoteData
drwxrwx--- root sdcard_r 2015-11-26 20:23 media
drwxrwx--- root sdcard_r 2015-11-26 20:07 yahoo
You can try Dr Fone from Wondershare. See what it sees.... There's a trial version, I think you may be able to recover a few files as a limit, then you need to purchase to do more. Its been awhile since I've used it.
Click to expand...
Click to collapse
Thanks, Dr. Fone says they can't recover encrypted data. I still feel like somebody just punched me in the gut. I'm so stupid man :'( All those family memories gone is what I feel the worst
travisgp19 said:
Thanks, Dr. Fone says they can't recover encrypted data. I still feel like somebody just punched me in the gut. I'm so stupid man :'( All those family memories gone is what I feel the worst
Click to expand...
Click to collapse
Give it a try anyways. See what it sees.
I read this again
-My video and image files were never private, only a handful of PDF legal document files. The long gray bar in the 31/32GB portion of the image is that set of missing files
That is telling me you had the stuff on the EXTERNAL Sdcard. The microsdcard. The size of it 32GB is what makes me think that.
So Dr Fone should see them.
dicksteele said:
Give it a try anyways. See what it sees.
I read this again
-My video and image files were never private, only a handful of PDF legal document files. The long gray bar in the 31/32GB portion of the image is that set of missing files
That is telling me you had the stuff on the EXTERNAL Sdcard. The microsdcard. The size of it 32GB is what makes me think that.
So Dr Fone should see them.
Click to expand...
Click to collapse
No, here is the image again, if you can see there are three bars: http://i.imgur.com/Puonis8.jpg
The one in the bottom is for the External Card whose files I can all see and they're all in color too in that graph. The middle graph is all the files inside the Note 4's internal memory. I had about 2.5 GB Free space in the internal storage before all this glitch happened so the amount is just about right, the only problem is they're not showing up at all
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?