Database Develop

google maps 3.2 not 3.1.2 [faster loading]

anyways im against piracy but on another forums someone got the map apk from 2.0 built eclair. and it works. heres the link to the 2.0 built downloa it and pull it and just install on your fone.
http://forum.xda-developers.com/showthread.php?t=567821
its in system/app

so this works with cupcake/donut builds?

Chedderknight said:
so this works with cupcake/donut builds?
Click to expand...
Click to collapse
Ya, working fantabuously on Cm 4.99999999999999999999999999999999999999 or whatever the latest CM is.

no dice on 4.0.4

Chedderknight said:
no dice on 4.0.4
Click to expand...
Click to collapse
Installation method? Did you get errors somewhere along the way? ect..

It would make sense, 4.0.4 is on the 1.5 kernal not 1.6.

I'm running Cyan 4.1.9999 and getting "Google Maps could not be installed on this phone" is there anything you did to get past this?

AdrianK said:
Installation method? Did you get errors somewhere along the way? ect..
Click to expand...
Click to collapse
Through terminal and the general file manager way.
Code:
cp /system/app/Maps.apk /sdcard/Maps.bak
mount -o rw,remount /system
cp /sdcard/Maps.apk /system/app/Maps.apk

gracias...seems a little slow on mine
Lemme take that back...locked up on first use...now working very nicely. just seems like a "pretty-fied" maps with layers...still nice though

So what is the real difference between 3.1.2 and 3.2?

It seems faster overall and includes layers so you can have multiple map modes active at the same time, ie: sat+traffic+locale.

sacrifice a few lambs and it should work fine.

Works Great on TheOfficial AOSP1.6_r1.2......

i think it only works on 1.6 only and not 1.5. its just a minor update, but ive notice gps works when on edge and 3g i get pin point acuarrcy .

its a great upgrade..

Sorry for the noob question but how do I do this through terminal?

re
Post #8 contains your answer.
Chedderknight said:
Through terminal and the general file manager way.
Code:
cp /system/app/Maps.apk /sdcard/Maps.bak
mount -o rw,remount /system
cp /sdcard/Maps.apk /system/app/Maps.apk
Click to expand...
Click to collapse

I tried that and it said "cannot stat '/system/app/Maps.apk': no such file or directory

Well if you extract the file from the Build, then get it on your sdcard... it would probably look like this:
cp /system/app/GoogleMaps.apk /sdcard/GoogleMaps.bak
mount -o rw,remount /system
cp /sdcard/Maps.apk /system/app/GoogleMaps.apk
Click to expand...
Click to collapse
Then Remember that the GoogleMaps.bak on your sdcard, is a backup.. and to put it back if your phone cant handle it, would be:
cp /sdcard/GoogleMaps.bak /system/app/GoogleMaps.apk
give it a try and post back

Well try Adb, make sure you: mount -o rw,remount /system....

Help a Captivate brother out?

Can Galaxy S users backup their bootup animations for me? I want to get rid of as much of the AT&T crap as possible.
They are as follows
Startup
/system/etc/PowerOn.wav
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
Thanks

here you go...
View attachment gt-i9000.zip
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother

Thanks! Going to try them out now

Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.

Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?
Sent from my GT-I9000 using XDA App

Didn't they free the brothers back in January 1865?

Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
decepticon said:
Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.
Click to expand...
Click to collapse

KJPDX said:
Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?p
Click to expand...
Click to collapse
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.

bestwebs said:
Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
Click to expand...
Click to collapse
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
jodue said:
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.
Click to expand...
Click to collapse
This is the reason why, the generic Galaxy S FW does not work with the Captivate.

Hi,
For some reason root explorer wouldn't paste these.
But I did figure out a way with adb.
I copied all 3 files to my sdcard 1st
These are the commands I used in case they are of help to anyone:
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9
mount -o rw,remount -t rfs /dev/block/stl9 /s
# busybox cp /sdcard/PowerOn.wav /system/etc
busybox cp /sdcard/PowerOn.wav /system/etc
and
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9 /system
mount -o rw,remount -t rfs /dev/block/stl9 /system
# busybox cp /sdcard/bootsamsungloop.qmg /system/med
busybox cp /sdcard/bootsamsungloop.qmg /system/media
# busybox cp /sdcard/bootsamsung.qmg /system/media
busybox cp /sdcard/bootsamsung.qmg /system/media
Thanks
decepticon said:
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
This is the reason why, the generic Galaxy S FW does not work with the Captivate.
Click to expand...
Click to collapse

