im chinese, and my phone couldnt support the router which using wifi channel 12or13,but it works used to ... and i dont know why and when the phone couldnt works in some day~~
although i have set the location seems to be "chinese(hongkong....)"
in my opinon i know UK,CA support wifi channel 1 to 11, but in china(most in asia), channel 13 will be seted in default model, such like "Netgera 614" and so on~
the point is~ i dont kown why the phone lost support in the time when it works used to(i used channel before,and no problems~~)
how can fix it? its some system file control that "channel support" ?and i lost it?
THX for help
Look in the old root thread for a post by jerpela under the main root post.. in it is a link to get you channel 13 wireless..
Sent via rooted X10 using XDA.
MeZmeriZe_ said:
Look in the old root thread for a post by jerpela under the main root post.. in it is a link to get you channel 13 wireless..
Sent via rooted X10 using XDA.
Click to expand...
Click to collapse
could you show me the link? im the "kid" in this bbs~ and my english is poor....
so im hard to commuicate to someone who use the "real english"..
http://forum.xda-developers.com/showpost.php?p=6970879&postcount=4
Thx alot, but i think it fail ,.. thats the cmd result(in windows.)
----------------------------
Unable to chmod /data/misc/wifi: Operation not permitted
Unable to chmod /data/misc/wifi/reg_code: Permission denied
0 KB/s (2 bytes in 0.031s)
/data/misc/wifi/reg_code: cannot open for write: Permission denied
Unable to chmod /data/misc/wifi: Operation not permitted
Unable to chmod /data/misc/wifi/reg_code: Permission denied
##############################
# WIFI PATCHED SUCCESFULLY #
##############################
reboot: Operation not permitted
----------------------------
i have used "Universal Androot" for root my phone, but why the system dir couldnt to write? so the cmd said` "Operation not permitted"
Go to Market and download scripter, then go to this post:
http://forum.xda-developers.com/showpost.php?p=7636933&postcount=231
And use your scripter scanner to scan the unsecure script (2nd one) then re-run the above patch.
When you have finished run your scripter scanner again and select the 1st script to secure shell. Thats it and your done.
THX lot!! ive fix my phone now!!!
just~~~ THx so much
ou~ no ~ there new trouble coming.. that the wifi_patch just can works one times..
i run the patch , it will auto restart and if the wifi is opening it can scaned and connected to the AP which channel i set to "12 or 13(higher than 11)". but it just works only one times~~ if i turn off the wifi and turn on again, it cant works..
i think that something will reset the wifi channel in the begining of the phone power on.
just because if the wifi is turn off already and i run the wifi_patch(succesfull), than wait the phone complitly power up, and in this time i turn on the wifi , it cant scan and connect any AP which seted channel "12 or 13". so, i think it is something will reset the wifi channel by the time which the phone power on..
Related
Hi,
as my employer uses LEAP security for the wireless LAN in the office I used the following workaround:
I added a wireless network using PEAP security and then manually edited my /data/misc/wifi/wpa_supplicant.conf to change PEAP to LEAP and my rooted Hero connects without problems to the network.
HOWEVER after each reboot it is impossible to activate WIFI until I do the following:
./adb pull /data/misc/wifi/wpa_supplicant.conf wpa_supplicant.conf
./adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf wpa_supplicant.conf
In other words I push/pull the very same file without changing any content .... and by miracle afterwards I can enable WIFI
I also tried a small script (GScript Lite) which copies the wpa_supplicant.conf to/from the SD card ... does not work.
Btw, it does happen with a rooted stock HTC 1.5 rom, VillainROM 5.5, VillainROM 6.0, 6.1 and 6.2 .....
I attached the file (with some xxx'ed lines)
Any clues????
krimskrams
Hi,
after some more research I found the problem ... normally wpa_supplicant.conf is owned by UID:GID 1000:1010 , after pushing the file via adb back to the phone, this was changed to 0:0 and rw-rw-rw- permissions, however after a reboot these permissions changed to rw-rw----- and the WIFI service could not read the file anymore, I changed the UID:GID back to 1000:1010 at now it works flowlessly.
Krimskrams
I have a similar issue with a Tmobile Vibrant, can you explain how to check the UID:GID on a file and also how to edit it ?
Use chown command to change owner.
It's a built in linux command to specify user and group.
Google it for syntax etc, then make gscript to chown the files you need done.
Also check chmod for permissions while you're there, as they might also need to be set.
edit: sorry i posted on the wrong tab -_-
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
superdx said:
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
Click to expand...
Click to collapse
I am not quite sure what your problem is.
Do you mean tethering?
And your phone does not keep the AP name and password for its own WLAN hotspot?
I am sure that there are some tethering apps on the Market.
Maybe one of them can help you to configure a customized AP name and password and saves it for later use.
Yep that's it exactly, tethering. The AP name and password keep resetting!
http://forum.xda-developers.com/showpost.php?p=18711488&postcount=128
clefster said:
This is because the permissions for the wifi settings got messed up so it can't write out your new permissions. The error handling isn't too good so it doesn't tell you about it
To fix, in a rooted terminal run this command:
chmod 770 /data/misc/wifi
Click to expand...
Click to collapse
After struggling with root, I tried your command and it doesn't work, says Operation not permitted
Hi im trying to change my wifi mac address.
i tryed this one
http://forum.xda-developers.com/showthread.php?t=1385577 but it's not working and many other way and almost any app on the market .
so please if anyone change his mac on Mini pro Please help.
Got root and busybox?
Sent from my WT19i using xda premium
I did and it's not working not on Xperia Mini Pro.
REQUIREMENTS
1) ROOTED PHONE
2) BUSYBOX INSTALLED
3) Terminal App
OPEN UP TERMINAL AND WRITE
:su
:busybox iplink show eth0
(THIS WILL SHOW YOUR CURRENT MAC ADDRESS)
NOW TYPE IN
:busybox ifconfig eth0 hw ether 00:11:22:33:44:55
(INSTEAD OF 00:11:22:33:44:55, YOU CAN WRITE YOUR WANTED ADDRESS)
Click to expand...
Click to collapse
And what happens then?
Explain, what does it show, what error or what message comes up.
Code:
Ifconfig: SIOCSIFHWADDR: Operation not supported
Thank you for your relpay.
@ murders10: are you sure the root worked? what firmware are you running? are you using the right interface, is it eth0 that you wanna change?
Yes im sure root it's working fine Stock Rom .62.interface Wlan0 There is no eth0 on Xperia.
I did the same thing but it replied me:applet not found...
I need some help
I hope someone can help as.
Sent from my SK17i using xda premium
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
it won't work with me what ever i did remove reinstall
But after all i fix my god dam router mac address problem. so i don't need to change any mac . thank you for the help.
Need to change MAC Address to try if Heywire works on a custom rom
urra901109 said:
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
Click to expand...
Click to collapse
I'm trying this, but get a message error in terminal emulator, when i type :su, theres a message that says :su: not found, or :busybox ..., the same :busybox: not found error displays.
I'm runing Real ICS lite r2, on my Sk17a, with locked bootloader, stock kernel, rooted, with busybox 1.20 installed,
Im trying this because i use heywire a lot, and this rom is the best ive tried, and its awesome, lighting fast, but heywire says this phone has a previous heywire number, and as i investigated, it has something to do with the MAC address, give me some light here please
ipconfig: applet not found - MAC spoofing
Someguyfromhell said:
And what happens then?
Explain, what does it show, what error or what message comes up.
Click to expand...
Click to collapse
Hello, I've been trying to follow this guide at:
http://forum.xda-developers.com/showthread.php?t=1385577
My phone has CM 7.2,busybox installed too.
Entering
Code:
busybox ifconfig
in terminal (not in su) gives me the local loopback address, and when I turn on my wifi, it shows my wifi card details too. (It's named tiwlan0 though)
Anyhow, since ifconfig needs to be run as root, I get ifconfig: applet not found after I enter following commands:
Code:
$su
#busybox ifconfig (and anything starting with this)
So it looks like ifconfig runs fine without su but is not detected at all after I make the switch to su. And since the line of code that changes the MAC cannot be run without su(then I get - SIOCSIFHWADDR: operation not permitted), I am stuck!
I tried other methods such as and similar to the one on
http://forum.xda-developers.com/showthread.php?t=1343695
where, after editing some configuration file, one could change his MAC address. Is there any such known file/method for the LWW?
Thanks!
Simple Tutorial to spoof MAC address
So I finally figured this out and it actually works for the purpose u needed, I will write down step by step guide, and write me if you need some help
1. You need your XMP to be rooted, with SU intalled, busybox installed and with terminal emulator app
2. Open terminal emulator app, and type: su
3.Allow terminal app to have super user access
4.Now type: busybox ifconfig (with your WiFi on)
5.Locate the text on the left side "wlan0" and in that paragraph locate HWaddr, write down this address just in case.
6.Now turn your WiFi off
7.In terminal write down this: busybox ifconfig wlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
8. Turn on your WiFi, And your MAC address should be the one you created (you can check that by typing in terminal: busybox ifconfig)
And ther you go, you spoofed your WLAN MAC address, tested by me in a simple tutorial, hope it helps
---------- Post added at 01:58 AM ---------- Previous post was at 01:52 AM ----------
In your case step 7 should be like this:
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
Click to expand...
Click to collapse
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
blackstallion1234 said:
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Click to expand...
Click to collapse
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Problem with busybox probably...
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
pikpok said:
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
Click to expand...
Click to collapse
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Xtrifer said:
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Click to expand...
Click to collapse
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
nice
blackstallion1234 said:
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
Click to expand...
Click to collapse
Good, I was sure it was busybox, don't forget to hit the thanks button, happy modding lol