Develop Bugs

[ROM][PORT][Hollyss][TRXteam]AOSP-6.0

Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
What works:
Bluetooth
Flashlight
WiFi
Sensors
Notification led
Something else(Report to me)...
What does not work:
Camera (It opens but it is reversed and when you try to take a picture it crashes)
Ril
NFC
SdCard(if partition,no bug)
Something else(Report to me)...
Download:
AOSP
Installation
Take a backup of system and data
Factory Reset(It will give an error with cache but it will wipe)
Install zip via twrp
Reboot
Source
Kernel
Contributors
TRXteam,ByBlaCk4,krkshalil, TheShadow
ROM OS Version: 6.0 Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2016-11-07
Last Updated 2016-11-07

Screenshots

reserved

I'm pretty sure the M5 have their own aosp on the developer website

ih8redsn0w said:
I'm pretty sure the M5 have their own aosp on the developer website
Click to expand...
Click to collapse
No sonyxperiadev is only releasing source for snapdragon.

TRXteam said:
No sonyxperiadev is only releasing source for snapdragon.
Click to expand...
Click to collapse
Wrong, kernel sources for all major M5 firmwares (5.0/5.1/6.0) are available on Sony Mobile Developer World.

mbc07 said:
Wrong, kernel sources for all major M5 firmwares (5.0/5.1/6.0) are available on Sony Mobile Developer World.
Click to expand...
Click to collapse
I said sonyxperiadev if you notice not Sony Developer World, so read carefully before answering.
sonyxperiadev is sonys github that sony releases AOSP device & vendor trees for their devices but not mediatek ones.

Should we expect furthur development?
Sent from my E5603 using Tapatalk

abdul.ar721 said:
Should we expect furthur development?
Sent from my E5603 using Tapatalk
Click to expand...
Click to collapse
Unfortunately not anymore.

Hey guys.
The ROM works very nice, but after about a week my memory would suddenly be filled up.
If any of you have the same problem or just whant to fix it anyways here is my solution.
1. Boot into your recovery and open the terminal(for twrp its located under advanced).
2. type "cd /data/misc/sensor/"
3. check with "du -sh sensord.log" if you have the same problem(for me the file grew to 5gb)
4.remove the file with "rm sensord.log"
5 make sure no more data can be written to the file "cp -a /dev/null sensord.log"
I hope this helped someone

[EXP][Kernel][athene] SomeAthK for Moto G4 Plus

This is SomeAthK kernel for device codename "athene".
This is the first time I build a kernel, also, the first time I post something in DevDB. Hope you like this kernel and please expect many releases.
The kernel should work in stock and custom ROMs, with any variant.
Disclamier:
Code:
[COLOR="red"]* Include <std_disclaimer.h>
* Your warranty is now void.
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*[/COLOR]
Features:
Updated to Linux 3.10.107.
Built with UberTC 5.3
Will soon include awesome features.
Downloads:
Click here or go to Downloads tab at the top of the thread.
NEW! Now, if something goes wrong with the XDA download server or you simply want to download from somewhere else, I've been approved as developer at AFH. All downloads will also be posted here.
NEW! Ask for features, report bugs, get help with installation, usage and everything else. Join us at Telegram: t.me/someathk
Bugs:
You tell me.
Bugs marked with a "*" will be fixed in the next release.
XDA:DevDB Information
SomeAthK Kernel for Moto G4 Plus, Kernel for the Moto G4 Plus
Contributors
facuarmo, chijure, Dark98, squid2, TeamMex
Source Code: https://github.com/FacuM/android_kernel_motorola_msm8916
Kernel Special Features:
Version Information
Status: Stable
Created 2017-07-05
Last Updated 2017-07-05

Changelog (v1.00exp):
Kernel changes:
Initial release.
Other changes:
None.
Download:
Main link: https://forum.xda-developers.com/devdb/project/dl/?id=25479
Alternative link: https://www.androidfilehost.com/?fid=961840155545579480
MD5: 74a97673b57d068a2e6ded8eb0536d0f

