Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?
mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?
EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!
mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.
Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do
Kali NetHunter for Galaxy A5 (SM-A500XX)What is Kali NetHunter?If you don't know what NetHunter is read this: https://www.kali.org/kali-linux-nethunter/
Q: Why don't I flash the original nethunter version by keeping my current kernel?
A: To get Nethunter fully work you need a kernel that supports its features, such as put a wireless adapter in monitor mode or perform a HID Keyboard attack
Special Patches included in this kernel:
mac80211 injection patch, to put wireless adapters in monitor mode; note that built-in wireless chipset doesn't support monitor mode and you have to use external wireless adapter (see supported wireless cards here)
HID patch, to perform HID keyboard attacks
CD-ROM patch, to emulate CD-ROMs in DriveDroid
Warning!!!:
This version works only with A500XX variants, but it's tested ONLY on A500FU.
DO NOT FLASH IN ANY A510 VARIANT
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK.
Required Downloads:
For CM
Download the CM13 ROM for Galaxy A5 ported by @TheWhisp here, or Resurrection Remix by mygalaxya here:
Optional: Download Google Apps from here: http://opengapps.org/
Download TWRP recovery for Galaxy A5 ported by me here, or CTR Recovery ported by me here
Download my Nethunter ROM here: https://www.androidfilehost.com/?w=files&flid=66902
NIGHTLIES: https://build.nethunter.com/nightly/ the kernel-nethunter-a5ulte-marshmallow-* ones
For TouchWiz
Download TWRP recovery for Galaxy A5 ported by me here, or CTR Recovery ported by me here
Kali Nethunter ported by me here: https://www.androidfilehost.com/?w=files&flid=94570
NIGHTLIES: https://build.nethunter.com/nightly/ the kernel-nethunter-a5ulte-touchwiz-marshmallow-* ones
How to Install (CM/RR):
Note: When you flash my zips, don't check "zip signature verification" box in TWRP recovery
1) Install TWRP with odin
2) Enter in TWRP recovery
3) Flash CM13 ROM, you can find instructions here: .
4) Optional: flash Google Apps
5) Flash NetHunter
7) Reboot
8) Open Nethunter app and go to menu<chroot manager<install chroot and download the full chroot, for devices which have more storage available, or minimal chroot, for devices which have less space available (if you've downloaded 700+MB version skip this step, chroot full is included )
9) Close NetHunter app and reopen it to complete the installation
10) Enjoy
How to Install (TouchWiz):
1) Flash TouchWiz (aka Stock ROM) with odin (you can find it on sammobile)
2) Flash TWRP or CTR with odin
3) Boot into TWRP/CTR and wipe cache and dalvik
4) Flash NetHunter
5) Reboot
6) Enjoy
Important: I called NetHunter "ROM", but it isn't a ROM, so, you don't have to wipe system partition.
Note: report only bugs related to NetHunter and not to CM13 or Resurrection Remix
Kernel Source Code:
Click here
Now you can build it by youself on official HetHunter source page HERE
For Any questions contact me at: [email protected]
NOTE: I'll release 3 kinds of updates
[KF]: I release them when there are updates regarding chroot full (they include full chroot, all nethunter apps, and my kernel)
[AU]: I release them when there are updates regarding all NetHunter apps (they include all updated NetHunter apps, and my kernel, but they don't include full chroot)
[KO]: I release them when there are only updates regarding the kernel (they include my kernel only, so NetHunter apps and chroot full are not included)
You can find all updates on main download page (here)
CHANGELOG:
Update v1.1 [KF] (01/07/2016):
NetHunter Update:
_Added chroot full to flashable zip.
_Added rolling version of kali to chroot
_Updated Apps
Kernel update: None
Update v1.2 [KO] (04/07/2016)
NetHunter Update: None
Kernel Update: Added Support for USB Bluetooth Dongles
Update v1.3 [KO] (15/07/2016)
NetHunter Update: none
Kernel Update:
_Add DVB Support
_Add some modules as built-in
_Some Minor improvements
XDA:DevDB Information
Kali NetHunter for Samsung Galaxy A5 (SM-A500XX), ROM for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Credits:
@TheWhisp for CM13 Kernel Sources @jcadduono, binkybear and offensive security for NetHunter source code
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: CM13 unofficial by TheWhisp: http://forum.xda-developers.com/sam...m-cyanogenmod-13-0-samsung-galaxy-a5-t3249704, CM12 by @mygalaxya or resurrection remix by @mygalaxya for CM/RR version and TouchWiz (for TouchWiz version
Based On: CyanogenMod 13 kernel (for cm/rr version) and on TouchWiz kernel (for touchwiz version)
Version Information
Status: Stable for CM/RR and Beta for TouchWiz
Current Stable Version: 1.3 for CM/RR and 1.0 for TouchWiz
Created 2016-06-10
Last Updated 2016-07-15
Sounds cool,i test it directly and report later,thanx.
-CALIBAN666- said:
Sounds cool,i test it directly and report later,thanx.
Click to expand...
Click to collapse
Thanks man, I hope you enjoy NetHunter on your galaxy A5
@mygalaxya
Genetik57 said:
@mygalaxya
Click to expand...
Click to collapse
Why?
DeadSquirrel01 said:
Why?
Click to expand...
Click to collapse
Dude, on A500FU it's says device not supported? Why?
azZA_09 said:
Dude, on A500FU it's says device not supported? Why?
Click to expand...
Click to collapse
explain me better
DeadSquirrel01 said:
explain me better
Click to expand...
Click to collapse
So, I installed on my friend's A5 RR Rom, then I tried to flash your kernel. Suddenly, in the middle of the procces, i saw "error:device not recognised. Aborting...".
azZA_09 said:
So, I installed on my friend's A5 RR Rom, then I tried to flash your kernel. Suddenly, in the middle of the procces, i saw "error:device not recognised. Aborting...".
Click to expand...
Click to collapse
Man, IT'S FOR CM 13 ROM, not for resrrection remix, so, I've only a question:
have you read the instructions before isntalling it?
DeadSquirrel01 said:
Man, IT'S FOR CM 13 ROM, not for resrrection remix, so, I've only a question:
have you read the instructions before isntalling it?
Click to expand...
Click to collapse
Are you sure your device was the A500FU variant?
Lol, i read it,but on lg asop kernels work on any cm based rom and yes it was FU
DeadSquirrel01 said:
Man, IT'S FOR CM 13 ROM, not for resrrection remix, so, I've only a question:
have you read the instructions before isntalling it?
Click to expand...
Click to collapse
azZA_09 said:
Lol, i read it,but on lg asop kernels work on any cm based rom and yes it was FU
Click to expand...
Click to collapse
Nope cm and aosp are different. Try flashing the cm 13 rom
If you get the same error, post me the twrp log
Very nice, thanks dude. I'll report bugs if I found some. Until now everything works well.
As I proceeded: Flash TWRP > Backup > Factory Reset > Installed CM 13 > Flash NetHunter & kernel modules > Reboot > install chroot > Update on Terminal > Upgrade on terminal.
DaveSoEasy said:
Very nice, thanks dude. I'll report bugs if I found some. Until now everything works well.
As I proceeded: Flash TWRP > Backup > Factory Reset > Installed CM 13 > Flash NetHunter & kernel modules > Reboot > install chroot > Update on Terminal > Upgrade on terminal.
Click to expand...
Click to collapse
thanks man
As you can read,NO!
-CALIBAN666- said:
As you can read,NO!
Click to expand...
Click to collapse
And... as caliban said no, sorry
You're supposed to include any kernel modules in the NetHunter installer under the devicename/modules directory and it is installed by NetHunter installer.
When this was merged into the NetHunter master branch, I added the proper devicename conditions that were missing as well, which should solve your unrecognized device errors.
If you don't mind, please open another pull request adding the missing modules to the repo to prevent user confusion.
Thanks.
Update: I've stripped them myself and added them to the repository. You should strip (debug symbols only) from your modules before distributing them. (so they aren't 55 MB, but rather 4 MB)
You can do this by adding to your kernel build script:
Code:
find * -name "*.ko" -exec ${CROSS_COMPILE}strip -g "{}" \;
jcadduono said:
You're supposed to include any kernel modules in the NetHunter installer under the devicename/modules directory and it is installed by NetHunter installer.
When this was merged into the NetHunter master branch, I added the proper devicename conditions that were missing as well, which should solve your unrecognized device errors.
If you don't mind, please open another pull request adding the missing modules to the repo to prevent user confusion.
Thanks.
Update: I've stripped them myself and added them to the repository. You should strip (debug symbols only) from your modules before distributing them. (so they aren't 55 MB, but rather 4 MB)
You can do this by adding to your kernel build script:
Code:
find * -name "*.ko" -exec ${CROSS_COMPILE}strip -g "{}" \;
Click to expand...
Click to collapse
Hi, thanks for you reply, now I'll try to recompile kernel on NetHunter (i don't know if it will work), because it's night and i don't want to turn on my pc
jcadduono said:
You're supposed to include any kernel modules in the NetHunter installer under the devicename/modules directory and it is installed by NetHunter installer.
When this was merged into the NetHunter master branch, I added the proper devicename conditions that were missing as well, which should solve your unrecognized device errors.
If you don't mind, please open another pull request adding the missing modules to the repo to prevent user confusion.
Thanks.
Update: I've stripped them myself and added them to the repository. You should strip (debug symbols only) from your modules before distributing them. (so they aren't 55 MB, but rather 4 MB)
You can do this by adding to your kernel build script:
Code:
find * -name "*.ko" -exec ${CROSS_COMPILE}strip -g "{}" \;
Click to expand...
Click to collapse
Hi, I've updated kernel, to support usb bluetooth adapters, can u push it on nethunter source page? Here's the link https://www.androidfilehost.com/?fid=24591020540823473. There are also new kernel modules. You can find them here: https://github.com/DeadSquirrel01/nethuter_a5ulte_modules
DeadSquirrel01 said:
Hi, I've updated kernel, to support usb bluetooth adapters, can u push it on nethunter source page? Here's the link https://www.androidfilehost.com/?fid=24591020540823473. There are also new kernel modules. You can find them here: https://github.com/DeadSquirrel01/nethuter_a5ulte_modules
Click to expand...
Click to collapse
this is your job if you've decided to maintain a device as official.
you have the kali-nethunter github repository on your PC?
if not, use
Code:
git clone --depth 10 https://github.com/DeadSquirrel01/kali-nethunter.git
cd kali-nethunter
(depth 10 will take up significantly less hard drive space)
you then need to add the offensive security nethunter repository as a remote, to do this:
Code:
git remote add ofsc https://github.com/offensive-security/kali-nethunter.git -t master
you can then fetch updates from ofsc using the command:
Code:
git fetch ofsc
if you want to make your repository the same as ours (in the case that your commits are already merged and you don't need to save anything):
Code:
git reset --hard ofsc/master
-or-
if you have current commits you want to move from older history to on top of our latest history, you can rebase them using:
Code:
git rebase ofsc/master
(you may need to fix conflicts!)
once everything looks good, you can use:
Code:
git diff HEAD
this will show differences between the current files in the repository with your changes, and the latest commit of the repository.
follow that up with:
Code:
git commit
then once you've made a reasonable title/message, save it, and you can push to your repository and send another pull request!
Code:
git push origin master
don't forget to strip your kernel modules as I have stated in my last post!
Mystery Kernel 3.18.35
Disclaimer:
Code:
I am not responsible if you bricked your device by using my work, it is your choice to use it and you are responsible for it alone.
You shall proceed at your own risk.
Hello guys...
Since Infinix and Google didn't give us a kernel source
I ported 3.18.35 kernel source from Doogee x5 to our Infinix Hot 2.
Thanks to SnowCatPDA for the source.
Current status:
First release (Testing phase):
Code:
- Touchscreen doesn't work
- Volume down button doesn't work
- No sound
- Primary camera is upside down
- Secondary camera broken
- No RIL
- Probably other
[B]To do:[/B]
- Enable the 2nd LCM driver for the other Hot 2 variant
- ...Further testing is needed
Kernel source:
https://github.com/Mysteryagr/Mystery-Kernel-3.18-N
And of course this work isn't done be me alone!
Credits:
@SnowcatPDA for his kernel source for Doogee x5
@I.nfraR.ed for decoding LCM driver, extracting x510.dts and helping a lot
@Nonta72 for the idea of porting the source, and helping a lot
@RendyAK for helping, testing and compiling with me
@kirito9 for helping
@DerTeufel1980 for helping
@andrea210701 for helping
and me
Sorry if I forgot to mention anyone else
XDA:DevDB Information
Nougat Kernel for Infinix Hot 2, Kernel for the Infinix HOT 2
Contributors
Mysteryagr
Kernel Special Features: Nothing yet
Version Information
Status: Testing
Created 2017-03-16
Last Updated 2017-03-16
Reversed
People keep asking for Nougat download link on facebook and through pms.
The kernel is in a very alpha stage; all drivers are broken for now including the touchscreen driver, and unstable for normal usage... But okay, as you wish.
1- First you need to check if your Hot 2 variant uses yushun LCM driver:
* Open terminal emulator on your phone and type:
Code:
su
cat /proc/cmdline
* If you have "nt35521_dsi_vdo_yushun_cmi_hd720" as your LCM driver, then you are ready to go, if not then stop here (THIS WON'T WORK FOR YOU)
* Screenshot: http://prtsc.ca/i/5gTRq
2- Find any MT6580 Nougat rom and download it.
* Here is one from Doogee x5:
https://yadi.sk/d/v32KqVP53Fa3mC
* Another one from Wiko lenny 3:
https://yadi.sk/d/pwHI_J-23AJ4Pz
* You can also use stock roms like the one from Doogee shoot 2.
* Unpack the rom (if necessary) and make it in a flashable zip format via twrp, you can use superR's kitchen for this process.
3- Download my compiled custom kernel from this post (It is a zImage), then unzip it.
* Now use any kernel kitchen, like carliv, for unpacking and repacking.
* Unpack the rom's boot.img and replace the (Kernel) zImage with mine; the one you downloaded from here. So we only need the ramdisk.
4- Zip the rom and the boot.img and flash it via twrp.
5- When the rom boots, you won't be able to use it because the touch driver isn't working, so use this tool to be able to control the device via adb:
https://forum.xda-developers.com/showthread.php?t=2786395
Have a nice day.
Mysteryagr said:
Mystery Kernel 3.18.35
Disclaimer:
Code:
I am not responsible if you bricked your device by using my work, it is your choice to use it and you are responsible for it alone.
You shall proceed at your own risk.
Hello guys...
Since Infinix and Google didn't give us a kernel source
I ported 3.18.35 kernel source from Doogee x5 to our Infinix Hot 2.
Thanks to SnowCatPDA for the source.
Current status:
First release (Testing phase):
Code:
- Touchscreen doesn't work
- Volume down button doesn't work
- No sound
- Primary camera is upside down
- Secondary camera broken
- No RIL
- Probably other
[B]To do:[/B]
- Enable the 2nd LCM driver for the other Hot 2 variant
- ...Further testing is needed
Kernel source:
https://github.com/Mysteryagr/Mystery-Kernel-3.18-N
And of course this work isn't done be me alone!
Credits:
@SnowcatPDA for his kernel source for Doogee x5
@I.nfraR.ed for decoding LCM driver, extracting x510.dts and helping a lot
@Nonta72 for the idea of porting the source, and helping a lot
@RendyAK for helping, testing and compiling with me
@kirito9 for helping
@DerTeufel1980 for helping
@andrea210701 for helping
and me
Sorry if I forgot to mention anyone else
XDA:DevDB Information
Nougat Kernel for Infinix Hot 2, Kernel for the Infinix HOT 2
Contributors
Mysteryagr
Kernel Special Features: Nothing yet
Version Information
Status: Testing
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
hey hi. great that u have ported the kernel for a device. i need a favor from you dear. can u port this same nougat kernel for my device running on mt6580 with kernel 3.18.19? i do not have the kernel source as micromax never provide kernel source. please dear. i wouldn't at all mind those bugs, just please do the porting. i would do anything in return if you help me.
below is the link to my devices boot.img and recovery.img. ask for any file if you want.
https://drive.google.com/open?id=0ByHObb-9DzhNNHNhM0FaeFVuNk0
Mysteryagr said:
People keep asking for Nougat download link on facebook and through pms.
The kernel is in a very alpha stage; all drivers are broken for now including the touchscreen driver, and unstable for normal usage... But okay, as you wish.
1- First you need to check if your Hot 2 variant uses yushun LCM driver:
* Open terminal emulator on your phone and type:
Code:
su
cat /proc/cmdline
* If you have "nt35521_dsi_vdo_yushun_cmi_hd720" as your LCM driver, then you are ready to go, if not then stop here (THIS WON'T WORK FOR YOU)
* Screenshot: http://prtsc.ca/i/5gTRq
2- Find any MT6580 Nougat rom and download it.
* Here is one from Doogee x5:
https://yadi.sk/d/v32KqVP53Fa3mC
* Another one from Wiko lenny 3:
https://yadi.sk/d/pwHI_J-23AJ4Pz
* You can also use stock roms like the one from Doogee shoot 2.
* Unpack the rom (if necessary) and make it in a flashable zip format via twrp, you can use superR's kitchen for this process.
3- Download my compiled custom kernel from this post (It is a zImage), then unzip it.
* Now use any kernel kitchen, like carliv, for unpacking and repacking.
* Unpack the rom's boot.img and replace the (Kernel) zImage with mine; the one you downloaded from here. So we only need the ramdisk.
4- Zip the rom and the boot.img and flash it via twrp.
5- When the rom boots, you won't be able to use it because the touch driver isn't working, so use this tool to be able to control the device via adb:
https://forum.xda-developers.com/showthread.php?t=2786395
Have a nice day.
Click to expand...
Click to collapse
@Mysteryagr can u add volte to kernel??
shr!pad said:
People keep asking for Nougat download link on facebook and through pms.
The kernel is in a very alpha stage; all drivers are broken for now including the touchscreen driver, and unstable for normal usage... But okay, as you wish.
1- First you need to check if your Hot 2 variant uses yushun LCM driver:
* Open terminal emulator on your phone and type:
@Mysteryagr can u add volte to kernel??
Click to expand...
Click to collapse
No, and this project is stopped a long while ago.
Hey the link for the ROM for wiko Lenny 3 is not working will you please update the l
Mysteryagr said:
Mystery Kernel 3.18.35
Disclaimer:
Code:
I am not responsible if you bricked your device by using my work, it is your choice to use it and you are responsible for it alone.
You shall proceed at your own risk.
Hello guys...
Since Infinix and Google didn't give us a kernel source
I ported 3.18.35 kernel source from Doogee x5 to our Infinix Hot 2.
Thanks to SnowCatPDA for the source.
Current status:
First release (Testing phase):
Code:
- Touchscreen doesn't work
- Volume down button doesn't work
- No sound
- Primary camera is upside down
- Secondary camera broken
- No RIL
- Probably other
[B]To do:[/B]
- Enable the 2nd LCM driver for the other Hot 2 variant
- ...Further testing is needed
Kernel source:
https://github.com/Mysteryagr/Mystery-Kernel-3.18-N
And of course this work isn't done be me alone!
Credits:
@SnowcatPDA for his kernel source for Doogee x5
@I.nfraR.ed for decoding LCM driver, extracting x510.dts and helping a lot
@Nonta72 for the idea of porting the source, and helping a lot
@RendyAK for helping, testing and compiling with me
@kirito9 for helping
@DerTeufel1980 for helping
@andrea210701 for helping
and me
Sorry if I forgot to mention anyone else
XDA:DevDB Information
Nougat Kernel for Infinix Hot 2, Kernel for the Infinix HOT 2
Contributors
Mysteryagr
Kernel Special Features: Nothing yet
Version Information
Status: Testing
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
Please update the link for the wiko Lenny 3 rom download thanks in advance
there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea
Well if your trying to build a device tree and kernel source and vendor start with downloading android source in linux there are many great guides for this then download the sources for the A600F/FN or any other current model of the A600 then there will be a file in the folder for whichever source you downloaded that will allow you to pull resources from your phone like kernel recovery device vendor files ect.. use that and then import it to the same folder than try to build TWRP and test it to see if you get a working build if not then go back and try again their are many sources for learning how to compile twrp for devices that dont have it read those and try again.
Sent from my [device_name] using XDA-Developers Legacy app
tmvkrpxl0 said:
there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea
Click to expand...
Click to collapse
I did find the kernel and source here: http://opensource.samsung.com/recep...menu_item=mobile&classification1=mobile_phone
(page 44 for SM-A605FN - A605FNXXU1ARD7)
I would like to build it myself, but my android development knowledge is limited (i do have a solid linux knowledge though).
Is this guide obsolete (https://forum.xda-developers.com/showthread.php?t=1943625)?
If yes, anyone knows where can i find an up-to-date one?
If not, any idea where BoardConfig.mk can be found?
Where can we find a guide on how to build a twrp? I would really like to learn how to do it
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Warnings: this kernel has been tested on the TB-X605F (SDA450) only. It will not work for the:
TB-X605F (M10) released with the SDA429 chipset
TB-X605L (M10 LTE). This kernel is currently for the wifi variant only.
TB-X505F/L (M10 HD) or any of the other M10 variants that use the SDA429 chipset.
TB-X605FC (M10 FHD). See the opensource released by Lenovo. Note that the X605FC kernel is 4.9.112.
Introduction
On 4 June 2020, Lenovo released the kernel source for the TB-X605F/L.
Prior to that, this kernel was developed by porting the kernel source for the the P10 (TB-X705F) released by Lenovo in January 2019.
Current version is: 3.18.120 merged with CAFCAF LA.UM.5.5.r1-05300-8x96.0.
The update zip will load some modules. So backup the "System Image", "Vendor Image" and boot partitions with TWRP before loading this kernel.
For kernel developers
Lenovo have released the opensource for the TB-X705F (Smart Tab 10 wifi) dated 31 January 2019 at s000018_20180913_row. This kernel is based on that kernel source (3.18.71). The default config (YM_X605F_defconfig) is almost identical to the kernel config of the M10. Some of the main differences with the P10 source are:
removed the MM8013 chipset config. The P10 uses the MM8013 for battery stats etc. There is no MM8013 on the M10.
upgraded drivers for the primary autofocus camera.
set CONFIG_MODULE_SIG_FORCE to "n" - so kernel will load stock modules from any version. Thanks to @yener90 for the suggestion.
While Lenovo releases the (compiled) stock M10 kernel at 3.18.120, the P10 kernel opensource is 3.18.71. Great job Lenovo!
The source will build signed system modules, if you want them. If you want the wifi driver it's pronto_wlan.ko, compile with CONFIG_PRONTO_WLAN=m.
Features
This kernel compiles and runs. It seems to be stable.
Working:
- wifi
- bluetooth
- power charging (USB and dock)
- camera
- FM radio
- touchscreen (including DT2W)
- audio
- OTG
Known bugs
you tell me
Installation
I assume you have unlocked bootloader, TWRP and Magisk. If not, follow these instructions.
The update zip is packaged using AnyKernel3 by @osm0sis .
if you are still on stock ROM & kernel, backup "System Image", "Vendor Image" and boot partitions in TWRP. You only have to do this once, not everytime you load a new version of this kernel.
download update_X605F_kernel.zip and copy it to your sdcard/OTG
boot to TWRP and use "update" to update the zip file
check that the update was successful, then reboot
confirm the kernel is loaded. It should start with "3.18.120-X605F-YM":
Code:
X605F:/ $ uname -r
3.18.120-X605F-YM-xxx
To return to stock kernel, just restore the stock boot, system and vendor backups you made in TWRP. If that doesn't work, then you'll have to reload system ROM using LMSA.
Changelog
Code:
11/03/2020 - 3.18.120-X605F-YM-g02f9b3e-00023-gcef72f9
- fixed camera - it's now recognised and autofocus works
- cleared out some dead code that's not needed for M10 (hangover from P10 source)
05/03/2020 - 3.18.120-X605F-YM-g02f9b3e-00018-g818259c3
- rebased kernel to 3.18.120
- merge CAF LA.UM.5.5.r1-05300-8x96.0
- added DT2W
- fixed "adb reboot". The rebase fixed it.
- added a defconfig for LineageOS
- included signed modules in zip file (including wlan)
20/01/2020 - 3.18.71-X605F-kernel-g0a9bdb1
- disabled signed module enforcement
- removed system and vendor modules from update zip
17/01/2020 - initial commit
Download
current release: update_X605F_kernel.zip
XDA:DevDB Information
M10 kernel, Kernel for the Lenovo Thinkpad Tablet
Contributors
Yahoo Mike
Source Code: https://github.com/Yahoo-Mike/android_kernel_lenovo_X605F
branch: msm-3.18.120 is source for this release (default branch)
branch: official-3.18.120 is official source released by Lenovo on 4 June 2020.
branch: msm-3.18.71 is the initial port from P10 kernel source
Kernel Special Features:
Version Information
Status: Testing
Created 2020-01-16
Last Updated 2020-06-05
Yahoo Mike said:
Lenovo releases the stock M10 kernel at 3.18.120. However, the P10 kernel source is 3.18.71. This means that system modules and the wifi driver need to be re-compiled, signed and distributed with this kernel. This means that the /system and /vendor partitions need to be touched, not just the boot image.
Click to expand...
Click to collapse
Just disable the modules, the kernel wont build it anymore. It's also not urgently required.
yener90 said:
Just disable the modules, the kernel wont build it anymore. It's also not urgently required.
Click to expand...
Click to collapse
Thanks for the neat suggestion.
I disabled signed module enforcement (CONFIG_MODULE_SIG_FORCE) so we can use stock modules. That means no need to update system or vendor partitions.
I left in *_SIG_ALL in the defconfig, so you can compile and sign modules if you really want to. But I haven't included any modules in the new update zip. If you've used the old version of the update zip, then restore stock boot, system and vendor images before using this new update zip.
I've released a new version. Main changes are:
rebased kernel to 3.18.120
merge CAF LA.UM.5.5.r1-05300-8x96.0
added DT2W
fixed "adb reboot". The rebase fixed it.
added a defconfig for LineageOS
included signed modules in zip file (including wlan)
I've updated the OP.
I've added a new (default) branch called msm-3.18.120 in the github repo: Yahoo-Mike/android_kernel_lenovo_x605f.
The camera auto-focus is still not working. I haven't looked at it. Lenovo have not released the source code. It looks like the P10 uses different cameras. The main camera is a hynix hi556 variant called: hi556_m10. I'll have a look at this soon. One of the ASUS Zenfone Max Pro (M1) variants uses the hi556. That might have a usable driver. There's also a new video driver for the hi556 (CONFIG_VIDEO_HI556) released by intel for the linux kernel.
If anyone wants me to rebase to 3.18.140, just ask.
Latest version fixes camera issues. Camera (Hynix hi556) is now recognised and autofocus works.
I copied the Hynix (eeprom OTP) code from the Lenovo Tab4 kernel source. The code in the P10 kernel source never worked - probably because the P10 was never released with Hynix hi556. The P10 uses OmniVision ov8856 (8MP) and GalaxyCore gc5025 (5MP). Whereas the M10 uses Hynix hi556 (5MP) and Superpix sp2519 (2MP).
This kernel is stable. I can't find anything wrong with it. I've tested it using stock ROM with no issues. So I guess it's safe to load up with the stock ROM (Android Pie)...at your own risk. Just be sure to backup the system & vendor images, plus the boot image in TWRP. You'll need these when an OTA comes along, anyway. The updater-script in the OTA will refuse to apply, because it won't recognise this kernel.
So until someone finds some issues with this kernel, I guess it's time to polish up some LineageOS code...
Two exciting announcements:
prima drivers added to staging
I've added prima drivers to the kernel github repository. It's used by the lineageos_X605F_defconfig to build the wlan.ko module (CONFIG_WLAN_PRONTO).
Lenovo released official kernel source yesterday
The official kernel source for the X605F and X605L has just appeared on Lenovo's support site.
I'll have a closer look over the next few weeks, but here's some preliminary observations:
it is released at msm 3.18.120. This is the stock kernel version. (Lenovo released 3.18.71 for the P10.)
there is only one download for both X605F and X605L. This might be good news.
the autofocus camera drivers for the Hynix appear to be included. I'll take a closer look.
kernel compiles without any changes. I haven't loaded it yet to test it.
edit: I've added the official source to the Yahoo-Mike/android_kernel_lenovo_X605F repo in the official-3.18.120 branch.
The opensource drop for the X605F from last week includes code for the kernel at msm-3.18.120. Surprisingly, it includes a defconfig for the P10. This confirms that the M10 (X605F/L) and P10 (X705F/L) are very similar.
I'm going to test Lenovo's kernel source on my TB-X605F this weekend. Is there anybody with a TB-X705F/L and the skills to build and test this code on their P10 ? PM me and we can coordinate.
The only differences I can see are:
Code:
m10_msmcortex_defconfig | p10_msmcortex_defconfig | Kconfig definition
----------------------- | ----------------------- | ------------------
| CONFIG_BATTERY_BQ27x00=y | drivers/power
CONFIG_CAMERA_TAB5_M10=y | | drivers/media/platform/msm/camera_v2
| CONFIG_CAMERA_TAB5_P10=y | drivers/media/platform/msm/camera_v2
| CONFIG_FOUR_PA=y | sound/soc/codecs & sound/soc/msm
| CONFIG_SENSORS_HALL=y | drivers/input
CONFIG_TP_MP_DIFF=y | | arch/arm64
The TP_MP_DIFF setting is used to load different firmware for the touchscreen drivers: one set for the M10s; another for the P10s.
Deleted
happyponcho42 said:
Great find! I've successfully built the kernel and was also pleasantly surprised I could use the browsable menuconfig (like the setup for my Linux Desktop) after using the P10 defconfig i.e.
Code:
make -j24 ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- O=out p10_msmcortex_defconfig && make -j24 ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- O=out menuconfig
I've disabled requiring signing of loadable kernel modules, as well as generated some modules for USB-to-Serial chipsets I use (pl2303.ko, ftdi, etc.) for projects.
Now to test the Image.gz-dtb: I have not had much luck unpacking boot-TB-X705F_S210120_191029_ROW.img and repacking with my tools. I just end up on a blank screen on the P10.
Do you have a recommended set of tools that have worked with your M10?
Click to expand...
Click to collapse
Glad to hear it compiled for P10.
I use AnyKernel3 to inject the kernel for me. It can also load kernel modules, if you build any.
I use these properties in the AK3 mod script. Modify it to suit your purposes:
Code:
# begin properties
properties() { '
kernel.string=X605F kernel built by Yahoo Mike @ xda-developers
do.devicecheck=1
do.modules=1
do.cleanup=1
do.cleanuponabort=0
device.name1=X605F
supported.versions=9
supported.patchlevels=- 2020-06
'; } # end properties
Then in my script I copy the kernel to AK3 root directory and modules to ./modules/system/lib/modules directory (or vendor equivalent) & zip it all up.
Code:
# zip it all up, ready for installing in TWRP
# this zip will replace kernel, plus any modules you included (if any)
# don't forget to TWRP-backup boot, system and vendor images
# also good idea to copy /system/lib/modules/* and /vendor/lib/modules/pronto/*
cd ~/tools/AK3
zip -r9 update_X605F_kernel.zip * -x .git README.md *placeholder
adb push update_X605F_kernel.zip /external_sd/
Optionally, you can also create a "version" file with something like this (before zipping):
Code:
MY_KERNEL_IMG="$(pwd)/out/arch/arm64/boot/Image.gz-dtb"
MY_KERNEL_VERSION="$(make kernelversion)"
cd ~/tools/AK3
# create a "version" file
MY_ZIP_DATE=$(date +'%Y-%m-%d %H:%M:%S')
MY_BUILD_DATE=$(stat ${MY_KERNEL_IMG} --format=%y | cut -c1-19)
echo "**************************************************" > $MY_ANYKERNEL_DIR/version
echo "unofficial kernel for Lenovo Smart Tab M10 (TB-X605F)" >> $MY_ANYKERNEL_DIR/version
echo " version: $MY_KERNEL_VERSION" >> $MY_ANYKERNEL_DIR/version
echo "compiled: $MY_BUILD_DATE" >> $MY_ANYKERNEL_DIR/version
echo " zipped: $MY_ZIP_DATE" >> $MY_ANYKERNEL_DIR/version
echo "**************************************************" >> $MY_ANYKERNEL_DIR/version
The Lenovo opensource seems to be working on the TB-X605F. The modules are also building and installing ok.
There is something odd about the device tree, so make sure you use Image, not Image-dtb.gz. When I used the dtb kernel, I kept getting the dreaded "Qualcomm HS-USB Diagnostics 900E" mode.
I'll add a "lineage-17.1" branch to the github repo. It includes an M10_lineageos_defconfig for building the kernel and modules, and wlan.ko source from CAF for Android 10:
Code:
June 01, 2020 LA.UM.8.6.2.r1-07600-89xx.0 msm8953_64 LA.UM.8.6.2.r1-07600-89xx.0.xml 10.00.00
Yahoo Mike said:
There is something odd about the device tree, so make sure you use Image, not Image-dtb.gz. When I used the dtb kernel, I kept getting the dreaded "Qualcomm HS-USB Diagnostics 900E" mode.
Click to expand...
Click to collapse
I can get the dtb kernel to work by replacing the arch/arm/boot/dts/qcom/ directory from Lenovo's opensource with the same directory from the "msm-3.18.120" branch of the repo. It boots fine with the stock ROM and LOS.
The "msm-3.18.120" branch is based on the original P10 opensource from January 2019.
So yes, there is definitely something screwy about the dt blobs from the June 2020 codedrop.
Not sure if this would be a valid kernel or not - On the back it says model is TB-X605F. I
In settings it says hardware is TB-X606F and so is the software.
It's the m10 gen 2 tablet. I believe Mediatek chipset.
dustofdeath said:
Not sure if this would be a valid kernel or not - On the back it says model is TB-X605F. I
In settings it says hardware is TB-X606F and so is the software.
It's the m10 gen 2 tablet..
Click to expand...
Click to collapse
If you have the gen 2, then this is the wrong kernel.
Lenovo has published the TBX606F/X kernel.
dustofdeath said:
I believe Mediatek chipset.
Click to expand...
Click to collapse
The CPU-Z app from the playstore will tell you which SOC you have.
I added pstore/ramoops support on branch msm-3.18.120. I have no idea why Lenovo never configured pstore/ramoops in the first place.
The ramoops device will dump console-ramoops, dmesg-ramoops-0, pmsg-ramoops-0 into /sys/fs/pstore/.
I'll add pstore support to TWRP for the TB-X605F in the next update. I'll use this branch (msm-3.18.120) to build the kernel.
I'm hoping pstore will tell me why GSI images fail to boot when installed over stock Pie.
Hello and thanks to all of you to invest so much time and effort. I'm not the best in this android world so forgive me if I ask something stupid Recently I got a Lenove Tab M10 TB-X605L and well I rooted it (with magisk) to use Linux on it. As I said I don't use android so much and I just got this product as present so when I saw this post I thought If I can put a new Kernel why not compile it with NetHunter Kernel and give it a try. After some effort (I'm not sure if it will work) I made the kernel. My problem is:
1st I rooted my Tablet with Magisk (as the same way you mentioned in another post) after the rooting I download twrp from google play. Till here all is good. Now:
TWRP is working when I boot it. But asks for a Password. I tried some swipe data, cache etc. but still I see that PASSWORD field. I can't pass it. (And when I pass it without Password I can't see the kernel neither yours nor mine)
I don't care what happens to my Tablet as I said I'm not a android user. I would even would try a crazy Idea even if its end with a dead tablet but I would really wanna check if the compiled NetHunter kernel works.
saizzou38 said:
...TWRP is working when I boot it. But asks for a Password. I tried some swipe data, cache etc. but still I see that PASSWORD field. I can't pass it...
Click to expand...
Click to collapse
TWRP will ask for a password if you have a password, PIN or pattern set on your tablet, and/or your data partition is encrypted.
If you have a password or PIN set on your tablet, try entering that. If you had a pattern, try this.
You can unencrypt the data partition by reformatting it and then installing Disable_Dm-Verity_ForceEncrypt.zip (created by Zackptg5). Just be aware that this wipes all your data and breaks OTA updates. (Magisk also needs to be uninstalled before OTAs work.)
saizzou38 said:
...And when I pass it without Password I can't see the kernel neither yours nor mine...
Click to expand...
Click to collapse
Remember: android recovery (twrp) uses the kernel in the recovery partition, not the boot partition.
So, where are you injecting your kernel?
If you are injecting your kernel into TWRP's recovery image, which kernel do you see when you issue this command?
Code:
adb shell uname -r
If you are injecting your kernel into the system ROM's boot.img, then you won't see your kernel in TWRP. You'll see the kernel with which twrp was compiled.
BTW...interesting project. Good luck. Let us know if you get it working.
Hi there,
I just compiled your kernel source you've uploaded on the Github (official branch) with m10_msmcortex_defconfig. Then, I flashed it to my device with anykernel 3, also included all modules, but the wifi does not work(It cannot be turned on). Before I flash it, my device was running well at the stock firmware, so I wonder what's wrong with my compilation.
After that, I also tried to compile the lineage branch, with lineageos_tbx605_defconfig. I flashed it to my device running well on AOSP 10(project treble), but the problem was same as the official source.
Could you please tell me that what's wrong with my compilation or how to compile it to work well? Thanks a lot .
Jun ASAKA
2021/02/03 (CST)
浅香ジュン said:
Hi there,
I just compiled your kernel source you've uploaded on the Github (official branch) with m10_msmcortex_defconfig. Then, I flashed it to my device with anykernel 3, also included all modules, but the wifi does not work(It cannot be turned on). Before I flash it, my device was running well at the stock firmware, so I wonder what's wrong with my compilation.
After that, I also tried to compile the lineage branch, with lineageos_tbx605_defconfig. I flashed it to my device running well on AOSP 10(project treble), but the problem was same as the official source.
Could you please tell me that what's wrong with my compilation or how to compile it to work well? Thanks a lot .
Jun ASAKA
2021/02/03 (CST)
Click to expand...
Click to collapse
It sounds like the wlan_pronto.ko module is not loading. That's why wifi is not working.
It might be easier to build the msm-3.18.120 branch with YM_x605f_deconfig. That should work.
It does not force module signature checks (CONFIG_MODULE_SIG_FORCE=n). So the stock wlan module (/vendor/lib/modules/pronto/wlan_pronto.ko) should load ok.
If that fails, check the kernel log (dmesg) for errors loading the wlan module. Let me know what the errors are.
official source
The stock wifi module won't work with the kernel from the official branch because CONFIG_MODULE_SIG_FORCE=y. You'll have to download the wlan source from CAF and build it with the same signature. That's a lot of work.
I also had some DT and dm-verity issues with the official source.
lineage-17.1
The lineage-17.1 branch includes the CAF wlan module (in drivers/staging/prima) for Android 10.0. I'm not sure why it's not working for you. Check the kernel log for wlan load errors.
The included CAF wlan module (and your GSI system) are Android 10. Your vendor is Android 9.0 or 8.1. Maybe there's a compatibility issue ? I'm guessing. I haven't tried that kernel with a GSI ROM.
Yahoo Mike said:
It sounds like the wlan_pronto.ko module is not loading. That's why wifi is not working.
It might be easier to build the msm-3.18.120 branch with YM_x605f_deconfig. That should work.
It does not force module signature checks (CONFIG_MODULE_SIG_FORCE=n). So the stock wlan module (/vendor/lib/modules/pronto/wlan_pronto.ko) should load ok.
If that fails, check the kernel log (dmesg) for errors loading the wlan module. Let me know what the errors are.
official source
The stock wifi module won't work with the kernel from the official branch because CONFIG_MODULE_SIG_FORCE=y. You'll have to download the wlan source from CAF and build it with the same signature. That's a lot of work.
I also had some DT and dm-verity issues with the official source.
lineage-17.1
The lineage-17.1 branch includes the CAF wlan module (in drivers/staging/prima) for Android 10.0. I'm not sure why it's not working for you. Check the kernel log for wlan load errors.
The included CAF wlan module (and your GSI system) are Android 10. Your vendor is Android 9.0 or 8.1. Maybe there's a compatibility issue ? I'm guessing. I haven't tried that kernel with a GSI ROM.
Click to expand...
Click to collapse
It's working! thanks a lot！