Database Develop

Easy 'sysrw' and 'sysro' scripts for remounting system in Android! (S-OFF only!)

Tired of typing out that long "mount" command for remount system as read/write in Android?
NOTE: This is for S-OFF only!
Before you start, run this command in adb:
Code:
ls /system/bin/bash
If you get "bash: no such file or directory", run this command
Code:
ln -s /system/bin/sh /system/bin/bash
A new command prompt means the command completed successfully.
Now ensure bash is there:
Code:
ls /system/bin/bash
If it finds "bash", then continue on!
Here are two easy ways to stop the typing and make your life easier!
If you like using adb:
1. Download this zip, extract, and push the "sysrw" and "sysro" files to /system/xbin
2. Then run chmod 755 /system/xbin/sysrw and chmod 755 /system/xbin/sysro
Now, all you have to do is shell in and type "sysrw" to remount as read/write, or "sysro" to remount back to read-only!
If you don't like using adb:
1. Download Scripter from the market, QR:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Open Scripter, and tap on "Scan script" and scan these two QR codes:
sysrw:
sysro:
You can run them to make sure they work.
3. Long press on each one and save as "system read/write" and "system read-only" to know which one does which. (If you forget, the one with the command remount,rw is read/write, and the one with remount,ro is read-only)
That's it! Just open Scripter and tap on each to run them when you need to remount system!

Cool, you beat me to it. I was going to post something similar. Another option to keep in mind if you are using adb is the command:
Code:
adb remount
Run that command before anything else and it will remount your partitions as rw. Then you can push anything you want to /system.

This makes developing within the phone much easier and more fun.
What I did before these scripts was when I opened my Terminal Emulator on my phone, I had the mount -r blah.. as an initial command. Worked nicely for a while. I like this better because I can set it back as read only with ease.
Thanks.

Awesome, thank you!

This is the same as going into root explorer and clicking mount R/W for read/write, correct?

Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.

mozetti said:
Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.
Click to expand...
Click to collapse
This has nothing to do with changing file permissions--it shouldn't permanently change anything. Running this script is like kinda giving Ubuntu elevated privileges -- you are authorizing read-write access for yourself to make changes to /system, temporarily. It ends when you run the other script, reboot, or kill the terminal session you started (I assume).

rynosaur said:
This has nothing to do with changing file permissions--it shouldn't permanently change anything. Running this script is like kinda giving Ubuntu elevated privileges -- you are authorizing read-write access for yourself to make changes to /system, temporarily. It ends when you run the other script, reboot, or kill the terminal session you started (I assume).
Click to expand...
Click to collapse
Ok, so if I run this script then should I be able to open build.prop with Astro (long-hold, open as text, using file editor), make changes, and then save the file?
Because if that's the case, it's not working. I'm not a Linux pro, but I run Ubuntu on my desktop. I'm pretty sure that if you mount /system as read-write (which this script is supposed to do), then the permissions that show in Astro for the /system folder shouldn't b dr-, correct?

mozetti said:
Ok, so if I run this script then should I be able to open build.prop with Astro (long-hold, open as text, using file editor), make changes, and then save the file?
Because if that's the case, it's not working. I'm not a Linux pro, but I run Ubuntu on my desktop. I'm pretty sure that if you mount /system as read-write (which this script is supposed to do), then the permissions that show in Astro for the /system folder shouldn't b dr-, correct?
Click to expand...
Click to collapse
AFAIK, Astro does not do root privileges, you need Root Explorer to do what you trying to do. Perhaps someone else will chime in who knows how to give multiple processes r/w. The way I would do that without Root Explorer is to open the build.prop in a text editor, make changes, then write it to /data, then in terminal emulator, remount /system, and then move the file to system with build.prop.new, rename the original something like build.prop.old, then rename new to build prop.

rynosaur said:
AFAIK, Astro does not do root privileges, you need Root Explorer to do what you trying to do. Perhaps someone else will chime in who knows how to give multiple processes r/w. The way I would do that without Root Explorer is to open the build.prop in a text editor, make changes, then write it to /data, then in terminal emulator, remount /system, and then move the file to system with build.prop.new, rename the original something like build.prop.old, then rename new to build prop.
Click to expand...
Click to collapse
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.

mozetti said:
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.
Click to expand...
Click to collapse
In your position, I'd use adb, actually. It's pretty easy to push/pull in adb rather than all that copying and renaming

