Related
hi guys . i wanna build omfgb for galaxy ace .. but i have some problem :
this terminal log :
[email protected]:~/omfgb/omfgb$ . build/envsetup.sh
including device/samsung/android_device_samsung_cooper/vendorsetup.sh
including vendor/omfgb/vendorsetup.sh
[email protected]:~/omfgb/omfgb$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. cooper-eng
3. cooper-userdebug
4. OMFGB_ace-eng
5. OMFGB_desirec-eng
6. OMFGB_heroc-eng
7. OMFGB_inc-eng
8. OMFGB_mecha-eng
9. OMFGB_sholes-eng
10. OMFGB_supersonic-eng
11. OMFGB_fascinatemtd-eng
12. OMFGB_mesmerizemtd-eng
13. OMFGB_showcasemtd-eng
14. OMFGB_vibrantmtd-eng
15. OMFGB_vivow-eng
16. OMFGB_shadow-eng
17. OMFGB_p999-eng
Which would you like? [full-eng] 3
build/core/config.mk:136: *** No config file found for cooper . Stop.
** Don't have a product spec for: 'cooper'
** Do you have the right repo manifest?
[email protected]:~/omfgb/omfgb$
Click to expand...
Click to collapse
any people can help me ?
thanks before btw sorry for my bad english
No config file present...
I got transformed into a potato while writing this post..
Prawesome said:
No config file present...
I got transformed into a potato while writing this post..
Click to expand...
Click to collapse
can you help to find config file ??
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!
NetHunter -
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The Kali Linux NetHunter project is the first Open Source Android penetration testing platform for Nexus devices, created as a joint effort between the Kali community member “BinkyBear” and Offensive Security. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports Wireless 802.11 frame injection, one-click MANA Evil Access Point setups, HID keyboard (Teensy like attacks), as well as BadUSB MITM attacks and is built upon the sturdy shoulders of the Kali Linux distribution and tool sets. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
Instructions -
1. Install any ROM of your choice (AOSP, CM, Tesla)
2. Flash Gapps
3. Reboot
4. Setup your phone settings.
5. Go to Recovery and flash nethunter zip.
6. Reboot (It might reboot a couple of times, please setback)
7. Open NetHunter app to finalize settings.
Notes -
- Major portion of Kali works on kernel. I'm maintaining a kernel specifically designed for this. Flashing of any other kernel will result in unprecedented consequences.
- There are underlying issues which might cause a reboot when PEN-TESTING. Personally, I had very very very few reboots while testing.
- I have tested this extensively with ath9k_htc wireless adapter. Problems might arise with it, but I have created solutions too.
- If anyone who has knowledge in pen testing and is willing to contribute, let me know following things works or NOT.
Wireless Injection - Working with ath9k_htc. RALINK, Realtek supported but not tested.
Bluetooth interfaces USB hacks - Not tested, since I have no knowledge nor time to learn it.
Y cable - This is also not tested, since I don't have any resources left to buy new stuff.
Other Pen testing stuff - Again, not tested. But I have checked cSploit on my network and it works awesome.
Bugs :
1) Since PRIMA wlan is built-in, when our external adapter is disconnected there is a kernel panic and it reboots.
Other things????
XDA:DevDB Information
[NH] Kali Nethunter, ROM for the Sony Xperia ZR
Contributors
Daedroza, Daedroza, binkybear
Source Code: https://github.com/daedroza/nethunter_kernel_apq8064
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-09-26
Last Updated 2016-09-26
Reserved
Renjen-n00b said:
for atheros chip based adapter users who are unable to get their wlan1 up or even shown in the terminal follow these instructions:
1- goto "nethunter terminal" app and tap on "Kali"
2- type "apt-get update"
3- type "apt-get install firmware-atheros"
4- check "airmon-ng" after re-plugging your adapter
-----------------------------------------------------------------------------
for realtek chip based adapter users who are unable to get their wlan1 up or even shown in the terminal follow these instructions:
1- goto "nethunter terminal" app and tap on "Kali"
2- type "apt-get update"
3- type "apt-get install firmware-realtek"
4- check "airmon-ng" after re-plugging your adapter
-----------------------------------------------------------------------------
for chips other than (realtek or atheros) users are asked to follow these instructions:
1- goto "nethunter terminal" app and tap on "Kali"
2- type "apt-get update"
3- type "apt-get install firmware-misc-nonfree"
4- check "airmon-ng" after re-plugging your adapter
Click to expand...
Click to collapse
- Also, remember that only 4 gigs is available after CM install. After chroot even less.
So, you might wana selectively install the pen-testings tools you want, unless you're using internal+external configuration.
Reserved
Download 1 -
https://drive.google.com/open?id=0B9yrk5QZnasiaUJXUVNSWTA5dWc
updated kernel(flash this over previous zip) and boot :
https://drive.google.com/open?id=0B9yrk5QZnasiaUJXUVNSWTA5dWc
Stuff to setup for wireless pentesting :
https://raw.githubusercontent.com/daedroza/bash-scripts/master/setup-for-work.sh
Sorry i have questions
1- its work on cm 13?
2- with this can i use aircrack
3- please insert screen shot?
Thanks
ostadmaster said:
Sorry i have questions
1- its work on cm 13?
2- with this can i use aircrack
3- please insert screen shot?
Thanks
Click to expand...
Click to collapse
Yes, and yes.
i didn't understand , it's a rom or app ?
and how i can delete it if it doesn't work well ?
Device must be UB or BL ?
Support to XZR Docomo/A?
Can't install linux-headers 3.4.0-perf-gbccb33a
Daedroza said:
- Also, remember that only 4 gigs is available after CM install. After chroot even less.
So, you might wana selectively install the pen-testings tools you want, unless you're using internal+external configuration.
Click to expand...
Click to collapse
Can't install linux headers 3.4.0-perf-gbccb33a ??
Pliz give me solution?
aggunawan said:
Can't install linux headers 3.4.0-perf-gbccb33a ??
Pliz give me solution?
Click to expand...
Click to collapse
Probably because there is 3.4.112 kernel present. You cannot overwrite this due to restrictions of Android system, what you are trying to achieve?
Daedroza said:
Probably because there is 3.4.112 kernel present. You cannot overwrite this due to restrictions of Android system, what you are trying to achieve?
Click to expand...
Click to collapse
Is there a custum kernel for LB users ?
Pliz
aggunawan said:
Is there a custum kernel for LB users ?
Pliz
Click to expand...
Click to collapse
No, the old stock ROM is bloated with security holes. You need a unlocked boot loader to flash a Kernel anyways, so why not use a custom ROM in first place and install this overlay without any troubles.
Im on tesla mm will it still be necessary to flash kernel ,this mm is on your airless kernel ?
An error occurred during the installation.
Hey. When I try to flash this zip, I get an error 1. Error: unable to extract! The zip may be corrupt or your device may not have enough RAM to proceed. Consider using a smaller installer if it is available. CM 13, the kernel is 3.4.112-cm, android is 6.0.1.
(TitTitTit) said:
Hey. When I try to flash this zip, I get an error 1. Error: unable to extract! The zip may be corrupt or your device may not have enough RAM to proceed. Consider using a smaller installer if it is available. CM 13, the kernel is 3.4.112-cm, android is 6.0.1.
Click to expand...
Click to collapse
Sorry, I haven't lately keeping track of this project.
It worked fine for me 6 months ago, that time we used 2.8.70 TWRP I guess.
Daedroza said:
Sorry, I haven't lately keeping track of this project.
It worked fine for me 6 months ago, that time we used 2.8.70 TWRP I guess.
Click to expand...
Click to collapse
YEEEEEEEEEEEEES, It was installed, thank you very much.
It does not quite work. I'm trying to pick up VNC, but the terminal print "command not found".
can this installed on custom rom with locked bootloader.?
download links not working!!
Please master @Daedroza, can you compile kernel for minitor mode internal wifi (wlan0) ?
@Daedroza . And please make the kernel support to magisk??
aggunawan said:
Is there a custum kernel for LB users ?
Pliz
Click to expand...
Click to collapse
Can this kernel use in Existenz ??
I am facing problem in building AOSP 18.1 i added the device tree given by remelia but i am facing error when i lunch.
Code:
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. full_fugu-userdebug
8. aosp_fugu-userdebug
9. aosp_car_emu_arm-userdebug
10. aosp_car_emu_arm64-userdebug
11. aosp_car_emu_x86-userdebug
12. aosp_car_emu_x86_64-userdebug
13. mini_emulator_arm64-userdebug
14. m_e_arm-userdebug
15. m_e_mips64-eng
16. m_e_mips-userdebug
17. mini_emulator_x86_64-userdebug
18. mini_emulator_x86-userdebug
19. uml-userdebug
20. aosp_dragon-userdebug
21. aosp_dragon-eng
22. aosp_marlin-userdebug
23. aosp_marlin_svelte-userdebug
24. aosp_sailfish-userdebug
25. aosp_walleye-userdebug
26. aosp_walleye_test-userdebug
27. aosp_taimen-userdebug
28. aosp_angler-userdebug
29. aosp_bullhead-userdebug
30. aosp_bullhead_svelte-userdebug
31. hikey-userdebug
32. hikey960-userdebug
33. lineage_grandprimeve3g-userdebug
34. aosp_grandprimeve3g-userdebug
35. cos_grandprimeve3g-userdebug
36. omni_grandprimeve3g-userdebug
37. du_grandprimeve3h-userdebug
38. aos_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 34
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "vendor/aosp/common.mk" does not exist. Stop.
@remilia15 @naimrlet
Help him , please
I think this thread is on wrong section now . Actually you need to post this in Q&A section
herawais said:
Code:
33. lineage_grandprimeve3g-userdebug
34. aosp_grandprimeve3g-userdebug
35. cos_grandprimeve3g-userdebug
36. omni_grandprimeve3g-userdebug
37. du_grandprimeve3h-userdebug
38. aos_grandprimeve3g-userdebug
Click to expand...
Click to collapse
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?
remilia15 said:
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?
Click to expand...
Click to collapse
Yes i copy pasted someone's but how to delete other's recepies? can you please guide me as i am new in this work. what is the solution to the error showing .
Thanks
remilia15 said:
LOL, my device tree doesn't have too many recipes for lunch like this
Are you sure you didn't copy-pasta'd somewhere else?
Click to expand...
Click to collapse
these are new recipes and new error occurred.
Code:
33. aosp_grandprimeve3g-eng
34. aosp_grandprimeve3g-user
35. aosp_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 35
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "/build/target/product/aosp_base_telephony.mk" does not exist. Stop.
@herawis
Ask any one of moderators to move the thread to Q&A section
unknown said:
I think this thread is on wrong section now . Actually you need to post this in Q&A section
Click to expand...
Click to collapse
respected member would you please move this post to Q&A section..
herawais said:
respected member would you please move this post to Q&A section..
Click to expand...
Click to collapse
Ask a moderator to do it
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
herawais said:
these are new recipes and new error occurred.
Code:
33. aosp_grandprimeve3g-eng
34. aosp_grandprimeve3g-user
35. aosp_grandprimeve3g-userdebug
Which would you like? [aosp_arm-eng] 35
build/core/product_config.mk:232: *** _nic.PRODUCTS.[[device/samsung/grandprimeve3g/aosp_grandprimeve3g.mk]]: "/build/target/product/aosp_base_telephony.mk" does not exist. Stop.
Click to expand...
Click to collapse
Edit that .mk file
maybe change it to full_base_telephony
And aosp has aosp_base_telephony , are you sure that you have synced the source completely ?? @herawais
If you are trying to build vanilla aosp with cm (or cm-based) device trees, you are very likely going to have to edit the device tree just to get it to build.
Synthetic.Nightmare said:
If you are trying to build vanilla aosp with cm (or cm-based) device trees, you are very likely going to have to edit the device tree just to get it to build.
Click to expand...
Click to collapse
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1
herawais said:
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1
Click to expand...
Click to collapse
I wouldnt know what all youd have to modify, but based on your build errors, id start with the Makefiles.
With that in consideration, id recommend you try building something based on lineage (or just lineage, itself) and start modifying that, just so you can start getting an idea of how aosp is compiled. Theres a lot to take in.
herawais said:
I dont know how to edit the the files and which file should edit? This is the device tree for aosp 8.0 and i am using it for aosp 8.1
Click to expand...
Click to collapse
Just use 8.1 kernel to build it
Hello
I’m building my own android image (so obviously I have the source code)
I want to add my own drivers (specific ones), but I have no idea about how to add them, so any help?
Regards
Any help guys ? srsly, i'm very stuck here
do you mean your device tree?
DSA said:
do you mean your device tree?
Click to expand...
Click to collapse
yes
If the device trees exist, you will need to add a local_manifests folder & roomservice.xml into your repo folder with the relevant details included, mine is attached as an example.
If not, you will need to create them, heres a couple of initial guides:
[GUIDE] How to make a device-tree for your phone
Welcome in this new tutorial! In this thread, i'll try to explain you how to create a device-tree. This is one of the most important part in the rom porting. So let's start right now! Warning: i took as example an Samsung phone and 7.0 rom. 1...
forum.xda-developers.com
How to create Device tree for Android Rom building
How to create Device tree for Android Rom building I assume you already downloaded source code before we start please do following 1. Install unpackbootimg Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git...
forum.xda-developers.com
Drivers can change for every device. Which devices do you want to support?