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 -_-
Related
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..
I've compiled 2.1 from source and I ran in to a problem. The device will boot and the touchscreen,keyboard, apps, and the phone all work but i'm having a problem trying to install apps from the marketplace. when i download an app it will download ok but always says installation unsuccessful and says insufficient storage. I checked the phone storage and it's over 100mb so i'm clueless as to why i'm getting this error.
I'm also having problems getting the sound working. I can select ringtones but nothing ever plays. I've copied the proprietary files from a ROM i was using on the device prior to flashing this and added them into this ROM. any help is greatly appreciated.
1) Try this from a command prompt (terminal app or adb shell):
chown system.system /data/app
chmod 0771 /data/app
If this works, you should add this to your update-script before flashing again:
set_perm 1000 1000 0771 DATA:app
2) Not sure about the sound issues, although I have an AOSP 2.2 ROM that acts the exact same way.
you actually inspired me to try to make my own ROM. I used your android builder and dsixda's kitchen. let me know if you figure something out with the sounds. It took me long enough to figure out how to get it to recognize the SD card.
That worked. I'm also havings issues with the camera and softkey lights. i copied the lights file into the proper folder but they still don't work. camera doesn't do anything either.
setcpu also for some reason can't get root either, it says root access not detected but i have su in /system/bin. too many problems!
update. apparently my permissions are somehow screwed up. i can use ADB and have root access but from the device itself using a terminal emulator i've figured out i don't have full root. any suggestions?
fixed the su issues. i had to adb remount and adb shell and chmod 06755 /system/bin/su if anyone was wondering
I'm still having issues with sound, camera, etc. i have moved all the proprietary files from a stock HTC 2.1 ROM over and i'm still having problems. I'm now using the new CFS kernel from conap and decad3nce and got overclocking to work. The main problems are sound and the softkey lights, once i get those working i can use this ROM everyday and work on the wifi, bluetooth and camera. If anyone has any tips or knows any other libs that might work it would be great.
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.
I have wasted more than 3 days trying to figure out how to configure openvpn
on S2.
I tried the following roms:
Villainrom 1.4
Cognition S2 v1.07
Skyrom 1.0
Lite'ning Rom v1.5
and none of them seems to work.
I tried everything mentioned in :
http://forum.xda-developers.com/showthread.php?t=1115984&highlight=openvpn
http://forum.xda-developers.com/showthread.php?t=1074492&highlight=openvpn
but openvpn does not work.
I also own a HTC desire and configuration files work without a problem.
I tried manually installing openvpn as described in the posts but it does not work.
The problems are:
If I install openvpn manually as described in the threads above it does not connect to the openvpn server.
I installed openvpn from the market by selecting the folder for the binary
/system/xbin
and tried all the possibilities for path for ifconfig/route.
- /system/bin
- /system/xbin
- /system/xbin/bb
The default folder for ifconfig/route should be /system/bin (result from which ifconfig) and only that selection does not give the horrible
"FATAL: Linux ifconfig failed: could not execute external program".
but openvpn still does not work.
Any ideas ?
Hello,
I have the same problem, with same error
but I have successfully get connected to my vpn (vpntunnel.se) but its useless since the route doesnt use the vpn connection.
If anyone could help...
i have same problem too. some help would be good
Could this help?
I'd love to get this working too but I have not made any attempts yet so I'm monitoring this thread.
Searching for that exact error message on google led me to this thread which you may already have found.
In particular, even though it's about the galaxy i5800, the following comment may shed some light:
you may not use the pre-installed busybox from samsung (which is found in /sbin). It is a reduced version of busybox that does not include suitable ifconfig- and route-commands for openvpn. thus you have to install a full version of busybox... normally this is done, when you root your phone according to descriptions found in this forum.
you can alternatively install titanium backup (which installs its own busybox) and copy the "full" busybox from titanum backup to /system/xbin.
Click to expand...
Click to collapse
Try to do it but impossible for me. Im with lite ing rom. Check my configuration tomorow
Sent from my GT-I9100 using XDA App
Alright, so after going nutts (several times) I solved this issue (several times) only to always find I dont really know what the error is. But then again, I know more about Geological disasters than I know about Android ...
Anyways, heres my solution which appears to work. However, it goes away once you reboot (easily fixed) and disappears completely after you update firmware - but I made shortcuts.
The thing is, that the original busybox is not installed where openvpn looks for it. Regardless of this, openvpn has no idea how to use ifconfig / route commands in /system/bin directory.
So this is what I do:
1) Install busybox (from the market, get ver 1.19) to /system/xbin
2) Install openvpn to /system/xbin and point ifconfig/route to /system/xbin/bb (during installation).
3) Link the new busybox to the /bb directory MANUALLY with these commands (customized to steps 1/2 - you can change them to your liking but dont forget to update step 3 as well):
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
ln -s /system/xbin/busybox /system/xbin/bb/route
Click to expand...
Click to collapse
What it does is place a busybox link to ifconfig and route in /bb directory.
Funny thing - Whenever I tried linking ifconfig/route to other places (like /system/xbin) it just didn't work. It made the tunnel, but tun0 int was always down (thats why it says "connect to as xx.xx.xx.xx" missing the tunnel internal IP - as in, no routing).
Challanges - when you soft reset, something dies. Not sure if its the busybox or the links. However, simply "reinstalling" busybox to /system/xbin solves it (its not really reinstalling, its just going into the busybox installer. Its only recreating links).
When you install an update/new cfw, everything dies. Reinstall busybox and re-enter the link commands.
Hope this helps, hope some android programmer tells me why it works this way. gluck.
Hi!
How do I change the WiFi mac address of an Amaze phone?
I got two Amaze phones that I put Sport's CM10.1 on them.
Problem is both have the same (well known!) mac address. Seems like either CM10.1 picks a fixes address, or perhaps the process or rooting it cause the mac address to be reset?
I tried searching for ways to change it. Some posts require using busybox, however, that's temporary.
Some posts refer to change it in an nvram.txt data somewhere in /data/misc/ (or similar, don't have it handy), however, I do not have that file in any of the phones. I do not know what format I would have to put it in if I were to venture to do it. I found one example of a different phone and it was a rather complex file with all sorts of settings, which makes me cautious about even trying something and possibly breaking the format of the nvram on the phone.
Thanks!
[/COLOR]
ihama said:
Hi!
How do I change the WiFi mac address of an Amaze phone?
I got two Amaze phones that I put Sport's CM10.1 on them.
Problem is both have the same (well known!) mac address. Seems like either CM10.1 picks a fixes address, or perhaps the process or rooting it cause the mac address to be reset?
I tried searching for ways to change it. Some posts require using busybox, however, that's temporary.
Some posts refer to change it in an nvram.txt data somewhere in /data/misc/ (or similar, don't have it handy), however, I do not have that file in any of the phones. I do not know what format I would have to put it in if I were to venture to do it. I found one example of a different phone and it was a rather complex file with all sorts of settings, which makes me cautious about even trying something and possibly breaking the format of the nvram on the phone.
Thanks!
Click to expand...
Click to collapse
flash any sense 4.x rom on any of your device,i heard that sense 4.x roms change the mac adress of your device,dont knw what is the reason though...read it alnog yor research and readings...
http://forum.xda-developers.com/showthread.php?t=2201216
hatim_rajput said:
[/COLOR]
flash any sense 4.x rom on any of your device,i heard that sense 4.x roms change the mac adress of your device,dont knw what is the reason though...read it alnog yor research and readings...
http://forum.xda-developers.com/showthread.php?t=2201216
Click to expand...
Click to collapse
Thanks for the reply, however, this is not a great solution, as it's rather invasive. I'm also finding that this image I am on is stable and yields good battery and it has the latest 4.2.2, so I am trying to avoid major changes like a rom from a different device might be (I'm new to this too ..).
Here is what I have tried:
brute-force search on the zip file that Sport posted
brute-force search on the phone itself via a root shell
searching various other files and forums
the brute-force search on the phone found the mac address. This is what i did:
find -exec grep -iH '00:d2:8b:43:9f:fd' '{}' \;
which yielded:
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/ieee80211/phy1/macaddress:00:d2:8b:43:9f:fd
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/ieee80211/phy1/addresses:00:d2:8b:43:9f:fd
/sys/devices/platform/msm_sdcc.4/mmc_host/mmc3/mmc3:0001/mmc3:0001:2/wl12xx/net/wlan0/address:00:d2:8b:43:9f:fd
However these files are in a "/proc/-like" mounted device that is read-only. These files look like status files from the OS, so even if I had been able to change them, it looks like the changes would vanish after reboot, and even if that would not be the case, it would not have changed anything.
Any ideas?
This is the solution for permanently changing the MAC of the WiFi in the Amaze (ruby) phone:
su -
mount -o remount -o rw /system
cd /system/etc/firmware/ti-connectivity
calibrator set nvs_mac wl1271-nvs.bin 00:d2:8b:XX:YY:ZZ
cd /
mount -o remount -o ro /system
change the XX YY ZZ to any other (hex) numbers as you please.
(The assumption is that you are connected with adb shell)