kentoe said:
This is the same as going into root explorer and clicking mount R/W for read/write, correct?
Click to expand...
Click to collapse
Yes, it's for people who don't want to spend the money or who like the command line.
mozetti said:
Is this supposed to make the build.prop file rw? Because when I run the script, the file still says -r-.
I'm not seeing a change to the /system folder when running the script. The permissions in Astro say dr- before I run the script and don't change after I run it.
Click to expand...
Click to collapse
No, this doesn't let you edit specific files on system, it just lets you add or delete files while in Android. If you want to change build.prop, you need to pull it, edit it, and push it back and reboot. Before, we had to do this in recovery mode, now you can do it in Android by making system read/write with these scripts.

mozetti said:
Ok, thanks. I'm not ready to pay for root explorer because I'm not sure how much I'm going to need it. I'll give your method a shot.
Click to expand...
Click to collapse
I think Android Mate has root file explorer. It's free as well. Try that.

ihtfp69 said:
I think Android Mate has root file explorer. It's free as well. Try that.
Click to expand...
Click to collapse
Thanks, installing it now.
**EDIT** Just in case anyone else is following this, Android Mate didn't work. It requested and received ROOT privileges but when I try to paste a file into /system, it doesn't work. It gives me a message that says it copied the file, but the file doesn't actually get put into the folder. **/EDIT**

ihtfp69 said:
Cool, you beat me to it. I was going to post something similar. Another option to keep in mind if you are using adb is the command:
Code:
adb remount
Run that command before anything else and it will remount your partitions as rw. Then you can push anything you want to /system.
Click to expand...
Click to collapse
remember that "adb remount" only works if the default.prop has the "ro.secure=0" in the boot.img(ramdisk), most most kernels are using the anykernel method, which uses the existing ramdisk. so unless you or the ROM cook change the ramdisk it will be set to "ro.secure=1"
CW recovery uses its own default.prop with the setting changed.

I think these scripts are something Adrynalyne has had in his ROMs since he put out the "One ROM to Rule Them All".
*shrug* Cool that you got a simpler/portable way instead of pulling them out of Adryn's roms

these work great, very handy thanks!

Howto Fix install issues specifiacally apps that fail with error code -18

NOTE: Root is required
When an application fails to install - even side loads - an error message is logged.
First thing to check is the logcat -> it will point to a secure file issue.
for error -18 it is
smdl2tmp1.asec
this file, and all other *.asec files are in the /mnt/secure/ directory.
If this file cannot be removed by the installing application a failure message results.
to manually remove this file you need a terminal application
android terminal emulator works just fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 1.
launch the terminal application of choice
Step 2.
SU
Step 3.
At the # command prompt type
cd /mnt/secure/asec/
Step 4.
type
ls
This will locate the file causing the issue.
Step 5.
type
rm smdl2tmp1.asec
Step 6.
close the terminal application
Step 7.
enjoy the fruits of your labor by installing the application that initially failed.

Thanks, manikin13!
Do you know any other error codes?

joe75 said:
Thanks, manikin13!
Do you know any other error codes?
Click to expand...
Click to collapse
I believe this fix works on most install error codes.

Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks

skeeterpro said:
Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks
Click to expand...
Click to collapse
Are you using a terminal app on the tablet?
this folder does not show up without using a terminal app on the tablet.
once in the terminal app
cd to /mnt/secure/ to see the files. There is no asec folder. The file extension is asec as in *.asec

You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!

skeeterpro said:
You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!
Click to expand...
Click to collapse
I saw the samething that nothing shows up in any file manager. only in the terminal ls do the files show up.
you should definitely get a not found for mnt/secure as the actual path is
/mnt/secure/asec/
the initial / is the root of the OS. (linux or unix)
so you are looking for a dir under root called mnt -> /mnt
so if you are having difficulty finding the full path break it down into each step, and do a ls to find the next step
ie
cd /
ls
cd mnt
ls
cd secure
ls
cd asec
ls
etc
hope that helps

Permission denied in Terminal
How do I get terminal permissions?

JackedNY said:
How do I get terminal permissions?
Click to expand...
Click to collapse
Typically typing su at the $ prompt should bring up the superuser prompt (allow / deny) as seen on screen 3. If not you should be able to go into the superuser app, and specifically add terminal.
once you allow the su request the prompt should change to the
# symbol

That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.

skeeterpro said:
That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.
Click to expand...
Click to collapse
Exactly
Dos = Dir
Linux, Unix, OsX, Android = ls (small letters)

Awesome little tut
Was having the same issue - but not receiving an error when attempting to install - walked straight through - had to stop in the dir and see the filename to rm but worked like a champ - thanks!

Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!

