You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /system
exit
adb push bin\sqlite3 /system/bin
adb shell
su
chmod 6755 /system/bin/sqlite3
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
reboot
Ohhhh it's good to see you here in the Iconia section!
I used to be a user of your great Desire Kernels/roms.
Hope to see some work from you soon.
richardtrip said:
You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push bin\sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
adb shell reboot
Click to expand...
Click to collapse
Thank you very much and great to see you here
OT: can you help us with the recovery issues ??
Thanks in advanced. I will try sometime in the near future.
Enviado desde mi GT-I9000B usando XDA Premium App
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
lpachuong said:
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
Click to expand...
Click to collapse
The rest of the ram is reserved for video on boot.
I thought so, but don't you think that is too much out of 1GB ram? I found the device is laggy if ram goes under 350MB. Hope modded kernel can help optimize ram.
sweet
Nicely done! It works. Yea it is good to see you here' meaning we have somebody who knows a thing or two about android development.
W
Fix worked!
For some strange reason adb remount command didn't worked and adb wasn't able to push sqlite3 file to /system/bin even after remounting /system rw from the device itself. I had to push it to sdcard and then move it to /system/bin.
By the way, channel 13 is working fine now.
Thx
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
EDIT: I can confirm that this works!
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
[Edit: worked with a terminal, but forgot to SU first, and I was typing mmcblkop3, not mmcblk0p3 !!]
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire).
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Try su before the mount command.
Edited the procedure in the first post so try that (should work now).
Sent from my A500 using XDA Premium App
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Just do
Code:
su
mount -o remount,rw /system
daveba said:
Just do
Code:
su
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
For the beginners (like me): I noticed that /system was set back to read-only on reboot...
Works brilliantly. Thanks.
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
hi
can anyone tell me whats this fix for?
is it going to make wifi receiver even better?
thx..
he_stheone64 said:
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
Click to expand...
Click to collapse
yes,
add this line
ro.wifi.country=EU
and reboot.
i have this message:
'Unable to detect a device over adb'
I've connected my nexus S via usb cable, i've tryed with the usb usb storage on an off, and i get the same message.
I'm using windows / x64.
Dexter_nlb said:
yes,
add this line
ro.wifi.country=EU
and reboot.
Click to expand...
Click to collapse
i've done that but i canot save the file i get the message that it's a read only file system.
how can i gain write access to that file??
Thanks the fix_wifichannel_EU.bat in the zip worked like a charm. Channel 13 now works on my Asus Eeepad Transformer purchased from the US as well.
Related
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
alias_neo said:
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
Click to expand...
Click to collapse
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
foxmeister said:
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
Click to expand...
Click to collapse
Thanks, so which should I actually use, the former or the latter?
I've personally used the first command, but I saw the second one on another thread and it seems to work as well.
To be honest, I think it's ignoring the parameter anyway.
Regards,
Dave
Hi,
I have rooted my Nexus one. I can do "'adb shell and then 'su' under the shell"
But on my MacOS Desktop, when I execute 'adb remount', it still said
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Can anyone please help me resolve this?
Thank you.
[size=+4]DO *NOT* POST QUESTIONS IN THIS FORUM - only tips/info/etc.[/size]
Right at the top. Why does this have to be repeated on a daily basis?
Can you please move my thread to the right forum? I can't find a way to do it.
Anyhow, to answer you question... you "adb remount" is disabled in production releases... just rooting does not allow this.
You need a modified boot image where ro.secure=0 in default.props, instead of ro.secure=1. The ro.secure flag in the boot image indicates whether the root filesystem can be remounted as read/write... 0 indicated it can be... 1 indicated it cannot be.
If ro.secure=0, this is referred to as insecure boot.
Most custom ROMs have this by default... some rooted stock ROMs do not have this...
Will the Modified GRI40 (2.3.3 Gingerbread) ROM from this
http:// forum.xda-developers.com/showthread.php?t=968396
Does what I need? Thanks.
Or you can also use these commands to mount and unmount the system partition as writable:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,ro /dev/block/mtdblock3 /system
Thank you. That seems to be an easier solution for me.
But after I did
$ adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I go to another shell and i did
adb push sqlite3 /system
failed to copy 'sqlite3' to '/system/sqlite3': Read-only file system
$ adb push sqlite3 /system/bin
failed to copy 'sqlite3' to '/system/bin/sqlite3': Permission denied
Click to expand...
Click to collapse
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
hap497 said:
Thank you. That seems to be an easier solution for me.
But after I did
I go to another shell and i did
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
Click to expand...
Click to collapse
Don't try to combine adb commands with shell commands.
Copy/move/push the file to your sdcard first.
Then open a root shell, mount it as rw, then copy the file from your sdcard to the directory you want.
Thanks. but I get 'failed on '/sdcard/sqlite3' - Cross-device link'
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/sqlite3 /system/
failed on '/sdcard/sqlite3' - Cross-device link
# ls -l /sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
and i have tried:
# mv /mnt/sdcard/sqlite3 /system/bin/
failed on '/mnt/sdcard/sqlite3' - Cross-device link
# ls -l /mnt/sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
I get the 'sqlite3' from SuperOneClickv1.7-ShortFuse.zip.
Wholly crap, don't use the mv command! Bad idea!!! mv does not move the data, it moves the hardlink to the data! Thank your lucky stars mv wouldn't let you do it.
Use cp instead. cp will actually copy the data to where you're going.
Thank you. But I don't have 'cp' in my adb shell.
# cp
cp: not found
# /system/bin/cp
/system/bin/cp: not found
Click to expand...
Click to collapse
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
How do you have mv but not cp? Do you not have BusyBox installed?
No. I just need to search 'BusyBox' on Android market and install it? That is?
hap497 said:
Thank you. But I don't have 'cp' in my adb shell.
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
Click to expand...
Click to collapse
The cat command will work fine, no busybox needed: cat source_file > dest_file
efrant said:
The cat command will work fine, no busybox needed: cat source_file > dest_file
Click to expand...
Click to collapse
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
OP, Yes, BusyBox can be installed from the market.
GldRush98 said:
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
Click to expand...
Click to collapse
Really? I was unaware of that. It worked every time I used it.
efrant said:
Really? I was unaware of that. It worked every time I used it.
Click to expand...
Click to collapse
On standard Unix/Linux/etc. systems, cat works fine for binary files. It's only under DOS that cat or type shouldn't be used for binaries.
back in my ADB days.. itd say remount failed or w.e but i could still access my phone..
but i dont know.. ever since i switched to linux i stopped using ADB.. hahah
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks
there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system
Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?
Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App
Thanks guys, but I resorted to busybox chmod command instead lol
I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**
Hello,
Has anyone gotten adb remount to work? I always get
remount failed: operation not permitted
Click to expand...
Click to collapse
I've also tried
Code:
mount -o remount,rw /dev/block/mmcblk0p4 /system
both from adb and in the terminal emulator but I get the same response
Trying to push anything to /system just results in
failed to copy '<file>' to '/system/<path>': Read-only file system
Click to expand...
Click to collapse
Any ideas?
Root?
You are rooted right? and didn't forget to "su" before those shell commands? because the shell command works fine for me, I remount system and changed the fonts
apparently I was just making it more complicated than it needs to be. You don't need to specify the mount point. Just use
mount -o remount,rw /system
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
So, basically you are without an Android launcher or file manager?
If you made a backup with NookManager, restoring it is your best bet. If not, make sure to do so once this is sorted out. Backup early and often.
Do you have wireless ADB working? You can install (or reinstall) apps that way. Or, if you have the Market working, install any file manager that will work. That will give you access to folders again and you can copy over apps via USB and then use the file manager to install them.
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
gsms said:
The device in question is Nook Simple Touch, rooted with NookManager.
I had deleted Relaunch.apk ver. 1.3.8 in order to install newer version.
But after de-installation, iam unable to charge the folder with apps....
How to install Relaunch again ?
Click to expand...
Click to collapse
Have you tried downloading the Relaunch.apk file via a web-browser? Once the download is completed you should get a prompt on whether you want to install it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:19 PM ----------
gsms said:
I have installed adb thru usb, but now have other problem.
Trying to copy file(s), it gives me message ,that folder is read-only.
What is exact command to mount folder as read-write in adb shell ?
I tried many times - with no success...
non working-
adb remount /system/
adb remount
adb remount root/system/
and so on.................................
Please help
Click to expand...
Click to collapse
To mount /system as read+write:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
exit
After you're done with copying over the desired file into /system, just reboot the nook to revert the mounting back to read-only.
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
Click to expand...
Click to collapse
The mount command line I provided is the correct command for your purpose. Note that the command is to be entered on the NST itself after you get on it using "adb shell" command.
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
The folder permission 755 is inoperative since the filesystem itself is still being mounted read-only.
gsms said:
After typing the first 2 rows of the code :
adb shell
mount -o rw,remount /dev/block/mmcblk0p5 /system
i receive message:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So this row
"mount -o rw,remount /dev/block/mmcblk0p5 /system" is not correct....?
upd1:
i was able to see the permissions for folder /system
drwxr-xr-x
This means :
(755) — The owner has read, write and execute permissions; the group and others can only read and execute.
This is strange, because iam the owner...
Click to expand...
Click to collapse
I have been able to successfully achieve this with this command:
mount -o remount rw /system
The command is simpler and thus I am less likely to make a typo.
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
gsms said:
Thanks for your entries, but i already re-rooted my Nook.
I was out of nerves to deal with adb shell....
----------------
But using "mount" command thru adb shell could be very helpful in some critical cases....
Click to expand...
Click to collapse
Make a backup