Hello
I want to build a resurrection remix Oreo ROM for my d2can/d2att but I can't seem to find the proper device tree and kernel tree for Oreo. Is there a way to either port the nougat trees or make my own tree compatible for Oreo?
It is but you are going to go through literal hell learning how to do so. i am working on the same thing and have some stuff figured out but getting help has been next to impossible. you have to read countless websites piecing the information together and trying things until it works. you can go into the lineageOS IRC but they dont talk too much, and like answering questions even less. What i learned was a bit easier then using the lineage repos for everything was just to sync lineage 15.1 or 16.0 and then to google around for a device tree and kernel. they usually still come from github but have different names. for example our s3 here goes by more names then d2att for example. SGH-i747 is another variant of s3. if you look for the other variants you will find more device trees. you can get lunch to show them to you by adding them to the vendor folder before you attempt to run the envsetup.sh as for the boot.img you will need to again google around a bunch and learn about mkbootimg and the tools needed to extract and repack them, if you use superrs-kitchen you will extract and see the files bot many will have a lock, and you cant edit the init.rc. you can extract your boot from your device directly via adb, or download a rom and unzip it n grab that boot.img if you use a rom you know works. you can change the OS version and all necessary info in the files to tell the phone its android 8.1 and whatnot. but as i said its not a short process. ive spent many many night getting frustrated because lunch fails partway into a build, or i flash a kernel i complied and it doesn't work. getting Pie 9.0 and Oreo 8.1 to boot on my s6 edge plus was a nightmare and a half, and the s6 files are all readily available to me from lineage to use as a base. the s3 was really popular however, and i know lineage has a nougat rom for it, so they must have repos with trees
---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------
https://github.com/Bdaman80/SGH-I747
device tree.
https://github.com/sgs3/SGH-I747M_Kernel
kernel
Related
hello,
I've noticed that there is a guide for building CM14 for the oneplus 3. Myself and others have been able to use it to make personal builds and to learn some things along the way.
I would imagine that the next step to progress to would be to make builds of ROMs that don't have a nougat/CM14 branch in their repo for our device. Its pretty easy to brunch, select your device, and wait for the build to finish. But I am very interested in learning how to build a ROM using a device tree from another repo.
I've noticed that @Eliminater seems to be very proficient at this, as he has built and posted unofficials of various ROMs.
I've been trying to teach/learn this myself through searching for guides, but havent been able to find anything that helps me get there 100% of the way.
I've been able to get as far as forking the device tree, editing the .mk and .dependencies files to match the format needed for the ROM I'm trying to build. I've also added the forked device tree and additional repos to the local_manifest. This has gotten me far enough that I have been able to do a successful "lunch", but I haven't gotten a build to finish. In fact, they fail pretty early on.
Is anyone able and willing to explain the process further?
Are there additional steps that I'm missing?
Or do you just need to be proficient enough to troubleshoot error after error when building?
Thanks in advance
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
daWeeZel said:
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
Click to expand...
Click to collapse
I have found the files in this repository : github.com/OnePlusOSS/android_vendor_oneplus_oneplus3/blob/oneplus3/6.0.1/sbin/dashd
Sorry the forum doesn't allow me to post link ...
I am after some help in building LineageOS 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx). I know it isn't officially supported (only 14.1 is official), however there are unofficial builds and apparently all the sources required are on GitHub.
I have tried LOTS of times to build this but each build has the same issues when flashed to the S6 Edge I have to test with.
I have followed the guide here - https://wiki.lineageos.org/devices/zeroltexx/build which officially covers building Lineage 14.1. I have wiped an i7 PC with 24GB RAM and 2 * 1TB disks. I installed Ubuntu 18.04 desktop, installed all updates, added all the required components listed in the guide (I also needed to add python that wasn't listed). I changed the repo sync command to be 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.1'. I then pulled in the 'zero.xml' repo manifest from here - https://github.com/Exynos7420/local_manifests and added it to /.repo/local_manifests/ and then built the ROM.
It appears to build OK - there are lots of errors in the log, however I think this is correct? It takes about 37-minutes and it outputs a .zip file in the out/product/zeroltexx directory. This installs OK to the S6 Edge, however there is an error at the start of it booting about selinux (small red text at the top of the screen for a couple of seconds). Once booted the audio doesn't work and neither does the RIL. This is compared to the unofficial ROM that Enes Uzun has created.
I have asked (and asked...) for help on the telegram group, however I keep getting told I am not doing anything wrong. If this is the case then I am doing something wrong in creating my build environment - i.e. Ubuntu or the Lineage build parts.
I am hoping someone on here has had a similar experience and managed to solve the issues or can point me in the right direction as I am stumped. I have wiped the machine and rebuilt Ubuntu 18.04 desktop 3 times so far. Following the build the results are the same each time so whatever I am doing wrong I am doing it each time.
Any help is really appreciated.
Andy
Help....
In my continuing failed attempts at building this I have now wiped another PC - Intel Core 2 Quad-Core Dell XPS with 16GB RAM and 2 * 640GB hard drives, installed Ubuntu 18.04, followed the guide etc etc etc and have hit EXACTLY the same issue so I am definitely doing something wrong.
I found this guide - https://forum.xda-developers.com/android/software-hacking/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 16.0, however there is a link to this - https://web.archive.org/web/2018061...ng/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 15.1.
So I wiped the original i7 24GB machine and installed Windows 10 Insider Preview 18290, enabled WSL and then added Ubuntu 18.04 from the microsoft store and then followed the guide TO THE LETTER and added the zero.xml from https://github.com/Exynos7420/local_manifests to the /.repo/local_manifests folder, did a 'repo sync' etc etc. Guess what? same f'cking issue..
Help please anyone? I just want to build my own Lineage 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx) so that I am not reliant on someone else releasing randomly periodic ROMs that are likely to stop when the developer stops building Lineage 15.1.
Help...
Fixed it....
The zeroltexx sources were incomplete. They were missing some files and a couple of files were wrong. These have now been updated by the maintainer (https://github.com/Exynos7420/android_device_samsung_zeroltexx), however these haven't been pushed to the official Lineage repositories yet (https://github.com/LineageOS/android_device_samsung_zeroltexx). Therefore if you are going to build it yourself you will need to use the Exynos7420 repositories (for the S6 Edge zeroltexx that is - the S6 zerofltexx has the right stuff).
Andy
Hi ADB100,
many thanks! I will try the same, after my lovely S5 get's the black-screen-of-death.
My colleague gave my an old S6, but I had lerned to love los 16.
My problem was to know howto add additional sources to the los 16 sources. Here your thread gave my some important tips.
I started to learn a build with the official sources of los 14.1, but it failed of less ram on my computer and an out of memory error message.
So I grabbed 6 gb of an old pc to give it a next try next week. If it will work I will tdy los16.
I'm not a developer, but familiar with Linux. My problem is to add all sources and to manage git and repo.
Additional to use the zero.xml. I put it on your mentioned folder, but "breakfast zero" or "breakfast zeroltexx" sent me a nothing found!
Do you have a good tutorial which I can follow?
I spent a lot af time to search for it, but all tutorials was for official build, same like the los build guide.
Hi,
I have compiled the master branch of vanilla AOSP for my Pixel 3a XL (bonito) multiple times now, and I can't get it to boot... It seems impossible
I was confused by Google's guide which of the two blobs are the right ones (either "latest Google's drivers" or "Binaries Preview" (I'm not allowed to post the link, it's the android source site, downloads, download proprietary binaries)), so I compiled AOSP with both of them each, none worked. It didn't work without the blobs either.
After flashing the self-compiled AOSP it reboots from fastbootd to fastboot saying the reason would be reboot bootloader. When I press start I get the orange message (that my device is customized and cant be trusted) and one second after seeing the Google logo the screen turns black and it reboots to the fastboot mode, again saying "reboot bootloader" would be the reason.
When I try to open the stock recovery the same happens, but the reason for the fastboot mode is "error booting boot.img"
I always reinstalled the factory images after an unsuccessful AOSP flash, the device is ok. Boot slot is B right now and didn't ever change as far as I remember. I even installed GrapheneOS as a custom ROM via fastboot, worked. So something is probably wrong with my image.
I don't have a server with 50GB RAM, Just a Ryzen V laptop with 16GB RAM. Compiling takes the computer about 10h. I did it 3 times until now, downloading the source took 4h. I don't know what to do next, but I don't want to give up, although I'm frustrated.
I just want to experience vanilla Android aka AOSP one time in my life. If someone has a successful build of AOSP without making major changes to the source code before compiling I would be very happy.....
Please help me
P.S. These are the instructions I used to compile it:
Code:
source build/envsetup.sh && lunch aosp_bonito-userdebug
Code:
m -j3
flashing worked with
Code:
$(which fastboot) flashall -w
there was only one error - "Erase successful, but not automatically formatting.
File system type raw not supported."
But this occured even with flash-all.sh from the factory images.
[edit: Sorry, I have a 3a XL (bonito), not a 3 XL]
Looking for any pie rom myself..
Did you have any luck? I'm looking for any 9 pie rom myself ..
I successfully built aosp 10 for my pixel 3a (not xl) but I had to chose the correct branch. Some versions aren't meant for specific devices. You can see what is suppose to be available for your device in the list I mention
Lookup "aosp codenames tags and build numbers" and open the first link. It has a list of all the different branches to build. I chose to build the branch "android-10.0.0_r38" (for future reference the build number associated with that branch is "QQ3A.200605.002") .
Now let me explain. When I check for updates on my devices it says I'm all up to date and that I'm running Android build "QQ3A.200605.002" but if you look at the chart on the webpage there are two more updates for the pixel 3a. They are Android-10.0.0_r39 and r40. "But wait, my phone says I'm all up to date, why don't I have those updates?" You may ask. Well. Your carrier or you device may not support it. There's different models of devices sharing the same name, they're for different carriers and international carriers.
So my own personal suggestion would be keep track of which updates are available to YOUR device, ignore what the chart says is available. For me Android r39 and r40 aren't available as updates so they probably won't work for me. But r38 is available and in currently running a modified version of it so it should be safe to build.
Now I just have to go get the binaries available. So for example I'm building the branch "Android-10.0.0_r38" and the matching build number is "QQ3A.200605.002" so I search the Googles for "nexus pixel driver binaries" choose the first link and find the set of binaries that match my build number "QQ3A.200605.002". Now I'm ready to build.
Funny enough, I have a repo sync going on right now and I'm gonna build in a few minutes. Let me know if you need more help.
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
kevinchristopherson said:
Did you have any luck? I'm looking for any 9 pie rom myself ..
Click to expand...
Click to collapse
Android 9 has been hell for me to build. No succesful builds with pie but Android 10 works amazingly ?
I'm trying to build for a device that has no known Android 10 device trees that I can find. I think I fleshed out the trees pretty well by following some sister/cousin devices and extracting a lot of stuff from the rooted phone itself, but my build fails at 2% due to a missing output file. The missing libdss.so file should be built as part of the kernel (whose source I have), but the build clearly isn't happening (or isn't happening in time to be recognized by the build system.)
I tried to build the kernel as a standalone module to see what might be wrong, and in trying to do that I can't seem to resolve all the issues with dependencies for cross-compilation to arm64. I've built for devices with existing trees by cherry-picking what I needed, but I've never built for something from the ground-up like this. I don't want to make the ROM with a pre-built kernel as the end-goal would be to become official. The attached image is the exact error I'm receiving, and the following links are to all of my source repositories that I'm using in addition to the Lineage17.1 base. Any help would be appreciated. I work as a full-time dev by day, I don't mind slogging around in some code if that's what I takes, I've just reached the end of my troubleshooting knowledge here and am not sure what the next step might be.
https://github.com/polaarbear/android_device_motorola_troika_sprout
https://github.com/polaarbear/android_device_motorola_universal9610-common
https://github.com/polaarbear/android_vendor_motorola_universal9610-common
https://github.com/polaarbear/android_kernel_motorola_universal9610