Wifi mac address to something like this "00:0A:F5" after pie ota please confirm? - Xiaomi Mi A1 Questions & Answers

Wifi mac address to something like this "00:0A:F5" after pie ota please confirm?
please comfirm does your wifi mac address changed to something like this "00:0A:F5" after pie ota update or not, before update it was something different

Not sure if it was different before the update, but yes it starts with this.
Sent from my Mi A1 using XDA Labs

TrueMS said:
Not sure if it was different before the update, but yes it starts with this.
Sent from my Mi A1 using XDA Labs
Click to expand...
Click to collapse
so that means your's has been also changed, as original mac addresses doesn't start like this before

taran181 said:
so that means your's has been also changed, as original mac addresses doesn't start like this before
Click to expand...
Click to collapse
What is the problem??

taran181 said:
so that means your's has been also changed, as original mac addresses doesn't start like this before
Click to expand...
Click to collapse
NOOOOO!
He sayd that he's not sure about the MAC address before the update
Taran, i just told you the same thing in another thread: mine is the same MAC as it was on Oreo, and starts like 00:0A:F5
Stop nagging!
Thanks

arkadeep2008 said:
What is the problem??
Click to expand...
Click to collapse
wifi mac address and imei shouldn't as they unique and related to your hardware..

jack_21 said:
Taran, i just told you the same thing in another thread: mine is the same MAC as it was on Oreo, and starts like 00:0A:F5
Stop nagging!
Thanks
Click to expand...
Click to collapse
but mine changed after pie, it shouldn't your's must have also been changed u haven't paid attention earlier and how come all of sudden in pie everyone's mac address starts with same initial?

taran181 said:
but mine changed after pie, it shouldn't your's must have also been changed u haven't paid attention earlier and how come all of sudden in pie everyone's mac address starts with same initial?
Click to expand...
Click to collapse
I'm sure about that: my internet router assigns the same static IP on a MacAddress basis.
I have always my IP from Nougat = no one changed my mac address
The initial identifies the Chip manufacturer, so it's normal that is the same

jack_21 said:
I'm sure about that: my internet router assigns the same static IP on a MacAddress basis.
I have always my IP from Nougat = no one changed my mac address
Click to expand...
Click to collapse
and i had enable mac address filtering in router and sudddenly after pie my moble couldn't connect to router then i realized my mac address has been changed and now it starts with 00:0A:F5,, where are you from? may be i flashed netherland's ota through vpn.. that could have changed

I also face same issue after update to pie, my wifi mac address changed but Bluetooth mac address stay same.
So, your original mac address should be 1 increment of Bluetooth mac address e.g "your Bluetooth mac is f4:f5:ab:c6:d5:21, then your original WiFi mac address should be f4:f5:ab:c6:d5:22."
Please everyone check and revert back.

taran181 said:
and i had enable mac address filtering in router and sudddenly after pie my moble couldn't connect to router then i realized my mac address has been changed and now it starts with 00:0A:F5,, where are you from? may be i flashed netherland's ota through vpn.. that could have changed
Click to expand...
Click to collapse
I flashed the same, but there is only one version of the update

infinitygagan said:
I also face same issue after update to pie, my wifi mac address changed but Bluetooth mac address stay same.
So, your original mac address should be 1 increment of Bluetooth mac address e.g "your Bluetooth mac is f4:f5:ab:c6:d5:21, then your original WiFi mac address should be f4:f5:ab:c6:d5:22."
Please everyone check and revert back.
Click to expand...
Click to collapse
yes bluetooth address is same as before like yours

jack_21 said:
I flashed the same, but there is only one version of the update
Click to expand...
Click to collapse
have you compared your bluetooth and wifi mac address are they same just a one number different? So, your original mac address should be 1 increment of Bluetooth mac address e.g "your Bluetooth mac is f4:f5:ab:c6:d5:21, then your original WiFi mac address should be f4:f5:ab:c6:d5:22."

