id10t Kernel v1.0
for LG G Pad 8.3 V500
Compatible with stock LG 4.2.2 roms ONLY!
This is a personal kernel build that I originally compiled to add support for Logitech Unifying receivers.
Decided to share it on here as I've seen other people looking for this as well.
Works like a charm with my Logitech K400r
If I make any further modifications as I get time, I'll definitely post them here.
Disclaimer:
Use this at your own risk. I have personally tested this build on my own device successfully.
I am not responsible for any damage or data loss encountered due whatever reason.
Please ensure that you make a full backup of your system before flashing anything.
Features\Changelog:
v 1.0 (3/16/14)
Compiled with Google Android Toolchain version 4.7 (arm-eabi-4.7)
Compiled using -o2 optimization flag
Default IO scheduler changed to Deadline
CPU governor changed to On Demand
Logitech Unifying wireless receivers support
Downloads:
v1.0
http://id10terror.net/dev/lg-v500/id10t_kernel-v1.0.zip
Mirror:
https://github.com/id10terror/id10t-kernel-v500/raw/master/id10t_kernel-v1.0.zip
Install:
Boot into TWRP recovery.
*** Make a Full backup before proceeding. ***
Flash .zip file in TWRP recovery.
Wipe Dalvik\Cache
Reboot device.
Enjoy!!
Full kernel source and config @ my Github:
https://github.com/id10terror/id10t-kernel-v500
Many Thanks to sleekmason for his how to guide that got me going in the right direction:
http://forum.xda-developers.com/showthread.php?t=2628951
2nd post is mine
Does this have init.d support? Does it also correct gamma like Bob's kernel?
Applaud the work
Sent from my LG-V500 using Tapatalk
Canadoc said:
Does this have init.d support? Does it also correct gamma like Bob's kernel?
Applaud the work
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I haven't added init.d support yet.
I believe that using version 4.7 of the cross compile toolchain fixes gamma as mentioned in other kernels (sleekAI and BOB).
good job on the kernel .
i want to try it but i keep getting a 0kb corrupted file when i download it. any help ?
Master SURGE said:
good job on the kernel .
i want to try it but i keep getting a 0kb corrupted file when i download it. any help ?
Click to expand...
Click to collapse
i uploaded it to my server.. try downloading it from there rather than the github link
http://id10terror.net/dev/lg-v500/id10t_kernel-v1.0.zip
id10terror said:
i uploaded it to my server.. try downloading it from there rather than the github link
http://id10terror.net/dev/lg-v500/id10t_kernel-v1.0.zip
Click to expand...
Click to collapse
thank you , that did it .
Is it possible to add overclock to this Kernel? Thanks mate!
im_high_tech said:
Is it possible to add overclock to this Kernel? Thanks mate!
Click to expand...
Click to collapse
+1
Also sleekmason had been doing some great things with his kernel but it is for the gpe edition only. Was hoping maybe you can collaborate add a way to get some of his tweaks and init .d support. Thanks
Sent from my LG-V500 using Tapatalk
I've been extremely busy lately but should have a little time this week to add init.d support. @sleekmason has been very open about his kernel changes and shared a few things with me. I should be able to incorporate some of his features since they've gotten a good reception on the v510.
Awesome can't wait
Sent from my LG-V500 using Tapatalk
When I try use my external HD, doesn't work. Looking dmesg log I found this:
<6>[ 1618.034393 / 03-25 08:36:36.152] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<3>[ 1618.279632 / 03-25 08:36:36.393] usb 1-1: device descriptor read/all, error -71
<6>[ 1618.394378 / 03-25 08:36:36.513] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<3>[ 1618.545715 / 03-25 08:36:36.663] usb 1-1: device v1058 p0748 is not supported
<6>[ 1618.545806 / 03-25 08:36:36.663] usb 1-1: New USB device found, idVendor=1058, idProduct=0748
<6>[ 1618.545898 / 03-25 08:36:36.663] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
<6>[ 1618.546020 / 03-25 08:36:36.663] usb 1-1: Product: My Passport 0748
<6>[ 1618.546112 / 03-25 08:36:36.663] usb 1-1: Manufacturer: Western Digital
<6>[ 1618.546173 / 03-25 08:36:36.663] usb 1-1: SerialNumber: 57583531453433434C464438
<6>[ 1618.547454 / 03-25 08:36:36.663] scsi12 : usb-storage 1-1:1.0
<6>[ 1618.580017 / 03-25 08:36:36.693] usb 1-1: USB disconnect, device number 3
<3>[ 1618.834503 / 03-25 08:36:36.953] hub 1-0:1.0: unable to enumerate USB device on port 1
Is possible fix it?
wagneremanuel said:
When I try use my external HD, doesn't work. Looking dmesg log I found this:
<6>[ 1618.034393 / 03-25 08:36:36.152] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<3>[ 1618.279632 / 03-25 08:36:36.393] usb 1-1: device descriptor read/all, error -71
<6>[ 1618.394378 / 03-25 08:36:36.513] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<3>[ 1618.545715 / 03-25 08:36:36.663] usb 1-1: device v1058 p0748 is not supported
<6>[ 1618.545806 / 03-25 08:36:36.663] usb 1-1: New USB device found, idVendor=1058, idProduct=0748
<6>[ 1618.545898 / 03-25 08:36:36.663] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
<6>[ 1618.546020 / 03-25 08:36:36.663] usb 1-1: Product: My Passport 0748
<6>[ 1618.546112 / 03-25 08:36:36.663] usb 1-1: Manufacturer: Western Digital
<6>[ 1618.546173 / 03-25 08:36:36.663] usb 1-1: SerialNumber: 57583531453433434C464438
<6>[ 1618.547454 / 03-25 08:36:36.663] scsi12 : usb-storage 1-1:1.0
<6>[ 1618.580017 / 03-25 08:36:36.693] usb 1-1: USB disconnect, device number 3
<3>[ 1618.834503 / 03-25 08:36:36.953] hub 1-0:1.0: unable to enumerate USB device on port 1
Is possible fix it?
Click to expand...
Click to collapse
I'll look into this when I get a chance..
Thanks for your work on getting the Kit Kat roms for us. I am wondering whether or not there are any kernels that we can use for the KitKat versions? Perhaps one of the one that's designed to work on the AOSP roms or CyanogenMod rom's that are out there?
Sent from my LG-V500 using Tapatalk
The source uploaded by LG originally didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Really!!! Thanks. :good:
I downloaded both posted ones and there were the same and without kernel too
If you PM me the contact i can ask for an official bootloader unlock so we can finally gpe this tablet
I was studying some bootloader hack tools qflash&qboot from moto so we can unlock the bootloader but i had to destroy my own to see if method is doable lol
I"ll upload them to V510 Stock Firmware (possibly covert V500 into V510) thread so other people(advance) play with them too
Demetris said:
Really!!! Thanks. :good:
I downloaded both posted ones and there were the same and without kernel too
If you PM me the contact i can ask for an official bootloader unlock so we can finally gpe this tablet
I was studying some bootloader hack tools qflash&qboot from moto so we can unlock the bootloader but i had to destroy my own to see if method is doable lol
I"ll upload them to V510 Stock Firmware (possibly covert V500 into V510) thread so other people(advance) play with them too
Click to expand...
Click to collapse
You can contact: [email protected]
They hide behind that general email so I don't have any direct contact info other than that. Good Luck!
Sent from my LG-V500 using Tapatalk
It is work with 4.4.2 Stock ROM ?
Pixore said:
It is work with 4.4.2 Stock ROM ?
Click to expand...
Click to collapse
+1
Related
Hi Folks!
I'm a happy owner of a Galaxy Tab 10.1, and an EE engineer who frequently uses a small USB microscope while assembling boards.
I would be really happy to be able to use my Galaxy Tab as a lightweight portable screen for this microscope. This would be much more handy than having a bulky laptop stand in there.
So I've seen that the Galaxy Tab 10.1 has USB host capabilities. And after a quick verification, I've noted that the stock kernel has the uvcvideo driver builtin (the microscope is UVC compatible, actually it's a Logitech C310 hardware with added optics).
Seems like everything is in place to make it work. However when I plug the device in, I get an unrecognized USB device message popping up.
Here's the output from dmesg:
Code:
<6>[11734.027241] Board P4 : tegra_otg_en = 1<6>[11734.037361] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[11734.037391] tegra-otg tegra-otg: tegra_start_host+
<4>[11734.038884] tegra_usb_phy_open() called instance :0
<6>[11734.038966] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[11734.039001] utmi_phy_power_on() called. instance : 0
<6>[11734.040244] tegra-otg tegra-otg: Acc power on detect
<6>[11734.057205] Board P4 : tegra_acc_power token : (1,1) on
<4>[11734.057234] utmi_phy_clk_enable() called. instance : 0
<6>[11734.058757] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[11734.059016] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[11734.067158] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[11734.087920] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[11734.107159] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[11734.107282] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[11734.107306] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[11734.107326] usb usb1: Product: Tegra EHCI Host Controller
<6>[11734.107343] usb usb1: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[11734.107359] usb usb1: SerialNumber: tegra-ehci.0
<6>[11734.111805] hub 1-0:1.0: 1 port detected
<6>[11734.113078] tegra-otg tegra-otg: tegra_start_host-
<6>[11734.113101] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[11734.327059] usb 1-1: new high speed USB device using tegra-ehci and address 2
<3>[11734.592745] usb 1-1: device v046d p081b is not supported
<6>[11734.618692] host_notify: ndev name=tegra-ehci.0: from state=0 -> to state=5
<3>[11734.620877] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11734.787068] usb 1-1: new high speed USB device using tegra-ehci and address 3
<3>[11735.040504] usb 1-1: device v046d p081b is not supported
<6>[11735.076960] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.077029] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.237112] usb 1-1: new high speed USB device using tegra-ehci and address 4
<3>[11735.505766] usb 1-1: device v046d p081b is not supported
<6>[11735.528455] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.528541] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.687712] usb 1-1: new high speed USB device using tegra-ehci and address 5
<3>[11735.950203] usb 1-1: device v046d p081b is not supported
<6>[11735.978040] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.978125] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.137097] usb 1-1: new high speed USB device using tegra-ehci and address 6
<3>[11736.393178] usb 1-1: device v046d p081b is not supported
<6>[11736.417207] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.419203] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.580821] usb 1-1: new high speed USB device using tegra-ehci and address 7
<3>[11736.840702] usb 1-1: device v046d p081b is not supported
<6>[11736.866992] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.867057] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.027074] usb 1-1: new high speed USB device using tegra-ehci and address 8
<3>[11737.279441] usb 1-1: device v046d p081b is not supported
<6>[11737.306990] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.307086] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.467126] usb 1-1: new high speed USB device using tegra-ehci and address 9
<3>[11737.736913] usb 1-1: device v046d p081b is not supported
<6>[11737.758513] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.758578] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.916947] usb 1-1: new high speed USB device using tegra-ehci and address 10
[email protected]:/ $ dmesg
Then it goes on and on with the 'new device [...] unable to enumerate' messages until I unplug it.
The device is found, and early init seems to go through (VID/PID are correct) but it doesn't seem to make it to the uvcvideo driver (or the driver is rejecting it, I don't know).
I am not very savvy as regards to linux's USB stack (though I know my way around linux, having cross compiled it, and tweaked it several times for boards I design), so I'm a bit lost as to what I could further investigate to pinpoint the issue.
I am certain that uvcvideo is present (dmesg shows 'usbcore: registered new interface driver uvcvideo' after boot).
Things works fine when I plug in a USB flash drive.
Things works fine too when I plug the microscope to my linux desktop (through uvcvideo).
Any idea or advices would be greatly appreciated!
Thanks,
Theo
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi tbeauchant,
I am also looking for same , till now i didn't get any success but after going through with the code , i have seen that samsung have disable the feature of detecting a few device , in my case it says , unkown usb device and
dmesg says :: device ######(product id) ######(vendor id) not supported ,
did you get any success or any approch which you will follow.
Hello guys!
I have a Huawei Ascend Y300 phone.
What did I do? - I was trying to expand the data partition. So I tried partitioning my sd card (external flash). I was very careful not to touch anything that said blk0 in /dev/mmcblk . My external flash was at /dev/mmcblk1 and the internal flash was at /dev/mmcblk0. I was clear and was doing everything right. But, I formatted the /dev/mmcblk0p2 accidentally while copy-pasting the code :crying: :crying: :crying: :crying: ....
Then I did "reboot to recovery" from ClockWork Recovery. (I was running a CWM recovery and CyanogenMod, very smoothly with no problems in the past 2-3 months).
That was the last time my phone was ever alive. :crying:
How is it now?
Super bricked with the following symptoms
- Power button / volume buttons won't work.
- The phone won't turn on in any mode whatsoever.
When I ran lsusb, the only mode that was detected was Qualcomm modem.
I used some tutorials and QPST to do some 'fixes'. It didn't seem to work though.
The tutorial I referred to was this: http://forum.xda-developers.com/showthread.php?t=2341320
I only went till getting the phone recognized as an sd card (even when the battery is off). Power buttons still don't work. On linux it shows 4 partitions:
/dev/sdb1 20KB
/dev/sdb2 150KB
/dev/sdb3 5KB
/dev/sdb4 600KB
Unallocated Space 3.64 GB
I am stuck here now. Is there a way I could simply flash an image/kernel onto this space and get my phone working again?
I have a few questions:
1. Is this a hard-brick? Can I get my phone working again?
2. Can the partition where fastboot or boot lies be deleted?
3. If the boot manager is deleted, the phone will not know what to do when it is powered on right? So it will look as dead as it looks in my case?
4. Are there any parts of the phone that are write proof?
Any help is greatly appreciated!
Thank you so much.
p.s. would it not be so easy if phones had BIOS like computers have - on a real ROM or EEPROM and not flash ? And if android came in a bootable flash SD card; so that we could boot from SD card and install android like we install other OS's ....?
ksatyaki said:
Hello guys!
I have a Huawei Ascend Y300 phone.
What did I do? - I was trying to expand the data partition. So I tried partitioning my sd card (external flash). I was very careful not to touch anything that said blk0 in /dev/mmcblk . My external flash was at /dev/mmcblk1 and the internal flash was at /dev/mmcblk0. I was clear and was doing everything right. But, I formatted the /dev/mmcblk0p2 accidentally while copy-pasting the code :crying: :crying: :crying: :crying: ....
Then I did "reboot to recovery" from ClockWork Recovery. (I was running a CWM recovery and CyanogenMod, very smoothly with no problems in the past 2-3 months).
That was the last time my phone was ever alive. :crying:
How is it now?
Super bricked with the following symptoms
- Power button / volume buttons won't work.
- The phone won't turn on in any mode whatsoever.
When I ran lsusb, the only mode that was detected was Qualcomm modem.
I used some tutorials and QPST to do some 'fixes'. It didn't seem to work though.
The tutorial I referred to was this: http://forum.xda-developers.com/showthread.php?t=2341320
I only went till getting the phone recognized as an sd card (even when the battery is off). Power buttons still don't work. On linux it shows 4 partitions:
/dev/sdb1 20KB
/dev/sdb2 150KB
/dev/sdb3 5KB
/dev/sdb4 600KB
Unallocated Space 3.64 GB
I am stuck here now. Is there a way I could simply flash an image/kernel onto this space and get my phone working again?
I have a few questions:
1. Is this a hard-brick? Can I get my phone working again?
2. Can the partition where fastboot or boot lies be deleted?
3. If the boot manager is deleted, the phone will not know what to do when it is powered on right? So it will look as dead as it looks in my case?
4. Are there any parts of the phone that are write proof?
Any help is greatly appreciated!
Thank you so much.
p.s. would it not be so easy if phones had BIOS like computers have - on a real ROM or EEPROM and not flash ? And if android came in a bootable flash SD card; so that we could boot from SD card and install android like we install other OS's ....?
Click to expand...
Click to collapse
OK, before you follow anymore "guides" let's try and get a understanding of what you have, where you are and where its possible to go from here.
Start by researching and posting about the device, its CPU etc, I can help once I know what it is, I don't have time to research every device I get asked to look at. Check the partition super thread too and see if your device is listed.
darkspr1te
Sent from my Nexus 7 using Tapatalk
darkspr1te said:
OK, before you follow anymore "guides" let's try and get a understanding of what you have, where you are and where its possible to go from here.
Start by researching and posting about the device, its CPU etc, I can help once I know what it is, I don't have time to research every device I get asked to look at. Check the partition super thread too and see if your device is listed.
darkspr1te
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
ksatyaki said:
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
Click to expand...
Click to collapse
try this might help you unbricking your device : http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
rophaq said:
try this might help you unbricking your device : http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
Click to expand...
Click to collapse
That guide seems to be aimed at mediatek chip set.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 09:00 AM ---------- Previous post was at 08:03 AM ----------
ksatyaki said:
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
Click to expand...
Click to collapse
What is the devices pid/vid in Linux or windows, in Linux do
lsusb
at prompt, in windows, goto device manager,
Sent from my Nexus 7 using Tapatalk
darkspr1te said:
That guide seems to be aimed at mediatek chip set.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 09:00 AM ---------- Previous post was at 08:03 AM ----------
What is the devices pid/vid in Linux or windows, in Linux do
lsusb
at prompt, in windows, goto device manager,
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lsusb returns:
Bus 002 Device 003: ID 05c6:9006 Qualcomm, Inc.
dmesg (with battery):
[ 5961.920193] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd
[ 5962.013745] usb 2-1.3: config 1 has an invalid interface number: 20 but max is 1
[ 5962.013757] usb 2-1.3: config 1 has no interface number 1
[ 5962.015114] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9006
[ 5962.015126] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 5962.015132] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 5962.015138] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 5962.017375] scsi7 : usb-storage 2-1.3:1.20
[ 5963.018250] scsi 7:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 5963.020249] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 5963.021533] sd 7:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
[ 5963.022398] sd 7:0:0:0: [sdb] Write Protect is off
[ 5963.022409] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 5963.023242] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5963.030465] sdb: sdb1 sdb2 sdb3 sdb4
[ 5963.036936] sd 7:0:0:0: [sdb] Attached SCSI removable disk
lsusb when battery removed:
Bus 002 Device 005: ID 05c6:f006 Qualcomm, Inc.
dmesg when I remove the battery:
[ 6010.193475] usb 2-1.3: USB disconnect, device number 4
[ 6010.196912] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 6010.197026] sd 7:0:0:0: [sdb]
[ 6010.197033] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 6010.904344] usb 2-1.3: new high-speed USB device number 5 using ehci_hcd
[ 6011.038520] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=f006
[ 6011.038523] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 6011.038525] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 6011.038527] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 6011.108889] usbcore: registered new interface driver usbhid
[ 6011.108897] usbhid: USB HID core driver
[ 6011.131114] hid-generic 0003:05C6:F006.0001: hiddev0,hidraw0: USB HID v1.10 Device [Qualcomm, Incorporated Qualcomm CDMA Technologies MSM] on usb-0000:00:1d.0-1.3/input0
Any insights yet?
ksatyaki said:
Any insights yet?
Click to expand...
Click to collapse
When the device is in sd card mode, does it always boot like.that with the battery?
darkspr1te said:
When the device is in sd card mode, does it always boot like.that with the battery?
Click to expand...
Click to collapse
I don't understand what sd card mode is. How do you put it in sd card mode?
ksatyaki said:
lsusb returns:
Bus 002 Device 003: ID 05c6:9006 Qualcomm, Inc.
dmesg (with battery):
[ 5961.920193] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd
[ 5962.013745] usb 2-1.3: config 1 has an invalid interface number: 20 but max is 1
[ 5962.013757] usb 2-1.3: config 1 has no interface number 1
[ 5962.015114] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9006
[ 5962.015126] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 5962.015132] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 5962.015138] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 5962.017375] scsi7 : usb-storage 2-1.3:1.20
[ 5963.018250] scsi 7:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 5963.020249] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 5963.021533] sd 7:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
[ 5963.022398] sd 7:0:0:0: [sdb] Write Protect is off
[ 5963.022409] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 5963.023242] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5963.030465] sdb: sdb1 sdb2 sdb3 sdb4
[ 5963.036936] sd 7:0:0:0: [sdb] Attached SCSI removable disk
lsusb when battery removed:
Bus 002 Device 005: ID 05c6:f006 Qualcomm, Inc.
dmesg when I remove the battery:
[ 6010.193475] usb 2-1.3: USB disconnect, device number 4
[ 6010.196912] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 6010.197026] sd 7:0:0:0: [sdb]
[ 6010.197033] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 6010.904344] usb 2-1.3: new high-speed USB device number 5 using ehci_hcd
[ 6011.038520] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=f006
[ 6011.038523] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 6011.038525] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 6011.038527] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 6011.108889] usbcore: registered new interface driver usbhid
[ 6011.108897] usbhid: USB HID core driver
[ 6011.131114] hid-generic 0003:05C6:F006.0001: hiddev0,hidraw0: USB HID v1.10 Device [Qualcomm, Incorporated Qualcomm CDMA Technologies MSM] on usb-0000:00:1d.0-1.3/input0
Click to expand...
Click to collapse
In the log it shows a 3gb partition sdb when battery is in, this is sdcard mode
ksatyaki said:
I don't understand what sd card mode is. How do you put it in sd card mode?
Click to expand...
Click to collapse
The answer to your original question is yes.
Thanks.
ksatyaki said:
The answer to your original question is yes.
Thanks.
Click to expand...
Click to collapse
So the first thing to do is take a copy of that partition, we then analyze it to see what data is not corrupt or missing, we should then be able to re-write the bootloader section and hopefully get it back online, that's a simplification of the actual tasks though.
darkspr1te
Hi,
You make it sound simple. I hope I can get it back online.
I think all partitions are now reset. This, I assume, is a consequence of using QPST. Is this right?
Or does QPST restore important partitions again?
How do I write/flash a bootloader?
Thank you so much for your help.
If this means anything at all, now my phone vibrates for a small duration when I press the power button. It is the same pulse that occurs when the phone boots. But now it keeps giving those pulses (as though in a loop trying constantly to boot but failing). Doesn't switch on.
Hiya mate, just wondering if you managed to sort your y300 out? I got a similar problem with mine, it says emmc is read only and can't do force update but can get into stock recovery and bootloader.. is there anyone with any idea of how to solve this problem?
Sent from my GT-I5800 using Tapatalk 2
No luck
I didn't get any fixes. I am thankful to what happened in a sense. Life is much better without a "smart" phone.
Hello,
I tested with three different REDMI 3 devices and three different rom versions and have the following problem:
initially everything with connecting an external usb camera was ok. My usb camera app received events asking for permissions for using usb camera. But after 3 or 4 full charges the app stopped receiving permissions. I checked with couple other apps but again no permission. If my battery drops under 60% suddenly everything is ok again and the app detects the camera. It is stranger, that before full detect of the camera the app starts some kind of permission loop. I click allow and after 2 seconds the permission dialog shows again and so on... I checked the source code and appears my USBManager returns empty device list. For me it looks like some kind of battery optimizer or usb state optimizer doing it. I will be more than happy if someone can help me with this issue. Additionally I checked with all other stock rom version. It is all the same.
Here is some log from dmsg.
Code:
<6>[12449.627983] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12449.647323] psy->name:usb
<6>[12449.652992] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12449.653558] healthd: battery l=94 v=4240 t=22.3 h=2 st=4 c=382 chg=
<6>[12449.744320] msm_hsusb_host msm_hsusb_host: EHCI Host Controller
<6>[12449.744844] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[12449.751356] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0x078d9000
<6>[12449.769480] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[12449.769624] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[12449.769636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[12449.769646] usb usb1: Product: EHCI Host Controller
<6>[12449.769656] usb usb1: Manufacturer: Linux 3.10.49-perf-g48b885e ehci_hcd
<6>[12449.769665] usb usb1: SerialNumber: msm_hsusb_host
<6>[12449.772688] hub 1-0:1.0: USB hub found
<6>[12449.772729] hub 1-0:1.0: 1 port detected
<6>[12449.876761] msm_otg 78d9000.usb: USB in low power mode
<6>[12450.296922] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12450.519306] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<6>[12450.949089] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<6>[12451.619450] usb 1-1: new high-speed USB device number 5 using msm_hsusb_host
<11>[12452.316729] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<11>[12453.339456] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12453.759449] usb 1-1: new high-speed USB device number 13 using msm_hsusb_host
<6>[12455.879543] usb 1-1: new high-speed USB device number 21 using msm_hsusb_host
<6>[12456.212015] XXX::smb358_get_prop_batt_status:reg=0x0
<6>[12456.216663] psy->name:rk-bat
<6>[12456.216678] status=3, percent=94
<6>[12456.216684] status=3, percent=94
<6>[12456.222182] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12456.222723] healthd: battery l=94 v=4248 t=22.4 h=2 st=4 c=401 chg=
<6>[12456.319281] usb 1-1: new high-speed USB device number 22 using msm_hsusb_host
<11>[12457.382047] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<6>[12457.499222] usb 1-1: new high-speed USB device number 26 using msm_hsusb_host
<11>[12458.407239] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12458.899381] usb 1-1: new high-speed USB device number 31 using msm_hsusb_host
<6>[12459.339269] usb 1-1: new high-speed USB device number 32 using msm_hsusb_host
Im now at tampered rom (the rom says miui global 7.1 | 7.1.1.0.0 stable) it not real global rom! gold colour. but i dont have any problem with otg or battery drops. All working fine. Except a few settings turns back to default if i reset the device. But its doesnt bothered me much.
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^