First.

2nd

3rd biatches
Sent from my Moto G4 using Tapatalk

Which is the difference between this kernel and any other?

You should try it and report back
Sent from my Moto G4 using Tapatalk

Finally it is released..??? Thank you dev..

Hey did anyone flash this kernel on the stock rom? Because I couldn't boot my phone after flashing.

So far this kernel seems solid...I'm on xt1644 dirty

Good work there
Sent from my lineage_athene using XDA-Developers Legacy app

No reboots... performance quality seem great so far...

Android USB Keyboard patch is applied according to pelya or not

[KERNEL] Lucky [O]

Lucky-Kernel​For​Exynos-Variant's​
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
* If you dont like this Kernel, Stay away from this thread!
*/
What to say... I come from Samsung Galaxy Nexus and its development until the beginning of September 2016...
I did a one-year break from kernel programming, and I came back here for you. To bring you a good kernel for this device that still has a lot to give.
My work is on kernel source, I add, delete, modifing code, but with a criterion, that everything, must make sense
I consider the kernel as beta, although it is very stable, I will update the kernel when needed, with the necessary security patches, and a few extra grays
Android8.0
This kernel Boot on 8.0(lineage-buid) but I think also on AOSPExtended rom 8.0 it will Boot..
Android7.1
EDIT: Don't Boot.. thank's to @spookcity138 for news
Good download at all, and let me know your opinion
XDA:DevDB Information
[KERNEL] Lucky [O], Kernel for the Samsung Galaxy S5 Mini
Contributors
Fenix46, hennymcc, spookcity138
Source Code: https://github.com/Fenix46/android_kernel_samsung_kminilte
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2017-11-11
Created 2017-11-11
Last Updated 2017-11-12

Reserved

Del.

Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards

Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.

tester02 said:
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Click to expand...
Click to collapse
Yep, with official twpr, flash without problem, this error 11 is related to the twpr for Oreo... however, I've add some commit on kernel source, and my work is this, add commit, and update the kernel

spookcity138 said:
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
Click to expand...
Click to collapse
@spookcity138 thank's for welcome However Thannk's again for feed on 7.x rom... this error is related at updater-script.. on Oreo the first line "assert" is not present, so cause this.. but with official twpr flash go fine, I think to change the updater-script if cause another problem

I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.

CHEF-KOCH said:
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
Click to expand...
Click to collapse
what changes did you want to find on the kernel? did you see the commit series I added? Do you think the changes are all in the name of who works on the kernel? for those who work on ROMs as @hennymcc or @spookcity138 or other's they can very well take my base and insert it to build the ROM..

I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.

CHEF-KOCH said:
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
Click to expand...
Click to collapse
What you saw, that you think is old, are needed on Nougat as well, because interfaces better the kernel, with the modules, because our kernel don't have support on kernel Device Three.. and it's just the beginning of this, because my main job will be to reformulate the theard for a rom. Nothing to take away from the kernel LOS, and I did not want to create useless controversies. if you do not want to use this kernel, it does not change anything. however if you look good on the download section, find the zip package to download.

Twrp 3.1.1 official, SM-G800F, AospExtended Oreo. Error 11 by flashing.

Where is the Download Link?

Open xda in Browser, under downloads
(look at the middle of my Screenshot)

MikeT. said:
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
Click to expand...
Click to collapse
Thanks

. . .

[EOL][ROM][10.0][CAF][OP5] Just CAF

