[Q] "Operation not permitted" trying to mount extSD as intSD - Sony Tablet S

Hi, I've been trying to move all my game data from my internal SD card to my larger external SD card with no joy.
I have used condi's AIO tool to install init.d support, which reported as successful, but when I follow obicom's instructions as listed in POST #43 of this thread http://forum.xda-developers.com/showthread.php?t=1490116&page=5
I repeatedly receive the message "Operation not permitted."
I have used both ADB Shell and Terminal Emulator with the same result.
I'm obviously doing something wrong as other people appear to have had success with these instructions, I just don't know what.
Here's what I've done: (on rooted ICS from condi's AIO tool)
Installed init'd support "successfully"
Moved all data from sdcard/Android/data over to sdcard2/game_data
In ADB Shell/Terminal Emu. entered the following line;
mount -o bind /sdcard2/game_data /sdcard/Android/data
and this is where I get the "Operation not permitted" message.
Any ideas?

Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.

Ahaaa
Awesome! Can't believe it was something so simple, thanks, and thanks for explaining the reason.
I must have somehow totally missed the "su" instruction in the other thread.
Half of my games work, the other just seem to need re-installing which is no big drama.
Again, thanks, it's much appreciated mate.

Script?
agc93 said:
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Click to expand...
Click to collapse
Hi, is there a way I can create a script (or the like) that would do this, and other similar directory changes, at boot?
At present I need to enter these manually each time the tablet starts, which isn't too much of a drama for me but when other people use it they end up downloading the data all over again when they start a game.
Thanks

There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.

agc93 said:
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
Click to expand...
Click to collapse
Okay thanks, yet again, I'll give it a try today.

Operation not permitted
Hi,i wanted to change my mac address on phone and even with that su command i get "operation not permitted" (my phone is rooted)...even apk named overclock for android could not grant root acces...in root checker my phone is rooted(and i have been rerooting it but still same).AND THERE IS NO FIX ON INTERNET

Related

passwd: command not found

short story:
There is no passwd command in my system bin, so I am unable to change the (or effectively, add a) root password.
longer story:
So, as soon as I got my HTC Droid Eris, I installed that root 2.1 leak from HTC. After going through several Terminal applications, I found one that didn't force close every time I tried to use it. I was about to log into root with "su" but I didn't know the root password. I tried Googling around, but I found nothing relevant. I then proceeded to try entering the "su" command anyway and to my surprise, their was NO ROOT PASSWORD. I've been panicking for the last two days trying to find a way to get the passwd command into my bin, but it doesn't look like it's going to work. I've even done some crazy things like try to copy the passwd command from my openSUSE box into the bin (Yes, I understand that it probably wouldn't have been compatible, but it's worth a shot). After doing some research, I learned that the /system/bin directory is read-only. That explains why I kept getting device cross-over errors whenever I tried moving the command from my SD card into the internal memory. Also, I found where the HTC devs installed the "su" command in the leaked 2.1root. It's in the /system/xbin directory.
Does anyone have a solution to this? I'm worried about hackers and being rickroll'd by some idiot's worm. I've been keeping my 3G mobile network off and only using secured Wi-fi to access the Internet
Umm, why are you trying to change the root password? Also when you do su in a shell our shouldn't ask you for a password. The risk of getting hacked are almost zero because the hackers have bigger targets to go after such as the iphone or motorola droid.
Sent from my Eris using the XDA mobile application powered by Tapatalk
This command will mount system as writeable
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Use one of the custom roms with SuperUser.apk (all of them) for security. We don't have passwords for shells on android.

Can someone get....

I'm in need of the stock kernal image and the clockwork recovery.zip file thingy.
NOT the zip verson of the kernal installer.
My situation, I was stupid and installed the voodoo thing, then for someone reason I tried to flash Froyo over Bionix with the voodoo kernal thing. It didnt work so I decided to deleted everything in clockwork. Then I was like omg I cant use clock work or boot my device (stuck on vibrant screen but I can get to odin and the stock recovery).
Later I read that voodoo stopped odin on the cm forum so I couldnt use it. Thats what some dude named viralblack said and theyre a mod so I'm guessing its true.
So my last 4 ideas are:
1)Try and flash a new Kernal Image in adb and hope it gets odin to work
2)Push the cw recovery to the phone
3)Run to the library and hope my computer is the problem
4)Pretend vb is wrong and keep trying the download screen thing
Sorry if this is in the wrong section but I guessed it could go here because I need some files....
flash Eugene's froyo that does not brick via Odin. he has instructions in his thread.
...and it's kernel NOT kernal people
Sent from my SGH-T959 using XDA App
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
RPGbig said:
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
Click to expand...
Click to collapse
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Wow
You guys have nothing better to do than flame a newb?
If you spent half the time helping instead of flaming there MIGHT just be some people with a bit more knowledge than they had yesterday.
If you cant say something constructive/helpful --Why bother!
fcbarca17 said:
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Click to expand...
Click to collapse
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
RPGbig said:
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
Click to expand...
Click to collapse
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
rpcameron said:
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
Click to expand...
Click to collapse
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
rpcameron said:
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
Click to expand...
Click to collapse
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
rpcameron said:
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
Click to expand...
Click to collapse
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
Click to expand...
Click to collapse
You have to be rooted.. But why would you even take the hard way to use clockwork? Just download it from the market..?
I have odin with all the files that will get u to stock of ur phone. Also the froyo files does not brick. So now i exactly dont know what u need. go cows
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
If your phone is stuck in a bootloop you need to flash your phone with odin
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
Click to expand...
Click to collapse
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
RPGbig said:
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
Click to expand...
Click to collapse
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
Can you boot into recovery using the VOL_DN and POWER method, or does the adb daemon ever come online during the bootloop? If so, then either boot into recovery from a powered-off state, or use the adb shell to boot it into recovery.
http://forum.xda-developers.com/showthread.php?t=810130
rpcameron said:
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
Click to expand...
Click to collapse
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Dude, if your phone is stuck in a bootloop, you HAVE TO FLASH IT VIA ODIN. There's no other work-around.
RPGbig said:
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Click to expand...
Click to collapse
Why did you try `adb root`? I don't quite understand that.
A shell session would be `adb shell`, yes. On your computer's command line, invoke `adb shell`. You are now in a shell session. What does the prompt look like? Is it "#" or "$". If it is a hash, then you have root access via adb. If it is a dollar sign, then you do not have root access; try running `su` from within the shell session. If the prompt does not change to a hash, then you are stuck for the moment, because you do not have root access via adb, and therefore nearly all of the adb commands will not work.
By "shell installed" I was referring to a shell interpreter installed on your handset. bash is the most commonly installed Linux shell, and sh is usually just a pointer to bash. If your handset does not have either /system/bin/sh or /system/bin/bash (or anything similar), then you have an incomplete system, and it got messed up along the way with something you did.
But, since it seems that you cannot gain root access through adb, and therefore cannot (re)mount your partitions, you are basically limited in your options. All you can really do is put your phone in download mode, and use Odin to reflash a complete system (including a kernel image). I would also recommend that you use the repartition option in Odin to make sure that your partitions are reformatted and you are essentially left with a wiped and clean handest to start with.
(Lack of root access via adb has severely limited your options. You are basically left with Odin as your only avenue of recourse, unless you are willing to disassemble your device to get to the internal SD card.)
Have you opened yours? Is it an actual (micro) sdcard that can be taken out like the external one?
I typed 'adb root because typing 'adb' showed this
adb root - restarts the adbd daemon with root permissions
so I guess that was what you ment by root.
When I type 'adb shell' all it gave was - exec '/system/bin/sh' failed: No such file or directory (2) -
You need to stop trying to do it the hard way and just use Odin. If your phone is not being recognized then you need the correct drivers. Once installed, you should be back up and running within 5 minutes. Stop lollygagging and fix your phone already.

Cant run Debian

Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here

[INFO] JRummy BusyBox Installer Warning

I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Please help
MonaLisaOverdrive said:
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Click to expand...
Click to collapse
Hello I installed BusyBox and I had same issue with WIFI also others for example after reboot of my tablet wholle setting is set to orignaly(language and everithing).How can put back everithing?Does exist some apps etc???Thank you.
OMG... i installed busybox with this app into /system/xbin on my dopo d7015 with advanced install... and then the problems started... 0 total internal size, wifi not acquiring ip with dhcp ... no factory restore could fix it. then i eventually learned that /system/bin/sh didn't exist when trying to adb shell. i've downloaded an sh binary and copied it, now i have valid internal total size, and android terminal works... but wifi won't even turn on now! like an idiot i didn't backup before i started playing with the tablet... i have no clue as to how to fix it! please someone help me!
With one version of this app, it said Busy box 1.20.x is not compatible for my phone. But busy box installer by Stericson does the job perfectly.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands

[Q] Installing X-posed on Archos 80G9 (Unofficial CM10.2): problem mounting /System

Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...

Categories

Resources