linesma said:
Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!
Click to expand...
Click to collapse
Android is actually very close to OsX in the respect that it is gui first, with the BSD base doing the heavy lifting.
Android is linux in the background with a gui first to allow the ordinary user some familiarity. The reason linux on the phone is not popular and linux on the desktop is not mainstream is because the command line gets equal or higher billing.
Google was smart with Android (basically a linux port with java framework) by promoting it as a gui just like iOS even though to truely see all the potential you need to get to the command line.

Droid 3 Root Issues

Ok so i followed the instructions to root my D3 twice and i have gotten the proper results, after the second reboot when i adb to my device i am given the root prompt.
That is about it though. I have installed superuser, tried to install jrummy16 busybox installer so i could get titanium working, but neither of the apps can find superuser or get root access.
Any ideas. Sorry for not putting this in the OG Thread but figured that would get real big real quick, thought it might be easier to start a separate thread for issues with the exploit.

need to find and push the su binary to the phone first. Superuser won't work without it.

Alright i got it working.
Anyone know of a good resource for how to kill all of the bloatware?

Is it safe to use titianium to remove the VZ apps, as in uninstall not just freeze

Titanium backup
Sent from my DROID3 using Tapatalk

at this point, i've just been freezing things. I'm waiting till we get a better list of what we can safely remove without breaking things.

Feels good man!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lordgodgeneral said:
need to find and push the su binary to the phone first. Superuser won't work without it.
Click to expand...
Click to collapse
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android. (edit: and planning on getting a droid 3 soon)
Also how to delete bloatware and install/use ADB

DoubleYouPee said:
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android.
Also how to delete stuff and install/use ADB
Click to expand...
Click to collapse
Here's exactly how I did it... all steps stolen from the thread in the developers forum:
1) Make sure you've installed the android-sdk from Google on your computer. (http://developer.android.com/sdk/index.html)
2) Connect phone to computer. In terminal or a dos prompt, navigate to the directory where you installed the sdk and where adb is located.
(example location)
and type the following:
Code:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
3) Power off and power back on your Droid 3.
4) Drop back to shell/prompt and back to adb location. Type the following commands:
Code:
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
5) Restart the phone again. You now have root.
6) Get a copy of su (http://www.megaupload.com/?d=82FH3AGI) and extract it to the same directory as adb on your computer. Type the following:
Code:
adb remount
adb push su /system/bin
adb shell chmod 6755 /system/bin/su
7) Install superuser from the android market.
Done!

Thanks! And then you delete apps with superuser?

I'm having trouble with:
Code:
adb push su /system/bin
It keeps returning:
Code:
cannot stat 'su' : No such file or directory
I have su (from the above link) in the same directory as adb...
*EDIT*
I have root within adb. So I definitely did everything before this right.

Did you extract su from the zip and put in the same directory as adb?

Yep.
10char

similar problem here. adb shell recognizes me as [email protected]_solana so im assuming its rooted..but when i try "adb remount" and press enter it says adb not found. i extracted the su file to my adb directory. Any ideas?

If you get an error like I did (top of 2nd page), try this:
Code:
C:\AndroidSDK\platform-tools\adb push C:\AndroidSDK\platform-tools\su \system\bin\su
That worked for me.

I hope this is helpful to any one that is having a hard time.
I found a one touch root video like 5 mins ago on youtube.
This is not my viedo all credits go to thedriodpeople the ones that made the video.
http://www.youtube.com/watch?v=RpGcuhoUp0k

k finally got the remount to succeed...now its say "chmod 6755: not found" after i enter "adb shell chmod 6755 /system/bin/su"

nevermind, simply retyped the same command and seemed to work on the third try mysteriously. working now

Hosed up my contacts after root and un-install --Help please--
---Solved---
So, I pulled a noob move and uninstalled a number of apps using titanium backup without understanding the repercussions of each. After uninstalling a few at a time, I would reboot my device and everything seemed fine. Little did I know, after uninstalling most, if not all, of the bloat I am unable to click a contact's picture to bring up the submenu and select call or text or whatever.
I didn't write down a list of items that I uninstalled and I should have frozen the apps prior to uninstall. I'm not a complete idiot and stayed away from obvious apps that shouldn't be uninstalled and what I thought was ALL motroblur stuff.
Long story short, I get a "com.motorola.contacts" stopped unexpectedly error(force close prompt) after trying to view a contact. I can look through all of the dialer menus showing contacts and recent calls and whatnot but I can't view a specific contact in detail. The searching I've done seems like there are a number of apps that use com.motorola.contacts and I believe I still have all of them installed but apparently not since there isn't a ton of detail on the latest motoblur that the D3 runs.
Does anyone have an idea of what apps use this process on the D3?
Thanks.
EDIT Javier78 ended up providing a solution to this issue.
http://forum.xda-developers.com/showpost.php?p=16998796&postcount=5
Quick fix and I was on my way again.