Code:
/*
* Your warranty is now maybe void.
*
* 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 ROM
* 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.
*
Near pure CAF rom with only small modifications to allow building and make device useable.
Download: here
Install instructions:
Make sure you are on firmware version 10.0.0 Hotfix 1
Clear system, vendor, data, cache, dalvik-cache
Install zip
Install Gapps
Done
Kernel source: https://github.com/Just-CAF/platform_kernel_oneplus_msm8998
XDA:DevDB Information
Just CAF, ROM for the OnePlus 5
Contributors
T1mb3, spirtix, Men_in_black007, codeworkx, LineageOS
Source Code: [url]https://github.com/Just-CAF[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: CAF
Version Information
Status: Stable
Stable Release Date: 2019-11-04
Created 2019-10-15
Last Updated 2020-08-03

Real-life stats:

Thanks ss )

Yes, thank

wow nice caf

Ultra-lite like Slim Roms is what we have been missing for Oneplus 5, Newer android version to start with is the way to go for me. Thanks a lot.

Added to the OnePlus 5 Index Thread here.

For the first time, I read up on what CAF really means. So now I'm looking very much forward to this ROM becoming more stable!
Thank you for developing!

New build: download
Changelog 20191016:
Fix outgoing phone calls
Fix microphone in calls
Add missing package Styles and wallpapers (com.android.wallpaper)

T1mb3 said:
New build: download
Changelog 20191016:
Fix outgoing phone calls
Fix microphone in calls
Add missing package Styles and wallpapers (com.android.wallpaper)
Click to expand...
Click to collapse
thanks for update
btw any telegram grup for this rom bro?

T1mb3 said:
Issues:
Security
Sepolicy
Selinux permissive
Tri-state -key
Stock camera app
Encryption
Click to expand...
Click to collapse
I'm unsure how these issues would affect me. Can anyone explain?
Does the encryption issue mean that encryption doesn't work at all?

Rydberg1 said:
I'm unsure how these issues would affect me. Can anyone explain?
Does the encryption issue mean that encryption doesn't work at all?
Click to expand...
Click to collapse
Your device will be less secure, as there is practically no sepolicy at all to prevent bad stuff from happening.
Encryption is not working (or has not been tested) so if your data is encrypted, the rom will not boot.

T1mb3 said:
Your device will be less secure, as there is practically no sepolicy at all to prevent bad stuff from happening.
Encryption is not working (or has not been tested) so if your data is encrypted, the rom will not boot.
Click to expand...
Click to collapse
I see. Thanks for the quick reply! To be on the safe side, I think I will wait a little bit with installing the ROM.

Can anyone tell me if it is valid for daily use?
Customization?

How would one be able to do this for the 5/T?

freyrnygaard said:
How would one be able to do this for the 5/T?
Click to expand...
Click to collapse
All source are here
The ROM manifest is here
It should be doable just by including 5T's device tree and vendor files. However the device tree will probably need some modifications to work with our build system.

New build: download
Changelog 20191022:
Fix encryption. Encrypt instructions
Merge CAF-tag LA.UM.8.4.r1-04500-8x98.0

Nice work! Can you please make one for 5t too?

Flashed last build on my device decrypted : bootllop
Clean flash: rom , gapps, magisk , no-verity

morfances said:
Flashed last build on my device decrypted : bootllop
Clean flash: rom , gapps, magisk , no-verity
Click to expand...
Click to collapse
No need for no-verity yet.
Your issue is propably Magisk. Try to first boot the rom and only after that, flash Magisk.

Development [Kernel] [5.10.142] [AOSP/OneUI] Loki Kernel | Exynos2200 | S22 (Plus / Ultra)

Loki Kernel for S22 (Exynos)
Code:
/*
* Your warranty is now void.
*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Supported devices:
- SM-S901B (r0s)
- SM-S906B (g0s)
- SM-S908B (b0s)
Features:​- upstreamed to 5.10.142
- disabled Knox crap
- added a wakelock blocker (along with a default list - TLDR would be much better idle drain)
- fixed Wi-Fi hotspot on GSIs
- some other tweaks
- etc.
Instructions:​Flash the zip via TWRP / FKM.
Changelog/Downloads​
Telegram Group​
Kernel Source​
Thanks to haridhayal for all the help.
Thanks to afaneh92 for the kernel source/base.

Well, I might root my phone soon haha, this looks pretty cool

The Marionette said:
Loki Kernel for S22 (Exynos)
Code:
/*
* Your warranty is now void.
*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This kernel has only been tested on GSIs. It might work on OneUI but try it at your own risk.​
Supported devices (for now):
- SM-S901B
Features:​- disabled Knox
- added a wakelock blocker
- minor tweaks
- etc.
Instructions:​Flash the kernel image via fastbootd:
Code:
fastboot flash boot Loki_Kernel_v1.0_r0s.img
Changelog/Downloads​
Telegram Group​
Kernel Source​
Thanks to haridhayal for helping me and for his S21 kernel that was used as a reference.
Thanks to afaneh92 for the kernel source/base.
Click to expand...
Click to collapse
Hi There!
I would like to give this kernel a shot but would like to build it myself.
Could you give me a hand here since this is my first time, I do have programming experience, but none compiling Android kernels.
I see in your readme that you are using these dependencies:
/home/jgudec/Exynos2200/toolchain/
/home/jgudec/build-tools/
/home/jgudec/gas/
Could you please tell me for the toolchain, build-tools and gas where and what versions of those you got for building?
Thansk!

New builds up.
Changes:
- Upstreamed to 5.10.138
- Added builds for One UI along ones for AOSP
- Other tweaks regarding performance and battery life (at least I hope so)
- Added more wakelocks to the blocking list

So as this is my first Samsung phone which seems less "mod" friendly then my previous devices;
I am rooted exynos base s22 on AVG6 as I'm not able to successfully flash newer firmwares.
Can I just flash this with FKM and live happily ever after?
Or are there some prerequisites or things to consider?
Appreciate the work! It's a shame to see the lack of custom development, so thank you!

bamn said:
So as this is my first Samsung phone which seems less "mod" friendly then my previous devices;
I am rooted exynos base s22 on AVG6 as I'm not able to successfully flash newer firmwares.
Can I just flash this with FKM and live happily ever after?
Or are there some prerequisites or things to consider?
Appreciate the work! It's a shame to see the lack of custom development, so thank you!
Click to expand...
Click to collapse
I've updated the kernel source with changes from the AVG6 firmware, so you should be good to go.
If any issue arises, you can always go back to the stock kernel.
It is a shame (the development state), but hopefully that will change as more time passes.

Thanks for your fast reply.
Just to be sure, when flashing with FKM there is nothing wiped?
If for some reason I would want to go back to stock i need to go through Odin or is stock kernel available somewhere?
If I would find a way to update to AVH9 (or newer) normally the kernel should still be compatible right?

bamn said:
Thanks for your fast reply.
Just to be sure, when flashing with FKM there is nothing wiped?
If for some reason I would want to go back to stock i need to go through Odin or is stock kernel available somewhere?
If I would find a way to update to AVH9 (or newer) normally the kernel should still be compatible right?
Click to expand...
Click to collapse
When you flash a kernel, there is no need to wipe the data of your device.
You can get the stock boot.img by downloading the firmware, opening up the AP file in 7-Zip Z-Standard and opening up boot.img.lz4 (you need to use 7-Zip Z-Standard, not the regular 7-Zip, to extract .lz4 files) and taking out the boot.img.
After that, just compress the boot.img into a .tar file and flash that file through the AP slot of Odin.
You can also patch that boot.img with Magisk Manager (on any rooted or non-rooted phone) if you want it to be rooted from the get-go.

Jeik said:
When you flash a kernel, there is no need to wipe the data of your device.
You can get the stock boot.img by downloading the firmware, opening up the AP file in 7-Zip Z-Standard and opening up boot.img.lz4 (you need to use 7-Zip Z-Standard, not the regular 7-Zip, to extract .lz4 files) and taking out the boot.img.
After that, just compress the boot.img into a .tar file and flash that file through the AP slot of Odin.
You can also patch that boot.img with Magisk Manager (on any rooted or non-rooted phone) if you want it to be rooted from the get-go.
Click to expand...
Click to collapse
Thanks again!
Last question, couldn't I just flash the full (patched) AP file?
This would flash more than just the kernel, but that doesn't really matter right?

bamn said:
Thanks again!
Last question, couldn't I just flash the full (patched) AP file?
This would flash more than just the kernel, but that doesn't really matter right?
Click to expand...
Click to collapse
Of course, you can flash the whole AP package, I just am not sure if it will then wipe your data.

Jeik said:
Of course, you can flash the whole AP package, I just am not sure if it will then wipe your data.
Click to expand...
Click to collapse
So far it hasn't, I've been flashing a lot trying to get the latest update installed.

does this work on a snapdragon S22?

ngc1952 said:
does this work on a snapdragon S22?
Click to expand...
Click to collapse
For snapdragon have kernel bklyn in telegram group https://t.me/bklynrom

sloeberiaan said:
Hi There!
I would like to give this kernel a shot but would like to build it myself.
Could you give me a hand here since this is my first time, I do have programming experience, but none compiling Android kernels.
I see in your readme that you are using these dependencies:
/home/jgudec/Exynos2200/toolchain/
/home/jgudec/build-tools/
/home/jgudec/gas/
Could you please tell me for the toolchain, build-tools and gas where and what versions of those you got for building?
Thansk!
Click to expand...
Click to collapse
Did you get a proper manual @sloeberiaan ?
I also wanna build my own kernel for S22 and flash it with TRWP/FKM, but I cant find proper "newbie" friendly documentation so far.
I tried LineageOS self building setup, thats works great with S10 ... but unfortunately not with S22 of course
So my intention is to add some features to the kernel to run docker. As mentioned in https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
Cheers!

lowowly said:
Did you get a proper manual @sloeberiaan ?
I also wanna build my own kernel for S22 and flash it with TRWP/FKM, but I cant find proper "newbie" friendly documentation so far.
I tried LineageOS self building setup, thats works great with S10 ... but unfortunately not with S22 of course
So my intention is to add some features to the kernel to run docker. As mentioned in https://gist.github.com/FreddieOliveira/efe850df7ff3951cb62d74bd770dce27
Cheers!
Click to expand...
Click to collapse
Hi
I am afraid I never did find one, also could not spend anymore time on it
Did you ever manage to figure it out yourself?
Regards

sloeberiaan said:
Hi
I am afraid I never did find one, also could not spend anymore time on it
Did you ever manage to figure it out yourself?
Regards
Click to expand...
Click to collapse
No, not really. Couldn't find a manual. I found more like a solution inside the "build_menu" bash script from afaneh92 located inside the kernel config.
Just download/git clone the kernel source
The bash script "build_menu" will automatically install build-tools, gas and clang. Then you are good to go to compile your own kernel with the commands inside the build_menu. Steps are build kernel -> create flashable zip -> flash with TWRP or FKM. To adjust features you have to rewrite the defconfigs or adjust the build_menu script.
At the moment I stuck in bootloop after flashing my own kernel with additional features. Have a look at this post.

Can this kernel be flashed into a stock ROM?
What does it improve?

No updates?

lowowly said:
Not really find a manual more like a solution inside the "build_menu" bash script located inside the kernel config.
Just download/git clone the kernel source
The running bash build_menu, it will automatically install build-tools, gas, clang. The you are good to go to compile your own kernel with the commands inside the build_menu. Its more like build kernel -> create flashable zip -> flash with TWRP or FKM. To adjust features you have the rewrite the defconfigs or adjust the build_menu script.
At the moment I stuck in bootloop after flashing my own kernel with additional features. Have a look at this post, I explain my problem.
Click to expand...
Click to collapse
Good morning, i git cloned the source, then i make "build_menu", but i have this error.
How can i fix it?

insestito said:
Good morning, i git cloned the source, then i make "build_menu", but i have this error.
How can i fix it?
Click to expand...
Click to collapse
First time you started the build_menu script, did it automatically download the necessary tools (gas, clang, build-tools)? The location should be in the parent directory (../Downloads). Are there any folders with naming clang-r416183b, gas or build-tools?