Lately I have some troubles connecting to a certain router. My phone's MAC is blocked. Is there any method to change it or to foul the router with another MAC address? I've read something but nothing of it won't apply to our LG O3D.
First, fooling around with MAC addresses can cause huge problems if your MAC address conflicts with another on your network. Something about MAC addresses being unique and all.
That being said, the phone's unique identifying information is in /dev/block/mmcblk0p3. You can dd it out, edit it with a hex editor by finding your current MAC address and replacing it with another, then dd it back into the phone. No guarantees this will not break anything.
Read this: http://forum.xda-developers.com/showthread.php?t=1385577
You might need to use wlan0, instead of eth0.
New updates
post-mortem said:
Read this: http://forum.xda-developers.com/showthread.php?t=1385577
You might need to use wlan0, instead of eth0.
Click to expand...
Click to collapse
Tried the link you gave me... Should clarify some things first:
- Those commands are working only with the WiFi module active, meaning that you must be connected to a WiFi network.
- On our O3D the WiFi module is addressed with tiwlan0, not wlan0 or eth0
- No matter what I can't get it done because it says something like this: "SIOCSIFHWADDR: OPERATION NOT SUPPORTED" - and YES! my busybox is updated
At the end I'll give it a try to what pandaball wrote. Thanks everybody, I'll keep in touch.
Hi Bro,
I got mentioned file and I used the Hex editor , but the problem I couldn't find the my mac address 1c:b0:94:ca:dc:33 in order to change it and move back to my phone as new mac address .
help me out pls
BR
Babi
pandaball said:
First, fooling around with MAC addresses can cause huge problems if your MAC address conflicts with another on your network. Something about MAC addresses being unique and all.
That being said, the phone's unique identifying information is in /dev/block/mmcblk0p3. You can dd it out, edit it with a hex editor by finding your current MAC address and replacing it with another, then dd it back into the phone. No guarantees this will not break anything.
Click to expand...
Click to collapse
sarababak said:
Hi Bro,
I got mentioned file and I used the Hex editor , but the problem I couldn't find the my mac address 1c:b0:94:ca:dc:33 in order to change it and move back to my phone as new mac address .
help me out pls
BR
Babi
Click to expand...
Click to collapse
Hopefully you weren't searching with the colons, so it should be 1CB094CADC33. Also, it might be backwards, as in 33DCCA94B01C. Capitalization matters (since it's hex), and I think the letters should be capitalized.
BigBadSheep said:
Lately I have some troubles connecting to a certain router. My phone's MAC is blocked. Is there any method to change it or to foul the router with another MAC address? I've read something but nothing of it won't apply to our LG O3D.
Click to expand...
Click to collapse
Hidden menu -> port settnigs ->cp image download; then on pc run tutty and at%mac= is the command youre looking for.
Sent from my LG-P920 using xda app-developers app
Related
I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:
adb shell wpa_supplicant -v
and it returned v0.6.10 on my (wifi only) xoom.
Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....
The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again
My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.
I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!
Thanks for your help!
-amruthwo
Stock wpa_supplicant file from Xoom
(lives in system/bin)
amruthwo said:
I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:
adb shell wpa_supplicant -v
and it returned v0.6.10 on my (wifi only) xoom.
Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....
The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again
My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.
I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!
Thanks for your help!
-amruthwo
Stock wpa_supplicant file from Xoom
(lives in system/bin)
Click to expand...
Click to collapse
ooooh You are close. Imma gonna play with this over the weekend. I want this.
next question...
Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.
Can anyone shed some light on a good program for win/linux that might work better?
amruthwo said:
Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.
Can anyone shed some light on a good program for win/linux that might work better?
Click to expand...
Click to collapse
we cant edit it directly with notepad, we need the source code of HC then add the adhoc code then compile it..
one thing that curious for me is the wpa_supplicant version is the same as in froyo or ginger android, but we can't just put that already adhoc enable compiled wpa_supplicant file to our HC..it will make our wifi can't see any wifi network..
hmm perhaps there is some other file involved..lets dig it..
exactly, i've been rubbing my chin for about a week on this one. I don't see why the froyo/ginger v0.6.10 file doesn't work...
maybe there is another file involved though, i'm going to go digging in the system folder to see if anything looks related i guess.
hopefully source is released soon, it would make this a little easier...
Pretty sure wpa_supplicant is a GPL project so you shouldn't need to wait for HC source for that.
What errors are you seeing in the logcat after replacing it?
i actually didn't record the log, let me do it again and i'll see what the log says. I'll report back.
log file
here is a bit of the log when trying to connect to wifi...
basically, it says wpa supplicant unable to initiate ap scan
Being Android noob, and since I'm trying to get this xoom to see ad-hoc networks for work (this is really important.. spent 600, expecting it to connect it to adhoc.. dang it.), would it be worthwhile to port wpa_supplicant from droid x?
Droid x reports 0.6.10. Unlike EVO, since they are both motorola products, they have something in common??
Or maybe, xoom uses a different driver? I see that droid x has tiwlan0 as its wireless, whereas xoom simply says wlan0.
Reading from here: htt p:/ /sz ym . ne t/2 01 0/1 2/a dh oc - w i fi - in - an d ro i d /
(sorry, being a new user, it doesn't let me post a link... )
someone says that wpa_supplicant needs to be compiled with the correct driver.
Does anyone know how to do this? Or am I just wrong? lol
from what i understand, the wpa_supplicant is part of the gpl, not unique to any phone manufacture. I'm no expert on the subject either though. I have no idea what is different in the xoom, but i have used the v0.6.10 which matches that of the xoom, but no dice. If you want to extract one from the droid x and edit it (assuming you know how) then it is definitely worth a shot!
let us know what you find
lesjaw said:
we cant edit it directly with notepad, we need the source code of HC then add the adhoc code then compile it..
one thing that curious for me is the wpa_supplicant version is the same as in froyo or ginger android, but we can't just put that already adhoc enable compiled wpa_supplicant file to our HC..it will make our wifi can't see any wifi network..
hmm perhaps there is some other file involved..lets dig it..
Click to expand...
Click to collapse
You're right about not being able to edit in notepad, but I opened it in notepad++ to at least view it. I don't have visual studio installed on my laptop at the moment or else I would try with that.
At any rate searching through the file in notepad++ I found two instances where it refers to adhoc that looked interesting.
One line says: WPA: Invalid mode %d (not IBSS/ad-hoc) for WPA-None
and the other line says: skip - IBSS (adhoc) network
That second line looks to tell it to skip adhoc networks when scanning.
Pretty sure wpa_supplicant is a GPL project so you shouldn't need to wait for HC source for that.
Click to expand...
Click to collapse
It is. It even says so within the file.
EDIT: I was able to open it in Visual Studio and it looked much better. I'll see if I can figure something out with what to edit in the file.
Solution found!
hey, someone finally got the binary figured out!
check out the thread here
and, if you're away from your computer, or just hate using adb, my buddy mr_wrong_0 has root explorer instructions here!
Hi,
I had to change my Transformer because of an issue. Before getting the new one I made a nandroid backup from the old one. Now, I restored this backup to the new one and saw that the Wifi MAC address is the one from old one.
I assume, the nandroid backup has restored old Transformer's mac address to the new one.
How can I revert back to the original MAC address of this new Transformer ?
Btw, I don't know the MAC address of the new Transformer. How can I find it ?
Thanks.
I was able to change the mac address by modifying mac line in /data/misc/wifi/nvram.txt
but I don't know how to find the original mac address.
If I remove the mac line from this file, it generates a mac address but I don't know if that's the correct original one.
any idea ?
I need help about how to find the original mac address. I've also done a factory reset.
It now shows a new mac address starting with 14A:E9 but when I search this on MAC-VENDOR search, I can't see any vendor. So is it fake ? or random ?
How can I find the real mac address of my device ? Shouldn't it be available on the box or the device itself ?
any ideas on this ?
how can I get my Transformer's original mac address ?
mrmrmrmr said:
any ideas on this ?
how can I get my Transformer's original mac address ?
Click to expand...
Click to collapse
Rumor has it that if you delete the line that starts 'macaddr = ' , and whatever trash follows (the MAC) , that a reboot will restore the original.
It doesn't really make much sense since organizations, (e.g. ASUS) are assigned a 'small range' of MACs by whoever is the bureau for those things now (always was Xerox in the past), and changing for example a MAC to 00:00:00:00:00:00 will be out of that range. How do you know the allowable range, or is this just to spoof someone else's to get an IP from their router? Changing the MAC has big implications just because you'll never pick one out of a hat that isn't already being used by anyone and that'll mean troubles on the net.
Actually, I don't care, but to MASK it for awhile, you should be able to do what you did, and to get it back, you "should" be able to use 'wordpad' or whatever format that nvram.txt file is in and change it back. I used 'od -h /data/misc/wifi/nvram.txt' to figure out that the last line was the MAC.
By the way, you probably now this, but to really check the MAC, probably the best way is to use (from term or adb shell):
#ifconfig wlan0
and look at it.
thanks for your comments.
if I remove mac line from nvram.txt, I get a totaslly different mac address.
And when I search that, it says "Murata Company"
with the older MAC, mac search finds "AsusTek"
mrmrmrmr said:
thanks for your comments.
if I remove mac line from nvram.txt, I get a totaslly different mac address.
And when I search that, it says "Murata Company"
with the older MAC, mac search finds "AsusTek"
Click to expand...
Click to collapse
Well, at least the nvram.txt file does something. The ASUS (well, how up to date could this be?) range for their wifi devices, one of their suppliers is 'Murata', is this:
f4-6d-04-ZZ-XX-YY. (well, for my transformer anyway)
Murata and ASUS appear to have a bunch of overlapping ranges. Maybe since ASUS Transformer has a Murata chip onboard, they also have some dealings regarding MACs. I have no idea really, but is having a Murata MAC (as said by who-knows-how-reliable web-search), a problem? Just curious.
1. Why does everyone care what their original MAC address was? I've used DE:AD:BE:EF:FA:CE as the MAC address on every device I owned, at one point or another.
2. "Changing the MAC has big implications just because you'll never pick one out of a hat that isn't already being used by anyone and that'll mean troubles on the net."
This isn't really accurate. The MAC address is used by your local network for DHCP, routing, etc, but it does not leave the LAN. Your MAC address will never be visible to the internet on the TF, so there is almost no chance of an address conflict. There'd have to be someone on your LAN with the same MAC to cause a problem.
I doubt that "everyone" cares what their original MAC was, but the OP does. I don't personally care or have a desire to change it and I suspect most have no idea what a MAC is anyway.
IPv6 might make MACs more prevalent past the LAN or WLAN but I think only with stateless config. ARP cache using static config could "possibly" lead to trouble in a LAN, but I basically agree and it seems like not a big issue.
hachamacha said:
I doubt that "everyone" cares what their original MAC was, but the OP does. I don't personally care or have a desire to change it and I suspect most have no idea what a MAC is anyway.
IPv6 might make MACs more prevalent past the LAN or WLAN but I think only with stateless config. ARP cache using static config could "possibly" lead to trouble in a LAN, but I basically agree and it seems like not a big issue.
Click to expand...
Click to collapse
Sorry, didn't mean to generalize, but there are actually two posters in this thread with the question, so by "everyone" I meant the two of them.
I agree about IPv6, but very few people will be stateless, so I suspect it still won't matter in 99.9% of cases.
Also, to mrmrmrmr, if you removed the config line that changed it in the first place, I would be surprised to see it randomly generate a new one. I'd expect the MAC address seen now is the original, whether it's registered with Asus or not. Changing the config again, and then reverting again, should show whether it's statically or randomly generated, just to make sure.
thanks for your posts.
I care about this because I really don't want to use a mac address which is not mine.
I know the mac address is not leaving the LAN but for regulation purposes it is used in LAN records.
I would like to obey the regulatory authority
anyway, if I remove the line from nvram.txt ,each time I re-enable wifi, I get a new mac address. maybe if I reboot, I will receive a permanent one.
Also, if I factory reset, I get totally a new one.
weird ...
No nvrm.txt file.
What to do.
wifi is not turning on, mac address unavailable
So I've been putzing around with this thing for a few days since I got it. One thing I've been trying to do now that I have root access is get it to connect to adhoc wifi. To be specific, I want to use my data-enabled cellphone as an adhoc wireless access point so that I can connect the LePan to it over wifi to surf the net, email, play games, etc. Of course, by default, Android is set up NOT to connect to adhoc wireless, or even recognize adhoc networks.
I installed a wifi sniffer app on the LePan, and it can see the adhoc network that my phone is broadcasting, but it won't connect. I managed to find a few webpages with instructions on how to mod android to connect to adhoc, but most of the instructions are device specific, and obviously there's nothing out there for the LePan yet, as its a relatively new device (I would have posted this in the TC970 forum here on xda, but there isn't one yet). Most of the instructions talk about modifying two files in the /system/etc/wifi folder. The first is tiwlan.ini, and the other is wpa_supplicant.conf.
I basically mixed/followed the instructions on these two webpages:
http://www.slatedroid.com/topic/1054...adhoc-on-a81e/
and
http://www.slatedroid.com/topic/1819...rk-android-22/
So right now I've added the following lines to tiwlan.ini:
WiFiAdhoc = 1 (Change from 0 to 1)
dot11DesiredSSID = InsertyourSSIDhere
dot11DesiredBSSType = 0 (Add this line in)
And I've replaced everything in the wpa_supplicant.conf file with this:
ctrl_interface=tiwlan0
update_config=1
eapol_version=1
ap_scan=2
network={
ssid="Ad-hoc ssid here"
scan_ssid=1
key_mgmt=NONE
mode=1
priority=1
}
network={
ssid="Your Accesspoint ssid here"
psk="your wpa key here"
key_mgmt=WPA-PSK
priority=2
}
(obviously I have my own settings in the real file)
In addition, I copied the wpa_supplicant file from the zip in this post:
http://forum.xda-developers.com/showthread.php?t=754961
into /system/bin/.
Now when I try to use my wifi, it turns on, says its trying to connect for a bit, but then the eventually just turns off without connecting or detecting any networks (so it probably doesn't actually turn on at all).
I've backed up all my files, so no problem getting it all back and working like stock, but I'd really like to be able to connect to adhoc with my new tablet. Suggestions are most welcome.
***Sorry if this is posted in the wrong forum. Like I said, there is not yet a dedicated forum for this device, otherwise I would have posted there. Mods - any chance of creating a forum for this device? I've seen a few other stray TC970 posts here on xda.
Sandmonkee,
After messing about with this myself, I found a supplicant that works on our tablet (I tried about 6 different supplicants until I found this one). It is the one for a nook color. See this thread http://forum.xda-developers.com/showthread.php?t=868354
It works on my Nokia N900 with the MobileHotspot app.
I believe that the problem with the supplicants that were in the post that you referred to is that they were linked to use wext instead of the statically linked libCustomWifi for the TI chip. See the comments section on szym's blog about the patch.
It would be better to apply szym's patches to the code tree that was used to create the wpa_supplicant for this tablet instead of TI's reference code as this one did. That might fix the sleep problem. I don't know where to find the sources. Anybody have any ideas? If the sleep issue becomes a problem, I might look into modifying the reference code (altho' I have enough on my plate without spending too much time on this toy).
***** UPDATE ****
This supplicant doesn't have a problem on this tablet with sleep as was described in the above thread.
***** END UPDATE ****
BTW the wpa_supplicant.conf that you want to modify is in /data/misc/wifi NOT /system/etc/wifi
Here is my version (replace the ****** with values appropriate for you)
The 1st entry is for my AP using WPA, the 2nd one is for my ad-hoc phone using WEP. You might need to add the line "ap_scan=2" if you don't broadcast a SSID.
Code:
ctrl_interface=tiwlan0
update_config=1
network={
ssid="*****"
psk="*********"
key_mgmt=WPA-PSK
priority=1
}
network={
ssid="*********"
scan_ssid=1
key_mgmt=NONE
group=WEP104
auth_alg=SHARED
wep_key0="********"
priority=2
mode=1
}
I don't know if the "group=WEP104" line is needed, I found it in another thread somewhere but it doesn't seem to hurt.
Let me know if this works for you too.
-Shawn
Works!
Shawn, yer a genius.
I have been struggling with this for a week or so now, and it is finally working. You just increased the usefulness of my tablet by 100x
Thanks again man!!
Mike
yeah, bro. That's what's up.Thanks!
This is great stuff...thanks for sharing. One quick question for you guys: are you using adb to modify the files? I can't seem to get adb to work...do i need a driver different than the one derkoch linked to in the root achieved thread?
joofeloof,
I used the one that you referred to. I rooted the tablet. Then for my own sanity I installed HackersKeyboard to get a real keyboard, bash shell so I could get filename completion, and nano for a small editor from the shell. Now the tablet is much like a standard linux system from the command line. I used adb to push the files to the sdcard and copied the files to the correct locations from a local shell. Don't forget the permissions. Any text editor will work to edit the configuration files, altho' I prefer nano. If you are familiar with vi, it is available also.
If you can't get adb to work, you could just copy the files to your sdcard and move them locally.
To do this mod, the tablet must be rooted.
Hope this answers your questions.
-Shawn
P.S. Does anybody know how to get a bluetooth hid device (keyboard/mouse) to work on this tablet? There is a nice folio that has a BT keyboard built in that would make this a great terminal for doing remote system admin stuff.
**** UPDATE****
Found it. For BT keyboard use EasyConnect which is available in the market.
**** END UPDATE ****
Non-terminal instructions
joofeloof said:
This is great stuff...thanks for sharing. One quick question for you guys: are you using adb to modify the files? I can't seem to get adb to work...do i need a driver different than the one derkoch linked to in the root achieved thread?
Click to expand...
Click to collapse
Shawn's method above will work, but I did it using ES File Explorer with root permissions enabled.
1. Root your phone as described in DerKoch's post
2. Download Shawn's wpa_supplicant file to your PC and extract
3. On your tablet, download and install ES file explorer from the market (its free)
4. Open ES explorer and go into the settings. At the bottom of the list, enable "root explorer" and "mount file system"
5. Use ES file explorer to copy your /data/misc/wifi/wpa_supplicant.conf to your SD card
6. Plug the tablet into your PC and turn on USB file sharing and USB debugging
7. Copy the wpa_supplicant.conf file from your SD card to your PC and modify per Shawn's instructions above, with your own settings.
8. Save the file and then copy it back to your SD card, along with Shawn's wpa_supplicant file
9. Stop USB file sharing on the tablet
10. turn off wifi on your tablet.
11. Open ES file explorer on the tablet, copy the wpa_supplicant.conf file from your SD card to the /data/misc/wifi directory (overwrite), then copy Shawn's wpa_supplicant file to /system/bin (also overwrite).
11.5 Note that these files need to have the right permissions (by default, they should already). In ES file explorer, do a long press of the wpa_supplicant file you just copied to /system/bin, then click on properties, then "change permissions". It should be chmod755, ie the X's should look like this:
X X X
X 0 X
X 0 X
For the wpa_supplicant.conf file, it should be chmod777 (ie ALL the boxes should have X's)
12. Turn on wifi. That should do it.
I noted that although I included the lines from Shawn's file for the adhoc WEP security, when my tablet saw the phone (which was unsecured), it created a new entry in the list of available networks for the open signal. So those lines may not be necessary. In fact, I suspect the only part that may have been necessary would be the header information (ap_scan=2 and all that), since Andriod just makes entries in the wpa_supplicant.conf file when you tell it to remember an access point. If its not already in the .conf file, it still shows up in your list of available AP's, it just doesn't remember it in your list.
Either way, thanks again to Shawn for figuring this out!
Much appreciated! Working fine, just fine...I was heading down this path anyway, more curious about how to get adb working than anything.
Many thanks.
Also, does or has anyone play[ed] around much with /proc settings?
I'm more familiar with linux server admin than any of the android specifics - but it seems like many of the kernel settings are readily configurable. I just don't know which would really be of interest in a tablet configuration/setting.
Now, my next question is.. anyway to enable Wifi channel 12-14?
Worked Great. Thank you for figuring this out. Now I can make use of that 6gb data plan.
Wireless Tether 3.1 Beta Supports ad-hoc
SilverFang83 said:
Worked Great. Thank you for figuring this out. Now I can make use of that 6gb data plan.
Click to expand...
Click to collapse
hey y'all....
just a heads up (and y'all might already have this info but jussssst in case there are ppl like me out there that read this thread and said, "um, maybe i don't need to have my LePan use my phone's network after all"...(lol) it seems the most recent version of wireless tether 3.1 beta i think http://code.google.com/p/android-wifi-tether/) supports ad-hoc. I just downloaded it, changed from "disabled to enabled" in Acess Control, and then "in CHANGE Device Settings" picked a phone like mine (they didn't have The Infuse but Galaxy S worked)
You might have to restart the Wireless tether ap but after it automatically showed my network on LePan. made a quick video on it here: http://www.youtube.com/watch?v=wACwGZ0XyuA&list=UU-xOxPoQXnvEQKqkucrM_Cg&index=1&feature=plcp
No matter what settings i tried on earlier versions of Wireless Tether it would NOT work, but the new 3.1 v8 Beta did : )
Anyway, i'm a little out of my depth here so if i have posted this in wrong place or if it doesn't directly correspond to the issue at hand, please forgive, just tryin' to help other numbnuts like me : )
Ms D
Alright! Gave it a try with MyWi 4.0 on Iphone 4, can see the SSID and try to connect but fails to get an IP, goes to a loop of trying then scanning then trying to obtain IP. Oh well.
EDIT: made it forget network and re-entered password from settings, worked. I'll post the .conf file in a sec.
EDIT2:
Here are my settings for MyWi 4.0 using Iphone 4
--------------------
ctrl_interface=tiwlan0
update_config=1
network={
ssid="yournetwork"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=yourkey
priority=4
mode=1
--------------------
The tablet should enter those for you when you first try to connect to your network, though.
GOOD JOB EVERYONE
Now this is bizarre to me... The supplicant and the mods on the *.conf file works great, yet if I reboot the tablet, the *.conf file's permissions gets automatically modified to
X X 0
X X 0
0 0 0
thus causing an error on the wifi's startup.
I used Es file explorer to set the permissions and when I change 'em back, well everything works fine.
I'm quite puzzled atm.
Tried to use Terminal Emulator app to set the permissions with adb but I get a permission denied, and no SuperUser prompt :/ .. do you guys use adb from sdk via usb?
Help? Trouble with Barnacle
First off great work guys.
I never connected ad hoc before, and didn't realize I needed to root at first. I finally got it to see my droid eris' wifi network (thanks largely to Sandmonkee's step by step guide) using barnacle and to actually connect but as soon I try going to a webpage on the tablet barnacle freezes and then generates a boat-load of NAT:restart: network is unreachable errors.
What are you all using to broadcast the ad hoc network?
***EDIT
NEVERMIND, Ms.Dummbunny's solution worked for me too
BreeZyer said:
Now this is bizarre to me... The supplicant and the mods on the *.conf file works great, yet if I reboot the tablet, the *.conf file's permissions gets automatically modified to
X X 0
X X 0
0 0 0
thus causing an error on the wifi's startup.
I used Es file explorer to set the permissions and when I change 'em back, well everything works fine.
I'm quite puzzled atm.
Tried to use Terminal Emulator app to set the permissions with adb but I get a permission denied, and no SuperUser prompt :/ .. do you guys use adb from sdk via usb?
Click to expand...
Click to collapse
I have been trying to do this for the past two days without success too. I have this permission problem. Plus, my tablet just shows "obtaining IP address" for a moment then disconnects. I am not trying to tether from my phone though, I have an old laptop with an intel 3945 card, trying to setup an adhoc network and connect to it. My SGS2 with MIUI works perfectly fine, so it is doable. Any suggestions what else I can try?
OK, this is sort of related...
I go Le Pan TC970 connected on Ch 12!
Base on http://forum.xda-developers.com/showthread.php?t=1067944
I manually modified the settings.db and it sort of worked (Ch 12 only, and no go on Ch 13 for some reasons....)
Steps...
Copy /data/data/com.android.providers.settings/databases/settings.db to sdcard
Modify settings.db using SQLite "Manager" by adding extra row 116, wifi_country_code, EU in "secure" table
Rename /data/data/com.android.providers.settings/databases/settings.db to /data/data/com.android.providers.settings/databases/settings.db.bk just in case
copy the newly modified settings.db from sdcard back to /data/data/com.android.providers.settings/databases folder
Reboot
==
Update: WiFi Analyzer can see my AP when set to Ch13 too. But it can't connect, and I think maybe is my router....
whatid said:
OK, this is sort of related...
I go Le Pan TC970 connected on Ch 12!
..
Click to expand...
Click to collapse
Hey whatid,
Just curious - what is the advantage of having channel 12? Also, did you have to mod your router at all?
Sandmonkee said:
Hey whatid,
Just curious - what is the advantage of having channel 12? Also, did you have to mod your router at all?
Click to expand...
Click to collapse
Depends where you are located, in Europe you can use Ch 12&13 and Japan with additional Ch14.
Some router will let you select Ch 12-14. Or if you have DDWRT installed.
MsD...Thanks for the info. I tried this on my phone (Xperia Play R800X) and none of the phones in the list worked for me...but I did get a nice little interruption from Verizon in my browser about using my phone as a hotspot when I decided to give up and just opened my browser. It would not go away until I rebooted the phone...I'm guessing Verizon doesn't like tethering...lol
Hey whatid,
Thanks for the info. Are you using the unit in North America? If so, you might just want to double check the frequencies on some of the other devices in your house (phone, microwave, etc), as they are often very close to wifi frequencies (~2.4GHz). I know its unlikely to actually happen, but you could get crosstalk.
Also, would you consider starting a new thread with your method of unlocking these channels? I don't mind the info being here in this thread, I was just thinking it might make it easier for other people to find, and it is good info. Plus, the more we pollute the general forum with our TC970 stuff, the more likely they are to finally give us our own forum
Is it possible (or has anyone) to chance the MAC address of the TF300? My tablet has different addresses than the one ASUS has on file (they probably messed it up when I sent it in for RMA)...and they want me to ship it in T_T. Is there a quick fix for this?
tjy8tim said:
Is it possible (or has anyone) to chance the MAC address of the TF300? My tablet has different addresses than the one ASUS has on file (they probably messed it up when I sent it in for RMA)...and they want me to ship it in T_T. Is there a quick fix for this?
Click to expand...
Click to collapse
Offhand I don't know about changing mac although I'm sure it is possible. I googled "android spoof mac address" which I know can work and got lots of hits. Do the same with play google, search "spoof mac address".
Good Luck!
On Nook Tablet we used dd command to write rom partition to computer, edited the mac, serial, etc and dd back to the partition.
MOVED: http://forum.xda-developers.com/android/software-hacking/app-nmac-nil-mac-changer-t3391283
F.A.Q. :
Q: My phone can't connect to any Wi-Fi network after I change my MAC address!
A: Make sure that you haven't changed the first 2 bytes of your original MAC address. Although more than one acceptable combination is available, you will be unable to connect if those 2 bytes are invalid.
Q: I messed up!
A: Restore the backup (original MAC address) by clicking on the button.
Q: I messed up and I deleted the app!
A: Reinstall the app and restore the backup (original MAC address) by clicking on the button. The backup file is saved on your external storage under /.nMAC/ and you may also restore it manually.
Change log:
12 May 2016 - v1.01
Removed arm64-v8a ABI
Faster app startup
Reduced app size
7 May 2016 - Initial release - v1.0
/Reserved
Looks quiet good bro.
You can also add support for a huge range of Samsung devices.
They're storing their mac addresses at <<consored>>
If you want further information just ask.
Updated to v1.01! Change log in 3rd post.
nMAC has officially moved to Android Software Hacking with support for more, non-Nexus devices!
@ViRb3
I need some help please...
In short: before one week my phone stops to connect to my corporate network - didn't wont to obtain IP address. And after several attempt from my side to change login parameters - DHCP, ststic adderss & etc. I decided to change my MAC address with "Change my MAC"... before the change i have created screen-shot with original MAC. But unfortunately the program does not want to revert the address back. I'm stuck on randomly generated MAC from the program. Last ting that I have made i to restore my EFS Backup. Yes, I have received new MAC address but the new address is still not the original one. Also i found that the corporate Cisco router identifies my phone not as a LG Electronic & nexus 5x, but as a Qualcomm device.
After quick research I have found your program but after installation I'm receiving err msg - your device is not supported...
Can you give me advice - how to restore the original MAC address (I have the original one as prtscr), also I have EFS Backup and full factory image backup of my phone that I have made on the day that i have bought the device (but i want to use it as a last resort)...
Thanks in advance.
BR
nunu
dr.nunu said:
@ViRb3
I need some help please...
In short: before one week my phone stops to connect to my corporate network - didn't wont to obtain IP address. And after several attempt from my side to change login parameters - DHCP, ststic adderss & etc. I decided to change my MAC address with "Change my MAC"... before the change i have created screen-shot with original MAC. But unfortunately the program does not want to revert the address back. I'm stuck on randomly generated MAC from the program. Last ting that i have made i to restore my EFS Backup. Yes, I have received new MAC address but the new address is still not the original one. Also i found that the corporate Cisco router identifies my phone not as a LG Electronic & nexus 5x, but as a Qualcomm device.
After quick research I have fount your program but after installation I'm receiving err msg - your device is not supported...
Can you give me advice - how to restore the original MAC address (I have the original one as prtscr), also I have EFS Backup and full factory image backup of my phone that i have made on the day that i have bought the device (but i want to use it as a last resort)...
Thanks in advance.
BR
nunu
Click to expand...
Click to collapse
Don't panic and check PMs
dr.nunu said:
@ViRb3
I need some help please...
In short: before one week my phone stops to connect to my corporate network - didn't wont to obtain IP address. And after several attempt from my side to change login parameters - DHCP, ststic adderss & etc. I decided to change my MAC address with "Change my MAC"... before the change i have created screen-shot with original MAC. But unfortunately the program does not want to revert the address back. I'm stuck on randomly generated MAC from the program. Last ting that I have made i to restore my EFS Backup. Yes, I have received new MAC address but the new address is still not the original one. Also i found that the corporate Cisco router identifies my phone not as a LG Electronic & nexus 5x, but as a Qualcomm device.
After quick research I have found your program but after installation I'm receiving err msg - your device is not supported...
Can you give me advice - how to restore the original MAC address (I have the original one as prtscr), also I have EFS Backup and full factory image backup of my phone that I have made on the day that i have bought the device (but i want to use it as a last resort)...
Thanks in advance.
BR
nunu
Click to expand...
Click to collapse
Just a Short question, die you solve the Problem?
Thargorsson said:
Just a Short question, die you solve the Problem?
Click to expand...
Click to collapse
Yep, ViRb3 was so kind to spend couple of minutes to chat with me and yes... everything is OK now.
BR
nunu