atrix2 mac address - Motorola Atrix 2

atrix2 mac address collision fix it.

Diamond2550 said:
atrix2 mac address collision fix it.
Click to expand...
Click to collapse
Huh? :what:

1BadWolf said:
Huh? :what:
Click to expand...
Click to collapse
I found the problem that my two devices have the same mac address

Diamond2550 said:
I found the problem that my two devices have the same mac address
Click to expand...
Click to collapse
The mac address is assigned to each device at the factory. Changing the mac address on this phone accidentally is unlikely, if it's even possible. You probably have an app on one, or both, of the phones that is reporting a false or spoofed mac address. To find out, turn the phone(s) off completely. Then when you turn it/them back on wait until you see the red and white Motorola logo. As soon as you see that press and hold both of the volume buttons until the phone is booted up. That boots the phone up in Safe Mode in which no user applications are available. At this point check the mac addresses to see if they're now correct. If they are then you know it was caused by a user app and you'll just have to figure out which one it is. If all else fails you can either factory reset the phones or re-flash the FXZ files.

Fixing the problem is not the MAC address . 00: da: 36: 16: de: eb.

Diamond2550 said:
Fixing the problem is not the MAC address . 00: da: 36: 16: de: eb.
Click to expand...
Click to collapse
This is actually the same exact MAC both the phones are reporting.
Necroing this thread because it's relevant and didn't provide a solution/fix either.
Does anyone know a fix for this, or a MAC spoof that works on THIS device? Everything I've found with using busybox or nvram doesn't seem to work.
To note, both devices are using CM11, if that's relevant.
Edit:
So.. fixed this.
Moved a copy of wl1271-nvs.bin from /system/etc/firmware/ti-connectivity/ to the SD card /storage/sdcard0/
Opened terminal (my method was SSHing into the phone but adb, terminal emulator, or anything will work). As per directed from Texas Instruments Wiki I used the built-in calibrator to do the following:
/system/bin/calibrator set nvs_mac /storage/sdcard0/wl1271-nvs.bin 00:da:36:16:ed:ea
Note, you can use whatever MAC you wish.
From BMM, with aromafm.zip (I found it quickly with a google search of exactly that file name) in the SD card's clockwork folder, I copied the modified wl1271-nvs.bin from the SD card to the path above.

Related

[GUIDE] Bad WiMax MAC? Broken 4G after update? Fix HERE!

Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat

Help with WiFi

Hello,
I own a Motorola Milestone (rooted, unlocked). Two days ago a weird thing appeared: when i try to activate the wifi, it goes into a Turning on - turning off - turning on etc. loop and i can stop it just if i activate the airplane mode, restart the phone and deactivate the airplane mode. It does not see any wireless network, i can't stop it and i can't connect to any network.
If i try to see the MAC in the wifi settings -> advanced, it writes 00:00:00:00:00:00 when it is in the loop mode. In the service menu, the MAC Address appears Unavailable.
I tried to reflash different firmwares to solve the problem, but no luck. I reflashed the original rom on it, but also: no luck. I tried everything possible with no luck.
In sys/devices/virtual/net/ i don't have any eth0 folder which i think that contains the network drivers.
I didn't drop the phone, i didn't drop anything on it. It appeared from nowhere. There aren't any other problems with the phone. The bluetooth works fine so, i don't think it's a hw problem (i found somewhere that the two hw modules are the same...it's possible that i should got it wrong).
How can i solve it?
PS: i wrote this here because i saw that this happened to different persons around the world but nobody gave an answer. So, i don't think it's phone related.
If this happened to me I would try this:
1: Nandroid backup+Titanium backup
2: Run WiFi Fixer.apk
if it won't help:
3: Try some other ROMs
btw I don't really understand how did you come up with an idea that this is "Milestone Android Development" thread...
1. I don't have any Titanium Backup or nandroid backup
2. WiFi fixer doesn't work
3. i tested CM7, FroyoMod 2.3.3, CM6, original sbf file...nothing works
I posted this here because the other Milestone threads are not read by most of you.
then RMA it.
After you try to enable wifi, paste kernel log (output from 'dmesg' or 'logcat -b kernel' commands) and main log (logcat) to pastebin.com and post links to it here for inspection.
Is your /pds/wifi/nvs_map.bin file in place?
Hello kabaldan,
I was waiting for your reply master.
The /pds/wifi/nvs_map.bin is there but i can see it only in terminal, with ls, after su. In default file explorer from CM7, the folder is empty.
Here is the output of dmesg: http://pastebin.com/Ngz9iaQU
I'm currently using CM7 RC15 (the last night build).
PS: I promise to donate as soon as i get my money from the company i'm working for.
sdiodrv_data_xfer_sync() transfer error! STAT = 0x108011
Click to expand...
Click to collapse
Sorry to say that, but this is a hardware failure. The wlan sd card does not respond to commands sent to it.
You should send your phone for repair.

