Database Info

[DEV] Apps2SD and Darchstar-2.1 ROM

The focus of this thread is to sort out the Apps2SD issue in cyanogenmod-darch 2.1 ROM (like the title says). Please do not post here unless it relates to this issue.
That being said, here is where I was at in the original darchstar 2.1 thread:
watzone69 said:
Taken from the instructions darchstar gave in the first post of his thread...
Code:
adb remount
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod a+x e2fsck
a2sd
reboot
First, the "chmod a+x e2fsck" command doesn't work for me (EDIT: I discovered that it WILL work in recovery mode). I had to use "chmod 777 e2fsck". After entering "a2sd" it gets enabled. After rebooting, apps2SD is NOT enabled anymore. I realized this by doing this test:
Code:
adb shell
cd /data/app
pwd
If your apps2sd is enabled, you will get "/system/sd/app" returned to you.
If you get "/data/app" returned instead then apps2sd is NOT enabled!
Click to expand...
Click to collapse
Gbhil then replied...
gbhil said:
After you restart, can you re-enable a2sd by running a2sd from a terminal as root?
If so, do all your apps still appear and are they usable?
If the above is true, try adding this to the end of gumbo.sh
Code:
su -C a2sd
for a quick fix.
Start a thread (to keep things less cluttered) about it and I'll help you guys dig into the boot image and see why it's not sticking.
Click to expand...
Click to collapse
So, I rebooted and tried to run "a2sd" from the android terminal but it spits out a long string of errors:
Code:
--- Checking ext filesystems
e2fsck 1.41.6 (30-May-2009)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted.
/dev/block/mmcblk0p2: clean, 13/249856 files, 31387/499713 blocks
mount: permission denied. (are you root?)
chown: /system/sd: Read-only file system
chmod: /system/sd: Read-only file system
mkdir failed for /system/sd/app, Read-only file system
chown: /system/sd/app: No such file or directory
chmod: /system/sd/app: No such file or directory
cp: cannot create '/system/sd/app/android.tether.apk': No such file or directory
cp: cannot create '/system/sd/app/android.tether.usb.apk': No such file or directory
cp: cannot create '/system/sd/app/at.abraxas.mountusb.apk': No such file or directory...
(etc.)
...rm: cannot remove '/data/app/org.gmote.client.android.apk': Permission denied
rm: cannot remove '/data/app/org.hermit.substrate.apk': Permission denied
rm: cannot remove '/data/app/org.iplatform.android.apk': Permission denied
rm: cannot remove '/data/app/org.mikeyin.livewallpaper.apk': Permission denied
mkdir failed for /system/sd/app-private, Read-only file system
chown: /system/sd/app-private: No such file or directory
chmod: /system/sd/app-private: No such file or directory
cp: can't open '/data/app-private/com.android.aldiko.apk': Permission denied
cp: can't open '/data/app-private/com.protocol.x.su.fbs.apk': Permission denied
cp: can't open '/data/app-private/com.rerware.android.MyBackupPro.apk': Permission denied
rm: cannot remove '/data/app-private/com.android.aldiko.apk': Permission denied
rm: cannot remove '/data/app-private/com.protocol.x.su.fbs.apk': Permission denied
rm: cannot remove '/data/app-private/com.rerware.android.MyBackupPro.apk': Permission denied
ln: /data/app/app: Permission denied
ln: /data/app-private/app-private: Permission denied
+++ Apps-to-SD successfully enabled
So, there is no "app" or "app-private" in the "system/sd". Is a2sd supposed to generate those directories or are they supposed to be there before hand?
Anyway, the result is that I lose all of my shortcuts to the apps and market shows them as not installed even though they are.
BTW, I am not a dev or even that great at code or linux but I can usually pick stuff up fairly quickly. Just want to help fix this!
EDIT: The only thing I have found to work is to flash this kernel:
http://forum.xda-developers.com/showpost.php?p=5712377&postcount=1406
However, some people get stuck in a boot loop after flashing this.

Running into the same issues as Watzone so I can confirm that he is doing it correctly. =P

