Related
Hi All,
I'd need someone to test ICS touchscreen drivers for 80G9. I patched them "blindly" as I don't have a 80, it would be nice if some could test them and confirm that patches are working.
If someone is up to it, here is how to test:
Install my ics build.
unzip the attached file to a directory
boot ics.
get list of loaded modules, please report what is written there to this thread.
Code:
adb shell lsmod
push kernel module:
Code:
adb push cypress-tma340.ko /lib/modules
adb push tr16c0-i2c.ko /lib/modules
reboot:
Code:
adb shell reboot_into sde
Test touch screen and report here if it works.
Thanks!
LeTama
lsmod:
Code:
Module Size Used by Not tainted
btwilink 2696 0 - Live 0xbf027000
hso 25266 0 - Live 0xbf01a000
usbserial 24035 0 - Live 0xbf00e000
tr16c0_i2c 3860 0 - Live 0xbf008000
cypress_tma340 11232 0 - Live 0xbf000000
works great
any chance for a git repo with your work?
i also tried to compile ICS on my own but couldnt get around the crashing servicemanager.
a1Pha said:
works great
any chance for a git repo with your work?
i also tried to compile ICS on my own but couldnt get around the crashing servicemanager.
Click to expand...
Click to collapse
So it works for you? Great news! I'll update my build then...
Both modules are loaded, do you know which one is in use ?
Regarding repo, well, I'm far from having a structured build. It's currently a mix of stock firmware+ics for panda with few patches for surface flinger and wifi+binaries for 3D from TI Gingerbread
I can give you the few diffs I have if you want...
rmmod tr16c0_i2c doesnt have any effect while rmmod cypress_tma340 kills my touch functionality.
so i guess cypress_tma340 is used
yeah, diffs + config from kernel & ics would be very very great
a1Pha said:
rmmod tr16c0_i2c doesnt have any effect while rmmod cypress_tma340 kills my touch functionality.
so i guess cypress_tma340 is used
yeah, diffs + config from kernel & ics would be very very great
Click to expand...
Click to collapse
Thanks for the test. We'll see if tr16c0_i2c is used on others...
Here are my diffs, raw, with lots of traces commented not used anymore. On kernel side, it has the ram_console on top of the touchscreens changes.
Location for ram console is poor as it is, I did put it there because I was experimenting 3.0 drivers. 0x9EEE0000 is better if you want to keep it. Config is the same as archos with extended dmesg (CONFIG_LOG_BUF_SHIFT=17).
Last point, 3D driver binaries are from there:
git://git.omapzoom.org/device/ti/proprietary-open.git, refs/heads/gingerbread
need to delete this..
jpacleb85 said:
need to delete this..
Click to expand...
Click to collapse
Obsolete now...
i meant that i need to delete that post.. sorry
jpacleb85 said:
i meant that i need to delete that post.. sorry
Click to expand...
Click to collapse
Yes, understood later... No problem!
Some background info:
I'm the author of PPP Widget which is an app that enables mobile data connections on Android devices with USB host capabilities - even if they are WiFi-only.
It turned out that many Android devices have the drivers for 3G sticks already on board, included with the stock kernel. The one large exception are Samsung devices ...
I started to provide the missing drivers as modules (mostly "ppp_async" and "option" which depends on "usb_wwan"). That worked well for some Google devices and also for Samsung devices running ICS, using the source packages from
http://opensource.samsung.com/
In their JB kernels though, Samsung enabled the "MODVERSION" option. Furthermore, compiling the modules with the officially recommended toolchain resulted in a different "module_layout" checksum than in the modules provided in the firmware.
This prevents using any additonal modules on the devices. "insmod" refuses to load these modules.
The only explanation for this problem is that the custom device configuration provided in the source packages does not match the configuration of the device kernel.
This is the case for all GT-P31xx and GT-P51xx models as far as I can tell.
My take is that Samsung is required to provide the correct kernel configuration under the rules of the GPL. Maybe anyone else wants to contact Samsung on this behalf; I already did several times - still waiting for an answer ...
That's the reason why I build everyting from source including the GPU driver and lost exFAT support http://forum.xda-developers.com/showthread.php?t=1859227 and the boot image result http://forum.xda-developers.com/showthread.php?t=1855700 .
ketut.kumajaya said:
That's the reason why I build everyting from source including the GPU driver and lost exFAT support
Click to expand...
Click to collapse
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
JFDee said:
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
Click to expand...
Click to collapse
Thanx alot for such a great development. ...
Adi™
Creator Of Sungsonic™HD
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
JFDee said:
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
Click to expand...
Click to collapse
If You will start to work with kernel I'm willing to beta test with my P5110. Only issue for me is that I need to know what 3G dongle to buy (well need it anyway so would prefer an advice from someone who know something about it). I'm living in Poland and Ireland (once here once there) so I can even test LTE modems (well donations here, myself can spend up to ~50€ on 3G one) because in Wroclaw, Poland I heard it's quite good, also I got H+/H on SGSII here. While in Ireland signal is not THAT strong due to fact most of places are quite remote (except Dublin, Galway etc). Hope I can help in either way
This is what I wrote to Samsung concerning the botched configuration file provided with the latest GT-P3110 kernel source:
Thank you for the source code update.
However, I have asked for the kernel configuration that matches exactly the kernel on the GT-P3110.
I have compiled the kernel from the provided update, but the module layout checksum does *not* match the one from the kernel running on my device.
On the device: module_layout 0xb5a27644
From source: module_layout 0x143474f1
I have used the recommended toolchain "CodeSourcery 2010q1" and the unchanged config file provided with the source ("android_espresso_omap4430_r04_user_defconfig").
Please be aware that you are obliged by the GPL to provide the correct config file for the binary kernel that you are distributing.
As a side note: the configuration provided with the kernel source for the GT-N8000 *does* match the kernel on the device, so there is no doubt that it is possible to get the configuration right.
Other Android vendors are just enabling the "embedded" config file in the kernel, so that the correct configuration is simply available on the device as "/proc/config.gz". This is so much less trouble. I suggest that you enable this option for Samsung kernels too.
Regards,
...
Click to expand...
Click to collapse
The GT-N8010 is also in the same situation you describe - config for 3.0.15 and jb stock kernel at 3.0.31, can't build working modules for stock.
davp, there seems to have been some activity at the Samsung open source center after my messages.
I suggest you make yourself heard as well. Use the "Inquiry" button next to the package download link in the table for your device.
To be able to add working modules to the device, the kernel configuration for the source has to be 100% compatible. It does not matter if any closed drivers are missing as we don't want to replace the kernel - but all those general debugging config options should be correct.
BTW, there is a history of similar issues:
http://forum.xda-developers.com/showthread.php?t=1123643
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
JFDee said:
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
Click to expand...
Click to collapse
So for now we might get stock kernel which will support 3G modems via USB OTG? How about other kernels such as CM10.1?
I'm looking for good 3G dongle then Any advices?
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
FTDI Single Port Serial Driver added.
cifs.ko not working on P3100 JB 4.1.2 (stock rooted)
ketut.kumajaya said:
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
Click to expand...
Click to collapse
Hi ketut.kumajaya,
I'm trying to use cifs.ko but i get:
/system/lib/modules # insmod cifs.ko
insmod: can't insert 'cifs.ko': unknown symbol in module or invalid parameter
I have:
/system/lib/modules # uname -a
Linux localhost 3.0.31-1084989 #1 SMP PREEMPT Mon Mar 25 14:53:07 KST 2013 armv7l GNU/Linux
I tried other cirs.ko with same result.
Can you give me some clues of what can I do?
Thank you.
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
ketut.kumajaya said:
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
Click to expand...
Click to collapse
Great!!!
That's the solution.
In my Tab 10.1 4.0.4 I'm loading (different kernel and different modules, of course):
insmod cifs.ko
insmod md4.ko
insmod nls_utf8.ko
So I was not thinking I should use a different order.
Thank you.
This is a dev thread for Cyanogenmod 12 for golfu. I finally got the time to update repos and push all my work on CM12 to HtcLegacy.
Three repositories are relevant for golfu:
kernel
device tree
vendor tree
Sync the repository
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/HtcLegacy/local_manifest/cm-12.0/local_manifest.xml
repo sync
apply patches
Code:
chmod 775 patches.sh
./patches.sh
and build
Code:
source build/envsetup.sh
brunch -jx cm_golfu-userdebug
ROM builds and boots sucessfully. However, there are bugs:
- no bootanimation
- RIL is not working - linker has permission problems with libhtc_ril.so, not sure what can be done about that and how it is working for pico
- Camera not working
- Bluetooth turns on, but not working
- Headphones do not work
and ROM will reboot after a while. Any contribution is welcome, as my time to work on device is limited. Thanks to KirmaniArslan for his work on common tree, which helped alot.
h1gh1 said:
- RIL is not working - linker has permission problems with libhtc_ril.so, not sure what can be done about that and how it is working for pico
Click to expand...
Click to collapse
Is SELinux permissive in pico build?
Have you tried to use "androidboot.write_protect=0" before "androidboot.selinux=permissive" like in MotoG Permissive SELinux?
kodirovshchik said:
Is SELinux permissive in pico build?
Have you tried to use "androidboot.write_protect=0" before "androidboot.selinux=permissive" like in MotoG Permissive SELinux?
Click to expand...
Click to collapse
Not really sure what mode it is in on pico, KirmaniArslan was not clear on that. An interesting switch...
h1gh1 said:
Not really sure what mode it is in on pico, KirmaniArslan was not clear on that. An interesting switch...
Click to expand...
Click to collapse
Well... if he has terminal in his current build "getenforce" will return SElinux mode. And if we can trust this two guys from galaxyace thread, CM12 can be switched to permissive mode.
upd: one more question. here is some fixed SElinux policies for motog i was thinking maybe we missed something. but i cant find them. where is our policies for selinux?
kodirovshchik said:
Well... if he has terminal in his current build "getenforce" will return SElinux mode. And if we can trust this two guys from galaxyace thread, CM12 can be switched to permissive mode.
upd: one more question. here is some fixed SElinux policies for motog i was thinking maybe we missed something. but i cant find them. where is our policies for selinux?
Click to expand...
Click to collapse
SELinux policies are defined in .mk files - we use qualcomm predefined policies.
here my boot everything works except wifi and bt.
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
So glad for you. If you found a way to fix something, github links are up.
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
Great ! I've tested it, and it's truth !
But like @h1gh1 meant : It will be better if you share your work on github
boot.img for cm12 golfu
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
thanks, i have tested the boot.img works well
Now, someone please help fix the rest Bugs
i had no sim card detected like in the images in the attachment
LINCOLINE1 said:
thanks, i have tested the boot.img works well
Now, someone please help fix the rest Bugs
i had no sim card detected like in the images in the attachment
Click to expand...
Click to collapse
RIL is not working. It's not working in my build, not sure about this boot.img, but if you flashed it, it has the same problem. SDCard and Wifi are working, as I said. But I am going to ask politely not to put any downloads here - all the development is public, and if someone wants to contribute, he can fork or create a pull request. Uploading boot.img with almost no information makes no sense to me.
h1gh1 said:
RIL is not working. It's not working in my build, not sure about this boot.img, but if you flashed it, it has the same problem. SDCard and Wifi are working, as I said. But I am going to ask politely not to put any downloads here - all the development is public, and if someone wants to contribute, he can fork or create a pull request. Uploading boot.img with almost no information makes no sense to me.
Click to expand...
Click to collapse
I agree
(RIL works fine for me with this particular boot.img)
i used ION kernel for my first build.
zvox said:
i used ION kernel for my first build.
Click to expand...
Click to collapse
That is not much info. Link to the source?
ION pico kernel
high1/android_kernel_htc_pico
zvox said:
ION pico kernel
high1/android_kernel_htc_pico
Click to expand...
Click to collapse
As I suspected, enforcing SELinux is the problem...
h1gh1 said:
As I suspected, enforcing SELinux is the problem...
Click to expand...
Click to collapse
Did you have the time to try my fix ?
Narudgi said:
Did you have the time to try my fix ?
Click to expand...
Click to collapse
No, but I found a proper fix later.
https://github.com/psndna88/AGNI-pureSTOCK/commit/3c530c181086a1caaafb57f86c5480c895c598b7
h1gh1 said:
No, but I found a proper fix later.
https://github.com/psndna88/AGNI-pureSTOCK/commit/3c530c181086a1caaafb57f86c5480c895c598b7
Click to expand...
Click to collapse
It will be better with that
i have done a new build. ( ION kernel like always )
everything works except bt
enforcing SELinux doesnt work ( and wifi gone )
4.9 was released and Nexus 5 it's support by mainline kernel
http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.9-ARM-Pull
Interesting. This might bring development back to the phone. Also 4.8 and 4.9 have some amazing features and speed improvements.
Will any dev merge and update our kernel? will this function with our android latest version?
santi1993 said:
Will any dev merge and update our kernel? will this function with our android latest version?
Click to expand...
Click to collapse
No, it's probably not even functional in many aspects, there will be a lot of patching/fixing needed to get it to work.
There is already been discussed about his.
Yes, it's impossible use 4.9 without patch related to panel, exc exc
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
TheReduxPL said:
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
Click to expand...
Click to collapse
There is support for the kernel, so yes, you could now run Arch, Debian, OpenWRT, or DD-WRT much more easily.
Android utilizes old libraries that are not compatible with new kernels (that's at least my understanding of the matter), so you would need to patch it to run a newer kernel, and that could only get you so far.
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
I wonder if someone could backport the necessary changes from 4.9 to the latest 4.4.x release though, that would already be something.
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
TheReduxPL said:
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
Click to expand...
Click to collapse
I don't think so, as they rely on Android bits to work with the bootloader and recovery.
But perhaps there is a chance with the new OS that KDE are cooking, which is supposed to be completely independent of Android.
The 4.10 kernel brings in mainline support for the Nexus 6P and the Nexus 5X.
I wish that mainline support would arrive for the Nexus 4.
moriel5 said:
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
Click to expand...
Click to collapse
Update: Apparently Android 6.0.x and up can now utilize kernel 4.9.x.
As there is a build of Android 7.1.x for the x86 platform (I have no idea whether it is an official build of Android-x86, nor do I know the precise Android version, though) with a 4.9.x kernel (again, I have no idea precisely which version).
My source is a newly thread opened in the Remix OS forum, in which the OP asks for the possibility of updating the kernel in Remix OS, and mentions that he/she managed to boot it (only in debug mode, though) with the aforementioned kernel.
The source: https://forum.xda-developers.com/remix/remix-os/remix-3-0-207-kernel-t3546057
anyone managed to boot a hh from any kind of 4.9 compilation?
Sent from my Nexus 5 CAF using Tapatalk
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
santi1993 said:
anyone managed to boot a hh from any kind of 4.9 compilation?
Click to expand...
Click to collapse
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
santi1993 said:
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
Click to expand...
Click to collapse
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Icyphox said:
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
Code:
bootsize = 0xe48800
pagesize = 0x800
kerneladdr = 0x8000
ramdiskaddr = 0x2900000
secondaddr = 0xf00000
tagsaddr = 0x2700000
name =
cmdline = console=ttyMSM0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 androidboot.selinux=permissive
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
scholbert said:
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
Click to expand...
Click to collapse
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Icyphox said:
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
No far away from any use together with a ROM or even anything the TWRP image uses inside.
No graphics... no usb...
This is just a proof of concept, playing around with the dts files and kernel. Nothing more.
If someone would create a console based ramdisk with some tools included, you may dig a little deeper into the soc or check which parts are responsive or not.
Cheers,
scholbert
It has been quite some time.
Does anyone think that using PostMarketOS's kernel as a stepping stone may help get at least kernel 4.4 to a daily-driver ready status?
Update: Perhaps it would also be a good idea to use the Nexus 7 (2013)'s sources to try porting the newer kernel there to the Nexus 4 (as they share the same SOC).
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
From the logs, it looks like the reason the boot stops is because of init.rc errors. I might be able to help with that, but my nexus 5's battery is toast.
I'm posting this in the OnePlus 6t section as that is the device I achieved it on. But like the title states, monitor mode can be activated on the internal wireless adapter in Snapdragon chipsets. Which means the majority of mainstream Android devices.
I just got a OnePlus7pro(which I'm still having fastboot problems with) and went to look at options for custom software, and so I went to Nethunter download page and bam, there it was! I updated my Nethunter with apt upgrade and apt-get upgrade. Also a new Nethunter app update showed up in the Nethunter store. And after updating I gave it shot and it actually works!
You still need to be rooted, with a custom kernel. Don't ask me about my build, as it's pretty messy in my device.
Believe it or not, it's very easy. I've succeeded in getting mon1 up and running on my oneplus3, oneplus5t, and now my 6t. But all were a pain in the a## . Not anymore...
https://github.com/kimocoder/qualcomm_android_monitor_mode
https://www.kali.org/news/kali-nethunter-updates/
One more screenshot...
And when you add the command in Nethunter, you want to send it to Kali, not Android...
There arent any instructions about how to install/build the patch. Mind sharing?
crashnova said:
There arent any instructions about how to install/build the patch. Mind sharing?
Click to expand...
Click to collapse
There's no patch that needs to be made from how I read it. Only on older, unmaintained chipsets. My kernel hasn't had a update in at least a year, and it still worked. I did forget to mention I originally installed Nethunter through the Majisk modules, along with the wireless firmware module also. Like I said, it's a mess inside my device and I'm surprised everything works right.
I'm guessing whatever patches were needed, were included in the recent Nethunter app update. That's all I did, was update Nethunter.
crashnova said:
There arent any instructions about how to install/build the patch. Mind sharing?
Click to expand...
Click to collapse
This was exactly how I did it...
Open Nethunter terminal, select "androidsu", and type "bootkali".
Then pasted the mon start command from the GitHub page into terminal. Then started wifite... Done.
https://drive.google.com/file/d/1xZPXdFeLapE2uTYk0WLNIFM1idYLi83S/view?usp=drivesdk
Mine worked right out the box...I just ran the custom commands for wlan0 that are included, the airmon-ng command didn't work neither did wifites python script for auto start monitor mode on wlan0. It had to be done via nethunters custom command. Only tried on liquid remix and crdroid but that being said liquid remix is android 9, crdroid is 10 and they both worked out the box....I can't get postgresql to run tho >_>
xenomorph318 said:
Mine worked right out the box...you have to run the custom commands for wlan0 that are included. Only tried on liquid remix and crdroid but both worked out the box....I can't get postgresql to run tho >_>
Click to expand...
Click to collapse
Yeah, I updated the custom commands and it works like a charm. Honestly, it's never worked so good.
rickunnis said:
Yeah, I updated the custom commands and it works like a charm. Honestly, it's never worked so good.
Click to expand...
Click to collapse
The first device I've had where monitor mode work for wlan0. Blew my mind lol.
xenomorph318 said:
The first device I've had where monitor mode work for wlan0. Blew my mind lol.
Click to expand...
Click to collapse
Only a handful of devices could do it... Even to get wlan1mon going was a massive headache for me for a long time.
rickunnis said:
Only a handful of devices could do it... Even to get wlan1mon going was a massive headache for me for a long time.
Click to expand...
Click to collapse
Have you gotten monitor mode going on wlan1 on the oneplus 6t?
xenomorph318 said:
Have you gotten monitor mode going on wlan1 on the oneplus 6t?
Click to expand...
Click to collapse
Yessir.
rickunnis said:
Yessir.
Click to expand...
Click to collapse
Right out the box? What kernel are you running? Are you on oxygenOS or custom ROM. I was debating compiling a kernel Cuz I can't get wlan1 to register if my life depended on it. I got a panda with proper chipset for sure. I've tried multiple adapters too
xenomorph318 said:
Right out the box? What kernel are you running? Are you on oxygenOS or custom ROM. I was debating compiling a kernel Cuz I can't get wlan1 to register if my life depended on it. I got a panda with proper chipset for sure. I've tried multiple adapters too
Click to expand...
Click to collapse
All my build info is in the screenshots I posted. I haven't been able to find a updated kernel, so I haven't updated in quite some time. I might now though with this recent development. Whats your build look like to get wlan0mon up?
xenomorph318 said:
Right out the box? What kernel are you running? Are you on oxygenOS or custom ROM. I was debating compiling a kernel Cuz I can't get wlan1 to register if my life depended on it. I got a panda with proper chipset for sure. I've tried multiple adapters too
Click to expand...
Click to collapse
Oh and I have the tp link 722 with atheros chipsets.
rickunnis said:
All my build info is in the screenshots I posted. I haven't been able to find a updated kernel, so I haven't updated in quite some time. I might now though with this recent development. Whats your build look like to get wlan0mon up?
Click to expand...
Click to collapse
I been swapping ROMs as of late Cuz of not having a RR for my daily. But so far Wlan0mon has worked on all of them!! Can't say as much for getting a wlan1 link up tho >_>
xenomorph318 said:
I been swapping ROMs as of late Cuz of not having a RR for my daily. But so far Wlan0mon has worked on all of them!! Can't say as much for getting a wlan1 link up tho >_>
Click to expand...
Click to collapse
Specifically, where are you getting your kernel from? I thought 6t wasn't officially supported by Nethunter.
rickunnis said:
Specifically, where are you getting your kernel from? I thought 6t wasn't officially supported by Nethunter.
Click to expand...
Click to collapse
Whoa I just realized it said Kali kernel.. I haven't flashed any kernel, no magisk module, nothing. My chroot is restored from a back up that I installed on my previous custom ROM which was crdroid. This was just yesterday. I flashed Los today and restored the tar. Its got to be some kinda bug or something. Uname -a is spitting the same kernel build in both terminals tho. Ima reboot and try external WiFi too since its saying Kali. But I should seriously have the Los kernel from nightly 17 I believe... Strange stuff tho lol
Edit/update:
Well after a reboot I bootlooped once then landed in twrp rescue party for some reason. Another reboot landed me on the Los Home screen and upon doing uname -a, it returned
Linux localhost 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Started chroot and did apt update && apt upgrade, i got a buncha linblockdev upgrades and ran uname -a to return
Linux kali 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Its being fickle atm, just saw an update for Los but I'm prolly changing ROMs again soon. Prolly gonna start staging for compiling a nethunter kernel
xenomorph318 said:
Whoa I just realized it said Kali kernel.. I haven't flashed any kernel, no magisk module, nothing. My chroot is restored from a back up that I installed on my previous custom ROM which was crdroid. This was just yesterday. I flashed Los today and restored the tar. Its got to be some kinda bug or something. Uname -a is spitting the same kernel build in both terminals tho. Ima reboot and try external WiFi too since its saying Kali. But I should seriously have the Los kernel from nightly 17 I believe... Strange stuff tho lol
Edit/update:
Well after a reboot I bootlooped once then landed in twrp rescue party for some reason. Another reboot landed me on the Los Home screen and upon doing uname -a, it returned
Linux localhost 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Started chroot and did apt update && apt upgrade, i got a buncha linblockdev upgrades and ran uname -a to return
Linux kali 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Its being fickle atm, just saw an update for Los but I'm prolly changing ROMs again soon. Prolly gonna start staging for compiling a nethunter kernel
Click to expand...
Click to collapse
And I thought my device was a mess. Lol. Do you have the Majisk Nethunter wireless firmware module installed? That might help with wlan1...
xenomorph318 said:
Whoa I just realized it said Kali kernel.. I haven't flashed any kernel, no magisk module, nothing. My chroot is restored from a back up that I installed on my previous custom ROM which was crdroid. This was just yesterday. I flashed Los today and restored the tar. Its got to be some kinda bug or something. Uname -a is spitting the same kernel build in both terminals tho. Ima reboot and try external WiFi too since its saying Kali. But I should seriously have the Los kernel from nightly 17 I believe... Strange stuff tho lol
Edit/update:
Well after a reboot I bootlooped once then landed in twrp rescue party for some reason. Another reboot landed me on the Los Home screen and upon doing uname -a, it returned
Linux localhost 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Started chroot and did apt update && apt upgrade, i got a buncha linblockdev upgrades and ran uname -a to return
Linux kali 4.9.223-gad6ad5c #1 SMP PREEMPT Sat May 30 17:59:53 UTC 2020 aarch64
Its being fickle atm, just saw an update for Los but I'm prolly changing ROMs again soon. Prolly gonna start staging for compiling a nethunter kernel
Click to expand...
Click to collapse
Oh and I'd love a copy of a updated Android 10 kernel for Nethunter
There is source for an updated Kernel. Not sure if anyone is willing to build it tho.