[SOLVED] Permanent change MAC adress in Sensation

How to do that? ARHD 4.1.11.
Calibration file dodn't work. nvram.txt? Where to put that?
I'v done that before, but lost my notes.
I'm not interested in MAC spoofing. Just want to have custom one.
Mike
sp5it said:
How to do that? ARHD 4.1.11.
Calibration file dodn't work. nvram.txt? Where to put that?
I'v done that before, but lost my notes.
I'm not interested in MAC spoofing. Just want to have custom one.
Mike
Click to expand...
Click to collapse
BUMP.
Anyone?
Hi,
Not sure if this will do it permanatly but it is a fix of a kind.
http://androidforums.com/t-mobile-g1/3506-changing-spoofing-mac-address.html
EDIT: and this should help too..
http://forum.xda-developers.com/showthread.php?t=750596
JMC31337
head into terminal emulation type su and go into /data/misc/wifi
Look for a file called nvram.txt
Copy it to your sdcard and then to your cpu desktop
open it with notepad and at the
bottom of nvram.txt is the mac address
This i was able to verify and test on android Citrus Ciena
Edit that mac address and save it as nvram1.txt onto sdcard
Now go back to data wifi misc and copy nvram.txt to nvram.bak
Head into gui and then settings then wifi then turn on the wifi but don't connect to any wifi
turn off the wifi,switch back to terminal
Copy the nvram1.txt to data misc wifi
remove the original (make sure you got it backed up)
Rename nvram1.txt to nvram.txt
head back into gui and then settings then wifi
Now for me it immediately stated unable to turn on wifi
Ignore it and try to turn it on anyways
When it turns on your newly edited mac address will take effect
Connect to your AP
NOW B4 REBOOTING YOU MUST CHANGE NVRAM BACK TO THE ORIGINAL!
did this and verified a fake mac address with tcpdump-arm
Busybox ip link show eth0
And a router with wpa2 table reflected the new fake mac
Click to expand...
Click to collapse
Solved
That worked.
http://forum.xda-developers.com/showthread.php?t=686789
Mike
You just follow the steps on this thread without doing anything else right? I just ask to be sure..
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
tzolov said:
You just follow the steps on this thread without doing anything else right? I just ask to be sure..
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Yes. I only had to change to Engineering SPL downloaded from here: http://wiki.cyanogenmod.com/wiki/HTC_Sensation:_Support_Downloads before changing MAC.
If you already have Engineering SPL you can skip this step.
Mike

[Q] Can't Establish A Connection SOLVED !!