taran181 said:
have you compared your bluetooth and wifi mac address are they same just a one number different? So, your original mac address should be 1 increment of Bluetooth mac address e.g "your Bluetooth mac is f4:f5:ab:c6:d5:21, then your original WiFi mac address should be f4:f5:ab:c6:d5:22."
Click to expand...
Click to collapse
No they are different, but i don't think if they were similiar before the update.

infinitygagan said:
I also face same issue after update to pie, my wifi mac address changed but Bluetooth mac address stay same.
So, your original mac address should be 1 increment of Bluetooth mac address e.g "your Bluetooth mac is f4:f5:ab:c6:d5:21, then your original WiFi mac address should be f4:f5:ab:c6:d5:22."
Please everyone check and revert back.
Click to expand...
Click to collapse
That's not strictly true, I'm still on 8.1 and mine differ as follows (all "X" identical)
XX:XX:XX:3b:XX:XX
XX:XX:XX:7b:XX:XX
The difference is not necessarily one increment at the end.

taran181 said:
please comfirm does your wifi mac address changed to something like this "00:0A:F5" after pie ota update or not, before update it was something different
Click to expand...
Click to collapse
yes indeed, my phone's mac starts from 00:0A: same as yours,
i have set static ip for my phone in router settings for old mac, so surely something is wrong

iammilind said:
yes indeed, my phone's mac starts from 00:0A: same as yours,
i have set static ip for my phone in router settings for old mac, so surely something is wrong
Click to expand...
Click to collapse
i think so it can be fixed by software update.. rest we will for official fastboot rom,,

lets hope for best, this shouldn't have happened in first place.

iammilind said:
lets hope for best, this shouldn't have happened in first place.
Click to expand...
Click to collapse
i know xiaomi developers have always been providing buggy updates to mi a1

kudos1uk said:
That's not strictly true, I'm still on 8.1 and mine differ as follows (all "X" identical)
XX:XX:XX:3b:XX:XX
XX:XX:XX:7b:XX:XX
The difference is not necessarily one increment at the end.
Click to expand...
Click to collapse
My point here is that mac address of Bluetooth and WiFi is similar not completely different.

Related

2 HD2's kicking each other off WiFi.

WiFi works perfectly fine until we are both using it on our hd2's. It seems our phones keep kicking each other off. We don't have this problem while in Windows though. We have different Android versions also. Hers is darkstones and mine is subtract. Don't think that matters though. Must have something to do with the network names or something like that confusing the router. Any ideas?
Sent from my HTC HD2 using XDA App
carhigh said:
WiFi works perfectly fine until we are both using it on our hd2's. It seems our phones keep kicking each other off. We don't have this problem while in Windows though. We have different Android versions also. Hers is darkstones and mine is subtract. Don't think that matters though. Must have something to do with the network names or something like that confusing the router. Any ideas?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I think it's because most (all?) the builds have the same MAC address.
if you are using the same builds it will be because of the mac address being the same as mentioned above, if you look it will probalby be something like 11:22:33:44:55 on each hd2
i know the desire hd build uses a different mac address
Most of the Desire/N1 based kernels use the MAC address 00:11:22:33:44:55, so to the router, both of your HD2s will appear to be the same device.
I had this issue, so changed the kernel on my HD2 to hastarin #4.1 which is an Evo-based kernel which uses the device's real MAC address, so they appear correctly as different devices.
CRAP !!!!! is there any way to change one of these? If not, I guess o have to go research what to replace one of them with, which sux
Sent from my HTC HD2 using XDA App
jamesjf said:
Most of the Desire/N1 based kernels use the MAC address 00:11:22:33:44:55, so to the router, both of your HD2s will appear to be the same device.
I had this issue, so changed the kernel on my HD2 to hastarin #4.1 which is an Evo-based kernel which uses the device's real MAC address, so they appear correctly as different devices.
Click to expand...
Click to collapse
ok just installed that on my shubCRAFT 1.5 and it solved the issue with mac address Thanks for the tip
Its a little confusing which will work with what.
Takes a while to pick up service though.
Dam, after reboot wifi error. It was just working, wtf
Ok thats crap. I install the new modules, and wifi works fine, on and off, but after i reboot the phone, wifi error.
Any other way to get different mac on each phone? or atleast one, with everything working normaly as it is now with both builds in use?
OK, i had to install some app and run a script and seems to be all good
jamesjf said:
Most of the Desire/N1 based kernels use the MAC address 00:11:22:33:44:55, so to the router, both of your HD2s will appear to be the same device.
I had this issue, so changed the kernel on my HD2 to hastarin #4.1 which is an Evo-based kernel which uses the device's real MAC address, so they appear correctly as different devices.
Click to expand...
Click to collapse
Just tried to put the same setup on the wifes phone with hastarin #5 and both had same mac again. I guess it really doesnt use the real mac address, just a different one than most of the other kernals
Maybe if you assign a static ip adress to each of your phones in your routers address range (in the phones wireless advanced menu) it will stop your router trying to assign an address. Also your router may have an option to turn off mac adress filtering.
LondonTownGuy said:
Maybe if you assign a static ip adress to each of your phones in your routers address range (in the phones wireless advanced menu) it will stop your router trying to assign an address. Also your router may have an option to turn off mac adress filtering.
Click to expand...
Click to collapse
ip address is different from a mac address, he will still have a problem connecting both hd2s. and that's not how mac address filtering works. will still have a conflict
Is there a fix for this yet? Does any Android build read the wifi MAC address correclty from the HD2?
The only fix so far is run different kernels. That's what I've been doing.
wineds said:
Is there a fix for this yet? Does any Android build read the wifi MAC address correclty from the HD2?
Click to expand...
Click to collapse
Sent from my HTC HD2 using Tapatalk
wineds said:
Is there a fix for this yet? Does any Android build read the wifi MAC address correclty from the HD2?
Click to expand...
Click to collapse
See this post if you want 2 of the same kernels with 2 different mac address. They are hard coded in, but its the best solution for now, for running 2 of the same sets on the same kernels.
Thanks to member wayubi for his help with this, and a partial solution
http://forum.xda-developers.com/showpost.php?p=8455440&postcount=7397

