Related
so I wanted to tether my device with my winxp PC, found out that it can't be done directly and had to download tetherxp.inf from android help page.
I followed instructions to the point to configure my PC but couldn't get it to work. so can anybody give me instructions on how to tether. even after configuring with the file when I go in device manager to check it comments that the device couldn't get started
Hey guys i saw a fix on general android here on xda. It works for me on windows 8.1
Hope it works for you, maybe this can get stickied so we dont get more questions about fastboot on windows 8,1.
http://forum.xda-developers.com/showthread.php?t=2598155
As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43.
This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1.
Microsoft said that the fix will come in February but for people who don't want to wait I prepaired a dirty solution:
proof - see attachment.
HTML Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
can u help me with win8
hhamzah49 said:
Hey guys i saw a fix on general android here on xda. It works for me on windows 8.1
Hope it works for you, maybe this can get stickied so we dont get more questions about fastboot on windows 8,1.
http://forum.xda-developers.com/showthread.php?t=2598155
Click to expand...
Click to collapse
i cannot entre fastboot mode in win8
any suggestions
austinrajiv26 said:
i cannot entre fastboot mode in win8
any suggestions
Click to expand...
Click to collapse
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
12.) Use Flashtool drivers and install fastboot and flashmode drivers.
Its easier on windows 8 than on windows 8.1 kinda
Hello to everybody, if necessary move this thread in the right place.
Yes , if you have a pc or mac/lunux you can have tethering working from your new Android L developer preview
How to :
first with cannot use the broken tethering from os, so....install the clockworkmod tether from the store
install abd driver on windows side if isn t installed before
install tether application for your os
Mac: http://download.clockworkmod.com/tether/tether-mac.zip
Linux: http://download.clockworkmod.com/tether/tether-linux.tgz
Windows: http://download.clockworkmod.com/tether/TetherWindowsSetup.msi
start the android app and the the pc/osx app
(debug mode must be on)
authorize adb use on android app pop up
ps
in this moment i m using it on mac osx 10.9.3
p.p.s
clockworkmod... can u create an wifi version ?
It worked like a charm, thank you very much for this solution!
It's not as comfortable as the stock solution but it allowed me to stay on Android L since I really need tethering for work :highfive:
Lannyx1 said:
Hello to everybody, if necessary move this thread in the right place.
Yes , if you have a pc or mac/lunux you can have tethering working from your new Android L developer preview
How to :
first with cannot use the broken tethering from os, so....install the clockworkmod tether from the store
install abd driver on windows side if isn t installed before
install tether application for your os
Mac: http://download.clockworkmod.com/tether/tether-mac.zip
Linux: http://download.clockworkmod.com/tether/tether-linux.tgz
Windows: http://download.clockworkmod.com/tether/TetherWindowsSetup.msi
start the android app and the the pc/osx app
(debug mode must be on)
authorize adb use on android app pop up
ps
in this moment i m using it on mac osx 10.9.3
p.p.s
clockworkmod... can u create an wifi version ?
Click to expand...
Click to collapse
Nice! Working for me
Please help
Clockworkmod Tether used to work on Kitkat but not anymore on Lollipop. Could you please help?
I'm sorry but why are you still on developer preview?
Thanks for asking. I am not on developer preview. I have lollipop 5.0.2. Do you have any ideas as to how to get wifi tether to work?
Thethering No Root Required
oldporkchops said:
Thanks for asking. I am not on developer preview. I have lollipop 5.0.2. Do you have any ideas as to how to get wifi tether to work?
Click to expand...
Click to collapse
Step 1 Enable Adb
Step 2 navigate to where you have ADB installed
Step 3 Run ADB shell
Step 4 Run settings put global tether_dun_required 0
Step 5 Type Exit
Wifi tethering works for me on the Nexus 5. This should prevent your carrier from seeing tethering usage until the next android update of course. You pay for data and have the right to use it however you want to I think it wrong for Google or carriers to tell you differently.
Thanks Napster!
I got it to work while your message came in. It was the Avast antivirus interferering with the way Clockworkmod Tether on Win 7 communicated with Clockworkmod app on Lollipop 5.0.2.
Could you please let me know how to operate the ADB Shell? Where do I download it?
I wholeheartedly agree with your last statement. I'm on the magenta company based in Seattle, WA and thankfully they havent bugged me about it, but I want to stay under the radar, so I would like to implement your suggestion
UPDATE 27th November 2014
I have added an Xposed module for the clients below that will work around the issue with Google Play services 6.5
UPDATE 25th November 2014
Google have released Google Play services 6.5 which has strengthened security, effectively making this app useless (clients will be unable to connect). Until Google either loosen the security (which is unlikely to happen), or someone somehow were able to get a hold of the private keys from the chromecast/Android TV this app will no longer work and will no longer be updated.
Thank you all for your support!
Hi everyone! I've decided to finally release my modified Cast Receiver app from the ADT-1 for Android that will work on most devices (though not sure what the minimum api requirement is).
If you don't know what this is it's basically a chromecast receiver for your Android; I use it on my Android mini PC that's hooked up to my TV.
Downloads
Last updated Nov 05 2014.
Recovery install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiaU5WSWRxeC02Tzg
Signed
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiVDR1a1o0WFVSWjg
System install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiNFJGUE1acGZTeFE
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiOTRoanlyX19pVmc
If you are not rooted and can only install it as a regular apk, use the signed version. Note however that casting the screen from another Android device will not work due to a signature mismatch (Google Play Services checks the signatures of the app before allowing screencasting).
If you are rooted you should go for the recovery/system install option, as that will allow screencasting to work.
Xposed module for receiver
If you want to be able to use the system install version on devices older than KitKat you can use the following Xposed module:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiZEFrN1RqLTRFdkk
Xposed module for client
Version 6.5 and newer of Google Play services makes it impossible to connect to the receiver due to some added security. This Xposed module works around that:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiWG1tU3NfYWwwV00
Install
Recovery install
No special instructions needed, simply copy SYSTEM-CastReceiver.zip to the internal storage (or sdcard) on your device and flash it through your recovery (follow the instructions for your specific recovery).
Signed
Simply install the apk as you would with any apk, either through adb:
Code:
adb install -r AndroidMediaShell-signed.apk
or by installing it from your sdcard.
System install
You will need rooted adb for this to work correctly.
If you come from an old install, you can safely remove the old lib first:
Code:
adb remount && adb shell rm /system/lib/libmedia_shell_content_view.so
Once that's done, run:
Code:
adb remount && adb push libcast_shell_android.so /system/lib/ && adb shell chmod 0644 /system/lib/libcast_shell_android.so
adb remount && adb push AndroidMediaShell.apk /system/priv-app/ && adb shell chmod 0644 /system/priv-app/AndroidMediaShell.apk
(Change priv-app to app on devices older than 4.4)
Running
Amazon Fire TV
Because the Whisperplay app implements a DIAL protocol of its own on port 8008, which the Cast Receiver app also uses and that causes a conflict between the two apps.
To get the app running correctly you need to rename WhisperplayCore.apk:
Code:
adb shell mv /system/app/WhisperplayCore.apk /system/app/WhisperplayCore.apk.bak
once that's done, reboot and follow the instructions below.
For the receiver to start you can simply reboot provided you are using the system install. If you are using the signed version you need to run:
Code:
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n com.google.android.apps.mediashell/.AutoStartListener
After that it will run automatically in the background after each reboot, so you will be good to go!
Keep in mind that it might take a few minutes for the receiver to show up in the cast list, if it doesn't show after 10 minutes, try rebooting the device.
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
Supported Apps
Currently not every app is supported. The ones I've tried are:
YouTube - Working
Google Play Music - Working
Google Play Movies & TV - Working
Google+ - Working
Google Photos - Working
Screen Cast - Working (if you follow the instructions above)
Chrome for computer - Working
Netflix - NOT Working (I'm looking into this)
Plex - Working
Chrome for Android - Workinghttps://drive.google.com/file/d/0B4FOzj4b2EYiWVlDTWNGOEw3UTg/view?usp=sharing
Those are the ones I've tried, others may or may not work.
Whether the app will work may also depend on what device you are running the cast receiver on, as well as the region you are in.
FAQ
My device doesn't show up in the official Chromecast app
This is a known "problem" that also affects the ADT-1. There is nothing I can do about it in the Cast Receiver app, only Google can fix it by modifying the Chromecast app. Screen casting etc should work though, it's only the Devices screen that doesn't show any devices.
The receiver doesn't work on my Amazon Fire TV
Please read the instructions under the Running category.
I can't find the receiver device in the cast list
Give it a few minutes. If that doesn't work, try backing out of the app, and enter it again. If it still doesn't show, post a new reply to this thread with a log from logcat.
App X doesn't work
Get me a log when you try to initiate the connection, keeping in mind that some apps may be easier to fix than others. And some may be next to impossible due to them being regional.
How?
I've had some people ask how this was done, so I've written up a list of the changes and a brief summary here:
https://docs.google.com/document/d/1tXnjDdurdoJ4ufulzaqGpuaNpLLt6LGAUk22MO2jta4/edit?usp=sharing
You can get a patch of the smali changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiTHZBRGVUWmlSV1U/view?usp=sharing
And a bsdiff of the lib changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
The source code of the Xposed receiver module can be found here:
https://github.com/HomerSp/XposedCastReceiverFix
The source code of the Xposed client module can be found here:
https://github.com/HomerSp/XposedCastClientFix
And finally here is the code I used while testing the receiver, and writing the MediaDrm and JmDNS code:
https://github.com/HomerSp/CastTest
Changelog
Nov 05, 2014
* Fixed receiver not working while connected to ethernet (may be restricted to the Fire TV)
Oct 29, 2014
* Fixed app not working on API level 15 (tested by me on a real device).
* Disabled logging to file - this should significantly reduce the size of the data that's used by the app.
Oct 26, 2014
* Updated to new 5.0 preview from the ADT-1.
* Lowered API level to 15 on the signed version, keep in mind that this is untested by me. This also includes disabling some DRM API calls that were added in API level 18, so Play Movies will not work on API 17 or lower.
Oct 17, 2014
* Fixed receiver not always starting correctly due to device not being provisioned, thanks to @rkirmeier!
Oct 10, 2014
* First version!
Finally I would like to give out a big thank you to @death2all110 for doing extensive testing for me, as well as providing me with the system dump from the ADT-1. I couldn't have done this without him!
Enjoy!
Great! Works flawlessly on my Ouya (CM11). Run on boot via ScriptManager.
If you need help with Netflix you know where to find me!
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
krosk said:
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
Click to expand...
Click to collapse
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
@death2all110 I probably will, yes. It seems to be restricted to the US for now - I've tried hard-coding a proxy in the code, which makes it go further, but not far enough for it to work. I'll get back to you when I have something for you to test!
HomerSp said:
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
Click to expand...
Click to collapse
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
krosk said:
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
Click to expand...
Click to collapse
Of course, I completely misread your post. Sorry!
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
rkirmeier said:
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
Click to expand...
Click to collapse
What version of Google play services do you have installed on the sender device? Also, a logcat from the receiver would be useful.
astro128 said:
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Click to expand...
Click to collapse
I don't own a Nexus Q myself, so I won't be able to do any testing. The Q is running a full Android system, right? If it is, the receiver app most likely requires a later API version, or the Q doesn't support some of the features the cast receiver app requires to function.
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
rkirmeier said:
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
Click to expand...
Click to collapse
You can attach the logcat to your post, or use something like pastie.org or pastebin.com
Log attached to this post.
rkirmeier said:
Log attached to this post.
Click to expand...
Click to collapse
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
That is correct. I'll work on getting the log from my minix and tablet tonight as they both have the receiver installed and do the same thing.
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
Minix log attached...
Thanks!
rkirmeier said:
Minix log attached...
Thanks!
Click to expand...
Click to collapse
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
HomerSp said:
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
Click to expand...
Click to collapse
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
rkirmeier said:
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
Click to expand...
Click to collapse
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
HomerSp said:
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
Click to expand...
Click to collapse
I confirmed USB Debugging is enabled. Wouldn't this be required to even make the connection?
Installing Nethunter
1. Download and install magisk module called KaliNethunter
2. Go to offensive security website and download generic arm64 nethunter image
3. Extract and install following apps from downloaded archive: NetHunter.apk, NetHunterTerminal.apk.
4. Extract kalifs-arm64-full.tar.xz on your phone.
5. Open NetHunter app and grant permissions and root permission
6. Open hamburger menu, select Kali Chroot Manager, select location where you had extracted kalifs-arm64-full.tar.xz and start installing chroot
7. Wait some time (~10 minutes)
8. Start chroot. Now you can use nethunter app and nethunter terminal app.
Enabling monitor mode on built-in wifi module
0. I could not enable it on custom roms. On stock 082 it worked, but there are some problems. Contact me if you have any info about enabling monitor mode on roms except stock.
1. Open nethunter app, go to custom commands
2. Click run on "Start wlan0 in monitor mode"
3. Now wlan0 is in monitor mode. I've tried capturing handshakes using airodump-ng, it worked. However, when I tried deauth attack using aireplay-ng, wlan0 was stuck on channel 0.
4. Note that if you turn wifi on/off or try to disable monitor mode, your phone will turn off.
5. Alternative way: you can enable monitor mode using other apps, like penmon. However, your phone will still turn off if you do anything to wlan0 while it is in monitor mode.
Using external wifi adapter
0. Your wifi adapter must support monitor mode. External adapter won't work without a kernel that supports it. I've built one based on darkonah (many thaks to @travarilo ). Atheros HTC based adpaters are not supported!
1. Flash the attached kernel (the latest version is NH_kernel_v2.zip).
2. Now you can use your exernal adapter.
Enabling monitor mode on external adapter
0. I only tested it with Alfa AWUS036NH (chipset ralink3070), but the instruction may be similar for other adapters
1. First, let's install firmware for your wireless adapter
Code:
apt update
apt upgrade
apt install firmware-ralink
2. Execute command iwconfig and check if your adapter is present there. For me it was displayed as wlan1
3. Turn your adapter off and put it into monitor mode
Code:
ifconfig wlan1 down
airmon-ng start wlan1
4. Check airmon-ng output. It will say you that your adapter is now in monitor mode and will give you new adapter's name (for me it was wlan1mon)
5. Now you can use monitor mode on your adapter (for example, to run airodump-ng)
P.S.: Do it at your own risk and don't use this info in illegal purposes. Only you are responsible for your actions.
Thank you very much sir! Really appreciate your work time and efforts!
Just one small query about what rom and firmware are you using?
Heven11 said:
Thank you very much sir! Really appreciate your work time and efforts!
Just one small query about what rom and firmware are you using?
Click to expand...
Click to collapse
Right now I'm using stock rom 082 (and fw 082, respectively), but it would be great if you tested this guide on any custom rom (if you are not going to use built-in wifi module. If you are, I recommend you to use stock rom)
Ok thank you!
tutaf said:
Installing Nethunter
1. Download and install magisk module called KaliNethunter
2. Go to offensive security website and download generic arm64 nethunter image
3. Extract and install following apps from downloaded archive: NetHunter.apk, NetHunterTerminal.apk.
4. Extract kalifs-arm64-full.tar.xz on your phone.
5. Open NetHunter app and grant permissions and root permission
6. Open hamburger menu, select Kali Chroot Manager, select location where you had extracted kalifs-arm64-full.tar.xz and start installing chroot
7. Wait some time (~10 minutes)
8. Start chroot. Now you can use nethunter app and nethunter terminal app.
Enabling monitor mode on built-in wifi module
0. I could not enable it on custom roms. On stock 082 it worked, but there are some problems. Contact me if you have any info about enabling monitor mode on roms except stock.
1. Open nethunter app, go to custom commands
2. Click run on "Start wlan0 in monitor mode"
3. Now wlan0 is in monitor mode. I've tried capturing handshakes using airodump-ng, it worked. However, when I tried deauth attack using aireplay-ng, wlan0 was stuck on channel 0.
4. Note that if you turn wifi on/off or try to disable monitor mode, your phone will turn off.
5. Alternative way: you can enable monitor mode using other apps, like penmon. However, your phone will still turn off if you do anything to wlan0 while it is in monitor mode.
Using external wifi adapter
0. Your wifi adapter must support monitor mode. External adapter won't work without a kernel that supports it. I've built one based on darkonah (many thaks to @travarilo ). Later I'll update this post to list adapters that should be supported by tis kernel.
1. Flash the attached kernel.
2. Now you can use your exernal adapter.
Enabling monitor mode on external adapter
0. I only tested it with Alfa AWUS036NH (chipset ralink3070), but the instruction may be similar for other adapters
1. First, let's install firmware for your wireless adapter
Code:
apt update
apt upgrade
apt install firmware-ralink
2. Execute command iwconfig and check if your adapter is present there. For me it was displayed as wlan1
3. Turn your adapter off and put it into monitor mode
Code:
ifconfig wlan1 down
airmon-ng start wlan1
4. Check airmon-ng output. It will say you that your adapter is now in monitor mode and will give you new adapter's name (for me it was wlan1mon)
5. Now you can use monitor mode on your adapter (for example, to run airodump-ng)
P.S.: Do it at your own risk and don't use this info in illegal purposes. Only you are responsible for your actions.
Click to expand...
Click to collapse
I love it when you put 0 first instead of 1. A true caffeine blooded being. Btw im on .087 fw ver (X00TDB var.). Gonna try the image out and see if internal wifi module works. Im running BT5 on my xp era machine.
ImperialNuggets said:
I love it when you put 0 first instead of 1. A true caffeine blooded being. Btw im on .087 fw ver (X00TDB var.). Gonna try the image out and see if internal wifi module works. Im running BT5 on my xp era machine.
Click to expand...
Click to collapse
What is BT5? I got it
does the kernel support atheros chipset: TL-WN722N v1?
ive done everything i could but my device still dont detect my adapter
...
apt update
apt upgrade
apt install firmware-atheros
airmon-ng... nothing..
xda_u$er said:
does the kernel support atheros chipset: TL-WN722N v1?
ive done everything i could but my device still dont detect my adapter
...
apt update
apt upgrade
apt install firmware-atheros
airmon-ng... nothing..
Click to expand...
Click to collapse
I had some problems building kernel, so I had to disable support for Atheros HTC based cards. You can try to add it as a loadable kernel module.
0. Flash the attached kernel, download and extract module file (ath9k_htc.ko) from zip
1. Go to NetHunter Terminal app and start androidsu shell
2. Go to the folder where you had extracted ath9k_htc.ko. For example:
Code:
cd /storage/emulated/0/Download
3. Install the module
Code:
insmod ath9k_htc.ko
If it throws error like "no such file or directory", check dmesg
4. Check if the module is installed
Code:
lsmod
You should see the name of the module (ath9k_htc) and its size (check attached screenshot)
5. Now try executing airmon-ng in kali terminal.
Module doesn't persist between reboots. Let me know if it works for you, I'll try to automate module installation process.
Throws me error..
xda_u$er said:
Throws me error..
Click to expand...
Click to collapse
Could you please execute dmesg command right after getting this error and show me the output?
its huge, so I put it in notepad
xda_u$er said:
its huge, so I put it in notepad
Click to expand...
Click to collapse
Sorry, my bad, I gave you the module for the previous kernel build (it has different name, that is why insmod throws error). Please try installing the attached module. If anything goes wrong, send me dmesg again.
@xda_u$er did it work?
Well, the installation went ok, but the external adapter its not working, it is not recognized by the device.
xda_u$er said:
Well, the installation went ok, but the external adapter its not working, it is not recognized by the device.
Click to expand...
Click to collapse
Sorry, I don't know what to do with that. You may try to find an old version (~2019) of TRB kernel, I've heard that its developer tried to enable Atheros HTC based adapters support.
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Heven11 said:
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Click to expand...
Click to collapse
As far as I know, it does. I haven't tried any usb attacks, but I'm going to.
Heven11 said:
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Click to expand...
Click to collapse
I've enabled everything that should be enabled to make bluetooth attacks work, but they don't. The adapter is recognized by the system, but nethunter app doesn't see it. I would be very thankful if you tested bluetooth with new kernel. Btw, usb attacks work with new kernel too. I've tried launching firefox on my PC, it worked. This is a really cool thing
Firstly sorry for late reply! I had to reset my device since I was testing some android 11 rom and Thank you sooooo much for V2 of this kernel,usb/hid is working like a charm but I haven't tried bluetooth yet but will definitely try it soon since I don't know how to do it!
Please continue the development of this kerneland remember you are a legend!
Thank you again!
Hii! I want to try Kali nethunter on my device but there are many bugs that I am facing my internet is not working in Kali not monitor mode is working!
Can you please make a nethunter ROM!please
Or give me a backup of your ROM KERNEL AND FIRMWARE THAT I can flash through TWRP !
Please!
PS. Currently I am using Android 10 corvus os and nethunter is not working!