Here are all of the related commands that have been suggested whenever the question of apps2sd has come up in the darchstar 2.1 thread.
Code:
adb remount
adb shell
mkdir /system/sd
Code:
adb remount
adb shell
busybox --install /system/xbin
a2sd
Code:
cd C:\android-sdk-windows\tools
adb remount
adb shell
chown system.system /data/app
chmod 0771 /data/app
For the next command, boot into recovery and do the following:
Code:
adb shell
mount /system
exit
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod 777 e2fsck
Now, boot normally and go back to your CMD prompt...
Code:
adb remount
adb shell
a2sd
EDIT: In other threads I have seen the command...
Code:
apps2sd on
...used to enable apps2sd.
Doing all of these WILL allow the final "a2sd" command to enable (testing with the "pwd" command) but it all goes KAPUT after a reboot.

why it's not being enabled at boot time is because the init.rc isn't calling /system/etc/init.d/04apps2sd . I'll be sure that we fix that in my next release

And there you go.
It works here, but now I know why. I'm still using an old version of the boot image that looks for /system/bin/a2sd to load it, and an older version of the ROM. No sense in me to keep flashing fixes until I'm done tweaking the kernel. When darch says the kernel is good, then I'll catch up lol.
We might as well use this thread to learn to play with the boot image though, that is if you guys want to.

Awesome can't wait for the next release then! Lotsa apps out there calling out to me! Thanks guys =)

gbhil said:
We might as well use this thread to learn to play with the boot image though, that is if you guys want to.
Click to expand...
Click to collapse
You bet. It's about time I got my hands dirty.

I'm game let me know if you need me to test anything!

Cool deal. You need Linux to extract and compress the boot.img, and you need to be current with Perl and running jre5 or higher.
Ubuntu 9.04+ is set up out of the box, but any version can be made to work.
Then grab these files from Lox -
http://forum.xda-developers.com/attachment.php?attachmentid=231902&d=1254004933
http://forum.xda-developers.com/attachment.php?attachmentid=234040&d=1254622769
and extract them into your sdk/tools dir. (or any dir in your path)
get all that, then pick a boot.img from a rom and put it in a work folder.
Holler when you get that far, or if you have any q's.

I wanna learn myself. This should apply to mac os as well?

I have Mint on another machine. Gimme a bit to get caught up...

david279 said:
I wanna learn myself. This should apply to mac os as well?
Click to expand...
Click to collapse
Darwin might work. Never tried
watzone69 said:
I have Mint on another machine. Gimme a bit to get caught up...
Click to expand...
Click to collapse
np. I'm @work so going slow is better anyway lol.

ok i just ran the files in terminal. so i guess it might work.

I'm back
Inisde the work folder you dropped the boot.img into, run this from a term:
extract-kernel.pl boot.img
extract-ramdisk.pl boot.img
it will give you several files and a new directory. That dir is the unpacked ramdisk. The init.rc file is the one we're looking for. Open it with a Unicode editor and read it. It has it's own syntax, but it's almost like bash and not too hard to figure out. Hopefully you loaded a bootimg that has a2sd in it. Look near the bottom of the file for the a2sd start up line. It will have a2sd, apps2sd, a2sd004 or something like that. Once you find it so you can see the name used, search the rest of the file for that name.
Those lines will show you how a service gets declared and called at boot time.

I'm up and running now. I downloaded python 2.6.4. Do I need to install it or just extract it somewhere? Please forgive my linux noobness.
The other 2 zip files are extracted and in my tools folder. I'm getting the boot.img now.

idk if this will work as i too am a newb to android and the way they deal with the boot process is somewhat a bit different from what i'm used to, but heres a new boot.img if you guys want to flash it to see if apps2sd works. note, this is not a zip, remove that suffix.
to flash it to your phone just move the boot image to your sdcard then reboot into recovery. from there go into adb and mount your sdcard, then flash the new boot image.
Code:
adb shell
mount /sdcard
flash_image boot /sdcard/newBoot2.img
reboot
tell me if it fixes your apps2sd problem or not.

watzone69 said:
I'm up and running now. I downloaded python 2.6.4. Do I need to install it or just extract it somewhere? Please forgive my linux noobness.
The other 2 zip files are extracted and in my tools folder. I'm getting the boot.img now.
Click to expand...
Click to collapse
try it without doing anything to Python first....especially since I meant perl
Just try my last post and see if it works for ya. I'll edit my first post

gbhil said:
try it without doing anything to Python first....especially since I meant perl
Just try my last post and see if it works for ya. I'll edit my first post
Click to expand...
Click to collapse
Nope, I got "command not found" both times.