I dont think we know what all uses that process.
Sounds like your are going to have to do a factory restore, give it sometime eventually we will have a list of what is safe to remove and what isnt

[Q]I am unable to edit/delete the hosts file

Hello my friends,
I can not edit the hosts file.
I think i have to mount the partition but i do not know how to do it.
Could somebody help me please?
Thanks,
Zuka.

Hello,
Ya, you have to mount the partition.
An easy way to do this is to download es Explorer here https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Then open the app, go to the left sidebar, tools, and click root Explorer. Select mount and mount /system.
In images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't forget to set system in RO back when finished.

When I click on the Root Explorer I get an error:
"Sorry,test failed.This feature can not run on your device"

Is your phone rooted?

Yes it is,i got SuperSU installed and the Root Checker says that my phone is rooted.

Strange... Did you allow root rights to es Explorer?

Yes,I gave ES file Explorer the permission, I got a screenshot:
Sent from my C6903 using XDA Free mobile app

I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.

It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app

quadrazid said:
It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first

Yenkazu said:
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first
Click to expand...
Click to collapse
What is Sony RIC and where can I disable it ?

Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too

odie70 said:
Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too
Click to expand...
Click to collapse
Yes i rooted my phone with KingRoot then I replaced KingUser with SuperSU with the Terminal Emulator.
So yeah,how to disable SonyRIC ?
Edit: I installed BusyBox after I installed SuperSU

Try to connect to flashtool, with usb debugging enabled

frankee207 said:
I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.
Click to expand...
Click to collapse
How to use the command line with the adb shell ?

First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work

frankee207 said:
First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work
Click to expand...
Click to collapse
Where do I type that? In the cmd or in the terminal emulator ?

You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!

frankee207 said:
You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!
Click to expand...
Click to collapse
I do not understand what to do.Where to put these commands ?

OK. Let's make easy
Go to play store and download Android Terminal Emulator : https://play.google.com/store/apps/details?id=jackpal.androidterm
Open the app.
type
Code:
su
The command prompt becomes # instead of $ after you have accepted root rights in the popup window.
Then type
Code:
busybox mount -o remount, rw /[email protected]/system
When your modifications in/system are finished, reopen the terminal, become root (type su) and then
Code:
busybox mount -o remount, ro /[email protected]/system
If busybox not installed, intall it first here: https://play.google.com/store/apps/details?id=stericson.busybox
Hoping you'll success

Doesn't see any folders in SDCARD folder with any file manager

Hi, I've got a problem. Some time ago I installed GPE ROM on ma M7. Then everyting was working properly except ADB. I wasn't able to debugg any app on my phone, cause it was still showing that device is offline. So, I decided to try to factory reset my phone. After that I can't see any folder in SDCARD folder. I used several file managers including "Root Browser" and "ES Eksplorator". Both shows that SDCARD folder is empty. Additionaly, when I plug my phone to PC i see only 4 folders, every of them are empty and I can't copy anything to my phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is more interesting, in TWRPs File Manager I can see all my folders and files:
http://i.imgur.com/Y9TSzDN.png
http://i.imgur.com/PrVoPoO.png
http://i.imgur.com/hZBhcN3.png
Do you have any ideas where the problem is? I've factory reseted my phone 2 times and still the same.

Unfortunately I didn't had any idea so I restored to my stock ROM and it solved my problem. Unfortunately, becuse I fallen in love with vanilla Android GPE ROM.

Mefa2 said:
Hi, I've got a problem. Some time ago I installed GPE ROM on ma M7. Then everyting was working properly except ADB. I wasn't able to debugg any app on my phone, cause it was still showing that device is offline. So, I decided to try to factory reset my phone. After that I can't see any folder in SDCARD folder. I used several file managers including "Root Browser" and "ES Eksplorator". Both shows that SDCARD folder is empty. Additionaly, when I plug my phone to PC i see only 4 folders, every of them are empty and I can't copy anything to my phone.
What is more interesting, in TWRPs File Manager I can see all my folders and files:
http://i.imgur.com/Y9TSzDN.png
http://i.imgur.com/PrVoPoO.png
http://i.imgur.com/hZBhcN3.png
Do you have any ideas where the problem is? I've factory reseted my phone 2 times and still the same.
Click to expand...
Click to collapse
When having problem to see your files on /sdcard when on lollipop roms, you can fix this problem normally by using these commands from a rooted rom with usb debug enabled:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
Then reboot the phone.
btw /data/media/0 = /sdcard
http://www.linuxcommand.org/man_pages/restorecon8.html

