Related
I have a request with a small donation as a reward. I'm not rich, but I can reward with some beer money.
I have managed to somehow delete my build.prop file while rooted and then managed to un-root my device. Naturally, I rebooted.
My request is for anyone with a bit of extra time to modify zergRush so that it does not look to a build.prop file to verify the android version.
If there are any other ideas on how to root a bricked Fire without a build.prop file, be my guest.
My hope is that once I am able to re-root my device, I will be able to mount /system/ as writeable and then be able to push in a build.prop file. However, obviously, until that happens I cannot put in a build.prop file.
If you have any questions I pretty much let it all out on the "How to unblock your kindle" thread.
If no one is able to do this I would understand. This is obviously beyond my technical expertise but I do appreciate any efforts or even suggestions. Even if there's no attempts made here, it is still shocking how much help is given on this forum.
EDIT: I was able to get my hands on a valid system.img and then flashed the system.img to my system partition. Doing so corrected my build.prop and my device became bootable. Thanks for all the help.
Did it update to 6.2 while in the midst of your needing around?
what does your device do?
Does it show under adb devices?
ajq said:
Did it update to 6.2 while in the midst of your needing around?
Click to expand...
Click to collapse
I updated to 6.2 on Tuesday. I have followed the directions on the "UNBRICK your kindle" thread. I have done that successfully. However, because my build.prop is missing, I can no longer re-root using zergRush. I believe that fastboot as directed in that thread restores the kindle to factory settings. I'm not quite sure if factory settings is 6.2 or if it goes all the way back to 6.0.
death2all110 said:
what does your device do?
Does it show under adb devices?
Click to expand...
Click to collapse
This is the post I created in the "How to unbrick your kindle" thread. It should answer most questions. I can use adb shell on the device but I cannot mount anything and SU responds "permission denied".
----from the other thread----
I am in a similar situation and am trying to work through it. I thought I rooted my device but when I restarted it, it didn't fully load. I've successfully done all of the steps listed in the OP but am still suck in a black screen (it's lit...but it's black) loop.
I believe I have deleted my build.pop file but have a backup listend as build.prop.bak. However, the device is trying to load and is failing. I need to rename my build.prop.bak as the primary build.prop. I have tried to access SU through ADB but am getting "permission denied" almost as if my device wasn't rooted.
I have tried to mount system as RW but I am also getting permission denied.
Any advice. Here is my /system/
:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>cd \KindleFireRoot\files
C:\KindleFireRoot\files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /system/
cd /system/
$ ls -l
ls -l
drwxr-xr-x root root 1970-01-01 00:00 lost+found
drwxr-xr-x root root 2011-12-01 19:03 app
drwxr-xr-x root shell 2011-12-01 19:03 bin
drwxr-xr-x root root 2011-11-30 01:16 etc
drwxr-xr-x root root 2011-11-30 01:16 fonts
drwxr-xr-x root root 2011-11-30 01:16 framework
drwxr-xr-x root root 2011-11-30 01:16 lib
drwxr-xr-x root root 2011-11-30 01:16 media
drwxr-xr-x root root 2011-11-30 01:16 tts
drwxr-xr-x root root 2011-11-30 01:16 usr
drwxr-xr-x root shell 2011-11-30 01:16 vendor
drwxr-xr-x root shell 2011-12-01 19:03 xbin
-rw-r--r-- root root 2143 2008-08-01 12:00 build.prop.bak
$
EDIT: I have tried to re-root through the method provided as well as superoneclick root, but both have failed because no android system is being recognized. This may have to do with the lack of a proper build.prop on my device.
EDIT2: I figure the above might not be enough information so I will now post what I have done so far to get it bricked, and what I have already tried.
1. I tried the rooting method on rootkindlefire.com and it seemed successful. I then was able to set /system/ as RW via root explorer. I copied a modified build.prop file that is available in the android development forums. However, unfortunately, I believe I may have edited the name of this file or done something wrong in handling it accidentally. Regardless, I pasted this file in the /system/ folder and renamed my original build.prop file to build.prop.bak. I then restarted my kindle fire. Now, it shows the kindle fire screen for a second and then goes black entirely. It is still on (the screen is lit), but the screen is black. It then remains like this until I do a hard reset and then it repeats this process.
2. I have tried to access SU but have been unable to do so. I have been unable to mount system as RW using the instruction a page back. In both situations I get the "permission denied" response from the command line.
3. Everytime I try to root using the method provided in the OP, I get a message saying that it can't find android 2.2 or 2.3
4. I am unable to root again using super click for the same reason.
5. I have otherwise been able to follow all of the steps in the OP successfully, but to no avail. My screen goes black after it shows the kindle fire screen for a couple seconds.
6. Any suggestions would be very very helpful. From my amateur amount of knowledge, it seems to me that I don't have a build.prop in my /system/ but am unable to rename or access my build.prop.bak so that I can set it as the regular bootable build.prop. This is because, even though I thought I had it rooted, I am unable to set the /system/ directory as writable.
7. ANY SUGGESTIONS OR HELP WOULD BE GREAT!
Just as a disclaimer: I acknowledge I'm a moron for not verifying everything when I pushed in a build.prop file into my /system/ folder and restarted. No need to call me names
For those who know a bit more than me...
Would pushing the 6.2 update (or any of the downloadable firmware) to the kindleupdates folder in the sdcard and then rebooting fix my problem? I remember reading that the updates re-writes the build.prop which would fix my situation.
Of course, do you need root permissions to be able to write to the sdcard? I only ask this because I can not get the sdcard to actually show up on my desktop. I would need to push it via terminal or adb shell.
Anyone know if this would work?
I am beginning to realize that I may actually still have root, but since I can't boot up the phone, I can't fill out the superuser access dialog that usually comes up when a program tries to access superuser. I had root before I caused the build.prop problems, but figured that I had somehow lost it when I tried to access SU from ADB. Anyone know of a way to bypass this access dialog?
I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.
damianarnold said:
I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.
Click to expand...
Click to collapse
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."
ejrubin said:
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."
Click to expand...
Click to collapse
My Fire was fully booted up. Did you remove and reinstall Superuser?
damianarnold said:
My Fire was fully booted up. Did you remove and reinstall Superuser?
Click to expand...
Click to collapse
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.
Can't get Write access to /System or /SDCard
ejrubin said:
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.
Click to expand...
Click to collapse
Still having the exact same problem! Was able to get the build.prob.bak pulled from /system but can't rename it and push it back to hopefully get this working again.
I am starting to think I may have to send this KF back soon if I don't get it working again.
Any help anyone can provide would be great.
I'm thinking since we are able to get into fastboot, do any developers know if it is possible to push in a new system.img via fastboot? This would solve our build.prop problems no? Any developers know if this is possible?
I would like to compile zergRush myself, but I don't know how to compile Android binary.
It seems require linux to do so.
Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App
JackpotClavin said:
Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
No , I think the sdcard is not yet mount. Tried cd sdcard and it's not possible.
Is it possible to mount it without root? Cause when we try to mount system folder it's permission denied.
And I'm afraid the system won't run the official update even the patch is inside the sdcard folder.
I think ejrubin's idea on how to fix our bricked kindle fire is completely right , we just need either one of the following :
1. A zergRush binary won't check the build.prop to let us run root and mount the system folder
2. Since we can get into fastboot, I think we need a correct update.zip or system.img to fix it. Any idea to build it from kindle's official update?
Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App
JackpotClavin said:
Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
If i just type "mount sdcard" it cannot recognize the command.
if try to mount it with -t and mount it to other folder, it just say permission denied.
Of course I wanna flash your clockwork build!!
Would you mind to guide us with all the step when you're ready? Because I'm quite new to root android machine.
Really thanks for your help!!!!!!!!!!!!!!!!
Yeah **** sorry guys can this wait till tomorrow? Sorry I said tonight, I got side tracked tonight
Sent from my DROID Pro using XDA App
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
SLOmtb said:
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
This is typically nothing to worry about. You will receive an error if the "check_rooted" folder didn't exist to begin with. Normal
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
Click to expand...
Click to collapse
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
Click to expand...
Click to collapse
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Wow! I'll give it a try tonight. Thanks!
soupmagnet said:
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Click to expand...
Click to collapse
Well, darn. I tried "adb root" and it says: "adbd cannot run as root in production builds." So I guess it isn't really rooted, after all.
Maybe the MoDaCo rom is the way to go, after all. Thanks, anyway!
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
sabithpkcmnr said:
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
Click to expand...
Click to collapse
The which system version?
Sent from my XT894 using Tapatalk
sd_shadow said:
The which system version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
sabithpkcmnr said:
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
Click to expand...
Click to collapse
That's Android version, not system version
Sent from my XT907 using Tapatalk
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
So you can't use boot unlocker so on play store?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Maybe you need to fix permissions.
Did you have ROM Manager by any chance with root access granted? If so you could flash CWM from there, and then apply the latest SuperSU zip from CWM.
skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
efrant said:
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
Click to expand...
Click to collapse
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
skyes113 said:
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
Click to expand...
Click to collapse
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
skyes113 said:
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
Click to expand...
Click to collapse
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
skyes113 said:
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
Click to expand...
Click to collapse
Strange. I have no idea what the problem would be then.
What I would do is boot up CWM, and re-flash an su package.
The permissions are fine: -rwsr-xr-x = 04755 and -rwsr-sr-x = 06755. Both will do the same thing.
Also I see nothing in the OTA package that would relock your bootloader. You're sure that's exactly what happened? If it did, maybe someone here could pinpoint the component of the OTA package responsible for this?
Sent from my Galaxy Nexus using Tapatalk 2
Looks to be a problem on su.
I download the latest binary and replace it using adb + busybox and now it works fine.
Thanks!
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one
Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053
Yeh thanks its working now after reflashing the cwm superuser.
Currently my KF2 is running stock amazon OS (10.4.3), and I rooted the device following http://forum.xda-developers.com/showthread.php?t=2075959
I believe it has been rooted successfully, as I am able to use Titanium Backup and grant root access to ES File Explorer. I also downloaded some root checker app from google play store to double check if it has root privileges.
As I want to flash CM10.1 to my KF2, I have been following Hashcode's guide to install a 2nd bootloader http://forum.xda-developers.com/showthread.php?t=2100963. I am getting stuck with Step 3. I get the following error:
Code:
C:\kfu\tools>adb push stack /data/local/tmp/
failed to copy 'stack' to '/data/local/tmp//stack': Permission denied
elegant_universe said:
Currently my KF2 is running stock amazon OS (10.4.3), and I rooted the device following http://forum.xda-developers.com/showthread.php?t=2075959
I believe it has been rooted successfully, as I am able to use Titanium Backup and grant root access to ES File Explorer. I also downloaded some root checker app from google play store to double check if it has root privileges.
As I want to flash CM10.1 to my KF2, I have been following Hashcode's guide to install a 2nd bootloader http://forum.xda-developers.com/showthread.php?t=2100963. I am getting stuck with Step 3. I get the following error:
Code:
C:\kfu\tools>adb push stack /data/local/tmp/
failed to copy 'stack' to '/data/local/tmp//stack': Permission denied
Click to expand...
Click to collapse
Can you navigate to your '/data/local' directory and confirm that you do have a 'tmp' folder?
soupmagnet said:
enter...
Can you navigate to your '/data/local' directory and confirm that you do have a 'tmp' folder?
Click to expand...
Click to collapse
Using ES File Explorer, I can navigate to '/data/local' directory and I can see a 'tmp' folder.
Problem solved. Instead of using "adb push", I just place the file into '/data/local' manually. The rest of the steps went fine!
No data/local/tmp folder...
So i go into my ES file explorer and i go to my data folder and it shows that i have no local folder, i actually have no folders in this directory. how would i create a local/tmp folder so i can successfully S-OFF my phone?
There are folders in there, key thing is in order to see them you need root. Its weird like that, they might show up over and adb shell if you
Code:
adb shell
cd /data
ls
Or for a more formatted column listing use "ls -n", it will also display permissions of files and folders.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app