Related
I've managed to build a version of wpa_supplicant that has ad-hoc enabled, by forward porting the patch in this thread:
http://forum.xda-developers.com/showthread.php?t=754961
After building and a couple of tests, it works.
To install, you need a rooted Xoom, of course, and just push the file to system/bin/wpa_supplicant.
Because zipfiles don't store permission, you have to make it executable as well.
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
adb shell chmod 755 /system/bin/wpa_supplicant
I also had to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Then reboot, and try it!
It works with my Nokia N8 with JoikuSpot; I can't tether it any other way as the N8 doesn't support the PAN Bluetooth profile, and Android doesn't support DUN.
Don't forget to backup your files, and I am not liable, etc, etc.
The code I used is here:
https://github.com/kelvie/android-wpa_supplicant
Ok heres what happened to me..
I was able to push the first file and when I input the adb shell code it said the device was not connected I am rooted and had no problems rooting or access shell before
So I got a little cocky and thought that the port 5037 that adb communicates with was blocked so I typed adb tcpip 5036 to see if I could get shell access on that port well now when I type adb remount it immediately tells me error: device not found....help!
Got myself stuck without wifi (error)
Thanks for developing such a great app. If i m not wrong i think its working with all 3G carriers.
You can also turn your Motorola Xoom tablets to WiFi hotspot without rooting by enabling setting which are given here http://goo.gl/mgwdn
Also my xoom has been in debug mode and now all of a sudden I noticed that its not entering debug mode when connected there used to a little icon come up and not anymore it acts like nothing yet i can access it on my computer by going my computer and I see Xoom
Ok I got debugging mode back and xoom is plugged in now my problem is when the daemon server starts in adb shell it starts on port 5038
So when I try to copy "adb shell chmod +x /system/bin/wpa_supplicant" it still says device not found and thats if I copy and paste it exactly if I type adb shell it gives me the # Symbol then i put it "chmod +x /system/bin/wpa_supplicant" and it says bad mode
One good thing is I can now type /remount again so what I am doing wrong still stuck without wifi ;\
Ok I've tried everything except reflash my devices I've literally only been able to do step 1 which leaves me with no wifi because i cannot execute the shell commands so please a little help it's been a long night messing with this appreciate your time and I'd love to get this working!
kelvie said:
I've managed to build a version of wpa_supplicant that has ad-hoc enabled, by forward porting the patch in this thread:
http://forum.xda-developers.com/showthread.php?t=754961
After building and a couple of tests, it works.
To install, you need a rooted Xoom, of course, and just push the file to system/bin/wpa_supplicant.
Because zipfiles don't store permission, you have to make it executable as well.
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
adb shell chmod +x /system/bin/wpa_supplicant
I also had to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Then reboot, and try it!
It works with my Nokia N8 with JoikuSpot; I can't tether it any other way as the N8 doesn't support the PAN Bluetooth profile, and Android doesn't support DUN.
Don't forget to backup your files, and I am not liable, etc, etc.
The code I used is here:
https://github.com/kelvie/android-wpa_supplicant
Click to expand...
Click to collapse
Ok...I tried this and got the same "bad mode" error at the
"adb shell chmod +x /system/bin/wpa_supplicant" stage.
So, I instead did "adb shell chmod 700 /system/bin/wpa_supplicant" and that was successful, so I finished the steps listed and can see my cell on my Xoom. I have a Windows Mobile 6.5 cell and my Xoom can NOW see my ad-hoc network. Thanks a lot Kelvie.
If not for the SDCard update from BRD, I think this thread would be getting alot more attention.
Not to be too mistrusting, but I am hesitant about loading this on my Xoom when it is posted by a new user with only one post.
Fusius said:
Ok...I tried this and got the same "bad mode" error at the
"adb shell chmod +x /system/bin/wpa_supplicant" stage.
So, I instead did "adb shell chmod 700 /system/bin/wpa_supplicant" and that was successful, so I finished the steps listed and can see my cell on my Xoom. I have a Windows Mobile 6.5 cell and my Xoom can NOW see my ad-hoc network. Thanks a lot Kelvie.
Click to expand...
Click to collapse
Hey that worked instantly love you!
PengLord said:
If not for the SDCard update from BRD, I think this thread would be getting alot more attention.
Not to be too mistrusting, but I am hesitant about loading this on my Xoom when it is posted by a new user with only one post.
Click to expand...
Click to collapse
I completely understand where you're coming from; but check my github repo, and google for me, I do leave a small internet trail...
I (mostly used to, don't do much anymore but answer the odd email) maintain an open source project (Basket for KDE), and try to participate in open source communities as much as I can.
I just did this to tether my Xoom Wifi to my phone, as I had no other way to get internet on the go.
Nice work. I tried to do this myself last week but ran into trouble just getting wpa_supplicant from the Android git to compile (with or without the changes)
First off, wow man thank you so much. I've been playing with this for a while and I've tried a number of different wpa supplicant files but they failed to initiate a scan of wireless networks. I just tried this one and it works great. I wanted to explain a different way to install it however for the people having ADB issues.
First you want to turn off your wifi. I have used the ADB method a couple of times but I find it easier to use Root explorer. Save the file to your Xoom, Copy it using root explorer, navigate to the system/bin folder and click mount R/W then paste the file into the folder replacing the original (make sure to make a backup!) then long hold on the file and view permissions, check all the boxes in the first two columns and the first 2 in the last column. (chmod 775) You can then restart your wifi and enjoy ad-hoc networks (no reboot needed.)
I've done this a couple of times and it works great. Thanks again.
First off, thanks a ton to the OP for getting this working!
Also, thanks to mr_wrong_0 for the root explorer directions. Not that I'm incapable of using the command prompt, it was just easier to do it this way.
mr_wrong_0 said:
First off, wow man thank you so much. I've been playing with this for a while and I've tried a number of different wpa supplicant files but they failed to initiate a scan of wireless networks. I just tried this one and it works great. I wanted to explain a different way to install it however for the people having ADB issues.
First you want to turn off your wifi. I have used the ADB method a couple of times but I find it easier to use Root explorer. Save the file to your Xoom, Copy it using root explorer, navigate to the system/bin folder and click mount R/W then paste the file into the folder replacing the original (make sure to make a backup!) then long hold on the file and view permissions, check all the boxes in the first two columns and the first 2 in the last column. (chmod 775) You can then restart your wifi and enjoy ad-hoc networks (no reboot needed.)
I've done this a couple of times and it works great. Thanks again.
Click to expand...
Click to collapse
Thanks so much for this! No issues at all. Wifi Xoom is tethered to my HTC Hero now.
Congrats on a killer mod! We are making progress nice and steady.
Installed, works great.
Thank you.
Great, thanks for your hard word.
I do have a question for those how have done this hack. I currently have an old iPhone 3g with tetherme installed and use Bluetooth tethering to give my Xoom (wifi only) internet access. This works great for me.
Is there are speed/battery life advantage to using wifi tethering instead?
Cheers
I don't know for sure. From what I understand wifi is potentially faster than bluetooth, but it can vary from device to device. I have noticed that my Epic seems to stay cooler and use less battery when broadcasting an Ad-hoc network vs broadcasting in infrastructure mode (using wifi tether 3.0.) But I've never been able to get my phone to tether with bluetooth so I don't know about battery life. One advantage of connecting over wifi is file sharing via apps like wifi file explorer. I have used that a lot to transfer files between my Xoom and my phone as well as the computer.
Noob question
Hello all,
Thank you very much for the patch.
I would like to try it out, but before that, I need to make sure of one thing;
If I root my Xoom, will I still be getting future updates from Motorola for the device if there is one? Or once I root it, is it impossible for me to update them from the manufacturer?
Thank you!
Thanks so much to the OP! I've been waiting for a reason to root my wifi Xoom. SDCard access was tempting, but I think this is the thing that pushes me over the edge!!
Thanks!!
Hello,
Bought my kindle fire year ago,
Just up to jelly beans: http://forum.xda-developers.com/showthread.php?t=1778010 :highfive:
worked perfectly in 2 days, then my wifi stopped working, I cannot turn it on, it showed: Wifi MAC address unavailable
I went panic, flashed to every roms I could find: CM9 gede rom, hellfire, CM7 kang,................
still no use. every times I checked, it still show mac address unavailable :crying:
right now I use the original rom, 6.3.1, downloaded form amazon, but .......:crying:
I tried every tips and tricks I found in the forum: some mac-.... command, rename some kind of file (the orig file I don't remember its name), put the wlan-loader file into it,.....etc
still unavailable :crying:
what should I do now, it's my dad's fire and he gonna burn my ass if I won't fix it soon:crying:
help me please
Use idme command to set mac address
If you can get to a point where you can run a terminal emulator on the KF in superuser mode, you can type the command
Code:
idme \?
. What you see in response should include a line like:
Code:
mac 0x0030 [I] hhhhhhhhhhhh[/I]
where hhhhhhhhhhhh is replaced by a string of 12 hex digits. If you see something else there, or nothing, your Kindle doesn't have a mac address. (Even if you do have a twelve-digit hex string here, it may be a bad one.) You can give the fire a hopefully-good mac address by typing the command:
Code:
idme mac F0A22563[I]hhhh[/I]
where I chose 'F0A22563' because it is the start of one of my mac addresses and the last four hex digits can be anything, I think.
If you can't get a terminal emulator running on your KF, you can do the same thing using adb or fastboot on your computer with the Fire attached, but I'm much too tired to get into that right now.
Wi-Fi MAC Address: Unavailable
I tried various ROMs even stock ROM but I cannot get my Wi-Fi to work. I am on the same boat as tungnq, I even tried aarons510 solution with a terminal emulator but still the Wi-Fi MAC Address is Unavailable. I dont have any wifi configuration on my /system and /data. I cannot even find the file wpa_supplicant.conf. When I connect the Kindle to KFU, the wireless chip gets detected in the device manager as WAN MiniPort. So I think the WIreless chip is working but has it drivers deleted or corrupted. Please someone help me out with my current predicament.
Current ROM: Energy.7.31.2012.Kindle.Fire.CM9.ICS
Kindle Fire Model: D01400
I have the same problem. Can anyone show the way to fix?
Thanks
I run a terminal emulator on the KF. Command: idme \?
It shows can not open so that I can change the Mac address
Pls, tell how I can run it.
vinhntna608 said:
It shows can not open so that I can change the Mac address
Click to expand...
Click to collapse
What exactly does that mean? Are you saying the command 'idme \?' doesn't work for you?
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
What exactly does that mean? Are you saying the command 'idme \?' doesn't work for you?
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
It shows that
Could not open /dev/block/mmcb1k0!
Can't read the idme.
So I can't change the Wifi Mac Address
vinhntna608 said:
It shows that
Could not open /dev/block/mmcb1k0!
Can't read the idme.
So I can't change the Wifi Mac Address
Click to expand...
Click to collapse
I don't know why it would say " Could not open /dev/block/mmcblk0" from entering the idme command. Can you post a screenshot?
"That's a special kind of stupid. The kind that makes me laugh."
This is from Terminal emulator running in superuser mode
Code:
[email protected]:/ # idme print
Reading idme data ...
version: 1.3
boardid: 807xxxx000000000
serial: D026A0A024xxxxxx
mac: E0CB1Dxxxxxx
sec: E9EPCF5OHIJFRP7UB6FD
bt:
pid:
pid2:
bootmode: 1
postmode: -
[email protected]:/ #
I've tried to change the wpa_supplicant.conf and figured out that ctrl_interface=wlan0 not tiwlan0. I've change it to tiwlan0 but then it was back to wlan0. I don't know why but I guess that makes my Mac address unvailable. How can I fix it?
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
10|[email protected]:/ # chmod 777 /data/misc/wifi/wpa_supplicant.conf
[email protected]:/ # cat /data/misc/wifi/wpa_supplicant.conf
update_config=1
[B]ctrl_interface=tiwlan0
[/B]
10|[email protected]:/ # chmod 755 /system/bin/wpa_supplicant
10|[email protected]:/ # chown system.wifi /data/misc/wifi/wpa_supplicant.conf
[email protected]:/ # cat /data/misc/wifi/wpa_supplicant.conf
update_config=1
[B]ctrl_interface=wlan0
[/B]
I have the same problem. Wi-Fi is grayed out. I cant turn it ON.
Installed v 6.3.2 Amazon pure stock software (unrooted) and when i go to settings / device wi-fi mac address shows as unavailable.
Tried changing Wi-Fi file in data/misc/wi-fi and didnt work, factory defaults reset didnt work, 20 sec pwr button reset did not work.
the idme \? shows the MAC address
idme mac XXXXXXXXXXXX changed the wi-fi mac address but the problem remains the same.
What else to do ?
same wifi and bluetooth issue
HEy iam having wifi and bletooth issue with this mod...
it says turning on wlan or bluetooth but takes forever and never turns on..
estored backup but nothing change problem still present....
in wifi and bluetooth mac adresses it is saying unavailable
Ernst tignedhe
I had this same issue and was able to solve it. In an attempt to put TWRP on my Kindle Fire HD, I broke the wireless.
These were the steps I followed: http://forum.xda-developers.com/showthread.php?t=2128848
The issue arises from flashing the incorrect boot version (kfhd7-freedom-boot-7.4.6.img). You have to use the version applicable to your OS, not simply the 7.4.6 version. Google for HashCode's goo.im page for the Tate device to find other versions.
fixed
tungnq said:
Hello,
Bought my kindle fire year ago,
Just up to jelly beans: http://forum.xda-developers.com/showthread.php?t=1778010 :highfive:
worked perfectly in 2 days, then my wifi stopped working, I cannot turn it on, it showed: Wifi MAC address unavailable
I went panic, flashed to every roms I could find: CM9 gede rom, hellfire, CM7 kang,................
still no use. every times I checked, it still show mac address unavailable :crying:
right now I use the original rom, 6.3.1, downloaded form amazon, but .......:crying:
I tried every tips and tricks I found in the forum: some mac-.... command, rename some kind of file (the orig file I don't remember its name), put the wlan-loader file into it,.....etc
still unavailable :crying:
what should I do now, it's my dad's fire and he gonna burn my ass if I won't fix it soon:crying:
help me please
Click to expand...
Click to collapse
if u have rooted phone turn off wifi and look for two files named .mac.info
delete them and do dalvik wipe. this worked for me!
aarons510 said:
If you can get to a point where you can run a terminal emulator on the KF in superuser mode, you can type the command
Code:
idme \?
. What you see in response should include a line like:
Code:
mac 0x0030 [I] hhhhhhhhhhhh[/I]
where hhhhhhhhhhhh is replaced by a string of 12 hex digits. If you see something else there, or nothing, your Kindle doesn't have a mac address. (Even if you do have a twelve-digit hex string here, it may be a bad one.) You can give the fire a hopefully-good mac address by typing the command:
Code:
idme mac F0A22563[I]hhhh[/I]
where I chose 'F0A22563' because it is the start of one of my mac addresses and the last four hex digits can be anything, I think.
If you can't get a terminal emulator running on your KF, you can do the same thing using adb or fastboot on your computer with the Fire attached, but I'm much too tired to get into that right now.
Click to expand...
Click to collapse
When I do the idme \? command in the KF terminal, with SU, it says "idme not found." What does this mean? I am trying to change the MAC address as I made a mistake earlier
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
http://www.xbmchub.com/forums/showthread.php?t=21380
Sent from my Nexus 7²
Vidikron said:
I've been side loading apps using ADB across my home network, but is there a way to use a file manager (like ES File Explorer) to install APKs? I put an APK on my Fire TV and tried using ES File Explorer and it gave my an error stating that the install was blocked because my "phone" was set to not allow installs from unknown sources. Is there a way around this restriction as this time?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
screwyluie said:
http://forum.xda-developers.com/showthread.php?t=593538
should make it easier anyways
Click to expand...
Click to collapse
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Vidikron said:
Do you know the proper way to edit that command to work over a network? It seems to be set up assuming a direct connection. I tried a couple of things like throwing "connect <IP address>" in there, but nothing worked. But I'm probably not setting up the commands correctly.
Click to expand...
Click to collapse
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
DeVSS said:
All I did was make sure port 5555 was open on my router and the shell install is working over my network without any changes to the reg file.
Click to expand...
Click to collapse
Interesting.. It just says "waiting for device" when I try.
Vidikron said:
Interesting.. It just says "waiting for device" when I try.
Click to expand...
Click to collapse
Just double checking, but you did turn adb on on your fire tv right?
DeVSS said:
Just double checking, but you did turn adb on on your fire tv right?
Click to expand...
Click to collapse
Yes. I've been installing APKs via the command prompt on my PC and that works fine. But when doing that I have to use the connect command to connect to a specific IP. I guess I'm unclear on how adb is actually supposed to find my device without telling it where to look.
[edit] Well, I've sort of gotten around the issue. I just made a second shell command to connect. So now I right-click connect and then right-click install. Not as pretty as a single command, but much faster than what I was doing before. But if anyone knows how to merge the two into a single command please let me know.
Usually I let my fire tv update it self,cause I don't really care bout something going to be broken since I have no root in there..but not anymore since the last update (5.0.5)kick in,and that messed up one of my helpful app i used..Name is mouse toggle i used for the remote..uninstall tried to put it back but can't get none of the sideload apps to work with my fire tv..anyone out there kwn which one that's working or in PC..any links please? your help would be appreciate.I'm a none root user possibly will use for that purpose as well
Ths
im using this on 5.0.5 on my rooted AFTV2, my boys non rooted stick the one with the voice controller, & my AFTV stick without the voice controller & non rooted. Works on all of them, since you have installed OS5 things have changed in the settings of Firestarter which need to be changed, ADB only works with one device at a time so you have to look in your firestarter settings? try a fresh reboot? or reintall the app again?
Ok..deanr1977 I got it all figured..i now that i root, I'm waiting for a working costume recovery so I can install a nice launcher get ridded of somes bloats..thanks for your replied though
So do you own where to get the latest ADB software so I can try to block the update?
donjan3 said:
So do you own where to get the latest ADB software so I can try to block the update?
Click to expand...
Click to collapse
ADB -
http://www.aftvnews.com/how-to-setup-adb-and-fastboot-on-a-mac-or-windows-computer/
How to connect ADB to a Stick -
http://www.aftvnews.com/how-to-connect-to-a-fire-tv-or-fire-tv-stick-via-adb/
How to block updates -
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Commands -
adb shell
su
pm disable com.amazon.device.software.ota
exit
exit
PLEASE NOTE
On the su part be sure to select “Grant” if your Fire TV prompts you for superuser access!!!!
If this helps press that thanks button
Sent from my SM-G900F using Tapatalk
I'm trying to SFTP into Nvidia Shield TV but keep getting denied.
I have rooted the device and installed SSH Server. I do get prompted to accept the RSA Key, but then denied access.
The SSH Server app that I'm using was added to the Super User app and granted root access.
What am I doing wrong. I'm so close.....
FYI, I can use FTP but denied when using SFTP.
1) Are you rooted? Did you give SSH/SFTP root privileges?
2) Did you remember to change the default Password to something other than whatever the default was?
3) Did you remember to run the SSH/SFTP Server before trying to run it? It's NOT automatic. You have to run it Server side first!
4) Assuming you using something like Putty or WinSCP you need to login using the local IP Address of the Shield TV ex. 192.178.xxx.xxx
If you can follow most of that it shouldn't be a bother getting it to run.
Ichijoe said:
1) Are you rooted? Did you give SSH/SFTP root privileges?
2) Did you remember to change the default Password to something other than whatever the default was?
3) Did you remember to run the SSH/SFTP Server before trying to run it? It's NOT automatic. You have to run it Server side first!
4) Assuming you using something like Putty or WinSCP you need to login using the local IP Address of the Shield TV ex. 192.178.xxx.xxx
If you can follow most of that it shouldn't be a bother getting it to run.
Click to expand...
Click to collapse
1. Yes I'm rooted.
2. Yes I have a password
3. Yes, I ran SSH Server first
4. Yes I am trying to login with IP address
Give me something other then the basics here!
What about: Settings > Storage & reset > Over local network?
finsfree said:
I'm trying to SFTP into Nvidia Shield TV but keep getting denied.
I have rooted the device and installed SSH Server. I do get prompted to accept the RSA Key, but then denied access.
The SSH Server app that I'm using was added to the Super User app and granted root access.
What am I doing wrong. I'm so close.....
FYI, I can use FTP but denied when using SFTP.
Click to expand...
Click to collapse
What SSH server are you using?
Having Sideload 'Rooted SSH/SFTP Daemon. Which is listed as non Android TV compatible. I was greeted instantly with a "wtf not rooted" message. Which may be kinda the case since I never really enabled such RW permissions for SU though TWRP. Since having done so in the past kinda made OTA Updates malfunction. It's kinda the same case with Adaway as well.
But, on the Shield TV the only real tangible use of root that I have is, in being able to install Plex Channels. Which with a symlinked Folder. Works well enough.
I got it to work!
finsfree said:
I got it to work!
Click to expand...
Click to collapse
So what was the issue?
Please use the QUOTE feature when replying to me to get my attention. Thanks!
My guess would be he enabled root via TWRP. Hopefully it won't comeback to bite him in the arse. While this does make things incredibly easier, it also completely forks up any hopes of successfully installing any OTA Updates. Which may not be as much of a problem, as it was when I first got into the Shield TV last January. With the transition from Marshmallow, to Nougat.