[Q] XBMOD Mango WIFI [email protected] Problem

After a reboot, the wifi mac address change, is there a problem with the wifi?
axl59 said:
After a reboot, the wifi mac address change, is there a problem with the wifi?
Click to expand...
Click to collapse
Yes, I noticed this one too..
I have a MAC address filtering on my router and workaround is to change the mac address after the reboot.
I'd think this is a defect? Is there a fix to this yet?
gasanpride said:
Yes, I noticed this one too..
I have a MAC address filtering on my router and workaround is to change the mac address after the reboot.
I'd think this is a defect? Is there a fix to this yet?
Click to expand...
Click to collapse
It's a known problem, waiting for fix see http://forum.xda-developers.com/showthread.php?t=1264618

Does anyone have a proper workaround for the obtaining IP address?

Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?
This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?
C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7
Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).
I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.
Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?
Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence
First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app
bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.
strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.
Bump.
Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app
Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.
Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!
its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know
bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).

MAC Adress Changing everything?

I control at home the internet and wlan connetivity with the mac adress each user in my router.
The elephone s7 change everythin these mac adress when Phone new starting.
It is untypical and i not known.
I can't root to give a new or control the mac adress.
What can i do community?
Nice Christmas, Sören.
I noticed, there is no restart of the phone necessary. The MAC address changes everytime I switch of and on the wifi connection
sebi-hd2 said:
I noticed, there is no restart of the phone necessary. The MAC address changes everytime I switch of and on the wifi connection
Click to expand...
Click to collapse
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
Idakis said:
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
Click to expand...
Click to collapse
Can you make a post on how to do this with sn_writer and the files/links you used for the s7.
I doubt elephone will ever officially fix this, so a separate post will be great
FunkiBluDawg said:
Can you make a post on how to do this with sn_writer and the files/links you used for the s7.
I doubt elephone will ever officially fix this, so a separate post will be great
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/elephone-s7/how-to/elephone-s7-fix-changing-wifi-mac-adress-t3527478
Elephone won't fix that one I am sure. Maybe they will program a MAC in later badges.
Hello,
My Wifi tethering doesn't work ... when I'm putting on the wifi tethering, the other device connected on haven't Internet.
Could this Mac Adress be the problem ? or it's other one ?
Thx
I have the same problem at my place of work network. I have to keep adding different Mac addresses into the router.. I did log this bug with elephone, but surprise surprise nothing has been done to fix it
Wifi tethering works here. As for MAC address look at my post I linked before and follow that guide.
I wouldn't count on a official fix for already delivered phones. Maybe newer badges won't have the problem but as verified it is fixable.
Cheers
This works for me. Thanks a lot!

