Hello everybody,
I have a "problem" with /system/bin/ and bin folders (however, the phone works just fine, hence those quotation marks :angel.
Let's stick with /system/bin/: Inside I have the files that should be there, but there is also another bin folder with exactly the same files inside and another bin folder inside ... and so on, about 20 times/levels(?) nested.
Not sure what it is ... some hardlink problem?
The same is in /bin/ folder.
ES File Explorer says that there are about 7000 files/ 230 MB in the first nested bin subfolder.
I tried the following:
1. Delete the nested bin folders from ES File Explorer (root access granted) - unsuccessful ("can't delete ...")
2. From CWM: format /system/ + Factory reset + wipe + ROM reflash
3. Search the forum for this issue - maybe I can't search properly, but found nothing ... sorry
As I said, the phone works fine. But I think that it is not good to have such a mess inside the system folders.
I didn't try complete reflash (ftf file) ... I'm trying to avoid doing everything from scratch .
Can you help me, please?
Thanks a lot,
J.
Phone: Sony Ericsson Live With Walkman WT19i, unlocked bootloader (the Sony way), MESA Kernel 3.6 stock, Real ICS lite r4.
Update: It's a chain of symlinks. The depth of the chain is 40 (counted in DroidExplorer).
What else didn't work:
mount /system in TWRP, then starting file editor, deleting bin (even with chmod)
All attempts to delete the symlink via PC file managers (e.g. Droid Commander)
Solution {rooted phone):
It was a symlink in system/bin pointing to self,
1. Install Android Terminal Emulator (free at Google Play)
2. Start it
3. Then
Code:
# su
(allow root access)
Code:
# mount -o remount, rw /system
# cd /system/bin
# rm bin
That's it
Related
I am trying to install TapNTap keyboard in Vegan Ginger. (yeah, I know but I want to anyway). I need to copy two files to /system/app and system/lib. I presently have the files stored in /mnt/sdcard/download. I have terminal emulator installed and when I su I appear to get root (prompt changes to #). I was able to create an empty directory in /. When I try to copy the file to /system/app I get a message that it is a Read-only file system. When I do an ls -l the permissions show drwxr-xr-x for the directory. The owner is root and the group is root. It would seem that as su I should be able to copy the file there. Possibly it is mounted as RO. I tried to use a remount command but it failed. I'm not well versed in that so I may have done something wrong. Long and short - how do I get the file copied into the directory?
http://lmgtfy.com/?q=remount+system+rw+android
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Copy it to another folder edit the copy and then move the edited file in the correct folder.
tried that already, didnt work. got another error
I use Root Explorer to do any editing.
Any other suggestions? I'd rather not have to pay for it
joshtb86 said:
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Click to expand...
Click to collapse
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# /system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
joshtb86 said:
Any other suggestions? I'd rather not have to pay for it
Click to expand...
Click to collapse
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
cbay said:
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
Click to expand...
Click to collapse
if i use CM Mod, i cant see any files. if i use HiAPK, all the files have -rw and a lot of stuff before it and i cant read anything, but it does mount. CW had problems mounting the drive. im gonna try out the terminal commands
rajeevvp said:
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
Click to expand...
Click to collapse
when i tried the mv command to move it back, i still got errors in moving it and was not able to
joshtb86 said:
when i tried the mv command to move it back, i still got errors in moving it and was not able to
Click to expand...
Click to collapse
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
rajeevvp said:
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
Click to expand...
Click to collapse
thanks so much again. i finally got it to work, but i just wanted to get netflix to work, and it still doesnt. after all that work. ugh.
JoTeC said:
I use Root Explorer to do any editing.
Click to expand...
Click to collapse
Thanks, I tried two other applications and they didn't work. Was able to edit with Root Explorer. didnt fix the Netflix playback. Bummer.
***** changing the Nexus S to HTC Vision and samsung to HTC did the trick.
Root explorer will work, and is a great app. Worht the money.
Also, ADB from a PC will work as well. Just install the android sdk and use ADB.
From windows cmd prompts the commands are just adb remount (to remount as root) then "adb pull /system/build.prop" (this will pull it to the sdk platform-tools folder that adb.exe is in) and then edit to your hearts delite.
"adb push build.prop /system/build.prop" to send it back.
I was able to use ES File System by unchecking the Mount File System option in the Root options menu and then rechecking it. I imagine that it forced a remount of the file system in a writable mode.
This worked on our nabi big tab hd24
We now have true multiuser, where everyone has their own login, files, emails, bookmarks, web history, etc; as it should be.
I first did a factory reset, then installed kingo root, then another reset, did the build prop edit this suggested (es file explorer did not work) but build prop editor did....
We now have the nabi big tab hd 24 running as our primary desktop workstation computer...
No we just wish for a room update to be made available with the latest version of Android.
4.4.2 is getting old, and as is common little manufacturer long term support...
Hello ;
I did the procedures of the Thread:
"how flash player 10.3 work in stock rom[Guide] "
http://forum.xda-developers.com/showthread.php?p=18552527
And flash it's working, but I have a small Problem after disconnet/reboot the
Phone I lose the files of the folder lib an dit's necessary do always the following
steps:
step 2: copy lib file to /data/data/com.adobe.flashplayer/lib
step 3: change the permission of all .so file like screenshot
JG
First download autostart app from market it free.then create a file name it autostart.sh and put these command under the file.
" cp /sdcard/lib/libflashplayer.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libstagefright_froyo.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libstagefright_honeycomb.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libysshared.so /data/data/com.adobe.flashplayer/lib/
chmod 644 /data/data/com.adobe.flashplayer/lib/libflashplayer.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libstagefright_froyo.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libstagefright_honeycomb.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libysshared.so
"
Then create a folder lib in your sd card and copy all lib file to that lib folder then create a folder in/data and name it opt and place autostart.sh file to that opt folder and set permission to file 777.now when your phone se restart your lib file is automatically copy to appropriate folder.
Flash Lib Files
Hello;
I did all your indications, please see screenshots 1 to 4
but in the end after restart the phone, in the lib file only can see a strange file,
see screenshot 5
BR:
JG
Ok wait i will upload my autostart.sh
try this autostart.sh i am using it and it work for me it has save command but some time there is problem in file.
press thanks button if i help you
OK
Hello;
It's working thanks.
JG
does not work on 2.3
Autostart app does not work on 2.3.
Another autostart app is Script Manager this work correctly.
multibestia said:
Autostart app does not work on 2.3.
Another autostart app is Script Manager this work correctly.
Click to expand...
Click to collapse
I got LG p690 (Android Gingerbread). I copied the command into Script Manager file and manually (with execute command) the procedure goes but after reboot it does not go automatically. Do I have to copy the file created somewhere specifically?
please let me know
thks
download autostart from market it work in 2.3
vikasb32 said:
download autostart from market it work in 2.3
Click to expand...
Click to collapse
It is strange. After reboot the files have been copied but the first one libflashplayer.so is just linked and this blocks the browser. Instead if I launch the script from root explorer everything is fine. can somebody help me?
pekkio said:
It is strange. After reboot the files have been copied but the first one libflashplayer.so is just linked and this blocks the browser. Instead if I launch the script from root explorer everything is fine. can somebody help me?
Click to expand...
Click to collapse
Don't linked flashplayer to link2sd because after restarting link2sd run before the autostart so link2sd not able to link the file and btw if you manually link flashplayer then flashplayer not work in opera mobile so don't link flashplayer and keep it in internel memory.
vikasb32 said:
Don't linked flashplayer to link2sd because after restarting link2sd run before the autostart so link2sd not able to link the file and btw if you manually link flashplayer then flashplayer not work in opera mobile so don't link flashplayer and keep it in internel memory.
Click to expand...
Click to collapse
that's right! Thanks... so I won't have chance to get Flash Player linked on sd and have automatically copied the library files by autostart....maybe in the future we will have custom flash player for armv6....
Same problem, need help
vikasb32 said:
First download autostart app from market it free.then create a file name it autostart.sh and put these command under the file.
" cp /sdcard/lib/libflashplayer.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libstagefright_froyo.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libstagefright_honeycomb.so /data/data/com.adobe.flashplayer/lib/
cp /sdcard/lib/libysshared.so /data/data/com.adobe.flashplayer/lib/
chmod 644 /data/data/com.adobe.flashplayer/lib/libflashplayer.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libstagefright_froyo.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libstagefright_honeycomb.so
chmod 644 /data/data/com.adobe.flashplayer/lib/libysshared.so
"
Then create a folder lib in your sd card and copy all lib file to that lib folder then create a folder in/data and name it opt and place autostart.sh file to that opt folder and set permission to file 777.now when your phone se restart your lib file is automatically copy to appropriate folder.
Click to expand...
Click to collapse
Hello,
Not an android professional. I have a P690 rooted. Installed flash, worked fine, untill reboot (lib files vanished). Trying to setup the script u mentioned above.
Heres where i am so far.
1.installed "script manager"
2.copied the script above without "" marks into a file called autostart.sh
3.created folder "lib" in sdcard directly
4.copied 4 lib files to lib folder in sdcard and doublechecked the names with the names in the script (i use notepad to view the script)
5.created folder "Opt" in phone/data/
6.pasted the script file there. assuming 777 means rwx-rwx-rwx i did that for the sh file.
7.Ran SM, browsed as root to the directory /date/opt, chose the sh file, clicked "open as script/executable"
8.In SM Chose options run at boot, run as root and "executable" option
9.clicked run
Files are not copied:
says exec sh-c' /data/opt/autostart.sh'
# exec sh-c' /data/opt/autostart.sh'
cp: not found
cp: not found
cp: not found
cp: not found
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 1.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 2.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 3.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 4.so
no such file or directory.
Tell me what i did wrong or wat i need to do to get it copying automatcally
All help welcome.
PS. I have force2sd app on phone, ginger bread os, I didnt install app2sd software from google play, so i dont have it unless it comes inbuilt with gingerbread.
ok check file using root explorer.click to autostart.sh using root explorer and then click execute and then check files copy or not.
Sent from my LG-P500 using Tapatalk
axmanin said:
Hello,
Not an android professional. I have a P690 rooted. Installed flash, worked fine, untill reboot (lib files vanished). Trying to setup the script u mentioned above.
Heres where i am so far.
1.installed "script manager"
2.copied the script above without "" marks into a file called autostart.sh
3.created folder "lib" in sdcard directly
4.copied 4 lib files to lib folder in sdcard and doublechecked the names with the names in the script (i use notepad to view the script)
5.created folder "Opt" in phone/data/
6.pasted the script file there. assuming 777 means rwx-rwx-rwx i did that for the sh file.
7.Ran SM, browsed as root to the directory /date/opt, chose the sh file, clicked "open as script/executable"
8.In SM Chose options run at boot, run as root and "executable" option
9.clicked run
Files are not copied:
says exec sh-c' /data/opt/autostart.sh'
# exec sh-c' /data/opt/autostart.sh'
cp: not found
cp: not found
cp: not found
cp: not found
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 1.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 2.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 3.so
unable to ch mod /data/data/com.adobe.flashplayer/.......lib file name 4.so
no such file or directory.
Tell me what i did wrong or wat i need to do to get it copying automatcally
All help welcome.
PS. I have force2sd app on phone, ginger bread os, I didnt install app2sd software from google play, so i dont have it unless it comes inbuilt with gingerbread.
Click to expand...
Click to collapse
Hi.
I had also faced the same issue....
The thing that u have to do is to install busy box... then everything works fine for you...
Actually this error occurs because your system could not support these unix commands (chmod, cp,etc.).. and these commands only works when you install busy box in your phone.. so can also say that busybox installs common unix utilities to the android...
Press THANKS if I help you..!!
Sent from my [email protected] OpTiMu$ On€ [email protected]
Busy box Installed
Bhawan said:
Hi.
I had also faced the same issue....
The thing that u have to do is to install busy box... then everything works fine for you...
Actually this error occurs because your system could not support these unix commands (chmod, cp,etc.).. and these commands only works when you install busy box in your phone.. so can also say that busybox installs common unix utilities to the android...
Press THANKS if I help you..!!
Sent from my [email protected] OpTiMu$ On€ [email protected]
Click to expand...
Click to collapse
I have busybox installed,
ROM: DynamiteRomJB Themed ( already rooted)
Busybox : BusyBox v1.20.1-cm9 bionic
cp not working from script
but it works as individual command (without scrpit)
Trying to copy files from /storage/sdcard to the /system partition. Landvo L200 running Android 4.4. Rooted. Kitkat SD fix in place (in platform.xml, the media_rw-group is added to WRITE_EXTERNAL_STORAGE). This problem is about _reading_ from SD rather than writing to it.
Using adb, I can do su and become root. As root, I can remount /system as rw and rename files on it. But when I go to /storage/sdcard0/ or /storage/sdcard1/, I cannot see any of the files there. When I drop back to the regular user (so not root), I can see the files on both the /storage/sdcardn/.
Using Total Commander, exactly the same seems to happen, because I can rename files on /system (TC gets root and automatically remounts in rw), but I cannot copy a file from one of the sdcards to /system/<whatever dir>. I get as error message: su error: could not open source file. Apparently this was reported before, without resolution: http://www.ghisler.ch/board/viewtopic.php?t=38910&view=next
Anyone knows a workaround to this?
{EDIT} ES file explorer _is_ capable of copying from /storage/sdcard to the /system partition. How do they do it?
Hi guys. Does any of you know how to push su.d directory into su folder? I mean I need radio.sh script in su/su.d to get root call sms manager working. Every time I try it disappears after reboot.
Rooted rom 34.3.A.0.217 with TWRP.
Anyone?
It's late though, but for the guidance of other noobs like me. /su/su.d/ can't be flashed in recovery because this isn't available. For system-less roots, binaries/libraries required to start supersu daemon and to manage root permissions, don't reside in /system/bin but in /data/su.img while (at least) two files reside in boot.img i.e. boot.img/ramdisk/init.supersu.rc and boot.img/ramdisk/sbin/.*daemonsu*.sh. When ROM boots, init.supersu.rc mounts /data/su.img on /su directory and calls /sbin/*daemonsu*.sh for initial setup which starts /su/bin/daemonsu and other se-linux related stuff and then executes any scripts found in /su/su.d/ and /system/su.d.
You can find this:
Code:
mido:/ # mount | grep loop
/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)
So, the init.d scripts placed in /su/su.d actually reside in /data/su.img which isn't mounted in recovery mode and anything flashed to /su/su.d goes to volatile rootfs which is gone on reboot. Either mount su.img in recovery, or place this script while ROM is running or instead flash to /system/su.d which is permanent filesystem unlike rootfs (which lives in RAM). And finally don't forget to set permissions to 0700 as advised here. Another thing, mostly init.d scripts don't work with .sh extension. Avoid this too.