darchstar said:
idk if this will work as i too am a newb to android and the way they deal with the boot process is somewhat a bit different from what i'm used to, but heres a new boot.img if you guys want to flash it to see if apps2sd works. note, this is not a zip, remove that suffix.
to flash it to your phone just move the boot image to your sdcard then reboot into recovery. from there go into adb and mount your sdcard, then flash the new boot image.
Code:
adb shell
mount /sdcard
flash_image boot /sdcard/newBoot2.img
reboot
tell me if it fixes your apps2sd problem or not.
Click to expand...
Click to collapse
Thanks darchstar, I'll try that in a bit.

watzone69 said:
Nope, I got "command not found" both times.
Click to expand...
Click to collapse
you gotta make it executable
inside the directory with the perl scripts do this
Code:
chmod a+x ./

Clockwork mod help! PLEASE!!!

okay so I have tried installing clockwork too many times to count and it flat out will not install. i have gotten a series of errors, but have just today been able to keep a consistent error. I downloaded one click clockworkmod 2.5.1.0. plugged in my device, extracted to my desktop and ran both bat files. This is a copy of the cmd prompt window:
remove stock recovery patcher
mount: operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system-recovery-from-boot.p, Read-only file system
copy kernel and flasher
2043 KB/s <313888 bytes in 0.150s>
failed to copy 'zImage' to '/sdcard/zImage': Permission denied
flashing kernel
RedBend Update Agent 6,1,14,1
and then it goes on through there... bottom line, it looks like i don't have permissions for the install. and i have already tried remounting rw through adb shell, it comes back and say remounting and then thats it. and ideas? i can give the reset of the scripting in cmd prompt if needed. Thanks in advance.
4nic8

dude theres like 10 other threads on this page about the same exact thing... and this doesn't go in this forum!

Download rom manager from the market and. ...that would do it for u automatically....... and yes pls next time try to search all the forums before posting
Sent from my SPH-D700 using XDA App

Help ME ROOT!

Can someone help me root my phone.. I'm sure I'm doing everything right. From the one click to the manual method.
Everytime I do the manual method everything runs fine up until this part
"
[email protected]:/data/local$ ./zerg
./zerg
[email protected]:/data/local$ mount -o rw,remount /dev/null /system
mount -o rw,remount /dev/null /system
mount: Operation not permitted
[email protected]:/data/local$ cat /data/local/su > /system/bin/su
cat /data/local/su > /system/bin/su
cannot create /system/bin/su: read-only file system
[email protected]:/data/local$ "
"
Can someone Help me!

Where did you extract/unzip the files to?

I extracted the files to my desktop to a folder called Exploit. Everything works Until I get to the "remount part"

Important for those using Oneclick: 1.Extract the files from 1-click_exploit.zip. 2.Enable USB debugging. Do so by going into your settings, then to applications, then to development. 3.Set your connection type to charge only. You can change your connection type through the notification bar once your are connected. 4.Make sure you go to Settings, Applications, and check Unknown sources if you haven't done so already. 5.Click runme.bat while your phone is connected. Be patient and let the program do it's thing. YOUR PHONE WILL REBOOT! Do not be alarmed as this is normal. Your phone should now be rooted. Cheers!
This is the easiest way, I have personally done 2 of my friends this way and would recommend it to anyone, in fact I wish I had tried it first. Make sure you have all the proper drivers installed and follow it completely. You should have no problems ...hopefully!!!

Yea I'm positive I've done all of that. My phone reboots and all but no superuser appears under my applications when the program is done.

Try downloading the app from the market and see if it gives you access. If it was me I'd personally start over fresh. Back up my contacts through Google and perform a factory reset if not too much of a problem. Delete all the zips and redownload them and unzip them along with all drivers just to make sure nothing got corrupted . And try it again fresh.

Did you download cheesecake and install some updates? Is this the very first time installing root on this phone?
Sent from my MB865 using XDA App

No I didn't, whats "cheesecake"?

1. this doesnt belong in DEV section
2. it didnt mount system as r/w because zerg never finished running. ZERG HAS to complete which gives you temporary root, then the rest of the commands mount /system as r/w and pushes the 2 files needed. the su binary and superuser.apk
if zerg does not complete, STOP. figure out why zerg isnt running.

Yea I was told that part about zerg. I know it's not my phone or anything just the zerg part. Any ideas why zerg isn't working?