Unable to access internal network locations

Hi, wonder if anyone can give me any pointers on this one? Not certain it's a device issue, but it's only my 6p having the problem, so it's where I'm currently looking for the fix...
I'm currently unable to access locations on my internal network - eg, if I use ES File Explorer, I can usually connect to my file server, no problem. However this is no longer working. I get an error saying 'server not found'
Nor can I access any internal web pages (eg the admin pages for my servers), and even Plex can't create a direct connection - only an indirect one.
The only connection I can make internally is the router admin page - and any page where I have port forwarding and access via a host name.
My other devices - both wired & wireless, on the same SSID, have no issues at all.
These issues seem to have coincided with the update to 7.1.2 - perhaps a coincidence, but seems to be linked.
I've tried re-installing ES File Explorer, and I've used the 'Network Settings Reset' option - neither of these helped.
I'm not using anything fancy like a VPN - the router is the bog-standard ISP provided one with a few port-forwarding rules - I've looked through the settings and can't see anything that might be blocking it.
Any suggestions welcome!
Well, not sure what the actual issue was, but in the end I forced the router to give out a new IP address to the phone, and voila - worked!
I'd infer some sort of IP address conflict, but don't even have that many devices on DHCP, so not entirely sure.
aldredd said:
Well, not sure what the actual issue was, but in the end I forced the router to give out a new IP address to the phone, and voila - worked!
I'd infer some sort of IP address conflict, but don't even have that many devices on DHCP, so not entirely sure.
Click to expand...
Click to collapse
What was the actual problem? I read through it and don't even get what the problem was really.
DEVILOPS 007 said:
What was the actual problem? I read through it and don't even get what the problem was really.
Click to expand...
Click to collapse
aldredd said:
I'd infer some sort of IP address conflict, but don't even have that many devices on DHCP, so not entirely sure.
Click to expand...
Click to collapse
Hey,
Looks like he doesn't know either.
Cheers...
DEVILOPS 007 said:
What was the actual problem? I read through it and don't even get what the problem was really.
Click to expand...
Click to collapse
The issue was that my phone couldn't access any internal network resources...
I'm currently unable to access locations on my internal network
Click to expand...
Click to collapse
Given it was only this device having the issue, and the timing lined up with the 7.1.2 update, I suspected it was an issue relating to that update.
In the end, releasing the IP address and having a new one issued resolved it, which is why I inferred an IP address conflict.
5.1 said:
Hey,
Looks like he doesn't know either.
Cheers...
Click to expand...
Click to collapse
I knew what issue I was facing - just not entirely sure what caused it.
But thanks for your input.
aldredd said:
The issue was that my phone couldn't access any internal network resources...
Given it was only this device having the issue, and the timing lined up with the 7.1.2 update, I suspected it was an issue relating to that update.
In the end, releasing the IP address and having a new one issued resolved it, which is why I inferred an IP address conflict.
Click to expand...
Click to collapse
By internal network problem does that mean you had no issue connecting to WiFi with your phone and doing stuff like browsing the Internet?
DEVILOPS 007 said:
By internal network problem does that mean you had no issue connecting to WiFi with your phone and doing stuff like browsing the Internet?
Click to expand...
Click to collapse
Correct - browsing the internet, using apps etc - absolutely fine. Just nothing internal. So even PLEX would use an indirect connection rather than a direct one.
I'd restarted the phone several times, used the 'reset network services' option setting, but even after that the router was issuing the same ip address to the device. That's when I began getting suspicious that it was linked to the IP address. So changed the DHCP range to exclude the IP address it was giving out, restarted the router, and that sorted it.

Categories

Resources