Related
HI,
I need big help, any comments are appreciated.
I was rooting my kindle again after 6.2.1 update.
Everything was OK, until I changed the /system/apps folder permission to r/w for all users using file exporer.
After that, I started not to be able to launch anything.
I tied to reboot and my kindle now stuck at the screen saying "kindle fire" and it flashes every 10 secs or so.
I tried Kindle_Fire_Utility_v0.9.1 several options with no success.
I can connect via adb and see the directories but I can not do adb root.
It mount the files system as read only.
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb root
adbd cannot run as root in production builds
It is almost like, everything is fine but the system can not find the apps to run.
Is there any way I can recover?
Here are directories and permissions:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -l /system
drwxr-xr-x root root 1969-12-31 19:00 lost+found
drwsrwsrwt root root 2011-12-23 00:57 app
drwxr-xr-x root shell 2011-12-23 00:57 bin
-rw-r--r-- root root 2151 2008-08-01 08:00 build.prop
drwxr-xr-x root root 2011-12-23 00:57 etc
drwxr-xr-x root root 2011-12-23 00:57 fonts
drwxr-xr-x root root 2011-12-23 00:57 framework
drwxr-xr-x root root 2011-12-23 00:57 lib
drwxr-xr-x root root 2011-12-23 00:57 media
drwxr-xr-x root root 2011-12-23 00:57 tts
drwxr-xr-x root root 2011-12-23 00:57 usr
drwxr-xr-x root shell 2011-12-23 00:57 vendor
drwxr-xr-x root shell 2012-01-01 20:57 xbin
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -l /system/app
-rwsr-sr-x root root 2669573 2008-08-01 08:00 ATVAndroidClient.apk
-rwsr-sr-x root root 233689 2008-08-01 08:00 AccountAndSyncSettings.apk
-rwsr-sr-x root root 3581882 2008-08-01 08:00 AmazonVenezia.apk
-rwsr-sr-x root root 29574 2008-08-01 08:00 ApplicationsProvider.apk
-rwsr-sr-x root root 3574986 2008-08-01 08:00 AudibleAndroidApplication-venezia.apk
-rwsr-sr-x root root 164188 2008-08-01 08:00 CSApp-unsigned.apk
-rwsr-sr-x root root 152004 2008-08-01 08:00 CalendarProvider.apk
-rwsr-sr-x root root 116225 2008-08-01 08:00 CertInstaller.apk
-rwsr-sr-x root root 2981513 2008-08-01 08:00 Cloud9-unsigned.apk
-rwsr-sr-x root root 57201 2008-08-01 08:00 Cloud9SystemBrowserProvider-unsigned.apk
-rwsr-sr-x root root 2049942 2008-08-01 08:00 Contacts.apk
-rwsr-sr-x root root 145545 2008-08-01 08:00 ContactsProvider.apk
-rwsr-sr-x root root 20748 2008-08-01 08:00 DefaultContainerService.apk
-rwsr-sr-x root root 196150 2008-08-01 08:00 DownloadProvider.apk
-rwsr-sr-x root root 106749 2008-08-01 08:00 DownloadProviderUi.apk
-rwsr-sr-x root root 32432 2008-08-01 08:00 DrmProvider.apk
-rwsr-sr-x root root 2314082 2008-08-01 08:00 Email.apk
-rwsr-sr-x root root 16891 2008-08-01 08:00 Facebook.apk
-rwsr-sr-x root root 833544 2008-08-01 08:00 Gallery3D.apk
-rwsr-sr-x root root 22792 2008-08-01 08:00 HTMLViewer.apk
-rwsr-sr-x root root 1685594 2008-08-01 08:00 IMDb-2.3.apk
-rwsr-sr-x root root 16424248 2008-08-01 08:00 KindleForOtter.apk
-rwsr-sr-x root root 1082002 2008-08-01 08:00 LatinIME.apk
-rwsr-sr-x root root 12174501 2008-08-01 08:00 Launcher.apk
-rwsr-sr-x root root 1140587 2008-08-01 08:00 LiveWallpapers.apk
-rwsr-sr-x root root 51276 2008-08-01 08:00 LiveWallpapersPicker.apk
-rwsr-sr-x root root 224152 2008-08-01 08:00 MagicSmokeWallpapers.apk
-rwsr-sr-x root root 20783 2008-08-01 08:00 MarketIntentProxy.apk
-rwsr-sr-x root root 62533 2008-08-01 08:00 MediaProvider.apk
-rwsr-sr-x root root 149113 2008-08-01 08:00 MyAccount-unsigned.apk
-rwsr-sr-x root root 253119 2008-08-01 08:00 OOBE-unsigned.apk
-rwsr-sr-x root root 26979 2008-08-01 08:00 OTASilentInstall.apk
Some more and strange info:
$ cd /mnt
$ ls -l
ls -l
drwxr-xr-x root system 2012-01-02 01:38 obb
drwxr-xr-x root system 2012-01-02 01:38 asec
drwx------ root root 2012-01-02 01:38 secure
d--------- system system 2012-01-02 01:38 sdcard
I can not do su, I can not reach any directory. (including sdcard).
I can not do even whoami:
$ whoami
whoami
whoami: permission denied
as a first step you could try if this is successfull:
adb shell
look if your prompt is $ or # - if it is $ type su - must change to #
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
if not you can try to install twrp (if you not allready have)
http://forum.xda-developers.com/showthread.php?t=1414832
and flash a backup, the stockrom or one of the roms available in the forum
HI Thanks for the reply.
adb shell works and prompt changes to #
su does not work.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
does not work, says I don't have the permission. I think this is because of readonly file system.
have you tried the second solution ?
I will try tonight but, I am not sure whether it will work. Because, if I am not calling wrong, I tried to get into data directory last night and could not.
But I will try tonight again and will let you know.
Thanks again.
Second solution works, I fixed this same problem that way.
BUT. Be careful what you do next, as I flashed the stock rom and now my Fire is bricked again and with a non working adb. So, again, be VERY CAREFUL
osozraz,
So given you experience, which rom should I use?
absolutely right ! - i would suggest one of the prerooted stock roms from here
http://forum.xda-developers.com/showthread.php?t=1402440
uniqua97 said:
osozraz,
So given you experience, which rom should I use?
Click to expand...
Click to collapse
I can´t say, as my Fire is still bricked and that was the first rom i installed. For my experience, DON´T flash the stock rom.
Thanks a lot for all the help.
The solution about fbmode in the following thread is worked:
http://forum.xda-developers.com/showthread.php?t=1414832
Then I installed TWRP using Kindle Fire Utility v0.9.1:
http://forum.xda-developers.com/showthread.php?t=1399889
Then I used update-6.2.1-rooted-unsecureboot.zip with TWRP:
http://forum.xda-developers.com/showthread.php?t=1402440
The videos from the following links are also awesome:
http://www.jayceooi.com/2011/12/29/how-to-install-twrp-2-0-recovery-on-kindle-fire-video/
http://www.jayceooi.com/2011/12/30/...droid-rom-on-kindle-fire-with-twrp-2-0-video/
There are more videos in those links.
Hope this helps to others as well.
Problem fixed !!! Thansk!
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
would thing you get the $ prompt if you open the adb shell
enter "su" - the prompt should change to #
then the remount command should succeed
enter "su" - the prompt should change to # in shell mode
then type : # adb remount ?
could you get me a detail command set ?. because kindle fire is my first's android device , BIG THANKS!
this should be the way it works:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
the bold commands are the ones to enter ...
My file is saved in c:\apps\hk.cedime.inputmethod.apk
and also have a copy in c:\adb\hk.cedime.inputmethod.apk
Show many error ??? Any expert can help?
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# install c:\apps\hk.cedime.inputmethod.apk /system/app/
install c:\apps\hk.cedime.inputmethod.apk /system/app/
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
# install hk.cedime.inputmethod.apk /system/app/
install hk.cedime.inputmethod.apk /system/app/
install: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp hk.cedime.inputmethod.apk /system/app/
cp hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
Click to expand...
Click to collapse
it don't find the .apk file
i use to put the files to install in the directory where adb.exe resides
and do the command without a path ie: install hk.cedime.inputmethod.apk /system/app/
furthermore i'm not shure if the command works inside the adb shell
would also try (from command prompt):
adb install c:\apps\hk.cedime.inputmethod.apk /system/app/
or if .apk in current directory (where adb resides):
adb install hk.cedime.inputmethod.apk /system/app/
Adb command is my first choice
But the system show the error : can't find '/system/app/' to install
then it seems not to be mounted ...
try to check with:
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system"
"cd \system"
"ls -l" -> any directory listing here ?
"cd app"
"ls -l" -> any apk's listed ?
OH! my God!
c:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
no problem - if it's not mounted it's hard to remount
would try:
"mount /system" in adb shell
or
"adb shell mount -o remount rw /system" from the command prompt
Sorry, many problem can't fix...............
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# ls -l
ls -l
dr-x------ root root 2012-03-19 05:51 config
drwxrwx--- system system 2012-03-20 07:00 dropbox
drwxrwx--- system cache 2012-03-19 05:51 cache
lrwxrwxrwx root root 2012-03-19 05:51 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-03-19 05:51 acct
drwxrwxr-x root system 2012-03-19 05:51 mnt
lrwxrwxrwx root root 2012-03-19 05:51 vendor -> /system/vendor
lrwxrwxrwx root root 2012-03-19 05:51 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-03-19 05:51 etc -> /system/etc
-rw-r--r-- root root 4203 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 840 1969-12-31 16:00 ueventd.omap4430.rc
-rw-r--r-- root root 0 1969-12-31 16:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-01-19 04:27 system
drwxr-xr-x root root 2012-03-19 05:51 sys
drwxr-x--- root root 1969-12-31 16:00 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 14869 1969-12-31 16:00 init.rc
-rwxr-x--- root root 11357 1969-12-31 16:00 init.omap4430.rc
-rwxr-x--- root root 1677 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 94200 1969-12-31 16:00 init
-rw-r--r-- root root 118 1969-12-31 16:00 default.prop
drwxrwx--x system system 2012-03-18 06:53 data
drwx------ root root 2012-01-09 22:20 root
drwxr-xr-x root root 2012-03-19 06:01 dev
# cd app
cd app
cd: can't cd to app
#
from your post #5:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
this has seemed to work - or was there allways a error message following up which you did'nt copy and paste ?
usually "mount /system" is sufficient - "mount -w /system" should work too
# cd app
cd app
cd: can't cd to app
Click to expand...
Click to collapse
if you look to the directory listing you are on the root - there is no directory or mountpoint "app" - it is in the system directory - the command should be:
"cd \system"
"ls -l" -> any directory listing here ?
and then if you are in "system"
"cd app"
"ls -l" -> any apk's listed ?
as in post #8
Expert ! Next step what can i do?
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd \system
cd \system
# ls -l
ls -l
drwxr-xr-x root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2012-03-19 05:49 app
drwxr-xr-x root shell 2012-03-17 18:19 bin
-rw-r--r-- root root 2151 2008-08-01 05:00 build.prop
drwxr-xr-x root root 2012-01-19 04:27 etc
drwxr-xr-x root root 2012-01-19 04:27 fonts
drwxr-xr-x root root 2012-01-19 04:27 framework
drwxr-xr-x root root 2012-01-19 04:27 lib
drwxr-xr-x root root 2012-01-19 04:27 media
drwxr-xr-x root root 2012-01-19 04:27 tts
drwxr-xr-x root root 2012-01-19 04:27 usr
drwxr-xr-x root shell 2012-01-19 04:27 vendor
drwxr-xr-x root shell 2012-03-17 20:51 xbin
# cd app
cd app
# ls -l
ls -l
-rw-r--r-- root root 2669573 2008-08-01 05:00 ATVAndroidClient.apk
-rw-r--r-- root root 233689 2008-08-01 05:00 AccountAndSyncSettings.ap
k
-rw-r--r-- root root 3581879 2008-08-01 05:00 AmazonVenezia.apk
-rw-r--r-- root root 29574 2008-08-01 05:00 ApplicationsProvider.apk
-rw-r--r-- root root 3574986 2008-08-01 05:00 AudibleAndroidApplication
-venezia.apk
-rw-r--r-- root root 164188 2008-08-01 05:00 CSApp-unsigned.apk
-rw-r--r-- root root 152004 2008-08-01 05:00 CalendarProvider.apk
-rw-r--r-- root root 116225 2008-08-01 05:00 CertInstaller.apk
-rw-r--r-- root root 4019454 2008-08-01 05:00 Cloud9-release-unsigned.a
pk
-rw-r--r-- root root 57208 2008-08-01 05:00 Cloud9SystemBrowserProvid
er-unsigned.apk
-rw-r--r-- root root 2049942 2008-08-01 05:00 Contacts.apk
-rw-r--r-- root root 145545 2008-08-01 05:00 ContactsProvider.apk
-rw-r--r-- root root 20748 2008-08-01 05:00 DefaultContainerService.a
pk
-rw-r--r-- root root 196150 2008-08-01 05:00 DownloadProvider.apk
-rw-r--r-- root root 106749 2008-08-01 05:00 DownloadProviderUi.apk
-rw-r--r-- root root 32432 2008-08-01 05:00 DrmProvider.apk
-rw-r--r-- root root 2315338 2008-08-01 05:00 Email.apk
-rw-r--r-- root root 16892 2008-08-01 05:00 Facebook.apk
-rw-r--r-- root root 833544 2008-08-01 05:00 Gallery3D.apk
-rw-r--r-- root root 22792 2008-08-01 05:00 HTMLViewer.apk
-rw-r--r-- root root 1685594 2008-08-01 05:00 IMDb-2.3.apk
-rw-r--r-- root root 16424244 2008-08-01 05:00 KindleForOtter.apk
-rw-r--r-- root root 1082002 2008-08-01 05:00 LatinIME.apk
-rw-r--r-- root root 12174497 2008-08-01 05:00 Launcher.apk
-rw-r--r-- root root 1140587 2008-08-01 05:00 LiveWallpapers.apk
-rw-r--r-- root root 51276 2008-08-01 05:00 LiveWallpapersPicker.apk
-rw-r--r-- root root 224152 2008-08-01 05:00 MagicSmokeWallpapers.apk
-rw-r--r-- root root 20778 2008-08-01 05:00 MarketIntentProxy.apk
-rw-r--r-- root root 62533 2008-08-01 05:00 MediaProvider.apk
-rw-r--r-- root root 149119 2008-08-01 05:00 MyAccount-unsigned.apk
-rw-r--r-- root root 253116 2008-08-01 05:00 OOBE-unsigned.apk
-rw-r--r-- root root 26983 2008-08-01 05:00 OTASilentInstall.apk
-rw-r--r-- root root 110563 2008-08-01 05:00 OtterAppManager.apk
-rw-r--r-- root root 1907710 2008-08-01 05:00 OtterTutorial.apk
-rw-r--r-- root root 122758 2008-08-01 05:00 PackageInstaller.apk
-rw-r--r-- root root 22282 2008-08-01 05:00 PicoTts.apk
-rw-r--r-- root root 10496 2008-08-01 05:00 Provision.apk
-rw-r--r-- root root 2305323 2008-08-01 05:00 Pulse-amazon.apk
-rw-r--r-- root root 412698 2008-08-01 05:00 QuickSearchBox.apk
-rw-r--r-- root root 320688 2008-08-01 05:00 QuickSettings.apk
-rw-r--r-- root root 6302776 2008-08-01 05:00 Quickoffice_AMAZON_4.1.46
7_VC.apk
-rw-r--r-- root root 3751962 2008-08-01 05:00 Settings.apk
-rw-r--r-- root root 48682 2008-08-01 05:00 SettingsProvider.apk
-rw-r--r-- root root 604484 2008-08-01 05:00 SystemUI.apk
-rw-r--r-- root root 30187 2008-08-01 05:00 TtsService.apk
-rw-r--r-- root root 16928 2008-08-01 05:00 UserDictionaryProvider.ap
k
-rw-r--r-- root root 165579 2008-08-01 05:00 VisualizationWallpapers.a
pk
-rw-r--r-- root root 34247 2008-08-01 05:00 VpnServices.apk
-rw-r--r-- root root 1669753 2008-08-01 05:00 Windowshop.apk
-rw-r--r-- root root 6113490 2008-08-01 05:00 air_runtime.apk
-rw-r--r-- root root 2109670 2008-08-01 05:00 amazonmp3-unsigned.apk
-rw-r--r-- root root 2500819 2008-08-01 05:00 com.amazon.dcp.apk
-rw-r--r-- root root 45888 2008-08-01 05:00 oem_install_flash_player_
signed.apk
-rw-r--r-- root root 843503 2008-02-28 10:33 Superuser.apk
-rw-rw-rw- root root 89707 2011-12-07 02:26 GoogleFeedback.apk
-rw-rw-rw- root root 1401398 2011-12-07 02:13 GoogleServicesFramework.a
pk
-rw-rw-rw- root root 1529836 2011-12-07 02:15 Vending.apk
-rw-rw-rw- root root 4089926 2011-12-07 02:22 GO_Launcher_EX_2.65.apk
-rw-rw-rw- root root 2053065 2012-03-19 05:49 hk.cedime.inputmethod.apk
#
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
as you run a unsecure kernel i think the command should be:
adb shell su -c "remount"
or
adb shell su -c "mount -o remount rw /system"
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
the second attempt succeeded - so your question seems to be answered or not ?
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
Click to expand...
Click to collapse
Expert!
i follow this link
http://forum.xda-developers.com/showthread.php?t=1364543
to fixed my problem, Thanks for your support again!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
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:
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?
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