Database Develop

Change MAC address on rooted N1

Hi, does anyone know how to permanently change the MAC address on a rooted Nexus One? Thanks.

Considering the root of this file system is linux, it should be pretty similar to this: http://linuxhelp.blogspot.com/2005/09/how-to-change-mac-address-of-your.html
If at all possible. Obviously, change eth0 to whatever is appropriate. Also, you'll probably have to su to do any of the commands.

Hi, thanks for the reply. I did try that already but after the following command:
ifconfig eth0 hw ether 00:80:48:BA:d1:30
I get this error:
ifconfig: bad address 'hw'
Any ideas?

It worked for me. Before you ran that command did you switch to root user?

Also, this won't permanently change it. It'll only change it for your current boot. If you want it to be permanently done, you'll have to put the command into a init.d script.

So, I have been looking into and testing this some more and I have found something strange. It seems as though something within android keeps reverting my MAC address back to the real MAC address and I am unable to connect to the network I am trying to connect to (it has MAC address filtering). Any thoughts?
And nachod0g in response to your error, double check and make sure that when you type the command "ifconfig -a | grep HWaddr" that eth0 actually comes up. If WiFi is not enabled, this will not work.

Wifi not working after Wpa_supplicant patch

Hello all,
I have a problem. I looked all over and everybody is excited to get their Tab to hook up to Ad Hoc connection. But rarely anybody addresses the issue that follows... It kills regular Wifi!
I cannot connect to any regular wifi now, just my ad hoc connection via my Sprint CDMA Rhodium (touch pro2). I use wifi all the time and running wifi router on my phone all day is not a sensible thing to do.
I tried to put the original wpa file that I had backed up, but still the galaxy cannot connect to regular wifi.
All it says is "connecting" and then "disconnected" and keeps trying to connect to it but never to a point that it says "obtaining ip address"
Please help
Sent from my SPH-P100 using XDA App

try chmod new wpa_supplicant file to 777 had the same issue and solved it with this.

kromosto said:
try chmod new wpa_supplicant file to 777 had the same issue and solved it with this.
Click to expand...
Click to collapse
may sound like a stupid question... but what is chmod?
sorry im pretty good with winmo, but a total noob on android development.

Ok so I downloaded this app called chmod from the market. It's giving me a settings screen with an ability to change numbers and options like read, write, exec...
I feel like this is for the whole system... Not an individual file.
Please help. I really appreciate it! ! !
Thank you
Sent from my SPH-P100 using XDA App

i dont know the app but you can get and terminal app from the market go to the directory you copied the wpa file and write chmod 777 wpa_supplicant and it should be fine you may need su command to get super user access before this command

Did that.
#Su
#Chmod 777 system/bin/wpa_supplicant
Then the terminal registers and goes to next line.
I did reset term, app exited. Wifi doesn't work, ad hoc works
second time I backed out of the app. Still wifi- no, ad hoc-yes
Any clue?
Should I hard Reset?
Sent from my SPH-P100 using XDA App

so you problem is not same as mine. i can tell you what i did exactly maybe it helps.
i didnt use mount commands that wpa-supplicant thread i used androotfile program from the slideme market (normal android market doesnt have this or i couldnt find it) to backup the old one and use it to copy the new one. then got the same problem as you had so go back to old wpa file with again androotfile but still have the same problem. then tried chmod command with the old file and yes it worked (cant remember if i restarted the device) so again copy the new one and chmod it and all started to work.

Actually I just observed that my laptop didn't connect to the internet. So I reset the router and voila! The wifi on my pad works! ! !
All I needed to di was rest the router... stupid me! Didn't think to cover the basics...
And to think, I was soo close to painting a hard reset.. Haha
Thank you so much! ! ! I really appreciate it! !
You are the man!
Sent from my SPH-P100 using XDA App

Hy,
i did everything exactly as described here.
copied new wpa_supplicant to system/bin and thereafter
chmod 777
when i check the permissions with ls -l i can see
wpa_supplicant has following permissions: -rwxrwxrx root root
i can see AD-HOC and "normal" WIFI, but when i want to connect to adhoc, it says: receiving IP Adress, and thats it.
any thoughts?
(i try to connect to my HTC Touch diamond Wm 6.5)
Regards
R

