So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>
Related
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918
ROM Lineage 15.1 unofficial. Built with latest GCC+ compiler.
All credits go to Lineage team.
Download Link
https://www.androidfilehost.com/?fid=818070582850505463
XDA:DevDB Information
Lineage 15.1 Unofficial, ROM for the Nexus 6
Contributors
Rondeau79
Source Code: https://github.com/LineageOS/android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader ,latest TWRP
Version Information
Status: Stable
Created 2018-04-03
Last Updated 2018-04-03
Or you just use the official version here:
https://download.lineageos.org/shamu
does it force encrypt the phone?
mahir555 said:
does it force encrypt the phone?
Click to expand...
Click to collapse
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Render issue upon booting
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
aradhya10 said:
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
Click to expand...
Click to collapse
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
gothy.gothy said:
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
Click to expand...
Click to collapse
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
HueyT said:
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
Click to expand...
Click to collapse
In terminal adb/ recovery or app shell terminal:
Setprop persist.lineage.nofool true
That will fix that annoying notification.
toto-w said:
Or you just use the official version here:
https://download.lineageos.org/shamu
Click to expand...
Click to collapse
April fool's joke is terrible.
TheGreatess1223 said:
April fool's joke is terrible.
Click to expand...
Click to collapse
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
yes. yes they did. the dirty rat bastards
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
Yes and have not released a updated yet. Lol
There is the 4/12/18 15.1 version available.
Sent from my Nexus 6 using Tapatalk
@Rondeau79
Now that we have official builds I think this thread doesn't make much sense anymore.
Can you please delete it?
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
webdroidmt said:
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
Click to expand...
Click to collapse
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
I personally love UNOFFICIAL builds and don't see any harm especially since OFFICIAL builds can be just as unpredictable and/or unavailable
Rondeau79 said:
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
Click to expand...
Click to collapse
It's only because this is confusing users. I get so many logs from users thinking they use lineage but they're using some custom, inofficial homebrew build.
toto-w said:
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Click to expand...
Click to collapse
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
DDQW said:
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
Click to expand...
Click to collapse
In the meantime I found out that Magisk modifies the force encryption flag too and Magisk survives OTA updates.
Hi
After LeMax2 Project Treble port, I decide to bring up to our device too. Since I've x720 6/64 variant this project was possible to me tho due to QFIL tool in case of bricks, but wasn't need thanks for god.
Project Treble as Work in progress, please read the OP before flash/bla.​
and let's the party begin. check sreenshots in "Screenshots" or in the second post.
READ ME FIRST:
it's a buggy rom: I don't care about that, since I put [WIP] that mean new fixes will coming up.
Respect works of devs because they spend time and energy to do these things.
I did not tolerate ETA.
Compatible Devices:
x720: yes.
x722: yes.
x727: yes.
How is possible:
click here.
How I done:
Porting patches of TWRP to our one that I will release one for us too.
Applying the kernel patch from LeMax2 one to mount vendor on ZL1.
Compile the whole rom with Project Treble flags in device tree and proprietary blobs.
Works
Audio.
ADB.
Bluetooth.
Camera.
Display.
Fingerprint.
Graphics: hwcomposer & gralloc.
Internal Storages.
Hardware navigation buttons.
LeEco Extras.
Lights.
NFC.
RIL
Sensors.
USSD Codes: seems works
Wifi.
Bugs
Tell us more, all credits goes to codeworkx fir his fixes and works .
Installation Guide:
Copy my unofficial los to internal storage
Download my own TWRP and flash it via fastboot.
Download the partition.zip from linked thread. credits: @shivatejapeddi
Flash the whole partition.zip (don't panic if give the error it's ordinary administration.)
Go back to Wipe->uncheck all partition except the vendor, tap swipe to wipe it then.
Optional: you can go to Mount to see if mounted.
Wipe: dalvik, cache, data and system.
Now flash the whole rom that will install the vendor.img automatically, reboot device once finish installing then.
Enjoy Project Treble.
TWRP
Click here.
Credits:
LePro3 Developers.
LeMax2 Developers, without them wasn't possible for the unsed partition.
Sources:
https://github.com/hak86
XDA:DevDB Information
Treble x72x, ROM for the LeEco Le Pro3
Contributors
haky 86
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.18.x
ROM Firmware Required: EUI 20s or Newer
Based On: LineageOS
Version Information
Status: Testing
Stable Release Date: 2018-07-25
Beta Release Date: 2018-07-25
Created 2018-07-25
Last Updated 2018-07-24
** Note **
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
** Note **
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
How Can I flash Android P Developer Preview 5:
Click on the following link.
Download ARM64 System A image. and 3 zips for post GSI.
Flash the system.img of Android via fastboot (recommend).
Reboot to TWRP.
Go to Mount-> check Vendor partition.
Flash the 3 zip as they arranged (1-2-3),
Reboot, enjoy Android P DP5.
NOTE:
This project has nothing to do with official updates, I did Project Treble by my initiative that will not affect with official roms. Might someone will reconsider supporting Treble even with official update tho?
Damn Congratulations!
I can't do it today. But, I will definitely try it this weekend. Thanks for sharing these test builds. I am definitely looking forward to checking it out!
Thanks again!
I will go ahead and download it and get started ASAP.
---------- Post added at 08:48 PM ---------- Previous post was at 08:41 PM ----------
haky 86 said:
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
Click to expand...
Click to collapse
I just want to say again, that you are awesome for doing this, I didn't think it was possible with this phone. I am blown away! Nice job!
Hmmm can I shirk off my plans and install this right now? lol!
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
I have a question about Gapps, Magisk and firmware.
I assume Firmware is not an issue since it would still get flashed to the correct partition. With Magisk, I assume that you would prefer that we use 16.7?
What should we use for Gapps? Do you have a specific Gapps in mind?
Wonderful Work~
Its a great! Wonderful work, now wait to fix all bugs now.
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
what should i say , it is great job !!!!!
haky 86 said:
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
Click to expand...
Click to collapse
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Any info about IR support and NFC Smartcard Service?
Most hyped project for now, congratulation. Peoples don't even woke up and already you haven't 2 pages of comments and 15 likes. Congratulation! If everything will be good I'll buy you a beer
Crystal-L said:
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
Click to expand...
Click to collapse
let me fix all those bugs and I can port the rom you want then.
shivatejapeddi said:
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Click to expand...
Click to collapse
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
qqzwc said:
Any info about IR support and NFC Smartcard Service?
Click to expand...
Click to collapse
NFC already fixed just check "Works"
D1stRU3T0R said:
Most hyped project for now, congratulation.... If everything will be good I'll buy you a beer
Click to expand...
Click to collapse
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
xen2001 said:
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
Click to expand...
Click to collapse
) hopefully will work on x722, bcs always there is the problem.
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
Can you answer the question about Gapps?
Is a version of Gapps available for this yet?
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
shivatejapeddi said:
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
Click to expand...
Click to collapse
alright, I also forget to edit the mk files like Android.mk in the proprietary blobs probably that's why buggy.. I'll post new screenshots once got fixed :angel:
Damn, I sell my device.
Thank you for your support.
lazye53 said:
Damn, I sell my device.
Thank you for your support.
Click to expand...
Click to collapse
too late <3
well let's give this a go on x722 and see what happens .. Thanks for the hard work, it's highly appreciated !
are there any roms for the N200 5G that would give better performance?
let me know
Try a GSI for now. One specific individual had been cranking on getting a device tree together, and if you have any experience, he could use your help.
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
twomad said:
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
Click to expand...
Click to collapse
ok How do we flash roms on the N200 5G?
rinnycoop121 said:
ok How do we flash roms on the N200 5G?
Click to expand...
Click to collapse
There are multiple tutorials on the internet. Here's an example https://www.droidwin.com/install-android-12-gsi-roms-on-oneplus-nord-n200-5g/
Here is my guide:
GSIs on N200
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing. With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot...
forum.xda-developers.com
Note that I do not recommend GSI's as I cannot get Magisk or VoLTE to work with them.
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
great
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
There are a few projects in the works. I personally am waiting to sell my current laptop to fund a ryzen 5 5600 dev rig which will allow me to build a larger variety ROMs as I add storage. I have it worked out where the price of my laptop will give me enough to order everything but storage drives. Settling with a single 16GB dimm to maximize upgradability while maintaining the best price to performance ratio currently available.
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
hey buddy, i seen your trees, looking good. i just got my n200 and am waiting for unlock code. i built your rom with your trees and will flash once i'm unlocked. Thanks for all your hard work! as far as i can see you"re the only one working on n200 (dre9). do you accept pull requests rom and/or device side?
You can submit patches via review.evervolv.com gerrit. I am also on telegram if you have questions (just no eta requests). Kernel has been purged of Linux stable merges to be closer to the caf tag used. Trees are lineage compatible via 2 reverts if anyone wishes to build for lineage
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
andr01dfr3ak said:
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
Click to expand...
Click to collapse
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
rc420head said:
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
Click to expand...
Click to collapse
I also have a bunch of stuff on gerrit cleaning up previous issues and further refinement. Message me on telegram @andr01dfr3ak and maybe we can work together to avoid reinventing the wheel.
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
AboveTG said:
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
Click to expand...
Click to collapse
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
Alright not gonna lie man, im kind of new to all this, but I downgrade with the msm tool and ill try to figure out how to build. I know I need to fork it, but after that I have no clue what to do.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
I found a payload dumper on github that works well. I renamed it payloaddumper+ because I felt it fit the tool name better. should work as a portable app I believe. Just run the .exe. Hope this helps.