using tp link tl-wn722n reboots phone

[Psychoghost]

Well I can't use my tp link because of this kernel panic or issue with the firmware or anything

[binkybear]

Can you please provide more information. Is this the Nexus 5? Is it only the tplink? What android version are you using. Did you do install with windows installer? When does the reboot happen, every time you plug in usb? Can you do a: cat /proc/last_kmsg > /sdcard/panic.txt

A bit more information is needed to figure out what the issue might be.

[Psychoghost]

It is a nexus 5 and it happens right when I put the tplink in...I downloaded the image directly I'm on stock 4.4.4 and I don't know how to log this

[maximcherny]

Same thing happens on a Nexus 7, Android 4.4.3 (KTU84L - Google Factory Image) running NH 1.0.2. As soon as the dongle is plugged in the device reboots.

I can power the device off prior to connecting the dongle, connect while powered off and then power on. In this case, the green light on the dongle lights up indicating it's active.

However, when I SSH into Kali from another machine on the same network I can't see the interface in the list and the terminal shell is quite unresponsive.

[maximcherny]

Furthermore, same thing happens when I unplug the dongle from the device. I installed NH using a Kali machine.

Here is a extract from last_kmsg:

[  337.236419] [<c06571a0>] (hdd_netdev_notifier_call+0xc0/0x1a0) from [<c009c768>] (notifier_call_chain+0x38/0x68)
[  337.236846] [<c009c768>] (notifier_call_chain+0x38/0x68) from [<c009c7b8>] (raw_notifier_call_chain+0x14/0x18)
[  337.237243] [<c009c7b8>] (raw_notifier_call_chain+0x14/0x18) from [<c0826cc0>] (rollback_registered_many+0x1c8/0x2e0)
[  337.237670] [<c0826cc0>] (rollback_registered_many+0x1c8/0x2e0) from [<c0828adc>] (unregister_netdevice_many+0x18/0x60)
[  337.238067] [<c0828adc>] (unregister_netdevice_many+0x18/0x60) from [<c09994d0>] (ieee80211_remove_interfaces+0x98/0xb8)
[  337.238494] [<c09994d0>] (ieee80211_remove_interfaces+0x98/0xb8) from [<c098b0d4>] (ieee80211_unregister_hw+0x44/0xec)
[  337.238922] [<c098b0d4>] (ieee80211_unregister_hw+0x44/0xec) from [<c04884dc>] (ath9k_htc_disconnect_device+0x4c/0x8c)
[  337.239196] [<c04884dc>] (ath9k_htc_disconnect_device+0x4c/0x8c) from [<c0481dd8>] (ath9k_hif_usb_disconnect+0x4c/0x114)
[  337.239654] [<c0481dd8>] (ath9k_hif_usb_disconnect+0x4c/0x114) from [<c04c3694>] (usb_unbind_interface+0x58/0x158)
[  337.240081] [<c04c3694>] (usb_unbind_interface+0x58/0x158) from [<c03b3ec4>] (__device_release_driver+0x7c/0xbc)
[  337.240478] [<c03b3ec4>] (__device_release_driver+0x7c/0xbc) from [<c03b3f20>] (device_release_driver+0x1c/0x28)
[  337.240905] [<c03b3f20>] (device_release_driver+0x1c/0x28) from [<c03b39b4>] (bus_remove_device+0xf8/0x114)
[  337.241302] [<c03b39b4>] (bus_remove_device+0xf8/0x114) from [<c03b19bc>] (device_del+0x108/0x16c)
[  337.241729] [<c03b19bc>] (device_del+0x108/0x16c) from [<c04c17a0>] (usb_disable_device+0xac/0x20c)
[  337.242126] [<c04c17a0>] (usb_disable_device+0xac/0x20c) from [<c04b9d74>] (usb_disconnect+0x98/0x114)
[  337.242401] [<c04b9d74>] (usb_disconnect+0x98/0x114) from [<c04bc118>] (hub_thread+0x7ec/0x12ac)
[  337.242797] [<c04bc118>] (hub_thread+0x7ec/0x12ac) from [<c00972b4>] (kthread+0x84/0x94)
[  337.243225] [<c00972b4>] (kthread+0x84/0x94) from [<c000f8f4>] (kernel_thread_exit+0x0/0x8)
[  337.243621] Code: e59f00d4 e3a010f4 ebe88bcf ea00002b (e5d531ac) 
[  337.247863] ---[ end trace f88192a652c00f86 ]---
[  337.248229] Kernel panic - not syncing: Fatal exception
[  337.248535] wcnss_8960: crash shutdown : 0
[  340.755401] Rebooting in 5 seconds..
[  345.764495] Going down for restart now
[  345.764923] in panic

No errors detected
Boot info:
Last boot reason: Panic

[offensive-security]

With the Nexus 7 2013 model, this is a known issue, as documented here http://nethunter.com/issues/

[maximcherny]

Ah, of course. Still does not explain why I can't see it in the interface list when connecting using a method described above.

[maximcherny]

Okay, sometimes in the excitement of the moment one can forget the most basic of things. The dongle works, the interface needs to be brought up when it's not available.

For now, the OTG disconnect workaround is to power off the device and unplug. Inconvenient, but somewhat more graceful.

[Psychoghost]

Dam i tried changing kernel settings but still the reboot