Works like a charm
This fixed my problem getting disconnected from my AP all the time.
Thanks

@kromosto - dude.. THANK YOU! I created an acct on here just to say that. I thought I was in **** water cause my new wpa_supplicant would not work for the life of me, spend hours, and thought the tab was paper weight. Found your post, changed permissions to execute, and I no longer that that 'error' under the Wifi turn-on.
YOU ARE A LIFE SAVER..

armageddon!
Dear All,
I am in the same situation with wpa_supplicant on my brand new Samsung Galaxy S Wifi 5.0, running Froyo, firware: 2.2.2.
I did the following:
1. Download this file: wpa_supplicant
2. Start -> Accessories -> Command Prompt Run as Administrator
3. cd the directory
4. Connect your phone via USB to your computer, then execute the following command:
5. adb shell
6. su
7. mount -o remount,rw -t yaffs2 /dev/block/stl9 /system
8. cp /system/bin/wpa_supplicant /sdcard/wpa_supplicant_ORIGINAL
"/system" is now "rw" mode, original wpa_supplicant is saved.
9. Open another command prompt ( repeat step 2. and 3. ) Then execute the following commands:
10. adb push wpa_supplicant /sdcard/wpa_supplicant
( adb push localfile /remotedir/remotefile )
11. Get back to your other command prompt, and execute the following commands:
12. cp /sdcard/wpa_supplicant /system/bin/wpa_supplicant
13. sync
14. chown root.shell /system/bin/wpa_supplicant
15. chmod 755 /system/bin/wpa_supplicant
16. sync
17. exit
18. exit
So at the moment wifi does not work (ad hoc also, but i do not care) I have the original wpa_supplicant file, but I am too noob to restore it. If someone who already managed to get back wifi working could explain what to do it would be highly appreciated.
Thanks!!!!!!!
cusin

help
nubie said:
Did that.
#Su
#Chmod 777 system/bin/wpa_supplicant
Then the terminal registers and goes to next line.
I did reset term, app exited. Wifi doesn't work, ad hoc works
second time I backed out of the app. Still wifi- no, ad hoc-yes
Any clue?
Should I hard Reset?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Hello,
It's fantastic.. it's long time I'm looking for a way to connect via adhoc and now I see that you have already done and trying to get back to original.
Please let me know how you were able to activate this feature(adhoc) on android.
I'm really stopped!!

Still stuck
I actually didn´t backup my old wpa_supplicant :\\\
Still struggling with this!! Any help?
I´m on a galaxy tab 2 GT-P3110 on android 4.0.4.
Thanks!

[Q] Wifi ad hoc

Hi everybody
I have a little question. I want to connect to a wifi ad hoc network. With my PC everything is ok, but (obviously) my Tattoo can't find the net. I read about modifying two files (tiwlan.ini and another one). But.. How can I do?
I have the original ROM (1.6) rooted and with amon ra recovery.
Thank you
Regards
not development related thread CLOSED ask in the Q & A thread or general section

Have you try to upgrade to Froyo or GingerB ?

mensesneg said:
Have you try to upgrade to Froyo or GingerB ?
Click to expand...
Click to collapse
I'll surely try GingerB as soon as the devs will finish their work on the camera.. what i'd like to know is how can i get and put the files in this location and how should i modify them.
BTW, every Froyo and GingerB ROM can connect to ad hoc wireless networks and send files over bluetooth?
Thank you

solution
The G1 does not connect to ad hoc networks through the wifi manager but we can hack it to allow scanning and connecting to ad hocs. I’ve been trying to figure this out for the longest time. Before you begin, you need to root your G1 and be comfortable using the command line. We will be editing tiwlan.ini and wpa_supplicant.conf. I will be showing you 2 ways to edit the files. Using vi and adb.
Settings
edit tiwlan.ini to read:
WiFiAdHoc = 1
dot11DesiredSSID = HydtechAdhoc (or whatever name u want)
dot11DesiredBSSType = 0
edit wpa_supplicant.conf to read:
ctrl_interface=tiwlan0
update_config=1
eapol_version=1
ap_scan=2 (tells wpa_supplicant to scan hidden networks)
network={
ssid=”HydtechAdhoc”
scan_ssid=1 (for APs with multiple SSIDS)
mode=1
key_mgmt=NONE
group=WEP104
auth_alg=SHARED
wep_key0=”MyWepKey” (replace MyWepKey with your key)
}

