Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Alpaca_Bandit said:
Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Click to expand...
Click to collapse
As you said, ifconfig changes it, there are several apps that do it for you as well, chainfire also released a mac randomizer app. You also noted it's hardwired in, so i would just have a startup script that changes it if i were you, there night be a better way to do it though.
Sent from my Tw5ted SM-G900A using Tapatalk
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Alpaca_Bandit said:
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Click to expand...
Click to collapse
You can just use init.d to make the script, shell scripting isnt very hard and i won't give you a tutorial here. Also as noted many places when researchng changing a mac on android, you can't connect to secured APs, or it won't be easy at least. As i said before, there may be a better way to do this, but i do not know it.
Sent from my Tw5ted SM-G900A using Tapatalk
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Alpaca_Bandit said:
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Click to expand...
Click to collapse
I know on for example ddwrr and even some official router firmwares they allow you to spoof your mac, may be worth looking into how they do it, but i have a suspicion it might be done with a script.
Sent from my Tw5ted SM-G900A using Tapatalk
Hard Wired?
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
MAC for bt and wifi reside in the EEPROM or NVRAM. And that is not editable.
To put it simply you can't change it. Only spoof it. And if you know it's not legal you probably shouldn't be asking.
Reported Is different from original
gscripting said:
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
Click to expand...
Click to collapse
More info relative to these 2 phones
I installed an app called Change my Mac.
It Lists:
Original MAC 12:34:56:78:90:ab
Current MAC ff:ee:dd:cc:bb:aa
They Are Different.
I thought the original MAC address it's showing, was the one written in the EEPROM or NVRAM,
but it turns out, after installing Change My MAC on the other phone also, its lists the same Original and Current MAC addresses as the first phone.
The Current MAC address listed is the one reported in settings and my network.
I Use Change My MAC to set the reported MAC to the original every time the phone boots using Tasker on only one of them.
Using Change My MAC, the change lasts til boot.
Just passing it on for those that might be interested.
When I get link privileges, I'll add a screenshot of Change My MAC.
gscripting
Related
A brief history of what I've been through before this issue:
My Pro came with 2.2 Froyo from verizon, then flashed Vanilla's CM7 v8 (which is the absolute best ROM I've tested for this phone); no wifi mac address problem here. Then I messed up by installing another recovery, semi-bricked, and forced to SBF to stock Verizon 2.3.3 gingerbread. Then rooted with Pete's Motorola Root Tools, flashed recovery, kernel, wiped, and once again to Vanilla's CM7 v8.
After all this mess, my Wi-Fi MAC address is changing every time wifi goes off/on or reboot, and this is pretty inconvinient for me since both my workplace and home networks have MAC address filter, and changing the router configuration every time I'm forced to reboot my phone is not an option.
YES, I've flashed the Kernel that the developer provides with the ROM.
YES, I've tried reflashing both the rom and the kernel the way the diveloper suggests, doing system/data/cache wipes in between.
NO, this was not happening the first time I've flashed this ROM.
Any suggestions?
Please help!!
SOLVED READ BELOW!
Fix found
Here's the MAC address fix for your Pros running CM7. If you have had an issue connecting to wifi, it's probably because each time the device's wifi is restarted, a new MAC address is generated which will clog up your router as you can easily run out of IP addresses to lease to each and every new MAC address that's generated each time your device's wifi is restarted. The link can be downloaded here. The instructions are simple:
1. Flash CM7MAC.zip (attached) in clockwork no need to wipe anything
2. "Activate it" by going into the terminal emulator app, typing "su" (without the quotes) then typing "mac-address-fix.sh" (without the quotes). A bunch of weird symbols should come up, but that's normal.
What this does is it auto-generates and writes your permanent MAC address to a file called called nvs_map.bin under /data/misc/wifi/nvs_map.bin. It will remain there and your MAC address will remain the same unless you wipe your /data whereas you will simply have to redo it
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
For CM7, download -->
hi!
my phone does the same, each time WIFI is turned on it generates a temporary MAC address, but the file you mentioned (nvs_map.bin) can't be found in /data/misc/wifi...
could you help me please how the map_gen file is generated? i don't have CWM so i can't flash the zip file, but i have a terminal and two hands
thx
Do we have anything for Android 4.2?
negro_acdc said:
Here's the MAC address fix for your Pros running CM7. If you have had an issue connecting to wifi, it's probably because each time the device's wifi is restarted, a new MAC address is generated which will clog up your router as you can easily run out of IP addresses to lease to each and every new MAC address that's generated each time your device's wifi is restarted. The link can be downloaded here. The instructions are simple:
1. Flash CM7MAC.zip (attached) in clockwork no need to wipe anything
2. "Activate it" by going into the terminal emulator app, typing "su" (without the quotes) then typing "mac-address-fix.sh" (without the quotes). A bunch of weird symbols should come up, but that's normal.
What this does is it auto-generates and writes your permanent MAC address to a file called called nvs_map.bin under /data/misc/wifi/nvs_map.bin. It will remain there and your MAC address will remain the same unless you wipe your /data whereas you will simply have to redo it
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
For CM7, download -->
Click to expand...
Click to collapse
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
** How can I turn on Wi-Fi when there's no mac-address? No mac-address, no network! **
Hi,
I tried running this shell script but seems like its not executed successfully ... reason i believe so is ...
1. i dont see any wierd symbols coming up ... just a pause for a couple of seconds.
2. i dont see the "/data/misc/wifi/nvs_map.bin' file in the said location.
Please help.
thnx
Mac addrs and imei problm
Hi, in my gionee ctrl v4s the problem is two types, i have seen after i was updated lollipop , one problem is tht, whn i reboot my phn thn my mac address automatically changed everytime.. And 2nt problem is tht my imei also erased whn i updated lollipop so plz help me...
this is the best solution
https://www.youtube.com/watch?v=8ejnFB5i5o8
Is there a solution for this in Marshmallow?
yes this is the best solution
Thanks. This process worked well on my lenovo s650 cyanogenmod 13 custom rom. But could someone explain what is really happening through this solution?
my oppo f1s 64gb, it was dead, recovered working fine, but each restart it changes mac id, and remove all wifi stored connections
is there any solutions?
Seems its pretty common for MediaTek chipsets.
Thanks for the video link!
Hey everyone,
I rooted my NST Glow for the first time about a month ago and I was an idiot and didn't take a back up first. In the process I managed to totally mess it up. It got so bad that it was bricked and wouldn't boot no matter what I tried. Eventually I decided to try taking a backup of my wife's NST with glow and restored that to my Nook. That worked and allowed me to do a wipe, then root it properly etc. So everything was working and seemed good to go.
Today I was rooting my wife's nook and in the process put it online. At some point it said that there was an authentication error and it rebooted the nook and wiped it to factory.
I restored her nook from the fresh backup I took and it is back up and running, however it is unrooted and offline. My guess is that I cloned her nook's ID to mine when I restored from her backup and now B&N thinks that our nooks are the same device and registered to two different accounts. Thus anytime hers gets online it will get wiped.
Is there any way to reset my Nook's device ID or w/e so that it is unique again? How do I fix this problem?
And yes I learned my lesson and take backups regularly now.
unfortunately mate , we dont have any method to recover thr Rom partition that have ur unique files like nooks ID and MAc address and serial and etc , so i think if u dont have any chance to find an backup for ur device , then noway mate
but , u can use one device for online purpose and other offline always and for ever until u got recover ur original Rom partition
sry for ur loss mate , but try to remember that u take backup or anything or ur nook just will be used offline only
good luck
speedman2202 said:
unfortunately mate , we dont have any method to recover thr Rom partition that have ur unique files like nooks ID and MAc address and serial and etc , so i think if u dont have any chance to find an backup for ur device , then noway mate
but , u can use one device for online purpose and other offline always and for ever until u got recover ur original Rom partition
sry for ur loss mate , but try to remember that u take backup or anything or ur nook just will be used offline only
good luck
Click to expand...
Click to collapse
You could always try using Noogie to get at the rom partition - the S/N and MAC address are just text files
down in the devconf subdirectory on the rom partition. Nothing special, except no line termination.
If I were doing this from linux/Ubunto, I would try something like this after booting Noogie and attaching the
nook to my laptop, and assuming that Ubuntu mounted the Noogie-presented rom partition as /media/ROM:
echo -n "XXXXXXXXX" > /media/ROM/devconf/SerialNumber
echo -n "XXXXXXXXX" > /media/ROM/devconf/DeviceID
echo -n "58611Axxxxxx" > /media/ROM/devconf/MACAddress
If you log into your account on www.bn.com, go to manage your Nook, and put the pointer over the nook in
question, it will show you the S/N registered to that particular device associated with your account.
Of course, you say that you re-registered the nook, but if you're lucky, it will show up as a different device
under the management window(since it probably presented a different S/N from the original). Just ignore
the device with the S/N that matches what's in your cloned ROM(that S/N belongs to your wife). Hopefully
the original is still showing up as another Nook, which will have your original S/N. Put that into the
SerialNumber and DeviceID files.
As far as the MAC address, other than the 58611A prefix, which you need to leave the same(it's the manufacturer
code), pick a different series of six hexadecimal digits that are different from what you already have.
The MAC address only needs to be different from any other device attached to the same WiFi router.
If you pick something at random, you know it'll be different from your wifes Nook, and you've got a good
chance that you won't match anybody else that you're sharing a Wifi router with(at home, or the BN store, etc).
They must be 6 hexadecimal digits, and I would keep any alpha characters uppercase. Or you could just
pick 010101
What do you have to lose? I'm just guessing that this will work, but at this point what other options do you
have?
PS: If you do try this, please keep us updated.
Sure you can fix the serial number and mac address but you can't recover the public key and private key hash you need to authenticate with B & N. Fixing the serial number and mac address will keep you from messing up your wife's B&N authentication and allow you both to be on the same WiFi access point at the same time. But its unlikely you'll get B&N Authentication to work with the native NST apps. But you might be able to install the Nook app from the Market and use that to read your B&N books.
straygecko said:
Sure you can fix the serial number and mac address but you can't recover the public key and private key hash you need to authenticate with B & N. Fixing the serial number and mac address will keep you from messing up your wife's B&N authentication and allow you both to be on the same WiFi access point at the same time. But its unlikely you'll get B&N Authentication to work with the native NST apps. But you might be able to install the Nook app from the Market and use that to read your B&N books.
Click to expand...
Click to collapse
So this has already been tried, and it's known that the public/private key is used
to identify the specific Nook(not simply used for comm encryption to the BN server)?
If it were being used to identify the Nook shouldn't there have to be a full private key
half, as opposed to simply the hash? The only full "piece" of a key that I see is
the public half of the key, which you wouldn't normally use to specifically identify a
device.
Even then, even if it's a device identifier rather than a pre-loaded SSL or comm pubkey
for connecting securely to the Nook server(s), do we know that B&N has matched that
key to the device S/N, and keeps that matchup in a DB somewhere?
If not, then it should be possible to create a new key. You may lose the original registration
info, but re-registering should be possible.
Has anybody actually tried this yet?
...
Hmm, I just diff'ed the Pubkey in the rom backups for my NST and NST Glow, and
they're different, which doesn't make sense if it's an SSL/Comm pubkey being
used to connect to the same B&N server(s).
Thanks for the responses guys. It looks like I have made an erroneous assumption. I stumbled across this thread which says that the Nook Color Tools causes the factory reset, and that is exactly what I was doing when her nook reset on me.
I assumed that it was because I put the nook online for the first time since restoring mine with her image and B&N detected that they had the same ID or something.
When I get a chance this week I will check the serials and stuff in the ROM partition on both the nooks and see if they are the same or if mine is still unique from hers. The B&N website is only showing one nook under my account but says it was registered Sept 2, 2012 (long before I rooted it) and it lists a serial number there, so I am hopeful that my nook is still unique, and if not I may play with it and see if I can return it to the original serial. If I lose the ability to sync to B&N that isn't a big deal since I only have one book on my account (I sideload all my books through Calibre).
I'll let y'all know what I find out.
Here's a Nook Tablet users experience with restoring the serial number and mac address. Bottom line is he couldn't authenticate with B&N after restoring the serial and mac. He ended up lucky and got B&N to replace it under warranty.
serial number can found in the NST original Box , or u can found it when u look in memory card slot
for Mac address , i dont know how , but u can use cheat one , for how to edit , add this info to Rom partition , i dont know
good luck
You can follow that: http://forum.xda-developers.com/showthread.php?t=2104145
I faced a same situation and now my nook become normal :victory:
thanmeo78 said:
You can follow that: http://forum.xda-developers.com/showthread.php?t=2104145
I faced a same situation and now my nook become normal :victory:
Click to expand...
Click to collapse
That thread tells you how to save your ROM partition before overwriting it with a backup from a different Nook and then replacing the ROM partition with your backup. Unfortunately, it appears the OP had already restored a backup of another Nook before saving his ROM partition so the procedure on that thread is unlikely to do any good at this point.
Yah, unfortunately I did not back up my own ROM partition before writing a new one. I tried putting in my serial and changing the MAC address, but as in the other thread I could not register with B&N as I'm assuming the private keys don't match my serial (as they came from my wife's nook). So unless someone figures out how to recover or generate a new private/public key pair that will work with B&N's servers, I'm stuck with a cloned nook.
It's ok though because I side load all of my books and don't need to have it online or anything. So, it is working just fine for my purposes at this point.
Hello Guys, Before flashing we all have our unique mac address in our phone. But after flashing roms, it changed sometimes.
I flashed cm 14.1 and it changed to something weird like 02:00:00... . After many trials i didnt restored to my original one
Problem is , after flashing the cm14.11 rom, when phone first boot-up, it offers us to set it for the first time, there we have to set many things like, language setting/screen pattern/fingerprint/google login/wifi login/sim card select etc.
While setting up these things, when i was connecting to my wifi, i see my mac address was original and everything goes normal. after phone boots-up, i install many apps (as per my requirements). Later, after few hours, when something came up in my mind, i see the status of my phone and there the mac address was weird like 02:00:...
so, i google it to restore my original mac address. I found a method toFix the Wifi issue where it says :-
1) using /persist directory, normally you should see a file named “wlan_mac.bin”, open it with text editor you can see four lines of MAC address, but with the “No Wi-Fi with 02:00:00:...” problem, you can’t see that “wlan_mac.bin” file.
2) Located to another directory “/etc/firmware/wlan/qca_cld”, you should see the “wlan_mac.bin” file now, tap and edit that file, it should be nothing in it.
3) Add your Wi-Fi MAC address to wlan_mac.bin with these format:
Intf0MacAddress=Your Wi-FI MAC address without “:”
Intf1MacAddress=00AA00BB00C2
Intf2MacAddress=00AA00BB00C3
Intf3MacAddress=00AA00BB00C4
4) Save the file and reboot your phone, your phone’s Wi-Fi problem should be fixed.
But what i found on my phone amazes me the most, which is in my both DIRECTORIES (/persist and /etc/firmware/), the mac address written there consists of all 4 lines with my original mac address!
so, if these 2 files located in different directories have same wifi mac address (of 4 lines), then why it is showing me 02:00:00... in settings>status ????
now, guys if you understand my problem, kindly tell the any possible way to restore the mac address in settings to (except saying to reflash the rom clean).
Thanks.
Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.
lalontra said:
Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.
Click to expand...
Click to collapse
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.
DEVILOPS 007 said:
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.
Click to expand...
Click to collapse
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.
lalontra said:
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.
Click to expand...
Click to collapse
Have you tried forgetting your WiFi network and connecting again with the psk?
DEVILOPS 007 said:
Have you tried forgetting your WiFi network and connecting again with the psk?
Click to expand...
Click to collapse
If I hit known network in android wifi options I can see all my previously stored wifi. Everything works perfectly. If I add new networks they will be added with no issues and remembered for ever and ever. (and obviously will not be added to the file). It is like this list is just somewhere else now on the phone.
I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.
Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043
dechronic said:
I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.
Click to expand...
Click to collapse
I have created an app that supports both devices below and over the android Orio, give it a try from this thread -
https://forum.xda-developers.com/android/apps-games/app-wifi-password-view-saved-wifi-t3852668
Hotfingers said:
Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043
Click to expand...
Click to collapse
Great App!
They are now stored in:
/data/misc/wifi/WifiConfigStore.xml
OK, so I had a good idea, and did it badly...
I have a many-years old Nook Simple Touch (NST1 hereafter), which I had partitioned for more space to sideload. I decided a while back to simply load everything on a micro-SD card, which I did. I started having issues with NST1, so I purchased another (refurbed) Nook Simple Touch (NST2 hereatfer). I started looking for the info to undo the partitioning change, and came across info to backup and restore that involved deleting the partitions, and thus the restore process would rewrite them.
AH HAH! So, I figured I could backup the NST2, which was fresh, and restore it to NST1. Worked like a charm, too.
Now we come to the problem... It also overwrote both the serial number, which I have no way to get back that I can find, and overwrote the MAC address of NST1. The original MAC address I do have, if I knew where to put it. And, if there's a way to find the original serial number, that too would be good to put back.
So, there you have it. Anybody got any ideas? I'm sure someone, probably many someones here, know where this data is recorded on the NST, and the easiest way to modify the data so it reflects the original information. I'm also hoping that someone can give me ideas on how to find the original serial number again. (Yes, I know it is written on the case where the micro-SD card goes in, but over the years that has become mostly unreadable, so that's out.)
Thanks muchly for any help you can offer,
MildBill
MildBill said:
OK, so I had a good idea, and did it badly...
I have a many-years old Nook Simple Touch (NST1 hereafter), which I had partitioned for more space to sideload. I decided a while back to simply load everything on a micro-SD card, which I did. I started having issues with NST1, so I purchased another (refurbed) Nook Simple Touch (NST2 hereatfer). I started looking for the info to undo the partitioning change, and came across info to backup and restore that involved deleting the partitions, and thus the restore process would rewrite them.
AH HAH! So, I figured I could backup the NST2, which was fresh, and restore it to NST1. Worked like a charm, too.
Now we come to the problem... It also overwrote both the serial number, which I have no way to get back that I can find, and overwrote the MAC address of NST1. The original MAC address I do have, if I knew where to put it. And, if there's a way to find the original serial number, that too would be good to put back.
So, there you have it. Anybody got any ideas? I'm sure someone, probably many someones here, know where this data is recorded on the NST, and the easiest way to modify the data so it reflects the original information. I'm also hoping that someone can give me ideas on how to find the original serial number again. (Yes, I know it is written on the case where the micro-SD card goes in, but over the years that has become mostly unreadable, so that's out.)
Thanks muchly for any help you can offer,
MildBill
Click to expand...
Click to collapse
You can find the serial number on the edge of the NST, hidden behind the SD card "door".
As to the rest, you may be SOL. There are places on the device where the S/N and MAC address are stored as strings, but I think the actual information is stored more deeply and may be encrypted with keys. Still, can't hurt to scour the forum. I could be wrong.
nmyshkin said:
You can find the serial number on the edge of the NST, hidden behind the SD card "door".
Click to expand...
Click to collapse
As I stated in the OP, that data is no longer readable, after many years of use. I have the MAC address (did you *read* the post??) I need to know where to put it!
MildBill said:
As I stated in the OP, that data is no longer readable, after many years of use. I have the MAC address (did you *read* the post??) I need to know where to put it!
Click to expand...
Click to collapse
Yeah, I missed that last part. Search on "serial number" and you'll find a dev discussion about this. Unless you have a copy of the original ROM partition I don't think you can do anything.
nmyshkin said:
Yeah, I missed that last part. Search on "serial number" and you'll find a dev discussion about this. Unless you have a copy of the original ROM partition I don't think you can do anything.
Click to expand...
Click to collapse
Surely there is some way to insert/change the existing data to reflect the original. And, no, sadly, stupidly, I did not back up that data, I had forgotten it was coded in flash, and knew I was going to overwrite the entire device.
It's been a while since I worked on NSTs.
On the iMX6 (Glows), the serial number is in two places:
In mmcblk0 at offset 200 it says "SN-12345667890123456", I believe purely as informational.
In mmcblk0 at offset 80400 is an XML structure with the SN used by Android.
On the OMAP3 (NST), the serial number is in two places:
/rom/devconf/DeviceID (16 bytes ASCII)
/rom/devconf/SerialNumber (16 bytes ASCII)
/rom is normally mounted r/w so you can just write these and reboot.
Renate NST said:
It's been a while since I worked on NSTs.
On the OMAP3 (NST), the serial number is in two places:
/rom/devconf/DeviceID (16 bytes ASCII)
/rom/devconf/SerialNumber (16 bytes ASCII)
/rom is normally mounted r/w so you can just write these and reboot.
Click to expand...
Click to collapse
Bless you Renate, I knew you would know! How about the location of the MAC address?? This appears to also be software coded somewhere, as when I was finished with the process outlined above, both devices have the same MAC address.
MildBill said:
How about the location of the MAC address?
Click to expand...
Click to collapse
Code:
# cd /rom/devconf
# echo -n 1234567890123456 > DeviceID
# echo -n 1234567890123456 > SerialNumber
# echo -n 123456789012 > MACAddress
Renate NST said:
Code:
# cd /rom/devconf
# echo -n 1234567890123456 > DeviceID
# echo -n 1234567890123456 > SerialNumber
# echo -n 123456789012 > MACAddress
Click to expand...
Click to collapse
Renate,
Yes, I have successfully deciphered (mostly) the serial number/device ID printed on the case near the micro-SD slot. I had to guess a couple of numbers but I think I got them right.
And, I saw the MAC address file as pointed out, BUT, I changed that as well, maintaining the format involved, and when restarted the device info said 'Unavailable' for the MAC address, until I turned WiFi on, and then that reverted to the wrong address, as written from the other device. I'm assuming that there is some other place where it is stored in some form. Any ideas on that?
MildBill
P.S. Actually, I edited the files with a Windows editor, the serial/device ID change worked fine as far as I can see.
P.P.S. On further check, while the Device Info:About Your Nook shows the 'cloned' MAC address after turning WiFi on, the MAC Address file still reflects the original address (obtained from a separate source from prior to the whole business.
Read this thread
https://forum.xda-developers.com/showthread.php?t=1480974
Yeah, the initialization of the WiFi adapter is in /rom/devconf/WiFiBackupCalibration.
It's a series of register addresses/counts and data.
The MAC is in reverse order in hex, not ASCII.
Code:
0x00 - 0x01
0x01 - 0x6d
0x02 - 0x54
0x03 - 6th byte MAC
0x04 - 5th byte MAC
0x05 - 4th byte MAC
0x06 - 3rd byte MAC
0x07 - 0x01
0x08 - 0x71
0x09 - 0x54
0x0a - 2nd byte MAC
0x0b - 1st byte MAC
OK, I have decided to change directions...
After getting all the data changed, I tried to erase and deregister, then register again, and it gives me errors.
All the data, by the way, as well as the Main Board SN are on a sticker ON the motherboard, so I know I got them right. There are, however other bits of data not there, which no doubt need to all match up, and don't. So, I have decided this can be a test device for some of the various rooted ROMs, and other goodies out there, to see if any of them are worthwhile to use. If not, I will simple restore the NST2 backup to it, and simply make sure I don't have both of them powered up and online at the same time.
Thanks to all for trying to help, even if it didn't work out. The new (to me) device will last me for many more years I'm sure.
MildBill
MildBill said:
OK, I have decided to change directions...
After getting all the data changed, I tried to erase and deregister, then register again, and it gives me errors.
All the data, by the way, as well as the Main Board SN are on a sticker ON the motherboard, so I know I got them right. There are, however other bits of data not there, which no doubt need to all match up, and don't. So, I have decided this can be a test device for some of the various rooted ROMs, and other goodies out there, to see if any of them are worthwhile to use. If not, I will simple restore the NST2 backup to it, and simply make sure I don't have both of them powered up and online at the same time.
Thanks to all for trying to help, even if it didn't work out. The new (to me) device will last me for many more years I'm sure.
MildBill
Click to expand...
Click to collapse
Yes, I'm sure you noticed in the link I posted above that you will not be able to register the device. The original info is stored and processed with keys and these are used when communicating with B&N.
You may have missed the link within the link: http://forum.xda-developers.com/showthread.php?t=892426
This may allow you to fix the MAC address issue. Seems to have worked for others.
So the really big issue is then how to overcome the rapid battery drain of an unregistered NST. I tried many things when I got my second NST but was never able to find something that didn't just make things worse. A truly B&N-free NST is a really worthy goal, but only if the battery issue can be solved. It seems like every attempt to disable/delete parts of the B&N system sets up a constantly running panic in the system background. The same appears to be true if you skip OOBE.
Advice: do a reset, try the MAC fix. If it works, do a backup. That's your baseline.
Good luck.
Edit: I can confirm that the method described in the link above does seem to successfully spoof the MAC address, as least as far as my router is concerned. I used an online hex editor to make the changes on a copy of the /rom/devconf/WiFiBackupCalibration file and then copied it back to my NST and rebooted. Initially in my Nook Settings app the MAC address shows up as "unknown", but this seems to be true at every reboot. Once a WiFi connection is made, the spoofed address is shown by the router and it even shows up in the Settings app thereafter without any additional changes.