Goodevening . I factory reset the phone (HTC Desire S ) It is runnin g 4.0.4 and sense 3.6 and it is rooted HTC DEV unlocked . After that i can't log in my google account . it always say " couldn't establish a reliable connection to the server this could be a temporary problem or your android device may not be provisioned for data services "can someone know how to fix this error ? I upgrade my phone via RUU from 2.3.5 GB sense 3.0 . Everything works fine . I can browse via web use my facebook .
i have tried factory reset, hard reset, restarted my htc desire many times .. i have tried even the youtube app method. nothing seems to work google app in the apps doesnt work too.. what should i do?? i cant use apps market.. i have tried everything.. please come up with a proper solution.. there're alot of people i know facing this mind sucking issue
Thanks ! Sorry for my bad english .
Google is your friend
try these see if they work
http://www.guruht.com/2010/07/htc-android-marketgmail-connection.html
ContactFront said:
Google is your friend
try these see if they work
http://www.guruht.com/2010/07/htc-android-marketgmail-connection.html
Click to expand...
Click to collapse
sir i already do this step . not working .. but thanks for the help ..
2easy4you said:
sir i already do this step . not working .. but thanks for the help ..
Click to expand...
Click to collapse
Try clearing cache and data for Google framework services, playstore and play services
The real voyage of discovery consists not in seeking new lands but seeing with new eyes.
—Marcel Proust
2easy4you said:
sir i already do this step . not working .. but thanks for the help ..
Click to expand...
Click to collapse
ok. go into your recovery, clear cache and dalvik cache then reboot see if helps
never had this problem myself this is all i could think of, sorry dude
ContactFront said:
ok. go into your recovery, clear cache and dalvik cache then reboot see if helps
never had this problem myself this is all i could think of, sorry dude
Click to expand...
Click to collapse
i already do this dude . i already factory reset my phone 10x . and wipe cache wipe dalvik wipe and format . but still i experience the problem . hmm . this problem appears when i facatory reset my phone . after that i cant log in anymore on google . i try making new account . i try this [email protected] but it says that is unavailable username ..
I solved this issue
2easy4you said:
Goodevening . I factory reset the phone (HTC Desire S ) It is runnin g 4.0.4 and sense 3.6 and it is rooted HTC DEV unlocked . After that i can't log in my google account . it always say " couldn't establish a reliable connection to the server this could be a temporary problem or your android device may not be provisioned for data services "can someone know how to fix this error ? I upgrade my phone via RUU from 2.3.5 GB sense 3.0 . Everything works fine . I can browse via web use my facebook .
i have tried factory reset, hard reset, restarted my htc desire many times .. i have tried even the youtube app method. nothing seems to work google app in the apps doesnt work too.. what should i do?? i cant use apps market.. i have tried everything.. please come up with a proper solution.. there're alot of people i know facing this mind sucking issue
Thanks ! Sorry for my bad english .
Click to expand...
Click to collapse
Here's what you need to do.
Assuming that you have already rooted your device, use any file explorer app and go to 'etc' folder of your device. (I used Root Explorer and did this on my Samsung Galaxy Tab N8000).
In 'etc' folder, locate the file called hosts.
Touch/press and hold the icon of the file to get its context menu and open the file in text editor.
In the file, there will be one IP address to the localhost, i.e. 127.0.0.1. Leave this as it is.
There will be a second IP address which may vary depending upon your region or country. Put a # in front of it. (eg. #245.45.14.14). This will mark this entry as a comment and the device won't read it.
(I would suggest that you backup 'hosts' file before making any changes. In my case, a 'hosts.bak' file was automatically created when I saved the file after editing.)
Save the file and reboot your device.
This should resolve the issue.
VivekNayyar said:
Here's what you need to do.
Assuming that you have already rooted your device, use any file explorer app and go to 'etc' folder of your device. (I used Root Explorer and did this on my Samsung Galaxy Tab N8000).
In 'etc' folder, locate the file called hosts.
Touch/press and hold the icon of the file to get its context menu and open the file in text editor.
In the file, there will be one IP address to the localhost, i.e. 127.0.0.1. Leave this as it is.
There will be a second IP address which may vary depending upon your region or country. Put a # in front of it. (eg. #245.45.14.14). This will mark this entry as a comment and the device won't read it.
(I would suggest that you backup 'hosts' file before making any changes. In my case, a 'hosts.bak' file was automatically created when I saved the file after editing.)
Save the file and reboot your device.
This should resolve the issue.
Click to expand...
Click to collapse
Thanks alot my friend, You save my life
search first the key
GT-N7000 said:
Thanks alot my friend, You save my life
Click to expand...
Click to collapse
it post here.http://forum.xda-developers.com/showthread.php?t=2110225
Just install adfree.. Update the hostname and its done..
Worked for me
Worth a try..
Can't edit file
VivekNayyar said:
Here's what you need to do.
Assuming that you have already rooted your device, use any file explorer app and go to 'etc' folder of your device. (I used Root Explorer and did this on my Samsung Galaxy Tab N8000).
In 'etc' folder, locate the file called hosts.
Touch/press and hold the icon of the file to get its context menu and open the file in text editor.
In the file, there will be one IP address to the localhost, i.e. 127.0.0.1. Leave this as it is.
There will be a second IP address which may vary depending upon your region or country. Put a # in front of it. (eg. #245.45.14.14). This will mark this entry as a comment and the device won't read it.
(I would suggest that you backup 'hosts' file before making any changes. In my case, a 'hosts.bak' file was automatically created when I saved the file after editing.)
Save the file and reboot your device.
This should resolve the issue.
Click to expand...
Click to collapse
I tried everything you did but I cannot edit the hosts file,I have rooted my phone (Samsung Galaxy S3), I am using supersu.
Try This
CptCrotchKiller said:
I tried everything you did but I cannot edit the hosts file,I have rooted my phone (Samsung Galaxy S3), I am using supersu.
Click to expand...
Click to collapse
That's really strange. You should be able to edit the file as rooting process needs a reboot too. Well you can still try a workaround.
* Copy all the contents from the existing host file.
* Create a new file either on your smartphone or use a computer to do so. Make sure the name of the file is 'host' (without quotes) and file does not have any extension like .txt or .doc. If the file has any extension, remove it while rename the file.
* Now paste all the copied contents from the existing file to the new one and then make the changes as I mentioned in my answer.
* Save the file and replace it with the existing one.
Let me know if this helps.
Thank You
THANK YOU VERY VERY MUCH:good:
You are just awesome:good:
Thank you again.:good:
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
You are welcome
Ghaiooth said:
THANK YOU VERY VERY MUCH:good:
You are just awesome:good:
Thank you again.:good:
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Click to expand...
Click to collapse
You are most welcome friend. I am glad I was of some help.
Cheers mate, you are a true legend. My phone locked up on me, and this solved the problem, cheers mate.
Ok, I am having this issue as well. I have tried all of the above but just noticed that this file only has one IP address not two?
lopesamit said:
Just install adfree.. Update the hostname and its done..
Worked for me
Worth a try..
Click to expand...
Click to collapse
Thanks man this method worked, Thanks given
---------- Post added at 10:29 AM ---------- Previous post was at 09:41 AM ----------
but my question is what could be the possible cause of Problem
Sir what if there is no second ip adress? only the '127.0.0.1. Localhost' and no second line.....
thx bro...
its fix my oppo :highfive:
Thank you so ****ing much. This was very annoying.

