Related
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!
According to Project Treble lead Iliyan Malchev,
Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work.
Click to expand...
Click to collapse
Now that there's an Oreo beta for the Essential Phone that supports Treble, perhaps this can be used to further development on the device.
/u/foremi on Reddit confirmed that simply flashing a Pixel 2 system and boot image to the device is not enough, as it fails to boot, so the question is what constitutes a generic AOSP build?
I don't have Linux installed right now or I'd build it myself, but I suspect that building it with the simple target device of "generic" might be what Malchev is referring to.
If any devs would like to test this theory or give their input as to how they think this actually works I think it'd be incredibly useful for not just Essential phone development, but Android development as a whole.
EDIT: @phhusson confirms that the target device should be aosp_arm64_ab
FWIW "generic AOSP build" is really what it says it is.
I have access to the "Google certification generic AOSP build" (that's weirdly not public, I don't know why), so I gave it a try. (Edit: So if the ROM was Treble-certified, it would work)
I get the Android bootanimation, but that's all (I have to say that's still a big step forward compared to other Android versions
Looking at the logs, I see a loop of crash because of: /vendor/bin/hw/[email protected]
Which I guess is the HAL for the accessories, but that doesn't seem to be the reason for the crash
The reason of the crash, seem to be this:
11-15 12:59:04.491 5331 5331 F MediaProfiles: frameworks/av/media/libmedia/MediaProfiles.cpp:329 CHECK(quality != -1) failed.
in CAF, frameworks/av/media/libmedia/MediaProfiles.cpp we see vendor-specific (i.e. not in AOSP) quality attributes, like "vga"
And it is defined by Essential's framework (in vendor/etc/media_profiles_V1_0.xml)
Considering there are media_profiles xml files, I'd guess that _V1_0 is supposed to only contain AOSP-capable qualities
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Edit3: the generated fingerprint is too long to build, needs to do make BUILD_NUMBER=4412360
Edit4: To make the situation more clear:
- NO, current ROM is NOT Treble capable
- BUT, almost everything is available for that. Every HAL is using "hwbinder" which is the basis, and most work needed for Treble
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
phhusson said:
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Click to expand...
Click to collapse
I was gonna link to the aosp_arm64 make file but it said it was specifically for the emulator so I wasn't sure, that's good to know though.
phhusson said:
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
Click to expand...
Click to collapse
Thanks for this, I suspected such but couldn't find a clear answer from Google on the matter so I suggested trying the boot.img as well just in case.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2. I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
For what it's worth I only have a LG V20 right now which currently doesn't support Treble, so I'm pretty useless as far as testing anything goes, but if this is figured out it'll greatly influence what device I go with when I eventually upgrade.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2.
Click to expand...
Click to collapse
Yup. I feel like Treble deserves its own "device" section in XDA
I'm afraid I'm working on something that other people already did on other devices...
I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
Click to expand...
Click to collapse
That's my guess as well.
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
MishaalRahman said:
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
Click to expand...
Click to collapse
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
PhantomGamers said:
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
Click to expand...
Click to collapse
Google Pixel/Pixel 2 will do, yes?
MishaalRahman said:
Google Pixel/Pixel 2 will do, yes?
Click to expand...
Click to collapse
Yeah they should be fine
PhantomGamers said:
Yeah they should be fine
Click to expand...
Click to collapse
Alright, I'll find you some testers
MishaalRahman said:
Alright, I'll find you some testers
Click to expand...
Click to collapse
Here's the system image if you find anyone, it's a straight fresh build of aosp branch 8.0.0r34
If it doesn't work it's possible that I messed the build up, but it should be fine.
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
PhantomGamers said:
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
Click to expand...
Click to collapse
Hero you go
TheDethEgineer said:
Hero you go
Click to expand...
Click to collapse
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
PhantomGamers said:
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
Click to expand...
Click to collapse
That's true only for new devices, not for devices upgrading for nougat to oreo.
I wasn't aware there was an AMA yesterday... Too bad we could have asked.
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
How about flashing the system image directly from a Pixel 2 XL?
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
PhantomGamers said:
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
Click to expand...
Click to collapse
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
MishaalRahman said:
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
Click to expand...
Click to collapse
I believe it should work as normal
fastboot flash system system.img
EDIT: Apparently with the A/B partitions you'd do fastboot flash system_b system_other.img to flash the b partition, but the aosp build didn't include a system_other.img so I'm assuming perhaps it's not necessary
So far I still can't find anyone willing to flash this on their Pixel haha. People are really hesitant to flash stuff on the Pixel it seems. Times are not like they used to be =\
Neutrino Kernel began as an effort to keep the stock LineageOS 15.1 kernel up-to-date with the latest linux-stable releases and has since evolved into an intensive crash course in maintaining my own custom kernel. Although some of you would accuse me of modesty, I think it's important to acknowledge that I am a "kernel developer" in the same way that Amy Schumer is a "comedian". That is to say, my work is highly derivative and built on the backs of individuals who are far more talented than I am. My role here is to have a vision, establish a design philosophy, and use the resources at my disposal to bring that vision to fruition.
Those of you who've perused my staging repo will know that I'm very particular about cleanliness. All changes and additions are vetted based on viability and purpose. Neutrino is based on kernel.lnx.4.4.r35-rel, pure CAF source for Android 9.0 tracking and upstreamed to the latest linux-stable release. I have manually rebased Essential's stock kernel source on top of CAF using relevant OEM commits from PPR1.181005.034. All major features and patchsets are assembled on independent staging branches of this codebase base and merged into the release repository.
I do not commit changes that I cannot justify or explain, and I do not go on indiscriminate cherry-picking sprees. There are a handful of developers that I highly respect, and who's projects have served as inspiration for my own. My intention is to incorporate the best of what they've brought to the table in a way that most effectively achieves and enhances this project's design goals.
I like to think that Neutrino is relatively subdued in terms of "features", with a stronger focus on optimizations over fluff. That being said, there have been quite a few additions which I feel have merit in terms of increased performance and/or efficiency provided the former does not compromise the later:
Revamped EAS implementation for Pie
sultanxda's CPU/GPU Boost Drivers
Dynamic SchedTune Boosting
Maple I/O Scheduler
Broader subsystem support for Power Efficient Workqueues
KCAL Color Control
Backlight Dimmer
Fsync Toggle (enabled by default)
GPU Underclock @ 180 MHz
CPU (partial) Overclock, Silver Cores @ 2035 MHz
Boeffla Wakelock Blocker v1.1.0
Wireguard Support
VDSO Support
Treewide memory allocation/overflow patches from mainline
OOM Reaper and various memory management enhancements to improve LMK
Treewide compiler warnings corrected
Built with self-compiled Clang 8.0.3 and GCC 8.2.0 toolchains, with a local initialization sanitizer and polly optimization flags
INSTALLATION:
**Neutrino now utilizes AnyKernel2 zip format for universal compatibility**
As a result, you can now flash this kernel on just about anything including Oreo/Pie custom and stock ROMs. The only requirement is that your firmware is current and up-to-date with PPR1.180905.036 at a minimum. Flashing on older firmware will result in broken input detection and a non-functional touchscreen.
That being said, this is an EAS kernel and is best suited for use on EAS-compatible ROMs. Just because it can be flashed on stock does not mean that you should do so. Installation on ROMs which do not natively support EAS (such as stock) will likely result in sub-optimal battery performance and I will not entertain any complaints stemming from the use of Neutrino on ROMs which are incompatible with EAS. Stock support is a perk and an experiment on my part, please do not make me regret giving you the ability to flash on stock, I will drop public support for it if this disclaimer is routinely ignored. If you choose not to heed my recommendations, you are doing so at your own discretion.
For ease of use, I would recommend using an app with built-in zip flashing functionality such as EX Kernel Manager or FK Kernel Manager. Of course, I cannot expect all of you to utilize a paid app for installation and as such, conventional installation via TWRP is certainly possible as well.
Neutrino will preserve existing Magisk installation during kernel update, meaning if you already have Magisk installed on your device you need not worry about reflashing Magisk when updating your kernel. If you do not already have Magisk installed and desire root access then Magisk zip must be flashed following kernel zip via TWRP.
DOWNLOADS:
Current releases can be downloaded here.
Archival builds (boot images) for lineage-15.1 can be found here.
SOURCE & SPECS:
Neutrino Kernel Source
Neutrino Staging Repo
Changelog
Linux Kernel Version: 4.4.166
CAF Release: LA.UM.7.4.r1-03900-8x98.0
Neutrino Kernel Version: hercules
Clang Version: neutrino clang 8.0.0-r348460
Build Date: 20181206
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
You're as awesome as you are humble. Thank you for this. Life is getting easier and easier for common users thanks to contributions like this. Awesome.
Arju said:
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
Click to expand...
Click to collapse
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
rignfool said:
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Hey, great to see you here. I remember you from the Nexus 6 forums. Thanks for the answer
Arju said:
Hey, great to see you here. I remember you from the Nexus 6 forums. Thanks for the answer
Click to expand...
Click to collapse
Yeah... I couldn't help myself... When I found out buying this phone was a direct thank-you to Andy Rubin...
Sent from my PH-1 using XDA Labs
Arju said:
@return.of.octobot Awesome! Thanks for bringing us upstream updates! So if I've understood it correctly if I do flash the root version and want to take an ota update, I'll have to revert to stock kernel for the lineage os version I was on or flash the non root version that you've provided us with before updating?
Click to expand...
Click to collapse
rignfool said:
When I had magisk installed and was running lineage... The OTA program didn't care about signatures...
Since it's not a Delta... It's not patching anything... Just overwriting what is currently there... So it SHOULDN'T matter...
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
He is right, I was recommending that the unrooted image be flashed prior to OTA but you could also certainly restore the boot.img that was originally included in invisiblek's build for maximum peace of mind. I would tend to agree that it doesn't actually matter as the OTA should be installing a completely new image on the opposite slot so I'm not sure what difference it would make, I was just leaning my instructions towards the safe side, perhaps I'll try and clean them up.
only for lineage can it work on aosp rom?
Sent from my PH-1 using Tapatalk
kakabobo said:
only for lineage can it work on aosp rom?
Click to expand...
Click to collapse
Yeah, it's literally built from Lineage source with upstream Linux kernel merged in. I wouldn't recommended flashing this on AOSP any more than I would recommended flashing the stock Lineage kernel on an AOSP build. Even if it booted I imagine there's a good chance it would break things to the point of being unusable. That being said, I haven't tried it so I'm only speculating. If you do, make sure you've got a copy of your ROMs stock boot.img to recover with. But seriously, I wouldn't.
return.of.octobot said:
Will be uploading 4.4.118 images within the next day or two, currently experimenting with merging the latest CAF tags into upstream source. Jury's still out on whether or not that's going to prove successful but I will be releasing standard linux-stable builds regardless.
Click to expand...
Click to collapse
Without further ado, 4.4.118 images are available for download here.
Same deal as before, built from unadulterated upstream linux-stable source. Stock and Pre-Patched Magisk variants available.
I did manage to get a CAF-based version of this kernel building and booting, however it broke my touchscreen and is clearly not ready for public consumption. So, until further notice we're going to stick with the 'if it ain't broke..' philosophy, although you may or may not see me releasing some experimental builds in the future.
For now, enjoy 4.4.118
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
return.of.octobot said:
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
Click to expand...
Click to collapse
That's for the build today right?
shooterlgk said:
That's for the build today right?
Click to expand...
Click to collapse
In theory these images should work on any LineageOS install, regardless of build date, but yes it's compatible with both the 02/26 and 02/28 releases from invisiblek. I've updated the screenshot in OP which shows this kernel installed on the latest Lineage OTA.
return.of.octobot said:
***OP updated for 4.4.118 release, revised comprehensive installation instructions***
Click to expand...
Click to collapse
flashed your kernel with magisk support on todays (28th) lineageos build. Magisk is not passing safteynet.
edit: followed your instruction to patch the boot img using magisk and now it passes safteynet. had to use the non patched on from here.
Arju said:
flashed your kernel with magisk support on todays (28th) lineageos build. Magisk is not passing safteynet.
edit: followed your instruction to patch the boot img using magisk and now it passes safteynet. had to use the non patched on from here.
Click to expand...
Click to collapse
Good to know, I'll have to make note of your findings in the OP. I would've never figured that out myself as I've got xposed installed and to the best of my knowledge my SafetyNet checks will always fail because if it. I've really just been offering the prepatched images because I thought it would be helpful to allow some to bypass the step of patching manually. However, I'll have to consider whether it might be a better idea to just provide the clean image with instructions on how to patch it.
return.of.octobot said:
Good to know, I'll have to make note of your findings in the OP. I would've never figured that out myself as I've got xposed installed and to the best of my knowledge my SafetyNet checks will always fail because if it. I've really just been offering the prepatched images because I thought it would be helpful to allow some to bypass the step of patching manually. However, I'll have to consider whether it might be a better idea to just provide the clean image with instructions on how to patch it.
Click to expand...
Click to collapse
So this is what I did.
1. Flashed lineage os. Set it up.
2. Flashed your kernel (non magisk version) using fastboot and booted back into rom. (Not sure if this is necessary as I later on flash the patches version by magisk manager).
3. Install magisk manager. Have the non magisk version of your boot image on my phone. Patch it with magisk manager.
4. Transfered the patched boot image to computer.
5. Flashed the patches boot image using the computer (fastboot). Reboot into system.
6. Safetynet check passes.
Arju said:
So this is what I did.
1. Flashed lineage os. Set it up.
2. Flashed your kernel (non magisk version) using fastboot and booted back into rom. (Not sure if this is necessary as I later on flash the patches version by magisk manager).
3. Install magisk manager. Have the non magisk version of your boot image on my phone. Patch it with magisk manager.
4. Transfered the patched boot image to computer.
5. Flashed the patches boot image using the computer (fastboot). Reboot into system.
6. Safetynet check passes.
Click to expand...
Click to collapse
Thanks for sharing. I essentially went through the same process to patch these images myself after they were built, perhaps there is some kind of security measure in place where the boot.img needs to be installed to the same device it was patched on? I find it strange that it would successfully root the device, but not pass SafetyNet. I'll think on that and figure out if it makes more sense to just release unpatched builds in the future.
return.of.octobot said:
Yeah, it's literally built from Lineage source with upstream Linux kernel merged in. I wouldn't recommended flashing this on AOSP any more than I would recommended flashing the stock Lineage kernel on an AOSP build. Even if it booted I imagine there's a good chance it would break things to the point of being unusable. That being said, I haven't tried it so I'm only speculating. If you do, make sure you've got a copy of your ROMs stock boot.img to recover with. But seriously, I wouldn't.
Click to expand...
Click to collapse
I flashed it on AOSIP without issue. Not sure if it's considered the same as AOSP.....
return.of.octobot said:
Thanks for sharing. I essentially went through the same process to patch these images myself after they were built, perhaps there is some kind of security measure in place where the boot.img needs to be installed to the same device it was patched on? I find it strange that it would successfully root the device, but not pass SafetyNet. I'll think on that and figure out if it makes more sense to just release unpatched builds in the future.
Click to expand...
Click to collapse
I wouldn't realy mind and I think it would make it easier for you too. If the patching is unique per phone then it makes sense that we patch it ourselves. But we need upstreamed updated kernels!!! so don't stop doing those!!
Arju said:
I wouldn't realy mind and I think it would make it easier for you too. If the patching is unique per phone then it makes sense that we patch it ourselves. But we need upstreamed updated kernels!!! so don't stop doing those!!
Click to expand...
Click to collapse
Yeah of course, no sooner had I uploaded 118 than 119 was pushed. I'm not sure if I'll be able to get one out for each release before the next one comes out, but I'm going to be keeping these updated a frequently as I can. Anyway, I was only speculating about device-specific images, but I'm going to try and flash an image that was patched by my buddy and see if I can reproduce any issues. Regardless, I'll likely stick to uploading unpatched images in the future.
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
If you have come across this thread you probably want a ROM that provides better security than what AOSP provides
You have 3 ROMs actually:
1) Official grapheneos (can run with locked bootloader)
2) Unofficial grapheneos (I haven't released the keys to lock the bootloader on purpose as these are highly experimental builds that test features before they land in grapheneos)
3) glassrom (these are private builds I use for myself. Not possible to lock bootloader as I build them for myself. There will be no support provided for glassrom but the stability should be pretty good and there won't be any serious bugs)
1) Installing official grapheneos
Ask for support in grapheneos IRC/official matrix. Check grapheneos.org
Important! Lately there has been a lot of spam and off topic on grapheneos IRC. Please be on topic and keep the discussion about grapheneos. Please read the grapheneos FAQ before asking questions. Starting discussions unrelated to grapheneos or spreading misinformation will definitely get you banned. Please do not do so as this wastes time of the developers.
Bugs must be reported on the os_issue_tracker on the github. Include the steps to reproduce, a log and a dmesg. Include the exact build of grapheneos as well. Reporting bugs with a modified version of grapheneos (that is, flash grapheneos and only grapheneos, nothing else) will get your report closed. See if your issue has already been opened by someone else. Do not ask for apps to be included by default on grapheneos. Read the FAQ before requesting features
If you are unsure, ask in the glassrom support group at https://t.me/glassrom and we'll redirect you to the appropriate place. That will save both your and our time. Remember to only ask about the pixel 4, for other devices you must head to the grapheneos IRC and follow the rules carefully
Follow the official installation instructions https://grapheneos.org/install
Lock your bootloader
You're done
All sources, including kernel sources are here. The build script has the exact defconfig used
https://github.com/GrapheneOS
2) unofficial grapheneos:
Ask for support in glassrom chat. https://t.me/glassrom
Kernel sources follow the same format as grapheneos and are here: https://github.com/GlassROM-devices/kernel_google_coral
Please join the telegram report or provide active feedback if you're on these builds
Go to https://github.com/GlassROM/glassrom-landing/releases
Prerelease builds are grapheneos
Download both files and verify them against glassrom-verification
Be on the latest bootloader and run:
Code:
fastboot update fastboot-image-bootable-only.zip
If you're not on the latest bootloader the bootloader is actually bundled in the update. Extract the bootable only zip and flash the boot.img to boot partition.
Use the volume buttons to select reboot recovery regardless of how you flashed it and then boot to recovery
Format data
Sideload the zip with adb sideload
Reboot
3) Glassrom
Ask for support o- you don't ask for support
Glassrom is a lineage build that provides the grapheneos patchset
Sources and flash instructions are the same as unofficial grapheneos
Use it if you miss lineage on your pixel 4 for some reason
Go to https://github.com/GlassROM/glassrom-landing/releases
All releases for pixel 4 are glassrom
Glassrom has a couple additional features:
Targeted optimization for pixel 4 CPU
An exfat driver
Forced 90 hz display
Everything you'd expect from lineageos
Fdsan is enforcing
Happy flashing
I'm assuming glassrom has no gapps? Or does it?
dpryor88 said:
I'm assuming glassrom has no gapps? Or does it?
Click to expand...
Click to collapse
There is no support for them at the time of writing. Even if I bundle them right now you'll have to go through hoops to get it working like registering your device ID with google and so on
You are right about being carefull locking the bootloader, I forgot to unlock the bootloader of a device before formatting and now it's resting in peace. Oem unlock not possible due to no recovery and no OS, only fastboot.
trancinguy said:
You are right about being carefull locking the bootloader, I forgot to unlock the bootloader of a device before formatting and now it's resting in peace. Oem unlock not possible due to no recovery and no OS, only fastboot.
Click to expand...
Click to collapse
official grapheneos goes through a lot of testing so locking the bootloader is safe. the others? at least not yet
theres 1 more calyx os
Have you guys been able to run banking apps on any of the OS's??
markmywordz said:
theres 1 more calyx os
Click to expand...
Click to collapse
I'm running DU, no problems at all. ?
BrainStormCEO said:
I'm running DU, no problems at all. ?
Click to expand...
Click to collapse
have u lock ur bootloader after flashing du
markmywordz said:
have u lock ur bootloader after flashing du
Click to expand...
Click to collapse
No, I don't want to ever do that.
Guys this is a reminder. While OT is allowed this is a thread about grapheneos and glassrom. Please do not bring discussions about other ROMs into this thread
Next time I won't be this polite
Hi, i`m considering buying pixel 4 to move to graphenOS(currently s10e with LOS), but i can't find anywhere info what screen unlock functions does it support from the box. As it doesn't have fingerprint sensor, is face unlock realised anyhow, or the only possibility is password? Thanks!
face unlock is not secure, a picture of or someone that looks like you can unlock.
I was asking about other thing. If there is no finherprint sensor how is realised unlocking: pattern, password, face unlock or maybe there some other workarounds, i need to know becouse i use keepass with fingerprint autenitication(original password is 64 symbols long.
I know that original face unlock is google proprietary, but i have seen allready some open source code for it, so maybe there is secure solutiin allready.
With right face unlock you cannot unlock it with picture, maybe on very old phone with first attempts, pixel 4 as i know has 1 or 2 IR Scanners+front camera, to it can surely get the depth and layers, so with pucture it shoud be impossible to unlock, maybe with 3d head print in theory, but definitly not with picture, and scanners shoud be able to read eye fingerprint, like apple devices do
how's about battery life?
Does this ROM support VoLte and WiFi Calling?