marquavious said:
Yea I was told that part about zerg. I know it's not my phone or anything just the zerg part. Any ideas why zerg isn't working?
Click to expand...
Click to collapse
You see. If you don't really understand what you are doing, it makes this 100 times harder.
If you open a command prompt and get to the part where you type ./zerg what is the output?
Just stop after running zerg. Obviously if that piece doesn't run the entire process will fail. It does no good to continue until you get zerg to run.
Sent from my MB865

su not updated

I have my Polaris NAND flashed with 2.6.25 kernel + casacristo's RLS18 ROM.
I have updated from the market the Superuser but now I get the pessage that SU is not updated and to download the new one (3.0.3.2).
I download the new one , the Root access is granted but at the end more or less I receive this message translated from italian:
...
...
md5sum ... OK
Mod file su 06755... OK
Moving su to its final position ... failed...
TRY Again
I tryed several times but ... no chance to update it... how can I manage ?
miazza

Here is latest su binaries v3.0.3.2. Download and unzip file. Push this to /system/bin and /system/xbin and then change rights with chmod to 6755. Reboot phone. Done.

Thanks, I will try.
Shall I do via ADB or can I try with RootExplorer for example ?
miazza

ADB, unless your root explorer can set 6755 rights

whitealien said:
ADB, unless your root explorer can set 6755 rights
Click to expand...
Click to collapse
It worked great. I managed with RootExplorer but it can be done also via FTP with Filezilla.
Thanks
miazza

file permissions doesn't work
Hi,
I use a HTC wildfire S, who have been rooted, but still in original ROM.
My SU doesn't want to be updated, as described in the first post.
So I downloaded the ZIP, and put SU on the sdcard. With ROOT BROWSER I copy it on /system/bin (SU have been copied automaticaly in /system/xbin).
I tried to change the permissions files, but after reboot, permissions are ---rwxr-x.
I tried with ADB. My phone is well recognised :
C:\Program Files\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH191TR05136 device
When I tried to change permissions file SU :
C:\Program Files\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$ chmod 6755 /mnt/sdcard/temp/su
chmod 6755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$ chmod 755 /mnt/sdcard/temp/su
chmod 755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$
Do you have an idea ? Thanks by advance, because right now, my phone is not still root...

I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza

miazza said:
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
Click to expand...
Click to collapse
Root browser seems to work the same way.
How can you use FTP with a phone ? It's suppose to use an IP adress. But by USB, there is not... But I will,l try asap.
However, my apps couldn't take root permissions, so I feel bad...

Use SwiFTP (it should be free from the market).
It works over Wireless connection to your internal WLAN and provide you with an FTP address like 192.160.0.x.
While you are connected through FTP client (like Filezilla), you can see your mobile File System as well as your SD.
with a right click on the su file you can change your rights.
But I do not know if it works even if you are not rooted...
miazza

I solved my problem my re-rooting my phone, using http://forum.xda-developers.com/attachment.php?attachmentid=672519&d=1312136127.
My phone says that the binary SU was obsolete, but when I tried "AGAIN" to update it, it was successful that time.
Strange, I don't understand why now the update was ok. But all is right.
Thanks everyone for the help.

[Root] Please test new rooting idea

Hi all,
well i made a small script to root Xperia devices, as it turns out more devices are affected to this.
Paul O'Brien over at Modaco tested it on his Nexus 7 [UK] and it worked, well some users in my thread over @ Xperia S section report it not working and some report it working.
I am opening this thread to get the idea why it is working for some users and why not for others.
So, as i don't have this device i cannot test it myself, so if you are a interested user or maybe a dev feel free to test it. Maybe you even get the idea why it is working on some and not on others. (BTW, are there any diffs between UK and other devices? How many firmwares are out for the device? Can i download somewhere firmware dumps?)
Paul's test: http://www.modaco.com/page/news/_/android/a-new-and-effective-root-method-for-ics-jb-r715
Best Regards