feversanj said:
I will be showing you 2 ways to edit the files. Using vi and adb.
Click to expand...
Click to collapse
what adb commands should i use? I think that i have to
1) get the files (adb pull /directory_on_phone/tiwlan.ini tiwlan.ini)
2) modify it with notepad
3) set the system dir rw (
Code:
adb shell
$ su
# insmod tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock3 /system
4) push the files on the phone.. but how? with adb push tiwlan.ini /directory_on_phone/tiwlan.ini ? Is this correct or when i type "exit" to come back to dos prompt the phone unmounts the partition?
feversanj said:
network={
ssid=”HydtechAdhoc”
scan_ssid=1 (for APs with multiple SSIDS)
mode=1
key_mgmt=NONE
group=WEP104
auth_alg=SHARED
wep_key0=”MyWepKey” (replace MyWepKey with your key)
}
Click to expand...
Click to collapse
Is this for every ad hoc connection or i have to modify tiwlan.ini and wpa_supplicant.conf every time i change SSID or WEP KEY? what if i want to keep more than one ad hoc network in memory?
Thank you a lot

change my Mac adress

I cant seem to find anything about the sgs 1 and changing its mac adress (permanently/temporarily) ?
Can someone help pleaseeee!!!
Thanks in advance

I dont think we can change the mac address.

can't you spoof it?

I havent heard of this in android yet.
Sent from my GT-I9000 using Tapatalk 2

Mac address is a permanent address hard coded into the phone's hardware, or any wireless device's hardware for that matter.. Each wireless device in the world has its own unique mac address, just as each computer's bios has its own unique code..
You cannot change your device's mac address..

Hi
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)
Code:
http://forum.xda-developers.com/showthread.php?t=1385577

hardrockk said:
Hi
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)
Code:
http://forum.xda-developers.com/showthread.php?t=1385577
Click to expand...
Click to collapse
I started to grant SuperUser rights to my terminal app . After this, i started with the command "busybox iplink show eth0" and received the following error message:
iplink: can't find device "eth0"
Additionally tried the other command (with eth0) and there is the following error message:
ifconfig: SIOCSIFHWADD: No such device
Im using a Samsung I9000 with root access and all root-related apps already have root access all in all.
Even when Im typing ":su" or ":busybox ~", the device means:
sh: :busybox: not found
I don't get it, the terminal can work without these colons but the "eth0" could not be found, too
Any hints/tipps? Would be great, thank you

Wlan0 not eth0 no Ethernet on galaxy s
Sent from my GT-I9000 using xda premium

At first, thanks for the fast reply and I think your right..
..but at least, I already tried "Wlan0"
It seems, that the command (including wlan0) could be executed and I'm also able to display the wlan0 settings by typing: busybox iplink show
All related content is displayed including the "wlan0". The recently added mac-adress is successfully taken at this point (xx:xx:xx~ instead of the original one) and could be displayed there but even when im checking for the MAC adress in my android wlan settings, there is still the old one and my smartphone still connects with the old MAC to my gateway

I'm not sure then sorry will have to see if anyone else knows how
Sent from my GT-I9000 using xda premium

error eth0
eth0 not found in terminal what i should to do ? how to fix this error and ip link not found i know xda devloper in work fine but they have not solution for this...........

flexoduss said:
I cant seem to find anything about the sgs 1 and changing its mac adress (permanently/temporarily) ?
Can someone help pleaseeee!!!
Thanks in advance
Click to expand...
Click to collapse
1. A rooted device
2. Busybox installed </system/xbin>
3. Terminal Emulator
open terminal
type 'su' press Enter
grant super user access
then type 'busybox iplink show wlan0' press Enter
this shows ur current mac address of ur android phone
then type 'busybox ifconfig wlan0 hw ether XX:XX:XX:XX:XX:XX' press Enter
type the desired mac in XX:XX:XX:XX:XX:XX
voila Done!!!

