Related
What is it?
This is a FlashCast mod to give your Chromecast a nearly stock OS. Although Team Eureka (obviously) believes that the features we've added to Eureka-ROM make it superior to the stock OS, we realize that it's not for everyone. Perhaps you want a clean base to develop from, or maybe you want want to try out a new feature from Google before Eureka-ROM is updated. Either way, the last thing we want to do is force you to use a ROM you don't want. To that end, this ROM is completely stock, save for two modifications:
update_engine is removed so that your vulnerable bootloader is preserved.
FlashCast is installed to the recovery partition instead of the stock recovery, to mitigate any bootloader updates Google may try to push through other methods.
Please note that this ROM contains no SSH, ADB, Telnet, or other means of remote shell access. In addition, it has no OTA system, so it is your responsibility to update to newer versions using FlashCast. We recommend that you use Eureka-ROM instead unless you have a specific reason for wanting a stock experience.
Where do I get it?
Build 44433 (latest version):
http://pdl.team-eureka.com/minimal/44433.zip
SHA256: 3cdebca7789d3024b036fdd2e82a06bbf6015d8fa2bf8f0a4f85fe819419cc73
MD5: c536136b76839fca00cf49dd220bb6a0
Build 27946:
http://pdl.team-eureka.com/minimal/27946.zip
SHA256: 56d35b1c06ed116aa3ee93f10fcf08b92b6a92c280a53d20c98a2d949d29b9f9
MD5: c74e4d3791847152ebde11e2090970eb
Build 26653:
http://pdl.team-eureka.com/minimal/26653.zip
SHA256: b1c62828e76b35da918aad438bc598c52c407e657431bc397664616e83d24fc9
MD5: 6db4d1c8fe7ab20268f4e99f3c70667f
Build 22062:
http://pdl.team-eureka.com/minimal/22062.zip
SHA256: cf6c2b4b1b2603abed51efc2cb39d7a6f882669946e8d879b5d1e4fd13156db9
MD5: cfaa7e4ca5f9686eb96dcb36e531c3f2
Build 19084:
http://pdl.team-eureka.com/minimal/19084.zip
SHA256: 74fa139c87c7affc5dab5f27cd1623845a89606d80fbfa7d5505bc137ece25a6
MD5: 271e628598dff919199e684921d158ff
Build 17977:
http://pdl.team-eureka.com/minimal/17977.zip
SHA256: fd5fd2daa40b5915f729e96e467c904a79f541196bb512679a61b3376cc49672
MD5: 54f4513432447156cd46fc868dffc487
Build 17250:
http://pdl.team-eureka.com/minimal/17250.zip
SHA256: 26d127c75d57d7aa4b8900cb27f3a3bba5f2690840f3e1dfa7c581bfb7c0aeec
MD5: c9adbd48d6e58113ec30ed8cd136bf16
Build 16664:
http://pdl.team-eureka.com/minimal/16664.zip
SHA256: 9a657d0b7945cf69c8127deb5a98f198a74cd959c09aae250f81ec3ad4a0f7e4
MD5: d961b63a2112294cfa6eefcf3eee205d
Build 16041:
http://pdl.team-eureka.com/minimal/16041.zip
SHA256: 212dfde7cd34a09a8699b9eb2064da34bac3f973cbce5bb7952ecdcdd1608c09
MD5: eac8b93a2da723fb29eb7ea7be4744cf
Build 15250:
http://pdl.team-eureka.com/minimal/15250.zip
SHA256: 54af712df8edf165de63d6f690642d234d12e8cd01889f877bf9fe93ef8a807a
MD5: e8a51bdbcd4e96da3a13b539ca314da4
Just to clarify. It has Google Whitelist right?
mathorv said:
Just to clarify. It has Google Whitelist right?
Click to expand...
Click to collapse
Yeah, all stock Google, no custom whitelist in this one.
If we are currently still running the Eureka ROM based on 14975 and using the custom whitelist feature that you guys integrated into the 14975 Eureka ROM image, would it CURRENTLY be possible for us to take advantage of all these new apps that are going to be flooding the Google Play Store/Chrome(PC browser apps/extensions) Web Store, or MUST our Chromecast be the newest updated version 15250(with either a future Eureka ROM update to 15250, by flashing this "nearly stock OS build" 15250, or simply someone just has a stock, NON-rooted Chromecast that has taken all the OTA updates and has recently updated itself via an OTA to the newest stock 15250 firmware build) ? I understand that by using Eureka ROM's "custom whitelist" that you guys manually update the whitelist yourselves and it's obviously not physically possible to update your whitelist fast enough to keep up with the "stock Google whitelist," thus always lagging slightly behind the stock Google whitelist AND quite possibly accidentally leaving out some of the lesser-known Android apps and/or Chrome Apps and/or Chrome Extensions that have been added by Google to their stock whitelist, due to the simple fact that you guys just haven't learned of them yet or just haven't been told of them yet?
Basically, if one wants to be able to take advantage of all these new apps that will be flooding Google's stock Chromecast whitelist over the coming weeks/months, etc., to cover all our bases right now so that we're not either hoping that you guys find out about lesser-known apps such as, for a hypothetical example: XCompany's "FancySchmancy Chromecast Media Caster", should we use this upload that you posted so that we're on the newest 15250 and use the stock Google whitelist? Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Could this installed on ANY ChromeCast or just ROOTABLE Chromecasts?
does this require a chromecast that has been already rooted?
or can i use this on my unrooted chromecast without the vulnerable bootloader?
In order to install this Vanilla Chromecast 15250 with blocked OTA.
Chromecast has to be ROOTable and has to be flashed with [FLASHER][v1.1.1 - 2013-11-29] FlashCast
It works 100% THE SAME AS non rooted 15250 Chromium, nothing special about it. It's taste of 15250 for develpers and people bored with feature rich 14975.002 eureka mod.
BTW: Great idea for future development cycle - quick minimal releases before major releases.
EDIT:
Works as should and for sure Whitelist is by Google so Fling is not available, AllCast is working like a charm.
jsdecker10 said:
Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Click to expand...
Click to collapse
No. It's not a whitelist issue as the Team-Eureka whitelist includes what's on the Google whitelist.
Apps built on the released SDK require:
On Chromecast: The "magic stuff" that is in the 15250 build (or newer)
On casting device (for Android): The "other magic stuff" that is in Google Play Services 4.2.34 (or newer)
Being present on Google whitelist (or Team Eureka whitelist)
Eureka-ROM v1.1 is built on 14975, so it fails condition 1 for new apps.
Stock Chromecasts should have auto-updated to 15250 already.
Installing this stock, root-preserving, non-updating, no features added ROM will give you:
All Google official apps, including the new releases built on the released SDK
That's it.
No unapproved/beta apps (at the time of this post this includes fling, vbukit, and Audiour)
No ADB, SSH or Telnet
None of the other Eureka-ROM features (static IP, alternate DNS, web panel, etc)
jsdecker10 said:
If we are currently still running the Eureka ROM based on 14975 and using the custom whitelist feature that you guys integrated into the 14975 Eureka ROM image, would it CURRENTLY be possible for us to take advantage of all these new apps that are going to be flooding the Google Play Store/Chrome(PC browser apps/extensions) Web Store, or MUST our Chromecast be the newest updated version 15250(with either a future Eureka ROM update to 15250, by flashing this "nearly stock OS build" 15250, or simply someone just has a stock, NON-rooted Chromecast that has taken all the OTA updates and has recently updated itself via an OTA to the newest stock 15250 firmware build) ? I understand that by using Eureka ROM's "custom whitelist" that you guys manually update the whitelist yourselves and it's obviously not physically possible to update your whitelist fast enough to keep up with the "stock Google whitelist," thus always lagging slightly behind the stock Google whitelist AND quite possibly accidentally leaving out some of the lesser-known Android apps and/or Chrome Apps and/or Chrome Extensions that have been added by Google to their stock whitelist, due to the simple fact that you guys just haven't learned of them yet or just haven't been told of them yet?
Basically, if one wants to be able to take advantage of all these new apps that will be flooding Google's stock Chromecast whitelist over the coming weeks/months, etc., to cover all our bases right now so that we're not either hoping that you guys find out about lesser-known apps such as, for a hypothetical example: XCompany's "FancySchmancy Chromecast Media Caster", should we use this upload that you posted so that we're on the newest 15250 and use the stock Google whitelist? Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ?
Click to expand...
Click to collapse
1. Any new apps that use the new API will not be available in the current Eureka-ROM that is based on 14975. This is because the new API is not enabled in its Eureka_shell binary, which is the program on the device that literally runs almost every application.
2. Our custom whitelist is no longer a manual entry process, and auto updates when google pushes new applications. This means rooted devices now get apps just as fast as stock devices, as long as they are on a ROM version that supports said application.
3. Disabling the custom whitelist on the 14975 based rom will not allow you to use the V2 API apps, as I stated in #1
We are working on a new version of Eureka-ROM, but are just having a few small things hold us back. This is why the release is taking longer then normal, and as such, we released this minimal image for those who would like to update for the time being.
Just posted build 16041 for you crack flashers out there, enjoy!
Can you post the Google ota link also for these?
Sent from my XT1060 using XDA Premium 4 mobile app
jay0lee said:
Can you post the Google ota link also for these?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We do not post those publicly because we don't want users accidentally flashing the update and loosing the ability to root. Please shoot me a PM if you would like the direct link from google for the OTA.
ddggttff3 said:
We do not post those publicly because we don't want users accidentally flashing the update and PERMANENTLY losing the ability to root. Please shoot me a PM if you would like the direct link from google for the OTA.
Click to expand...
Click to collapse
(Emphasis and typo fix added ). Remember, FlashCast relies on an exploit that any unmodified Google OTA will patch, so applying a stock Google OTA won't just result in a tempory loss of root, it's a permanent and irreversible loss of root.
A new exploit would need to be found in order to get root back, and at least so far there doesn't seem to be one in sight.
So that's why Team Eureka is being overly cautious.
Just wondering if this was sent out to Chromecasts? I just checked my version number and am on the latest. Unless something else happened (I've had frequent unable to boot messages a couple weeks ago and rebooting fixed them).. my Eureka ROM may have been wiped.
ralphwiggum1 said:
Just wondering if this was sent out to Chromecasts? I just checked my version number and am on the latest. Unless something else happened (I've had frequent unable to boot messages a couple weeks ago and rebooting fixed them).. my Eureka ROM may have been wiped.
Click to expand...
Click to collapse
No, this is strictly a download and manually flash thing.
What makes you think your Eureka ROM has been wiped? Can you no longer get to the web panel at http://ip_of_chromecast ?
bhiga said:
No, this is strictly a download and manually flash thing.
What makes you think your Eureka ROM has been wiped? Can you no longer get to the web panel at http://[i]ip_of_chromecast[/i] ?
Click to expand...
Click to collapse
No web interface, and Chromecast app shows the latest.
The one I flashed manually was the one with the older FlashCast (which would be the first Eureka ROM). At some point I may have come back to stock without my knowledge.
ralphwiggum1 said:
No web interface, and Chromecast app shows the latest.
The one I flashed manually was the one with the older FlashCast (which would be the first Eureka ROM). At some point I may have come back to stock without my knowledge.
Click to expand...
Click to collapse
Spontaneously returning to stock is highly unlikely - the update parts are removed/disabled in Eureka-ROM and rooted stock ROM. And true stock ROMs aren't posted to avoid accidents.
There was a previous potential issue where interrupting an update could leave you in a partial state that seemed like a stock ROM, though. (Can't find the post...)
The $1M question is - does FlashCast still boot? If so, you are fine and can simply re-flash Eureka-ROM or rooted stock.
bhiga said:
Spontaneously returning to stock is highly unlikely - the update parts are removed/disabled in Eureka-ROM and rooted stock ROM. And true stock ROMs aren't posted to avoid accidents.
There was a previous potential issue where interrupting an update could leave you in a partial state that seemed like a stock ROM, though. (Can't find the post...)
The $1M question is - does FlashCast still boot? If so, you are fine and can simply re-flash Eureka-ROM or rooted stock.
Click to expand...
Click to collapse
I just posted a question here: http://forum.xda-developers.com/showpost.php?p=51084756&postcount=575 which is exactly the same. I was on EurekaROM before and am now on 16041 stock firmware without my consent. I'm going to try flashing to see if I'm still rooted.
Can you still flash a different DNS with this ROM?
Rooksx said:
Can you still flash a different DNS with this ROM?
Click to expand...
Click to collapse
Yes you can flash the DNS modification packages that were released awhile ago.
Just posted OTA 16664, enjoy!
Hi everyone,
I got my mako in apr 2013. Apparently, on cm12/13 it seems to be affeected by this bug. So, to clear any doubt about it, I wondered if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram-foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keeps supporting kitkat).
Zio Guiduccio
NB: If you can't open Messages, flash first june rom, then august one.
26/08/2016
I made available a second build (FOSS) with some little differences. Here they are:
- Replaced Browser with getChromium app, because zero-day exploits in kitkat webviews (use only updated chromium!);
- Replaced Email with K9-mail, because kitkat webview and zero-day exploits;
- Removed Exchange2 because zero-day exploits (don't know alternatives othen than normal gmail);
- Added F-Droid;
- Added Offline Calendar, otherwise standard calendar is useless;
- Added Adaway;
- Added Document Viewer (many formats reader);
- Added Kolab Notes;
- Added Yaab (Minimum brightness on-demand).
Download
CM-11-20160820-GUIDUCCIO-FOSS-mako.zip
CM-11-20160820-GUIDUCCIO-mako.zip
CM-11-20160611-GUIDUCCIO-mako.zip
Just as you mentioned battery drain has lowered.
Thanks for ROM!
zio guiduccio said:
Hi everyone,
I got my phone in apr 2013. Apparently, on cm12/13 it seems to be affected by this bug. So, to clear any doubt, I wonder if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
The only change I had to do was to replace these files
/system/framework/webview
/system/framework/webviewchromium.jar
/system/lib/libchromium_net.so
/system/lib/libwebviewchromium.so
/system/lib/libwebviewchromium_plat_support.so
with ones from cm-m12-official because logcat tells me that the webview i compiled goes segfault when I try to open messages in mms.apk, k9 mail and settings in rar and amaze. In general, the code is untouched.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keep supporting kitkat, which I hope is long).
Obviously, the ROM is updated to the latest android security bulletin of 1st june 2016.
Zio Guiduccio
Download
MD5SUM: 4B129774050768E8D21114D7816A8D56
CM-11-20160611-GUIDUCCIO-mako.zip
Click to expand...
Click to collapse
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)
Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?
thegodsmustbecrazy said:
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)
Click to expand...
Click to collapse
Sorry. The day cyanogenmod mantainer approved the patches (31th july) I went away from home (and the building machine.) I will come back next week at minimum. I'll publish next build for 15th August at maximum.
EDIT: Still no july patches merged to cm11 branch.
espionage724 said:
Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?
Click to expand...
Click to collapse
Can't see why non.
The rom has been updated to August 2016 ASB.
zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
Thank you!
I'm running this with my n4 underclocked at 700mhz (might bump it up to 1ghz, but I haven't really noticed any crazy lag to speak of) and the battery life must be at least double! Freaking awesome if you ask me :good:
zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
In your OP, you mention running this ROM "without gapps." Is the ROM designed to be run only in a state that is without any gapps package, or is it OK to use a gapps package if we want? I would use Open GApps for KK 4.4.
Of course you flash KK gapps.
Hello Everyone,
The AOSP pushed a patch that effectively breaks xposed. The CM team doesn't support xposed (in fact they don't even take bug reports from users who have it installed). That being said, they don't actively work against it either.
There is a comment found here, though it is for the d2, it applies to the other devices as well
http://forum.xda-developers.com/showpost.php?p=69631802&postcount=1162
The patch that AOSP pushed is going to require the xposed dev(s) to do something to work around it (or users can compile their own builds with a workaround).The CM team won't be reverting this new AOSP security measure, for obvious reasons
With that being said, the official XPosed Dev, Rovo89, is currently working on an XPosed modification/solution to this. You can see the work Rovo89 is performing here:
https://github.com/rovo89/XposedBridge/issues/129#issuecomment-260498284
When they figure out a solution, you will find it posted here:
http://forum.xda-developers.com/showthread.php?t=3034811
In the meantime, and unfortunately, if you want to keep using XPosed, you will have to keep using the last CM release that XPosed was working on (the pre-security updated release). And when XPosed has been modified to work on the pre-security releases of CM, then you will be able to update your CM ROM and all will be at peace (hopefully LOL!).
Good Luck...
Peace and Love!
Peace and Love!
~Ibuprophen
Thank you very much for the announcement, I'm really grateful!
It was difficult and difficult to always answer the uninformed about this subject, are causing a certain irritation to developers those users who repeat the same questions (as in the case of VoLTE)
Thank you for keeping us informed!
Some progress from CM team?
https://review.cyanogenmod.org/#/c/170575
Shivver said:
Some progress from CM team?
https://review.cyanogenmod.org/#/c/170575
Click to expand...
Click to collapse
CM's patch is aimed to fix issues on some devices having proprietary blobs that have file descriptor leaks which result in errors during boot.
(e.g. shield tablet in particular)
While this patch allows to white list xposed specific stuff at device configuration level, it was not aimed to serve this purpose at all.
This might help you http://forum.xda-developers.com/showpost.php?p=69699345&postcount=4504
here is the official fix => http://forum.xda-developers.com/showpost.php?p=69702111&postcount=4526
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.