Hi,
Because of an issue at work (and it not wanting to reboot Cisco APs) My phone cannot connect to the Wi-Fi. I have tried several methods (apps & terminal commands) to change my phones' MAC address.
Nothing seems to work. Does anybody have a surefire way that will work?
Thanks
Kevin
Try this
http://forum.xda-developers.com/showthread.php?t=2286440
Also saying nothing seems to work without saying what you have done is not helpful.
I'll look at the link thanks. I did not feel it worthwhile to say which apps and terminal commands I used as I followed the core out there. And even though it sometimes said it switched, in reality it had not. Apps tried MAC Ghost, and others. CMD tried via busybox ifconfig and couple other can't remember.
Did not try changing NVRAM.txt and the phone doesn't seem to have a wl file.
There's a way to do it using fastboot oem commands...it's been a while though, so I forget the specifics and where I saw it
You will probably have to be on an eng hboot though
Related
When I type in any adb commands on my computer, I'm suddenly getting a "bus error". It works fine on my PC at home but not on my work computer. Could I have possibly deleted a file that is needed for adb? Does anyone have a way to fix this?
I'm on a MAC and have the same exact problem. I've tried ADB on two home computers with no luck. Although, my problem is on a MAC I'm hoping someone can provide some help to better direct my search for an answer
srkmagnus said:
I'm on a MAC and have the same exact problem. I've tried ADB on two home computers with no luck. Although, my problem is on a MAC I'm hoping someone can provide some help to better direct my search for an answer
Click to expand...
Click to collapse
My problem is on a Mac as well. It worked fine on this Mac until just the other day. When I get on a PC things still work fine.
Nobody has an idea?
I pulled the crash report and can't make much of it. A friend of mine suggested I backup the computer then re-install the OS to see if that fixes it, considering the error never existed until recently. I'm at a lost and have been very frustarted. It occurs on two computers (Macbook and an iMac) and differenct User accounts.
Staunty, My problem has been resolved. I am on Mac 10.4 (Tiger) and the newest SDK packages don't support it. If you are on Tiger and downloaded the most recent SDK then I'd suggest downloading an archived one from here:
http://developer.android.com/sdk/older_releases.html
Sorry if I post in this old topic but i have a problem!
Im on tiger and i have downloaded the sdk 1.6r1 in your link to avoid the bus error problem, but i discovered that in this version there isn't the command "adb connect" to use adb wireless!
I've done some search but i haven't found a more recent version for tiger... can you help me?
Which app did you try? Give this one a try and be sure to enter the command with the given IP.
ADB Wireless (Widget)
The problem isn't the app but the sdk version! In 1.6 there isn't the command "adb connect" so i can't connect the phone with my mac.
In the version that i had used before update to the last relase (that doesn't support tiger), this command was present, but i can't found it!
Sent from my HTC Magic using XDA App
Did you try older SDK releases other than the 1.6r1?
http://developer.android.com/sdk/older_releases.html
there are several older version further down the page.
I will try...
Sent from my HTC Magic using XDA App
Hi, does anyone know how to permanently change the MAC address on a rooted Nexus One? Thanks.
Considering the root of this file system is linux, it should be pretty similar to this: http://linuxhelp.blogspot.com/2005/09/how-to-change-mac-address-of-your.html
If at all possible. Obviously, change eth0 to whatever is appropriate. Also, you'll probably have to su to do any of the commands.
Hi, thanks for the reply. I did try that already but after the following command:
ifconfig eth0 hw ether 00:80:48:BA:d1:30
I get this error:
ifconfig: bad address 'hw'
Any ideas?
It worked for me. Before you ran that command did you switch to root user?
Also, this won't permanently change it. It'll only change it for your current boot. If you want it to be permanently done, you'll have to put the command into a init.d script.
So, I have been looking into and testing this some more and I have found something strange. It seems as though something within android keeps reverting my MAC address back to the real MAC address and I am unable to connect to the network I am trying to connect to (it has MAC address filtering). Any thoughts?
And nachod0g in response to your error, double check and make sure that when you type the command "ifconfig -a | grep HWaddr" that eth0 actually comes up. If WiFi is not enabled, this will not work.
Hi everyone,
I appreciate any help you can give "the newbie" here.
I swear I'm not a total moron, but I can't get this to work. I've tried searching the forums and google, and I've found posts with similar problems, but no solutions. Until I can get another computer to test this on, I don't know if the problem is with my Droid Bionic (unrooted, running JB stock 4.1.2), or my computer (Mac OSX 10.8.3) or my modem.
I would LOVE to root my phone, but I can't even get the darned thing to connect to my computer through the file app!
The phone is on the same wifi network as my computer. Both have no trouble accessing the internet. Both can ping each other (packets sent and received fine). But I can't connect one to the other.
I turn on file sharing on my computer with SMB only
select a folder on my computer to share
Assign a user and password permission to access that folder
make sure permissions for that folder are set to read and write
then go to my phone, open the stock file app
Select "Remote Storages" and "add storage"
Then I enter the IP address for the computer
WORKGROUP for the domain name
The name of the shared folder
The user name and password
then I try to connect.
And I get an alert box on the phone that says
"Network Error
There is a problem in your network connection with remote host. Please repair your network connection and try again."
I'm doing everything that's obvious to do, so I'm guessing there's something "not obvious" that I'm missing. - Anyone here had a similar problem and solved it?
Some things I've tried:
Moving the shared folder to different directories including root, desktop, and "public folder" (each time I moved it, I removed it from the shared list and re-added it)
Creating a guest account and allowing it access to the shared folder - no password needed
Creating a 2nd admin account and allowing it access to shared folders (password)
Turning off computer's firewall
Seeing if I could connect through the computer and phone's browsers (no go!)
Lots of turning things on and off (sharing, users, permissions, wireless...etc.)
Gone into recovery mode on the phone and done a factory reset and wiped the cache partition.
When I check my modem's admin page, I can see both the computer and phone listed there as connected devices. The modem sees them both, and they can ping each other. Why the heck can't I connect them to each other?
Oh, and though I don't think this is relevant, when I connect via cable in USB Storage mode, I can see the internal and external cards on my Mac just fine. They both mount as drives and I can drag stuff back and forth. - Wish I could find instructions to root THAT way!
I finally get the nerve to try to root this and get it on TMobile, and I can't get past the part that should be a no-brainer!
Any help would be appreciated.
BB01
-------------
Editing on 1/8/14 to add that the problem may be related to a Samba issue in OSX Mountain Lion. I'm also wondering if it could be an issue with my modem, which is several years old. I'm going away for about a week so I may try this on a friend's computer. I'll report back WHEN I am successful with this (because I will be!)
Can't root through Mac Mountain Lion. Use Easy Root in VB
Replying to my own post, to follow up. I was unable to connect through samba on my mac running Mountain Lion, while at a friend's house. So the problem was not the modem, but my OS itself.
I'd read that Easy Root ( http://forum.xda-developers.com/showthread.php?t=2256439 ) using Virtual Box hadn't worked on a Mac, but I decided to try it anyway. I had to change one setting in Virtual Box from NVidia to "en1: Wi-Fi (AirPort)", and then the Easy Root worked flawlessly. When it got to the part about connecting the Bionic to the Remote Storage folder, I thought "Here we go... this is the part that won't work!" but with Easy Root running in Virtual Box, the bionic connected to the shared folder perfectly.
Mac users with Mountain Lion or above, use Easy Root in Virtual Box to root your Droid Bionic running Jellybean 4.1.2 (here's the link again: http://forum.xda-developers.com/showthread.php?t=2256439 ). I know there are posts by people who were able to root their droids through the Mac terminal, but I'm guessing they were on an older OS where smb still worked correctly.
QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.
Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.
Are you running the latest adb/fastboot tools on your PC?
Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/
I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.
ok i had used the desktop version of kingroot to root the device, and despite my adb drives still refusing to work on windows it worked for both the tablets. but now when i plug it into ubuntu to start removeing kingroot and adding supersu i don;t get the aurthorizeation notafication and i have tried revoking all and disabling and re-enableing adb and restarting computer and tablets but now it just wont authorize. all these simple tutorials have turned out to be complete nightmares for me. i have never had such a difficult time hacking a single device in my life and that includes wiis psps other kindles eta.
Nightmare-Rex420 said:
ok i had used the desktop version of kingroot to root the device, and despite my adb drives still refusing to work on windows it worked for both the tablets. but now when i plug it into ubuntu to start removeing kingroot and adding supersu i don;t get the aurthorizeation notafication and i have tried revoking all and disabling and re-enableing adb and restarting computer and tablets but now it just wont authorize. all these simple tutorials have turned out to be complete nightmares for me. i have never had such a difficult time hacking a single device in my life and that includes wiis psps other kindles eta.
Click to expand...
Click to collapse
Don't know what to say...securing adb access/authorization has not been a high hurdle for most visitors to these pages including many with little/no technical background. Possible you have a finicky USB cable?
Once rooted the SuperTool is only needed to gracefully remove Kinguser. You could pop open the batch file and issue the relevant commands manually as needed. Blocking OTA involves renaming a single file. After that FlashFire can be sideloaded from APKMirror.
yea problem is that super tool is not working on linux it says it is working and success but dose nothing, i can't use the super tool on windows becasue adb drivers not installing despite folowing tutorials closly how to install i just run into problem with no what if that problem not solved. it really sucks howcome is this 5.1.2 so ****ing hard to hack root on. i would rather have to hack 30 wiis blind and 30 psps blind than this. it is just for some reason i keep running into errors. where normaly i run into no errors or common errors that a google search can fix. :/
Nightmare-Rex420 said:
yea problem is that super tool is not working on linux it says it is working and success but dose nothing, i can't use the super tool on windows becasue adb drivers not installing despite folowing tutorials closly how to install i just run into problem with no what if that problem not solved. it really sucks howcome is this 5.1.2 so ****ing hard to hack root on. i would rather have to hack 30 wiis blind and 30 psps blind than this. it is just for some reason i keep running into errors. where normaly i run into no errors or common errors that a google search can fix. :/
Click to expand...
Click to collapse
- sorry for your troubles
- not hard for most; many with no technical background have made it
- perhaps find a friend with a different host