Related
I am willing to pay someone if someone can figure out how to remove factory apps like
facebook
footprints
peep
quickoffice
stock
visual vm
stock massages
i never use them for some reason they run in the background
Just take a look at this thread from the android forums
http://androidforums.com/all-things-root-eris/53646-unwanted-apps.html
NOTE: you MUST have ROOT in order to remove those apps.
If the instructions in that thread about "adb" are too complicated for you, then go buy the Root Explorer app, navigate to the folders you were told to in the thread, click the "r/w" button at the top of the app, then long press on the files you are told to delete.
Deleting system apps is risky if you delete the wrong ones. As usual, you are responsible if anything happens.
As I see it, you must have root to modify system files on your ROM (anyone correct me if I'm wrong)
But I was able to use Titanium Back up (downloaded from the Android market, free) to see all installed programs and I successfully deleted Visual VM, Peep, and stock messages... I use the others...
now so far, my ROM that is installed [2.1 version .3] hasn't had any problems with the removal of these system programs, So I think it is a safe method.
I believe this is a good alternative to adb commands... since you know what you are deleting.
and of course, I am not responsible if you do happen to mess your phone up.
C:\Users\admin\Desktop>cd android-sdk-windows
C:\Users\admin\Desktop\android-sdk-windows>cd tools
C:\Users\admin\Desktop\android-sdk-windows\tools>adb shell
$ mount -0 rw,remoun /dev/block/mtdblock3 /system
mount -0 rw,remoun /dev/block/mtdblock3 /system
mount: invalid option -- '0'
BusyBox v1.15.0 (2009-08-25 15:17:43 BST) multi-call binary
Usage: mount [flags] DEVICE NODE [-o OPT,OPT]
Mount a filesystem. Filesystem autodetection requires /proc be mounted.
Options:
-a Mount all filesystems in fstab
-f Dry run
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Read-only/read-write mount
There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems
$ cd /system/app
cd /system/app
$ 1s
1s
1s: permission denied
$
this is what i get am i doing something wrong here
Type adb shell than su and tell me what happens.
binny1007 said:
Type adb shell than su and tell me what happens.[/QUOTE
never mind i got it to work i used different method i bought the titanium backup. show all the installed apps easy to uninstall it works great now my phone is running much faster thanks for all the help
Click to expand...
Click to collapse
FYI, you were typing the commands wrong.
Right after you do "adb shell" you'll need to type "su" and the $ prompt should change to a # prompt. Check your phone as well after typing "su" as you should see a popup asking for permission.
$ mount -0 rw,remoun /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
should be: mount -o rw,remoun /dev/block/mtdblock3 /system
The -o is the letter o, not a zero.
$ 1s
Click to expand...
Click to collapse
Should be: ls
That's the letter l (lowercase L), not a one.
grdlock, I believe there is a "t" missing in your post:
mount -o rw,remount /dev/block/mtdblock3 /system
Ahh, ya, you're right. I just copied/pasted what he wrote and didn't catch that.
ampinc said:
binny1007 said:
Type adb shell than su and tell me what happens.[/QUOTE
never mind i got it to work i used different method i bought the titanium backup. show all the installed apps easy to uninstall it works great now my phone is running much faster thanks for all the help
Click to expand...
Click to collapse
Glad to know it works for someone else as well
Click to expand...
Click to collapse
I just downloaded Titanium Backup and deleted the "worldclock.apk" and I have to say it's a nice app, (Titanium that is)
So far, from the VanillaDroid ROM, I've deleted the following with no ill effects:
Stocks
Weather ( I use WBug)
Visual Voicemail
Browser ( I use Dolphin)
Quickoffice
MMS
Talk
Mail
Deskclock
I would like to delete the following but am having some difficulty finding the correct "apk"
Camcorder (I think it's built into the camera?)
Call History
People Search
Settings (just the app in the drawer, another NAND before I do this I guess)
Voice Dialer
Voice Search
Voice Record
NaviPanel ***Anyone know if this will mess with Maps?***
FACEBOOK !!!! I deleted the "Facebook.apk" but the FB app is still in the drawer and it still works fine. If anyone could help me with deleting this one I would be forever greatful! Trying to delete it using Titanium, it says: "cannot find Facebook.apk" But it's still friggin there......argh!
Edit: Woohoo! Facebook is gone.
Titanium tells me it needs root acess and that's out of question. Then again, I'm on the lg ally and it might be different... idk. Any other suggestions?
I have been experimenting with my new droid/milestone the past couple of days, odd problems which I am past now but still curious about.
Firstly after flashing the 2.1 sbf with rsd it will autoboot and screen slider will be there, then when I reboot, screen slider will be missing. This only happend when I flashed an sbf from the sbf site(2.1 uk version, not service), doing a factory reset didn't have any problem -could reboot as many times and slider would be there.... then suddenly after factory boot it would dissapear after first boot. Anyway solved this problem by installing screen mode widget after first boot after flash, solved problem, but still weird. Fixed this now but still curious about it.
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Also any thoughts on why nandroid backup is missing from my recovery menu even though my droid is rooted. I thought it was meant to appear.
I am still learning and researching, and appreciate any links or tips.
droidtech1 said:
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Click to expand...
Click to collapse
This is odd. Which OpenRecovery did you install? Androidiani? GOT? Or the "original" OpenRecovery? Are you aware, that you come into OpenRecovery by starting Recovery Mode and apply update.zip?
droidtech1 said:
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Click to expand...
Click to collapse
Using the app from the market worked like a charm for me. No idea, what might have gone wrong for you...
droidtech1 said:
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
Click to expand...
Click to collapse
For remounting, try "mount -o rw,remount /dev/block/mtdblock6 /system" and for undoing this, use "ro" instead of "rw".
droidtech1 said:
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Click to expand...
Click to collapse
You should download busybox and put the "busybox"-file in the directory /sdcard. After that do:
Code:
# su
# mount -o rw,remount /dev/block/mtdblock6 /system
# cp /sdcard/busybox /system/xbin
# cd /system/xbin
# chmod 755 busybox
# ./busybox --install
# mount -o ro,remount /dev/block/mtdblock6 /system
One thought at the end: How did you root?
I rooted by flashing "vunerable recovery" using RSD lite, copied milestone-root.zip to sd card, renamed it update.zip, rebooted into recovery mode, flashed update.zip from there.
I didn't realise I had to install something like open recovery, think because I remember not having to do that on my pulse? Anyway will try and install one of those now.
Thanks those commands at the end helped, actually managed to copy busybox to /system/xbin, however the 2nd last one "./busybox --install" gave me a load of errors -all being no such file or directory, for example "/usr/bin/wc: no such file"
about 30 of those path errors. Maybe the command path "./busybox" needs to be something else?
ah, okay. sorry, I thought you already installed an openrecovery. for many cool features you will need it (e.g. nandroid, for overclocking it's not a must but a nice-to-have). please don't use GOT, it's rather old already. androidiani is okay, I think.
I think your previous attempts to install busybox via the app etc. mixed up some internal links in the device. please reboot and try again (the above steps except the "cp ..."). seems like the app tried to install busybox to /usr/bin but failed... I hope this failed attempt will be fixed by a simple reboot. otherwise it would be great to have the output of:
Code:
# su
# ls /usr/bin
No I re-flashed my main sbf and also did a factory reset to do a clean start, only thing since that full wipe I have done is rooting in the method I described, installed the screenmode widget, textedit, and android terminal emulator.
I have no such file /usr, are you sure I should have this in droid/milestone?
Here is my full output of my root system using ls:
tmp
pds
cdrom
sqlite_stmt_journals
config
cache
sdcard
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
perhaps "/usr" is a sub inside one of the above folders? I tried using "find" to find it but that command dosn't seem to work since it won't even find the ones I can see with ls
I found it, /usr is inside /system... so if busybox was moved to /system/xbin, I'm guessing the ./ means install it to the parent directory which was /system which /usr is also in.
The errors I got said no such file "/usr" so It seems like it is trying to install to the wrong directory.... perhaps the command should be "busybox --install" or "/busybox --install" I don't want to experiment and mess things up before your opinion on this.
*edit almost forgot, output of /system/usr is
keychars
bin
srec
keylayout
share
output of /system/usr/bin is
panic_daemon
gki_pd_notifier
nvm_daemon
clean_dex.sh
brcm_guci_drv
bplogd_daemon
This is really strange. Maybe your busybox-file is corrupt.
Where did you download the busybox-file?
Which sbf did you flash?
So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".
If you want, you may try:
# /system/xbin/busybox --install
instead of
# ./busybox --install
Or maybe try this one:
# /system/xbin/busybox --install -s /system/xbin
Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*
My main sbf I flashed was android 2.1(uk version).
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
I also managed to install open recovery and do a nandroid backup succesfully
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Thanks for all your help so far.
droidtech1 said:
My main sbf I flashed was android 2.1(uk version).
Click to expand...
Click to collapse
Don't want to try one of the 2.2?
droidtech1 said:
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
Click to expand...
Click to collapse
Yes, this sounds very much like installation was successful.
droidtech1 said:
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
Click to expand...
Click to collapse
typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.
I had a look at the busybox syntax and it's actually
Code:
busybox --install [-s] [INSTALLDIR]
So you have to put the directory you want to install in at the end. That's what your last command makes use of
droidtech1 said:
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Click to expand...
Click to collapse
Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html
I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.
I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.
Hi,
I get through this with my eye's closed but when I have to type in the chmod line,and hit enter, it says, "unable to chmod : / Read-Only file system / I've asked this on many different forms, and researched it and tried a lot of code to fix it, none of witch worked, so now I'm just asking strait out if anyone knows how I can fix this, It's done this on 2 separate computers so It's doubtful that it's a PC problem.
Thanks for reading this and perhaps helping me, I'm about to rip my hair out, lol,
Kn0t
Wait what?
So it's rooted tab yeah and your? Terminal or abd? Into the system. So you have super user rights huh? And the system files are mounted as read/write? If you said yes to these questioned which I assume you will as it sounds like you are savvy with permissions and how android mounts its system files from the "eyes closed" part then its a new one on me, I have never heard of this problem?
Oh and what kernel you running? is it gingerbread or froyo?
Sent from my GT-P1000
Don't forget to grant superuser its permissions. Check if the app is asking for it. Perform adb with tab on, superuser will pop up.
I felt for that couple of times.
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
speldenaar said:
Don't forget to grant superuser its permissions. Check if the app is asking for it.
I felt for that couple of times.
Click to expand...
Click to collapse
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
And lastly I'm thinking this doesn't qualify to be in the development section bud .. its a little cause and general and should be in General section not Here.
Sorry but its out of control on these boards.... these threads shouldn't be in the development section unless you are developing something or are replying to a development thread about, well.... a development ... or finally, ahhhhh....ummm, bah... development... just had to say it one more time and couldn't get a third reason... I don't want to be harsh or you think I'm flaming you its just my 2 cents....
Sent from my GT-P1000
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
it's adb,, and I have super permissions, yes and it says it's a Read-only file system when I go to write my chmod. The "eye's closed" part of my post was just me being sarcastic about the amount of phones I've done this too and the amount of time I've done it with zero problems.. that's all.
Yup, I did that.. thanks a lot for the advice..!!
nobleskill said:
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes I agree but I don't know how to fix it that way.. thanks for helping
Sorry man. It was supposed to be moved to Q and A some time ago and it just never happened. My fault, my mistake. sorry to all that this bothers, and thank you to all that are helping me out.
~k~
nobleskill said:
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
Click to expand...
Click to collapse
Thanks a lot for this advice, I tried it and got a message that says, "System permissions cannot be changed because the file system is Read-only"
Thanks again, it was worth a try.
~K~
quick question....
When do I enter that into my command prompt? right before I try to chmod or right after????
thanks a lot
~K~
mchampeli said:
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
Click to expand...
Click to collapse
I think you have to put on a new rom that does that. try http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
good luck
~K~
GldRush98 said:
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Yea I tried that and it said "system permission cannot be changed becausethe file system is Read-Only" so I don' know. But I do really appriciate you trying to help me out.
knotrkr said:
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Click to expand...
Click to collapse
Whoops, I thought the file you were chmod'ing was in the system partition.
The data partition is already mounted with read/write.
Your chmod command is incorrect... there is an extra space in there.
It should be:
chmod 755 /data/local/bin/flash_image
I don't think the data partition is mounted as read only (I could be wrong, but I didn't think it was)
In the latest cm9 nightly build - update-cm-9-20120419-NIGHTLY, my wifi is not work with my own kernel.
So, I checked the catalog, and found this: wifi modules was changed.
http://review.cyanogenmod.com/#/c/14910/1/BoardConfigCommon.mk
old path: /system/modules/bcm4329.ko
new path: /system/lib/modules/bcm4329.ko
It will cause your wifi not work with custom kernel.
If your wifi is not work, just make a symbol link, type these command in the terminal:
su
mount -o remount,rw /system
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
#Thanks Paragon_X, I forgot to tell you to remount /.
mount -o remount,ro /system
Or, you are the kernel developer, your should put your kernel modules in both path, or link them.
Thanks
I confirm this change as well and the fix worked.
I have the wifi authentication problem. Do I flash the download link from the link you posted?
Paragon_X said:
I have the wifi authentication problem. Do I flash the download link from the link you posted?
Click to expand...
Click to collapse
That is not a download link, its a Git review...
Sent from my Nexus S using Tapatalk 2
DaXmax said:
That is not a download link, its a Git review...
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Okay thanks so regarding the command written... is there spaces in there or am I seeing things?
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
I'm not familiar with typing in superuser so I have to ask
There are spaces.
If you are unfamiliar with the spaces, then you will be unfamiliar with the before and after commands around that command too:
mount -o remount,rw /system
and
mount -o remount,ro /system
Thanks for the fix!
Sent from my Nexus S using XDA
Thanks that will be handy for surprised users, if CM actually thought things through, they would link the dirs to allow a transition time where kernels work with modules in old location and new location.
Sent from my Galaxy Nexus
Hi,im kinda really noob at this stuff atm but do we type this in command prompt or terminal emulator (or any other program like that). And can someone confirm the code is:
su
mount -o remount,rw /system
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
#Thanks Paragon_X, I forgot to tell you to remount /.
mount -o remount,ro /system
the "fix" is included in the latest trinity kernels. wifi works with the newest cm9(nightlies and kangs), older cm9, and every other rom.
simms22 said:
the "fix" is included in the latest trinity kernels. wifi works with the newest cm9(nightlies and kangs), older cm9, and every other rom.
Click to expand...
Click to collapse
Im using matrix kernel v19 cfs and the latest CM9 v7. Trying to get the wifi working now and its hard.
Heres what i have done using terminal emulator
Typed in "su". Pressed enter. I granted super user permissions.
Typed in "mount -o remount,rw /system" . Pressed enter. Didnt say anything
Typed in "ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko". Pressed Enter
It showed up "link failed File exists"
now its changed to "255|[email protected]:/". Before it was "[email protected]:/"
I than typed in "mount -o remount,ro /system"
My wifi still doesnt work
I'll reply here to. The reason you can not link (ln) is that there is a file where you are trying to add a "shortcut" just remove the bcm*.ko file in /system/lib/modules and copy the module from /system/modules there. I used root explorer then it's just cut and paste
Sent from my Nexus S using Tapatalk 2
TigaTiger said:
Im using matrix kernel v19 cfs and the latest CM9 v7. Trying to get the wifi working now and its hard.
Heres what i have done using terminal emulator
Typed in "su". Pressed enter. I granted super user permissions.
Typed in "mount -o remount,rw /system" . Pressed enter. Didnt say anything
Typed in "ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko". Pressed Enter
It showed up "link failed File exists"
now its changed to "255|[email protected]:/". Before it was "[email protected]:/"
I than typed in "mount -o remount,ro /system"
My wifi still doesnt work
Click to expand...
Click to collapse
same problem here, also when i use any root explorer ( free ) i cant get permision to do this, and i have rooted my phone... anyone knows why ?
Sejmir said:
same problem here, also when i use any root explorer ( free ) i cant get permision to do this, and i have rooted my phone... anyone knows why ?
Click to expand...
Click to collapse
Mount /system as R/W (read-write) first.
kong said:
Mount /system as R/W (read-write) first.
Click to expand...
Click to collapse
didnt quite get you, but il google it tnx for the tip m8
Thanks! Wi-Fi now working. Very simple. Just copy & paste to new lib/modules location using root explorer.
Beamed from my Nexus S using Tapatalk 2
Sejmir said:
didnt understand you, mount /system in recovery then run emulator or root explorer or smthing else ?? sry im totaly new to androids, but never too late to learn new things
anywys have a lots of googling to do, coz il learn how to do this via adb shell...
Click to expand...
Click to collapse
root explorer has an option in the top of the screen, mount r/w. press it, it will now say mount r/o, thats what you want.
skitapa said:
I'll reply here to. The reason you can not link (ln) is that there is a file where you are trying to add a "shortcut" just remove the bcm*.ko file in /system/lib/modules and copy the module from /system/modules there. I used root explorer then it's just cut and paste
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
I still have no luck. Is the error everyone getting the authentication problem? and simply wifi indicator wont popup?
For all the people who dont get this too well, especielly me. Could an experienced, someone who knows this, write out the complete instructions and codes to do it. Preferably in detail because some of us have no idea what we are suppose to do. And suggest what type of programs we should be using. thanks in advance.
Ok. Let's take it from the start. When android boots it loads the kernel to handle all the drivers and inner workings of the OS. It also loads modules, that's optional drivers loaded on demand. Now CM9, used to load it's modules from /system/modules but has changed it's location to /system/lib/modules. This is new to the people making custom kernels which kernel installs it's modules in the wrong place. This makes the new kernel try to load the old module but fails because of different kernel source versions. Now, our task is to move the new module in /system/modules to /system/lib/modules overwriting the old one.
Start a terminal.
Type su and enter to become superuser which is the only user with rights to change system files.
Now if there is a box asking you to allow this, press allow.
Now type:
mount -o remount, rw /system
This will make the system folder and child folders writable.
type:
rm /system/lib/modules/bcm*
That will remove the old module.
Type:
cp /system/modules/bcm* /system/lib/modules
Reboot and it should work.
Sent from my Nexus S using Tapatalk 2
I'm using the -mm (master-mount) option (or trying to) to be able to link folders from internal to external SD. Unfortunately it doesn't seem to work in a 'permanent' way. Any new app started after the mount does not receive the mounted folders, only apps already running will receive it!?
Furthermore, I tried various ways of using the -mm command, but only one seem to work:
su -mm -c 'mount command here' < /dev/null
Running su -mm and piping the commands fails, eg does not mount anything, but no failure message!?
Running su -mm -c <script_path> < /dev/null fails., eg does not mount anything, but no failure message!?
I also tried to run within different context, but it changes nothing. App started after the mount won't see it.
@Chainfire, can you help me make it work? Maybe detail a little more the How-to on this subject, because I fail to find a working method and I don't see how to make it work.
The only way to make it work seems to disable mount namespace separations.
Thanks.
@Chainfire, I understood you're likely not here for the rest of the summer, so you'll hopefully get this when you're back. Happy holiday until then.
I've made further investigations, on a stock-rooted LG G4, latest Lollipop 5.1.1.
For info, the mount commands are like this: 'mount -o bind,shared <source> <target>'... I run them using this syntax: su -mm -c 'mount... '.
EDIT:
All mounted folders are then accessible by any root shell started before or after they have been mounted. However other shells (be it started by the same app or another) do not see them if they are started after the folders have been mounted. If those standard shell are already running when the folders are mounted, they are all visible! Same behavior on a 4.4.2 device.
Then I tried disabling mount separation, but the result is exactly the same except for a very annoying side effect though, root shells actually loose access to /storage/emulated/0 !
EDIT2:
Found out that it only affects the emulated path (/storage/emulated/... and possibly /storage/extSdCard), if using /data/media and /mnt/media_rw paths, the mounts stick across processes, at least when the fuse filesystem is used.
Nevertheless is this a bug, is there something that can be done to make it work for emulated path (be it on fuse or sdcard filesystems) ? Or am I misunderstanding how all this works, or misusing the options? I'll appreciate any help you can provide on this. Let me know if you need any further information, I'll be happy to provide anything you need.
Thanks.