Cannot resolve forum.xda-developers.com

I have this really odd issue with my Z3 in that I cannot, on any network (wireless or carrier), resolve through DNS forum.xda-developers.com. I first noticed it because my XDA premium HD app couldn't connect to the forums at all. I did a bit of digging and managed to uncover that I can't connect to anything related to the forums. I CAN however connect to the main portal on www.xda-developers.com.
What I have tried:
1. Different wireless networks - no luck.
2. Other devices - all work fine on all the tried networks.
3. Carrier network (Rogers CA) - no luck, but again with other devices no problem
4. Ping and nslookup through Fing network tools - not able to resolve
5. Ping and nslookup through terminal emulator - not able to resolve
6. hosts file just has the standard localhost entry
7. Browse with Chrome just gives the standard error for unresolvable DNS
8. So far I have only seen this happen on the forums.xda-developers.com address.
I am running a Z3 (D6603) with a custom ROM per below.
Pre-rooted ROM from this thread: http://forum.xda-developers.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361
D6603_23.4.A.0.546_Customized_US_SuperSU_XZDR2.8.2 1 thanx to @julianbl
It's an odd one for sure, so if anyone has any creative ideas for me to test out please let me know. Thanks in advance.
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
julianbl said:
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Click to expand...
Click to collapse
I should note that I have not unlocked my bootloader. I tried this and it has unfortunately had no effect. Open to other suggestions though, thanks for trying.
[EDIT] I may have spoken too soon. I tried connecting after disabling (freezing) that app and didn't have any luck. I rebooted the phone, and things are back online. I will do some further testing to get concrete and repeatable behavior documented. Thanks @julianbl
bramybram said:
If you see a rule wiht xda-developers.com in it
Click to expand...
Click to collapse
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Swaziboy said:
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Click to expand...
Click to collapse
Try to add a XDA Rule with a "#" before the rule instead?
bramybram said:
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
Click to expand...
Click to collapse
bramybram said:
Try to add a XDA Rule with a "#" before the rule instead?
Click to expand...
Click to collapse
Thanks for your desire to help - given what we've found out so far this isn't a HOSTS file issue. There is no entry in the hosts file, and as such any DNS resolution for the domain should leverage DNS servers based on DHCP settings.
In my mind, adding a rule in the HOSTS file to force resolution of the domain, might work but it's not a real fix as to why this is happening.
Refer to my previous note that the suggestion to block the "PrototypeProtection" app is what has resolved the issue so far.
Thanks again though @bramybram, appreciate your willingness to help.
Hey there, I had the same issue... It is quite frustrating, I guess it's some bug in the firmware you installed (since I used the same to flash my z3)... I resolved it by flashing another firmware, I suggest you the D6603_23.4.A.0.546_Customized_NCB_SuperSU_XDR2.8.2 1 (https://mega.co.nz/#!GJQVBL6K!x8bB2HS-TbpbZTb5IamrJB_xduDMHl9j6jQyAqrJpVQ) one, it worked for me

Categories

Resources