Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supports Android 7.0 to 8.1
Recommended for all WiFi tools to work is Android v7.1.2. Installation steps is described further below.
FEATURES:
Features from @flar2 kernel which this is built on.
All credits to him for hosting awesome kernel sources.
* Easy installation and setup with Aroma installer
* Wake Gestures (sweep2wake and doubletap2wake)
* Sweep2sleep
* Overclock or underclock CPU
* Advanced color control (RGB, Saturation, Value, Contrast, Hue)
* Sound control (headphones, speaker and mic)
* Backlight dimmer option
* High Brightness Mode option
* Option to disable touchboost
* NTFS r/w and exFAT support
* Option to disable fsync
* Adjustable vibration
* MultiROM support
* WireGuard support
* Does not force encryption
* Does not modify system partition
* Compatible with systemless root and Android Pay
Added by me on top:
* Big collection of wireless drivers & firmware
* Big collection of ethernet USB, USB hubs and general USB adapters of various kinds.
* rtl8812au drivers from https://github.com/aircrack-ng/rtl8812au
* rtl8188eus drivers from https://github.com/aircrack-ng/rtl8188eus (added but not working yet)
* "linux-firmware" built in
* CD-ROM patch
* USB HID support
* WIFI injection patches for several adapters
* Nexmon support with both monitor mode & frame injection via internal adapter
* SELINUX patched
* USB OTG (w/ACA) is supported
* linux-stable patches merged inside
* wireless-tools (iw, iwconfig, ifconfig etc) is bulilt into Android /system (packing them in a new release in a few days)
[ TODO / W.I.P ]
* Add a bunch of compiled binaries
* Change to anykernel3 installer
* Merge more from linux-stable
* See if we may fix the Android 8.1 issue
[ Images / Media ]
Running wifite2 through SSH with JuiceSSH
Running airodump-ng using the external AWUS036ACH. - Hijacker packs aircrack-ng suite, reaver wps and mdk3 but also has a cracking & scripting option.
A few of my tools, for me WiFi and MITM is important.
[ Installation ]
We recommend you start from scratch and setup the device, full restore to fresh v7.1.2 is recommended,
even though this kernel supports Android 8.1 too, some of the tools can't right now unfortunately.
1. Find the original, stock firmware over here and choose the latest 7.1.2 (N2G48C, Aug 2017)
2. Press & hold VOLUME DOWN [ - ] and POWER to reboot to bootloader
3. Flash the stock firmware with "flash-all.bat" on Windows or "flash-all.sh" for Linux users
4. Boot into stock and ENABLE developer setting (the menu you get after SPAMMING 5-7 times on the "Build Number" in "Settings" and "About Phone"
-- here you may use the phone to download the kernel zip for flashing afterwards. or use "adb sideload" later on.
5. With ADB enabled, reboot to BOOTLOADER
6. Get TWRP recovery from over here and flash it with "fastboot flash recovery twrp-3.3.1-0-angler.img"
7. VOLUME UP or DOWN and choose "Recovery Mode"
8. In recovery mode
9. Either flash the kernel zip (if you downloaded in the phone before reboot), or go to "Advanced" and use "ADB Sideload"
10. If you ended up with "ADB Sideload" open Terminal or "Minimal ADB" prompt (Windows) and flash the kernel with "adb sideload < file.zip >
11. After flashing the kernel, you also would need root. We suggest using Magisk root which you may find over here
And flash the latest stable release. Same method as earlier.
12. Open "Magisk Manager" and search for "busybox" -- Install it and reboot again in order to activate it.
13. Start installing apps, e.g Hijacker official link
--- Nexmon and it's tools ain't a bad choice either, the WiFi SoC is BCM4358 and supported. Grab it over here
14. A Terminal would also be useful here, grap it from NetHunter repo right about here
15. The NetHunter App should also be in place. Direkt link
16. zANTI from Zimperium is loaded with nmap with NSE scripts/plugins and is pretty nifty one. grab it right here!
17. cSploit is available right here (it's getting outdated, but a few things work).
[ Downloads ]
https://github.com/kimocoder/android_static_tools/raw/master/nethunter_angler.zip
[ SOURCE ]
http://github.com/kimocoder/android_kernel_nexus6p
The recommended toolchain for this kernel sources is gcc-linaro-5.4.1-2017.05-x86_64_aarch64-linux-gnu
[ Tools ]
wifite2 - https://www.github.com/kimocoder/wifite2 (newly added to Kali / NetHunter repos)
Hijacker - https://github.com/chrisk44/Hijacker
aircrack-ng - https://aircrack-ng.org
Nexmon - https://github.com/seemoo-lab/nexmon
Magisk - https://github.com/topjohnwu/Magisk
NetHunter - https://gitlab.com/kalilinux/nethunter
zANTI - https://www.zimperium.com/
cSploit - http://wwwcsploit.org
[ Social Media ]
Follow me on Twitter
[ Credits ]
@flar2
@binkybear
@jcadduono
@aircrack-ng
@nathanchance @nexmon
@chrisk44
@NetHunter
@Re4son
kriswebdev at GitHub
kimocoder said:
[...]
Big collection of wireless drivers & firmware
* Big collection of ethernet USB, USB hubs and general USB adapters of various kinds.
* rtl8812au drivers from https://github.com/aircrack-ng/rtl8812au
[...]
Click to expand...
Click to collapse
Hi master!
First of all, thank you very much for this nice work!!
Downloading asap (the href of the URL seems broken. One need to copy paste the url)
Off-topic:
it seems that you have got a lot of knowledge when it comes to android and wifi drivers, maybe you are the one, who could help me:
I would like to add a wifi-driver for "Broadcom BCM94352Z" into "android-x86 9.0-rc1".
On Linux one would update/install "bcmwl-kernel-source" to get the card running.
On Android-x86 I can scan for wifis via terminal.
But I cant neither connect via terminal nor scan via the UI.
Any help would be AMAZING.
please install video, I do not understand English, a video can guide .. ???
@kimocoder
As per instructions, did I completely start from scratch, but wasn't sure where the chroot has to be installed..I copied the latest kalifs over to the SDcard and extracted it from there.. A direct download via the Nethunter.apk wasn't possible.
After I rebooted the Nh terminal is showing the kali chroot, but JuiceSSH via localhost (Snippet 'su -c bootkali_login').
The phone shows the wlan adapter with the according chipset via 'lusb', but cannot be set into Monitor mode with airmon-ng.
Best regards
Could you specify and/or correct the link to the kernel source, please.
As I wrote before, didn't I have much success in getting a external Wlan adapter to work.
After testing the kernel, I am unable to get the phone back to stock.
At startup I got constantly bootloop.Even after flashing the latest 7.12 and 8.1 factory rom and trying various things, like erasing/formatting the various partitions , trying to boot into TWRP..
I flashed the last 8.1 release last(before testing several times the latest 7.1 release and several times the 7.12 version, which is mentioned in OP, tried to boot into Twrp after successful flashing, Bootloader is unlocked and fastboot menu working.
It seems that userdata is creating some issues.
Help would be appreciated.
:>
PS
What for a wlan adapter are you using?
I have followed your instructions to a T but have had a few issues / questions. I've had very little issues getting nethunter (minux nexmon/hijacker) on several other devices.
Nexmon seems to be working but is there a way to keep the firmware and libraries installed permanently? I could not put them into the default /su/xbin and /su/lib, I got error messages so I put them into /system/xbin and /system/lib but it's not persistent.
Using the version of the nethunter app, a chroot can not be downloaded.
I have used the HiJacker that you posted and the latest beta from the Official git project and it keeps freezing the phone. Not sure what settings may need to be changed but no collection with it works.
When I plug an exfat and ntfs drive into the phone it wants to format the drive and if I don't it's can't mount the drive.
Hello download link not working
Hey there,
i ve got a few Questions. I ve spend a lot of time to test the Nexus 6p with different Setups and Android Versions and finally i decided to go with the latest los 14.1.
Your nexmon and Hijacker port are working with the internal wlan Adapter even in 5GHz.
But Default your nexmon installs the Tools and Firmware non persistent, this must done on every reboot. But thats very ok.
But, i am currently on nethunter 2020.1, on the Default kernel my tplink tl-wn822n (rtl8192cu i think) works out of the box.
With your kernel my tplink does not work because perhaps there is no modul Auto loading. I can insmod the rtl8812au for this device i have too, but when i try the 8192 for the tplink this does not work.
And also with your kernel the 8812au Adapter works but when wifite is running an atack the device reboots. Sooo, Long Story short:
Thanks for your hard work and perhaps there will be an update for this kernel.
P.S.: here is the correct link for the Tools
https://github.com/kimocoder/android_static_tools
Nick_Speed said:
But Default your nexmon installs the Tools and Firmware non persistent, this must done on every reboot. But thats very ok
Click to expand...
Click to collapse
Load the Nexmon app from the Nethunter store, because this seems to be a installation path issue.
Even with my antique Samsung Galaxy S2, which hits you with dozens of other problems and even the stupid addonsu has problems with the root recognition within Nexmon.
Hit the button by app start just again and everything, should the install not being screwed up beforehand, are patched firmware, utils etc.. in my experience detected.
But, i am currently on nethunter 2020.1, on the Default kernel my tplink tl-wn822n (rtl8192cu i think) works out of the box.
Click to expand...
Click to collapse
I assume that you meant the "working" setup..
These 2 kernel are for total differrent distributions and shouldn't be used in tandem; mkay..
With your kernel my tplink does not work
Click to expand...
Click to collapse
The adapter resp supported bands and this particular driver is quite old and like I wrote before, not a guarantee that it works in kimocoder's kernel beside; because one in another setup of you did work.That other kernel is LOS based for example, this one stock.
I read a couple months ago, that the RTL8192cu, apart the age, still unstable and buggy is/can be..but the driver is in the kernel..no clue, bud.
because perhaps there is no modul Auto loading. I can insmod the rtl8812au for this device i have too, but when i try the 8192 for the tplink this does not work.
Click to expand...
Click to collapse
Unfortunately did the device age finally caught up shortly after the first installation "try outs", so I didn't have time to try one of my nics with the Realtek RTL8812AU driver.
Your TP-Link should be detected without 'insmod', I am fairly certain.
Did you use iw-tools or airmon-ng for the 8812au?
If you look over kimocoder's repo, you see the regarding driver at 2 or 3 place.
Scroll down and look the commands up, if you have no experience with iw.
I am sure that kimocoder will get back if, he has the time.I am thinking of buying a new one, so let's hope he has time in the foreseeable future to get the kinks out.. ;E
@kimocoder It will spare many user from eventual screwing up their devices in regard to the install from a fairly newer stock release to an older..just look in the Nexus's sub-forum.
Battery issue is not that fantastic whatever, but this is not that safe, man. :/
Would it be possible, as long as the Oreo support is not in dry sheets, to use a stock like custom rom? Pure Nexus comes into my head should be the same, but without the eventuality of messing with the stock files (no idea)..?
thx for your Reply :good:
UsPdSr said:
Load the Nexmon app from the Nethunter store, because this seems to be a installation path issue.
Click to expand...
Click to collapse
Nope, from the store nexmon doesnt start at all, the app forced to close.
UsPdSr said:
These 2 kernel are for total differrent distributions and shouldn't be used in tandem; mkay..
The adapter resp supported bands and this particular driver is quite old and like I wrote before, not a guarantee that it works in kimocoder's kernel beside; because one in another setup of you did work.That other kernel is LOS based for example, this one stock.
I read a couple months ago, that the RTL8192cu, apart the age, still unstable and buggy is/can be..but the driver is in the kernel..no clue, bud.
Click to expand...
Click to collapse
Thats a Point i thougth you got me, of Course i am not on stock like kimocoder wrote in his Installation steps, and so his kernel does not work well with LOS.
So i went to stock and setuped everything and...
the behavior is the same.
Here is some Output from dmesg with his kernel on stock:
For the tplink:
[ 696.723240] hub 2-0:1.0: 1 port detected
[ 697.039016] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 697.056824] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 697.056884] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 697.056910] usb 1-1: Product: USB WLAN
[ 697.056934] usb 1-1: Manufacturer: Realtek
[ 697.056957] usb 1-1: SerialNumber: 00e04c000001
For the CLS (with 88XX):
[ 833.598100] xHCI xhci_add_endpoint called for root hub
[ 833.598119] xHCI xhci_check_bandwidth called for root hub
[ 833.599024] hub 2-0:1.0: USB hub found
[ 833.599077] hub 2-0:1.0: 1 port detected
[ 833.911239] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 833.926677] usb 1-1: New USB device found, idVendor=0bda, idProduct=8812
[ 833.926737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 833.926764] usb 1-1: Product: 802.11n NIC
[ 833.926788] usb 1-1: Manufacturer: Realtek
[ 833.926811] usb 1-1: SerialNumber: 123456
And no module is loading.
After insmod 88XX.ko the wlan1 interface appears, i ve read on GitHub About the steps with iw and monitor mode and did this, but...
With wifite the device reboots on this step: PMKID CAPTURE: Waiting for PMKID (29s) (After unplugging the Adapter the devices reboots also...)
So i installed nethunter 2020.1 with the Default kernel on stock and when i Plugin my tplink dmesg says this:
[ 213.223653] xHCI xhci_add_endpoint called for root hub
[ 213.223663] xHCI xhci_check_bandwidth called for root hub
[ 213.224293] hub 1-0:1.0: USB hub found
[ 213.224329] hub 1-0:1.0: 1 port detected
[ 213.224536] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 213.224554] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 213.224615] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 213.224624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 213.224631] usb usb2: Product: xHCI Host Controller
[ 213.224638] usb usb2: Manufacturer: Linux 3.10.73-nethunter-angler-1.1 xhci-hcd
[ 213.224644] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 213.225498] xHCI xhci_add_endpoint called for root hub
[ 213.225508] xHCI xhci_check_bandwidth called for root hub
[ 213.225990] hub 2-0:1.0: USB hub found
[ 213.226022] hub 2-0:1.0: 1 port detected
[ 213.537162] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 213.551861] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 213.551890] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.551898] usb 1-1: Product: USB WLAN
[ 213.551906] usb 1-1: Manufacturer: Realtek
[ 213.551913] usb 1-1: SerialNumber: 00e04c000001
[ 213.558318] rtl8192cu: Chip version 0x11
[ 213.615218] rtl8192cu: MAC address: c4:6e:1f:25:f5:4a
[ 213.615251] rtl8192cu: Board Type 0
[ 213.615398] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 213.615657] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 213.640232] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[ 213.643063] rtlwifi: wireless switch is on
[ 213.742373] SELinux: initialized (dev fuse, type fuse), uses mountpoint labeling
without insmod or something else. So...
I will wait what time will bring. I Count on this devices because its performant and the internal Adapter works even in 5Ghz with the Tools.
And sorry for my bad english, its not my native language.
@Nick_Speed
No need to apologise for possible language difficulties, mate.
The dmesg output reminds me of old ones with this device, which showed similar problems.
So it seems that we have to wait for the graciousness that kimocoder or somebody else will look into this.
I thought of building one in the meantime, but I have build only one kernel for android so far, so I consider myself therefore definitely still a beginner.
From what I read is the integration of the capabilities of Nexmon important..I had quite problems to build a kernel for the hammerhead.
Contrary to some opinions is it not that easy to build a kernel with Kali's main functions for Nexus devices.
I will definitely think about it and look over my schedule, but I couldn't accomplish it in the next week(s).Especially with the integration of Nexmon.
Let's hope that the dev comes around, right. :/
I forgot to ask what do you meant with the 2020.1 builds of Nethunter?
How did you install the chroot?
You thought to wipe and format everything, before starting over, right?
UsPdSr said:
I forgot to ask what do you meant with the 2020.1 builds of Nethunter?
How did you install the chroot?
Click to expand...
Click to collapse
I mean the release of kali nethunter 2020.1. It is a flashable zip for twrp. It includes everythink you Need. Nethunter App, Store, chroot, kernel. Ist the official one from the official site.
UsPdSr said:
You thought to wipe and format everything, before starting over, right?
Click to expand...
Click to collapse
Of Course. Always. And for stock i use the factory Image from Google. This means fastboot and flashall with the -w (wipe) Option.[/QUOTE]
Nick_Speed said:
I mean the release of kali nethunter 2020.1. It is a flashable zip for twrp. It includes everythink you Need. Nethunter App, Store, chroot, kernel. Ist the official one from the official site.
Click to expand...
Click to collapse
Yeah, sure.
I was talking about the chroot-installation with this kernel here?
Of Course. Always. And for stock i use the factory Image from Google. This means fastboot and flashall with the -w (wipe) Option.
Click to expand...
Click to collapse
Alright.
For the future: it's always better to wipe the former installation via Twrp and if you flash a stock image, don't use those crappy scripts from Google.
First is it inherently better to use fastboot/adb one command at a time and the '-w' in the flashall-script can by our BLOD-prone devices cause a bootloop, if the restart goes wrong.
Do u have any good links that r working to download the kernel
fowler82 said:
Do u have any good links that r working to download the kernel
Click to expand...
Click to collapse
Yeah, there seems to be some mess with the bbc code.
Here you go
->
https://github.com/kimocoder/android_static_tools/blob/master/nethunter_angler.zip
The rest of the apps and some pics from kimocoder can be found here
->
https://github.com/kimocoder/android_static_tools
Nick_Speed said:
thx for your Reply :good:
Nope, from the store nexmon doesnt start at all, the app forced to close.
Thats a Point i thougth you got me, of Course i am not on stock like kimocoder wrote in his Installation steps, and so his kernel does not work well with LOS.
So i went to stock and setuped everything and...
the behavior is the same.
Here is some Output from dmesg with his kernel on stock:
For the tplink:
[ 696.723240] hub 2-0:1.0: 1 port detected
[ 697.039016] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 697.056824] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 697.056884] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 697.056910] usb 1-1: Product: USB WLAN
[ 697.056934] usb 1-1: Manufacturer: Realtek
[ 697.056957] usb 1-1: SerialNumber: 00e04c000001
For the CLS (with 88XX):
[ 833.598100] xHCI xhci_add_endpoint called for root hub
[ 833.598119] xHCI xhci_check_bandwidth called for root hub
[ 833.599024] hub 2-0:1.0: USB hub found
[ 833.599077] hub 2-0:1.0: 1 port detected
[ 833.911239] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 833.926677] usb 1-1: New USB device found, idVendor=0bda, idProduct=8812
[ 833.926737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 833.926764] usb 1-1: Product: 802.11n NIC
[ 833.926788] usb 1-1: Manufacturer: Realtek
[ 833.926811] usb 1-1: SerialNumber: 123456
And no module is loading.
After insmod 88XX.ko the wlan1 interface appears, i ve read on GitHub About the steps with iw and monitor mode and did this, but...
With wifite the device reboots on this step: PMKID CAPTURE: Waiting for PMKID (29s) (After unplugging the Adapter the devices reboots also...)
So i installed nethunter 2020.1 with the Default kernel on stock and when i Plugin my tplink dmesg says this:
[ 213.223653] xHCI xhci_add_endpoint called for root hub
[ 213.223663] xHCI xhci_check_bandwidth called for root hub
[ 213.224293] hub 1-0:1.0: USB hub found
[ 213.224329] hub 1-0:1.0: 1 port detected
[ 213.224536] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 213.224554] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 213.224615] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 213.224624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 213.224631] usb usb2: Product: xHCI Host Controller
[ 213.224638] usb usb2: Manufacturer: Linux 3.10.73-nethunter-angler-1.1 xhci-hcd
[ 213.224644] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 213.225498] xHCI xhci_add_endpoint called for root hub
[ 213.225508] xHCI xhci_check_bandwidth called for root hub
[ 213.225990] hub 2-0:1.0: USB hub found
[ 213.226022] hub 2-0:1.0: 1 port detected
[ 213.537162] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 213.551861] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 213.551890] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.551898] usb 1-1: Product: USB WLAN
[ 213.551906] usb 1-1: Manufacturer: Realtek
[ 213.551913] usb 1-1: SerialNumber: 00e04c000001
[ 213.558318] rtl8192cu: Chip version 0x11
[ 213.615218] rtl8192cu: MAC address: c4:6e:1f:25:f5:4a
[ 213.615251] rtl8192cu: Board Type 0
[ 213.615398] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 213.615657] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 213.640232] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[ 213.643063] rtlwifi: wireless switch is on
[ 213.742373] SELinux: initialized (dev fuse, type fuse), uses mountpoint labeling
without insmod or something else. So...
I will wait what time will bring. I Count on this devices because its performant and the internal Adapter works even in 5Ghz with the Tools.
And sorry for my bad english, its not my native language.
Click to expand...
Click to collapse
@Nick_Speed were you able to get around the device reboots on your setup? I have the same issue, and it's driving me mad!
SharkCage said:
@Nick_Speed were you able to get around the device reboots on your setup? I have the same issue, and it's driving me mad!
Click to expand...
Click to collapse
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Nick_Speed said:
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Click to expand...
Click to collapse
Thanks for the quick reply. Hopefully @kimocoder stops in for suggestions.
Nick_Speed said:
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Click to expand...
Click to collapse
You can use the Nougat Nethunter kernel for the N6p with LineageOS(RR, Omnirom, DU etc.) and Stock, or customized Stock images like PureNexus as well.
I haven't give up.Even after 25 kernel sources for Oreo, am I still developing.
Unfortunately did it seem, that the Nethunter team overwhelmed with more "recent" devices are and the Nexus not a OnePlus 7t Pro is. :E
I think it's great, beside the sucky OnePlus fondling have they achieved remarkable innovations, not only the kernel for the 800 Euro Gaming PC aka 7xy.
Like Nick_Speed said, is the internal monitor mode including the screen size, USB-C and foremost the very affordable price (I bought my second one a month ago and paid 90 Euro in great condition.Accu-health is very good and so far no issues.
I recommend commercial reseller.They ensure , at least in my case, three month guarantee and are very selective in their buying.
For now would I choose the stable kernel for 7.1-7.1.2, with with the Ternux setup(not my cup of tea - Termux=bah.Why not Terminus, JuiceSSH or something less trashy? ), or the new Nethunter UI(installer).
The optimal choice is to self build one with the python installer. In addition pick some of the features of the tools from this thread.Nexnon,Hijacker,Zanti, Wiggle and a couple you have to look up for yourself.
It sucks that we can't use devices with AC capabilities,but maybe another dev or myself come around to make this happen.
The problem is that Nexus development really sucks in regard of the modules at least.
I had more success with the Nvidia Shield K1, which was practically claimed as dead.
Many heaps
PS
It's quite difficult to get your hand on a Nano adapter with RTL8811/12/14 chipset.I compiled the current kernel with said driver, but no luck.
I have still the DU repo in my m head.Maybe I get the driver to load.
The patch from a team member didn't work.
Just some nice props^
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.