All files became INVISIBLE/encrypted after Rand. Restart & Prompted a "New Phone".. - Galaxy Note 4 Q&A, Help & Troubleshooting

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

Related

[Q] Need a tad bit of help with using commands

K, i've got a wii emulator, but i don't understand how to run these commands !!! +_+
To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root.
Code:
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_pagefault_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ib_check
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/long_ib_detect
Can someone please educate me on how this is suppose to work? do i need an android terminal? or how do i go about running these commands?
(yes my phone is rooted)
Thanks
Ryan
milkydude12 said:
i don't understand how to run these commands
Click to expand...
Click to collapse
These are system commands and you need to run them from the "command line". The easiest way to do that would be to install a terminal application. Android Terminal Emulator by Jack Palevich is one good choice. Or you could run an adb shell.
After you install terminal emulator, enter
su [enter]
Click to expand...
Click to collapse
"su" is the command for superuser (root access). Then you can use the system configuration commands that you have for your wii emulator.
If any commands need to be reentered each time you use your emulator, then you could use a scripting app like gscript light which can be configured to enter these commands from a bookmark. i.e. just click on a bookmark and it will run a set of commands for you.
.
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
milkydude12 said:
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
Click to expand...
Click to collapse
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
jd1639 said:
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
Click to expand...
Click to collapse
I got the commands from here https://forums.dolphin-emu.org/Thread-opengl-es-3-guide i apologize if im not supposed to post link +_+
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are you trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You check your filesystem to see if those paths exist or if the file names can be found elsewhere. Then look to the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands (or install a text editor) to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
fffft said:
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You should look at your filesystem as jd1639 suggested to see if those paths exist or if the file names can be found elsewhere. And if necessary, re-read the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
Click to expand...
Click to collapse
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
milkydude12 said:
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
Click to expand...
Click to collapse
The answer to that will be in your emulator thread.
More to the point, you haven't done your homework yet. Do those paths and files exist on your phone? Does the emulator thread clarify if all of those settings are required? And did you try creating any missing files? People are trying to help you here, but we can't see what your phone screen actually shows. And you should be doing most of the work to see what does or doesn't work.
.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debugkgsl-3d0
tmp-mksh: cd: /sys/kernal/debugkgsl-3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 20:41 cache-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -namefast_hang_detect
find: unrecognized: -namefast_hang_detect
BusyBox v1.21.1-Stericson (2013-09-26 14:33:26 BST) multi-call binary.
Usage: find [PATH]... [OPTIONS] [ACTIONS]
Search for files and perform actions on them.
First failed action stops processing of current file.
Defaults: PATH is current directory, action is '-print'
-follow Follow symlinks
-xdev Don't descend directories on other filesystems
-maxdepth N Descend at most N levels. -maxdepth 0 applies
actions to command line arguments only
-mindepth N Don't act on first N levels
-depth Act on directory *after* traversing it
Actions:
( ACTIONS ) Group actions for -o / -a
! ACT Invert ACT's success/failure
ACT1 [-a] ACT2 If ACT1 fails, stop, else do ACT2
ACT1 -o ACT2 If ACT1 succeeds, stop, else do ACT2 Note: -a has higher priority than -o -name PATTERN Match file name (w/o directory name) to PATTERN
-iname PATTERN Case insensitive -name
-path PATTERN Match path to PATTERN
-ipath PATTERN Case insensitive -path
-regex PATTERN Match path to regex PATTERN
-type X File type is X (one of: f,d,l,b,c,...)
-perm MASK At least one mask bit (+MASK), all bits (-MASK),
or exactly MASK bits are set in file's mode
-mtime DAYS mtime is greater than (+N), less than (-N),
or exactly N days in the past
-mmin MINS mtime is greater than (+N), less than (-N),
or exactly N minutes in the past
-newer FILE mtime is more recent than FILE's
-inum N File has inode number N
-user NAME/ID File is owned by given user
-group NAME/ID File is owned by given group
-size N[bck] File size is N (c:bytes,k:kbytes,b:512 bytes(def.))
+/-N: file size is bigger/smaller than N
-links N Number of links is greater than (+N), less than (-N),
or exactly N
-prune If current file is directory, don't descend into it
If none of the following actions is specified, -print is assumed
-print Print file name
-print0 Print file name, NUL terminated
-exec CMD ARG ; Run CMD with all instances of {} replaced by
file name. Fails if CMD exits with nonzero
-delete Delete current file/directory. Turns on -depth option
1|[email protected]:/ #
That is what i get, for the life of me i can't figure out if that means i have it or i don't. "On the Thread it says To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root."
So I'm assuming i require all of them to work in order for any difference. Certain sites list the I337m varient as one of which supports Open Gl ES 3 so i assume it would work
All right, I can understand how a lot of this might be a challenge to understand if you have no experience with linux. But you at least need to make sure that you aren't making typos when using these commands.
e.g.
[email protected]:/ # find / -namefast_hang_detect
Click to expand...
Click to collapse
You missed a space between -name and the actual file name. And yes, that is critical. Nothing here is likely to work if you have typos. Try the following and paste the results back here. And I or someone else will better understand what is going on::
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
(exactly as above and paste the result for us).
If you are ambitious then also try the following for any "missing" files and let us know if that succeeds in getting your emulator up and running.
e.g.
# touch /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
# echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
.
:S thanks i didn't know i had missed a space, and yea i have little to no experience with linux.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debug/kgsl/3d0
tmp-mksh: cd: /sys/kernal/debug/kgsl/3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 22:44 cache
-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1
drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -name fast_hang_detect
find: /proc/718/task/1014/fdinfo/459: No such file or directory
find: /proc/718/task/1015/fd/459: No such file or directory
find: /proc/718/task/1040/fd/459: No such file or directory
find: /proc/718/task/1331/fd/459: No such file or directory
find: /proc/718/task/1702/fd/459: No such file or directory
find: /proc/718/task/15245/fdinfo/459: No such file or directory
1|[email protected]:/ # touch /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect
gsl/kgsl-3d0/fast_hang_detect <
tmp-mksh: can't create /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect: No such file or directory
1|[email protected]:/ #
You're still making multiple typos, so we didn't get the information that we need.
.
.
After fixing all my typos and spending hours trying to get it to work, ive come to the conclusion, yea ive got the wrong phone model :S .... well that was a waste of time
:cyclops:

[Q] UICCUnlock failure(306SH)

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

/sdcard read only filesystem?

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?

I screw my sm-g900h ¿Unrecoverable?

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?

Random images appeared on root of Internal storage

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?

Categories

Resources