[FIX] Mac address fix (Until new builds are done)

How to fix your MAC address
Info
Currently, all of the mac addresses are something starting with f0.
All the Kindle Fire 2s using CM10.1 now have the same exact MAC address. This can cause some issues and overall, it's better to fix it, even if you don't have 2 Kindle's on the same network.
Hashcode is going to include a fix in the next update, but until then, follow this guide!
Instructions
**You can do this from the desktop script, or by downloading the file to your device (I find it best to open the thread on the Kindle and download it directly that way) and using the terminal emulator to run the follow code**
Kindle
Download this
In the Terminal Emulator, type:
Code:
mount -o remount,rw /system
[*]rm /system/etc/firmware/ti-connectivity/wl1271-nvs.bin
[*]rm /system/bin/fix-mac.sh
Copy that file to /system/bin now either using cp /sdcard/Download/fix-mac.sh /system/bin/fix-mac.sh (or similar terminal command) or using your favorite file explorer (I recommend root explorer)
Code:
chmod 755 /system/bin/fix-mac.sh
[*]reboot
Desktop
Download and run this, seriously, that's it.
This is simply my guide, main credit for the fix goes to Hashcode. I told him about the MAC addresses needing to be fixed, and I helped with getting it fixed, but he did most of what needed to be done.
~Re-Formatted by iytrix

That worked great! Now both my kids KF2s have their own unique MAC addresses and are running perfectly without any conflicts! Awesome.
Thanks a lot fmkilo and Hashcode!

fmkilo said:
How to fix your MAC address
Info
Currently, all of the mac addresses are something starting with f0.
All the Kindle Fire 2s using CM10.1 now have the same exact MAC address. This can cause some issues and overall, it's better to fix it, even if you don't have 2 Kindle's on the same network.
Hashcode is going to include a fix in the next update, but until then, follow this guide!
Instructions
**You can do this from the desktop script, or by downloading the file to your device (I find it best to open the thread on the Kindle and download it directly that way) and using the terminal emulator to run the follow code**
Kindle
Download this
In the Terminal Emulator, type:
Code:
mount -o remount,rw /system
[*]rm /system/etc/firmware/ti-connectivity/wl1271-nvs.bin
[*]rm /system/bin/fix-mac.sh
Copy that file to /system/bin now either using cp /sdcard/Download/fix-mac.sh /system/bin/fix-mac.sh (or similar terminal command) or using your favorite file explorer (I recommend root explorer)
Code:
chmod 755 /system/bin/fix-mac.sh
[*]reboot
Desktop
Download and run this, seriously, that's it.
This is simply my guide, main credit for the fix goes to Hashcode. I told him about the MAC addresses needing to be fixed, and I helped with getting it fixed, but he did most of what needed to be done.
~Re-Formatted by iytrix
Click to expand...
Click to collapse
do you have the desktop script? link is dead....also would you think this is safe to run on the Kindle Fire 2 (non HD) ?

There is no reason to run this anymore.
--
Sent from my mind to your screen.

The only way 2 Kfires would have the same MAC address these days is if the boot0 block was copied from 1 over the other. (The boot0 block contains the device specific MAC, serial # etc).
Sent from my XT926 using Tapatalk 2

Hashcode said:
The only way 2 Kfires would have the same MAC address these days is if the boot0 block was copied from 1 over the other. (The boot0 block contains the device specific MAC, serial # etc).
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Dude. Really wish i could "shadow" you for a week. I've never been able to make the leap from "modder" to dev. I've found so many operate by rote without understanding what is being done.
Fortunately OR unfortunately for me (not sure which sometimes lol) I cant seem to convince myself to DO anything without some understanding of what it is I'm doing.
This was my long was of saying "thanks for the knowledge your smallest answers provide"
--
Sent from my mind to your screen.