I will try it now with my UK device.
The device is STOCK, Bootloader locked and updated to the latest JB Build via OTA.
Will report back after my try.
EDIT:
It doesn't work for me:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (13.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1252 KB/s (1085140 bytes in 0.846s)
1039 KB/s (22364 bytes in 0.021s)
1305 KB/s (843503 bytes in 0.631s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
With Version 2 I get the following output:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= version 2 (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1290 KB/s (1085140 bytes in 0.821s)
992 KB/s (22364 bytes in 0.022s)
1285 KB/s (843503 bytes in 0.641s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click RESTORE (once again)!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Ad Version 2: It doesn't ask me to restore 2 times. Only the first time it asks me and then the Nexus 7 reboots.

Ok thanks for this test.
Can you tell me if there is a /data/local.prop already present in you firmware version? If yes we need to alter the script a little, hopefully it can work then.
I am not sure which firmware version Paul tested, but i have a few feedbacks telling it works, so i suggest it is a firmware version "problem".
Regards

Bin4ry said:
Ok thanks for this test.
Can you tell me if there is a /data/local.prop already present in you firmware version? If yes we need to alter the script a little, hopefully it can work then.
I am not sure which firmware version Paul tested, but i have a few feedbacks telling it works, so i suggest it is a firmware version "problem".
Regards
Click to expand...
Click to collapse
Thanks for your answer.
Since I don't have root I can't answer you this question because /data is inaccessible.
The rooting success of Paul is the same as with the HTC One X. He could achieve root trough such a script with his One X, all the others couldn't.
Sent from my Nexus 7 using xda premium

Strange thing.
Can you try something for me ?
Do this manually:
adb restore stuff/fakebackup.ab
Do not click restore YET!
next command:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
this command will automatically stop when it "worked". Once this command runs please click restore on device!
Now please give me a:
adb shell "ls -ld /data"
I want to know if it changes the permissions of data folder, if all is fine it should be permissions of 777. Maybe then you can check for local.prop and if present rename or remove it
Regards

Bin4ry said:
Strange thing.
Can you try something for me ?
Do this manually:
adb restore stuff/fakebackup.ab
Do not click restore YET!
next command:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
this command will automatically stop when it "worked". Once this command runs please click restore on device!
Now please give me a:
adb shell "ls -ld /data"
I want to know if it changes the permissions of data folder, if all is fine it should be permissions of 777. Maybe then you can check for local.prop and if present rename or remove it
Regards
Click to expand...
Click to collapse
My output:
C:\Users\user\Desktop\stuff>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
xxxxxxxxxxx (censored) device
C:\Users\user\Desktop\stuff>adb restore fakebackup.ab
C:\Users\user\Desktop\stuff>adb shell "while ! ln -s /data /data/data/com.and
roid.settings/a/file99; do :; done" > NUL
C:\Users\user\Desktop\stuff>adb shell "ls -ld /data"
drwxrwx--x system system 2012-09-15 20:55 data
C:\Users\user\Desktop\stuff>
Click to expand...
Click to collapse
It seems it didn't get chmod 777

Ok thanks for the test. Too bad, it does not change the permissions, maybe there is something preventing it. For now i have no idea, but any dev can freely adapt the intial idea of the script. If someone owns this device i think it the basic idea maybe useful. As for now it seems all devices are initially vulnerable to the "problem", only a way to use it have to be found.
Regards

FYI here also, doesn't work on my fully stock 3568A-ME370T JRO03D Nexus 7

Bin4ry said:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
Click to expand...
Click to collapse
I think this, and things similar to this, are your problem as you already need root to access those folders.
Without root any running app/process is only allowed to access it's own subfolder in /data/data, nothing else.

This kind of works for me, clockwork mod says I'm rooted but titanium backup says I'm not.
I can't install clockwork mod recovery from the app. Something about assigning permissions.
My boot loader is unlocked. Dunno if that helps.
Sent from my Nexus 7 using xda app-developers app

Have you got Superuser or SuperSU installed?
Sent from my Nexus 7 using my toiletpaper

Yes SuperUser only because the script bin4ry posted contains the superuser.apk and installs it.

HellcatDroid said:
I think this, and things similar to this, are your problem as you already need root to access those folders.
Without root any running app/process is only allowed to access it's own subfolder in /data/data, nothing else.
Click to expand...
Click to collapse
This is not true, it is exactly the trick my scipt uses, in the moment you press restore in the Android Restore Service you will gain access to the partition
@Spazz Monk3y: I added v9 maybe it works now properly, in some old versions i had a nasty bug for giving permissions to su binary. Introduced because i wanted to make a singleline command and forgot atleast 1 command inside my line :crying:
Regards

Code:
mount: permission denied (are you root?)
With v9 and German Nexus 7

Nex 7 is really crazy, you some working some dont. i have no idea -.-

Welcome bin4ry! I remember you from my x10 days! Glad to see you doing well.
Sent from my Nexus 7 using XDA Premium HD app