emclondon said:
here you go...
View attachment 368161
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother
Click to expand...
Click to collapse
Thanks for posting this, exactly what I was looking for!

[MOD] Webtop Via HDMI Without a Dock Added support for 4.4.80.MB860 (South Africa)

I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
We got PROPS from Engadget: http://www.engadget.com/2011/03/05/motorola-atrix-docks-literally-and-figuratively-torn-apart-hack/
NOTE THESE FILES ARE FROM THE ATT BRANDED ATRIX v4.1.26
THEY WILL NOT WORK ON THE BELL ATRIX VARIANT
Added Support for:
Atrix 4.4.80.MB860 (South Africa) Users Go HERE: Updated Mod Files for Atrix 4.4.80.MB860 (South Africa)
Version 4.5.91 Users Go HERE: (This works now.) ATRIX 4.5.91 WEBTOP MOD FILES
ATT version 4.1.57 Users Go HERE: ATT ATRIX 4.1.57 WEBTOP MOD FILES
Bell Users Go HERE: BELL ATRIX WEBTOP MOD FILES
*new* CWM Install Method - CWM Required:
Get CWM here: http://forum.xda-developers.com/showthread.php?t=1019143
Then install the flashable zip here: CWM-ATT-4.1.26.zip
You no longer need to be rooted OR deodexed!!!!
Install Method 1 - No Root or Deodex Required:
Simpler install method:
Download The Mod Files here: HERE
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
RETURNING TO STOCK - Root Required:
This will restore the files that were backed up by the install script.
If you were Deodexed it will restore the modified files to the original Deodexed State, if you were not deodexed it will restore to stock and allow motorola updates to work again.
Note: If you were deodexed you can ignore the three lines about the odex files.
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/WebtopModBackup/DockProvider.odex.bak /system/app/DockProvider.odex
cp /mnt/sdcard/WebtopModBackup/DockService.odex.bak /system/app/DockService.odex
cp /mnt/sdcard/WebtopModBackup/PortalApp.odex.bak /system/app/PortalApp.odex
cp /mnt/sdcard/WebtopModBackup/DockProvider.apk.bak /system/app/DockProvider.apk
cp /mnt/sdcard/WebtopModBackup/DockService.apk.bak /system/app/DockService.apk
cp /mnt/sdcard/WebtopModBackup/PortalApp.apk.bak /system/app/PortalApp.apk
chmod 644 /system/app/*
Install Method 2 - Root Required:
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockProvider.odex /system/app/DockProvider.odex.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockProvider.apk /system/app/DockProvider.apk.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer to copy the files to /system/app and rename the .odex files to .bak
Make sure you set the permissions on the files to rw-r--r-- or they will not work.
Then Enjoy your fully functional webtop.
Having problems? Read Below.
Try clearing your Dalvik Cache:
Code:
adb shell
su
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
acardinale said:
It was INDEED permission issues.
If using the root explorer method, you MUST fix permissions for all three files to rw-r--r--
Thanks Fenny!
Click to expand...
Click to collapse
Additionally, try unfreezing any frozen apps in Titanium Backup.
Thanks to DG for his ADEO installer script.
Appreciate my work? Buy Me a Beer:

Fenny said:
I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
YOU WILL NEED TO BE ROOTED AND DEODEXED!!!!
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer.
Then Enjoy your fully functional webtop.
Click to expand...
Click to collapse
HAHA you beat me to it i was up all night last night doing this ... good work ill test yours out

Hehe told you the answer was in PortalApp.apk.

Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!

mercuryzzz said:
Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!
Click to expand...
Click to collapse
I have been looking into it, I don't think the DockPicker Activity HAS a mirroring option, but I think it should be possible with third party software.

Fenny said:
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Click to expand...
Click to collapse
We totally need a xda meetup I am in Kearns

Fenny said:
Hehe told you the answer was in PortalApp.apk.
Click to expand...
Click to collapse
Yep, i did waste alot of time in the others as well, than i spent morning posting themes etc , any how congrats and glad to see either way we on same page... now we got to get some drivers and functionality over to this webtop, as my magic track pad is lacking any multi touch but im confident in getting that done , i mean after all if is Ubuntu !!

AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.

clubtech said:
AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.
Click to expand...
Click to collapse
Yes if you dont understand why you need to re read up on it, as .odex files contain parts of the program that were moved out side to be optimized

So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.

So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?

ankitb4u said:
So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.
Click to expand...
Click to collapse
Yeah, you need to reboot after replacing the files, can't hurt to clear the dalvik cache either. But the crashing is expected until you reboot.
clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
Yeah, the on screen Trackpad, AND Keyboard work great.

clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
you dont need Adeo per-say but that might be the easiest way for you to get a deodexed system unless you know what you are doing... i do not have adeo but am deodexed

Works PERFECTLY.
Did have a continuous FC after loading PortalApp.apk, but it went away with a reboot.
Tested all the WebTop functions and from what I can tell, they all work without issue.
Nicely done!

Props to the OP + contributors for getting this much-needed functionality going so quickly.

I am super excited about this. Props to all that was involved. I will be trying this later. I really need to get more familiar with ADB. Thanks again.
clipse94

Webtop via HDMI cable is working great! Now to find a working ARM-based JRE...

Awesome
correct me if im wrong, but now a bluetooth keyboard and mouse are a neccessity for 'desktop computing' right
since the dock allowed us to use a USB one
?

If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.

clipse94 said:
If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.
Click to expand...
Click to collapse
Correct.
BT keyboard and mouse not required.
Built in track-pad mouse and keyboard work fine.
Takes getting used too though.
This comment was made via the webtop.

[MOD] 4.1.57 deodexed framework and app files (AT&T Only)

Here are the App and Framework system files for 4.1.57 fully deodexed.
You must already have Root access in 4.1.57.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Remember to make a backup of your existing framework and app folders BEFORE you do this.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Again, backup your original system/framework and system/app files BEFORE you do this in case you want to revert back to an odexed system.
Here is the correction:
Put your phone in USB Mass Storage Device mode.
Copy the app and framework directory and their contents from the zip file to the root of your sdcard.
***Verify the copy was successful before you continue.***
Set USB mode back to None.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot

Thanks, you beat me to it!

lindsaytheflint said:
Thanks, you beat me to it!
Click to expand...
Click to collapse
I deodexed them last night, but wanted to run through some testing before I packaged them up.
Anyone feel like scripting this, go for it.

I must have done something wrong in shell... soft brick, certain it was my fault.

tl_bull said:
I must have done something wrong in shell... soft brick, certain it was my fault.
Click to expand...
Click to collapse
Not your fault... I found an error in my instructions.
cp /sdcard/frame/* /system/framework/
should be
cp /sdcard/framework/* /system/framework/

rjohnstone said:
Here are the App and Framework system files for 4.1.57 fully deodexed.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
Been running all day with these files with no issues.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Here is the correction.
Copy the app and framework directory to the root of your sdcard.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system

lpsi2000 said:
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Thx. Updated OP.
The mount commands I originally posted did work for me without any issue though.
Sent from my MB860 using XDA App

It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.

Ririal said:
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Click to expand...
Click to collapse
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App

I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Edit:
Had to use usb port on the rear instead of the front when rooting.

zeyoner said:
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Click to expand...
Click to collapse
Sounds like you don't have root access.
Do you see a $ or a # in your command prompt?

i have $ in my root access... i'm getting permission denied at when i type 'su' but im pretty sure i rooted it earlier today
edit fixed i wasnt rooted

rjohnstone said:
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I looked it over again, should be fine.
EDIT: Nvm saw you updated.
I'm working on a new method to automate this, I'll post something when I have it working reliably.

looking for another way
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?

Very nice contribution!

Rad ryan said:
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Click to expand...
Click to collapse
This won't work without having root access first.
Sent from my MB860 using XDA App

I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.

Immix said:
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Click to expand...
Click to collapse
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.

shawnbuck said:
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
Click to expand...
Click to collapse
Thx for the tip.
I did use the stop command in my process and was able to prevent a reboot.
The process is so quick that I didn't see a single FC during the copy.

I think it should be mentioned in the OP that root is required.

ATTENTION: wifi modules path was changed in cm-9-0419

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