Are you using TWRP ?
Enviado de meu Moto G usando Tapatalk

@xxmarsubxx
Yes, as I said before, I'm using TWRP. I posted images from TWRP File Manager
@alray
Thanks for the reply. Unfortunately, I was facing another problem with adb and I wasn't able to use adb shell command, because adb shows me that phone is offline. I described my problem here:
http://stackoverflow.com/questions/33002856/cant-connect-to-android-device

Mefa2 said:
@xxmarsubxx
Yes, as I said before, I'm using TWRP. I posted images from TWRP File Manager
@alray
Thanks for the reply. Unfortunately, I was facing another problem with adb and I wasn't able to use adb shell command, because adb shows me that phone is offline. I described my problem here:
http://stackoverflow.com/questions/33002856/cant-connect-to-android-device
Click to expand...
Click to collapse
As for your adb offline issues, looks like you already tried everything I could think of. IS your screen unlocked when you try to use adb commands? Anyway you could use adb from twrp terminal so you can at least fix (maybe) your sdcard issue.

alray said:
As for your adb offline issues, looks like you already tried everything I could think of. IS your screen unlocked when you try to use adb commands? Anyway you could use adb from twrp terminal so you can at least fix (maybe) your sdcard issue.
Click to expand...
Click to collapse
Thanks, for the replay
I will try to fix SDCARD issue then, cause for now I need fully working phone.
BTW, it's interesting that I easly get 2.5-3h SOT on GPE ROM, while on stock ROM it's hard for me to get 2h with Energy Saving Mode On.

Ok, I still have problem with my SDCARD. Now, I even can't take a picture, because I get that communicat:
"Unable to save file to SD card due to insufficient file permissions."
I tried to run "restorecon" command on my phone via adb, but I get this error:
Code:
>adb shell
[email protected]:/ $ su
[email protected]:/ # restorecon -FR /data/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /data/media/0: Permission denied.
When I'm trying to run this command via TWRP, I get error, that there is no -F parametr (or something like this).
I'd like to add, that I was trying to root my phone and when I connect it to my PC, in "WinDroid Universal Android Toolkit v2.5" app I can see that my phone is already rooted, but when I run SuperSU app on my phone, then there is mentioned that my phone isn't rooted and I have to update "SU binary". Then I agree and after that I get info that it wasn't able to update "SU binary".
Does anyone faced problem like this?
EDIT:
Ok, I manually installed SU binaries (I sideloaded the file via TWRP adb) and now I have root access, but I still can't take any pictures. After restorecon command, now I get this:
Code:
[email protected]:/ # restorecon -FR /sdcard/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /sdcard/media/0: No such file or directory.

Mefa2 said:
Ok, I still have problem with my SDCARD. Now, I even can't take a picture, because I get that communicat:
"Unable to save file to SD card due to insufficient file permissions."
I tried to run "restorecon" command on my phone via adb, but I get this error:
Code:
>adb shell
[email protected]:/ $ su
[email protected]:/ # restorecon -FR /data/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /data/media/0: Permission denied.
When I'm trying to run this command via TWRP, I get error, that there is no -F parametr (or something like this).
I'd like to add, that I was trying to root my phone and when I connect it to my PC, in "WinDroid Universal Android Toolkit v2.5" app I can see that my phone is already rooted, but when I run SuperSU app on my phone, then there is mentioned that my phone isn't rooted and I have to update "SU binary". Then I agree and after that I get info that it wasn't able to update "SU binary".
Does anyone faced problem like this?
EDIT:
Ok, I manually installed SU binaries (I sideloaded the file via TWRP adb) and now I have root access, but I still can't take any pictures. After restorecon command, now I get this:
Code:
[email protected]:/ # restorecon -FR /[COLOR="Red"]sdcard[/COLOR]/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat [COLOR="Red"][B]/sdcard/media/0[/B][/COLOR]: No such file or directory.
Click to expand...
Click to collapse
Its not /sdcard/media/0 its /data/media/0

@alray
Thank you so much for restorecon tip and for notice my mistake! What a shame for me that I did such a mistake... Thank you again, it of course helped me, now I can take pictures and also save files in my memory.
Again, thank you and shame on me.