Database Develop

Unofficial build of CyanogenMod 11.0 for Galaxy Note GT-N7000

This is an unofficial build for all those who want to stay with CM11. The build is based on the pure CM code and does include the stagefright patches and other patches up to July 30.
It does run perfectly on my wife's N7000. However, use at your own risk.
https://www.mediafire.com/folder/wqacsxdn42n15d2,z707vvgb63q4b74/shared

New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.

NeuDLi said:
New version available:
https://www.mediafire.com/folder/ygkv6tryc7v7bgs,6ay7smbzruwxxrr/shared
Since - again - a severe security issue has been patched since the last time, I encourage everyone to upgrade.
Click to expand...
Click to collapse
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!

Jack4L_ said:
Please tell us what is the changes applied to the official version of Cyanogemod. You only says to test it, with no description? No , thanks!
Click to expand...
Click to collapse
Well it's up to you if you use my ROM or not (basically you always have to trust anyone providing a ROM, because you cannot confirm the actually used codebase anyway!). In the meantime there is another official version out, so you can readily stick to that. I did not wish to wait with a severe security issue until someone built another official version. Last time it was 2 weeks between builds... which is far too long with such severe issues as recently.
Apart from that, your accusation is incorrect! Did you read the initial post? Apparently not, because it clearly stated that "The build is based on the pure CM code". This is still the case and will be if not stated otherwise. So there are NO CHANGES APPLIED TO THE OFFICIAL CM CODE, period! I just build it when an important patch is out but no official build.

no thanks

New version available. This includes the - not yet merged - patches http://review.cyanogenmod.org/112044 and http://review.cyanogenmod.org/112043. According to stagefright detector app this has removed the vulnerability CVE-2015-6602 (also termed stagefright V2). Here you go:
https://www.mediafire.com/folder/0t8784a5at6h9z4,opbklzsle9igxfv/shared

Official version of November 22 available. As a number of bugs have been remedied, everyone should upgrade.
Only thing is that Xposed does not work due to some patches. I will try to compile a new version including a fix for that next week.

New version available. All patches up to and including the one of November 23, and also including a fix for Xposed (taken from here: https://gerrit.omnirom.org/#/c/15695/).
https://www.mediafire.com/folder/xy7zd919cv04ohf,b081a5orcm8et49/shared

Hi NeuDLi,
after many test with cm12 i am now back to cm11 because i think cm12 use to much rom and our old n7000 will work very slow.
I have had many break down and automatik restarts. cm12 has no advantages for me.
the official cm 11 builds -i agree with you- will not quick updated.
now i give your rom a chance to work for me and my n7000. Thanks.

New version available. Includes official patches including December 8. Unless stated otherwise all further version will include the Xposed patch as of the previous post.
https://www.mediafire.com/folder/h2bo3o5b7uqn4gw,40qmwwyfu2cb477/shared

OxygenOS Open Beta 32 for the OnePlus 3 and 23 for the OnePlus 3T

Hey everyone,
We’re back with the newest Open Beta builds for the OnePlus 3 and 3T
Changelog:
Gallery V2.5
New design for Collections tab
Added reorder function for Collections
Added recently deleted Collection
OnePlus Switch
Added support to migrate application data, allowing you to switch between devices seamlessly
System
Updated Android security patch to 2018-02
General bug fixes and improvements
Please keep in mind that this is beta software. These builds are sometimes not as stable as our official OTAs generally are. By installing this update, you accept the potential risks.
And please remember to tell us about any bugs you may find using the bug report forums, found here. https://forums.oneplus.net/feedback/
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta) you will receive this new build as an OTA.
If you ARE NOT running open beta software and would like to, please refer to the flashing instructions and the full ROM found on the downloads page here: http://downloads.oneplus.net/
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will NO LONGER receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (FULL WIPE of all data and cache)
Make sure to let us know how you feel about the beta builds here in the thread too, we are watching.
Note: If you want to join us in OxygenOS Open Ears Forum and talk with us f2f in San Francisco on April 7, welcome to fill in your application by Mar 14.

No 8.1?

Yes, this release will not bring a 8.1 to our devices... It's very strange and disappointed, but we can't do anything with this.

i think i wait till LinageOS is more stable and flash this instead. OxygenOS has an end on our 3 Devices...

I'm looking to Nitrogen OS, but the "google multitouch lag" is very annoying, so I will wait for time when google fix it, and then switch to Nitrogen.
I think 1+ will not update 3/3t as previously and finally switch open beta program to 5/5t.

i think we only get a few security patches and "general bugfixes" in the future. the timeline for the OP3's is over. that's my opinion.
i switch to LinageOS or Paranoid Android (i hope we hear some more news about Oreo soon)

Please search before posting and do not duplicate threads in the forum. You may continue in this thread for OOS Beta builds:
OxygenOS Open Beta 32 for the OnePlus 3
THREAD CLOSED
Sent from a government terminal using my sonic screwdriver
Playa82 said:
Hey everyone,
We’re back with the newest Open Beta builds for the OnePlus 3 and 3T
Changelog:
Gallery V2.5
New design for Collections tab
Added reorder function for Collections
Added recently deleted Collection
OnePlus Switch
Added support to migrate application data, allowing you to switch between devices seamlessly
System
Updated Android security patch to 2018-02
General bug fixes and improvements
Please keep in mind that this is beta software. These builds are sometimes not as stable as our official OTAs generally are. By installing this update, you accept the potential risks.
And please remember to tell us about any bugs you may find using the bug report forums, found here. https://forums.oneplus.net/feedback/
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta) you will receive this new build as an OTA.
If you ARE NOT running open beta software and would like to, please refer to the flashing instructions and the full ROM found on the downloads page here: http://downloads.oneplus.net/
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will NO LONGER receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (FULL WIPE of all data and cache)
Make sure to let us know how you feel about the beta builds here in the thread too, we are watching.
Note: If you want to join us in OxygenOS Open Ears Forum and talk with us f2f in San Francisco on April 7, welcome to fill in your application by Mar 14.
Click to expand...
Click to collapse

[DISCONTINUED ROM][8.1][OMS][SigSpoofing] Unofficial LineageOS builds by Admicos

(I'm new to all this ROM development stuff, apologies if there's anything wrong with what I'm doing)
These are my personal LineageOS builds. They aren't much different from regular LOS, other than some added patches.
More details and sources over at: https://git.issizler.club/LineageOS/LineageOS-by-Admicos
Download: https://www.androidfilehost.com/?fid=11410963190603912814
What's working/not working: Should be same as official LineageOS
XDA:DevDB Information
Unofficial LineageOS builds by Admicos, ROM for the ZTE Axon 7
Contributors
admicos
Source Code: https://git.issizler.club/LineageOS
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Beta
Created 2019-01-04
Last Updated 2019-01-04

CHANGELOG
15.1-20190201 1d456849f4b154381071c9ebae87ccff
15.1-20190121 45f811aecd226524c3c68394f0781e10
15.1-20190115 e9c47b0062b822c118f918318289a7e4
LOS Repo Sync
15.1-20190104-2 37ff7fb6510d0d819e10e932d3e18f9d
Fixed WireGuard
15.1-20190104
Initial Release

Nice. The addition of sigspoofing and substratum service would make plain LOS usable for me. Straight LOS and themes were always iffy.
[emoji106]
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy

As nobody really posted here, I just wanted to say that this is working really well.
I had huge gps problems with the last 15.1 unofficial, but it works perfectly in this one and it has some very nice additions as well and is 100% stable for me even with xposed and magisk.
 @admicos Thank you very much and I really hope that, if you have the time, you continue making these.

New build being uploaded right now, no changes other than a LOS repo sync.
The last couple test builds I made were somewhat iffy, but this one seems pretty well. (The recolored boot animation didn't make it in for some reason, but the rest are fine)

Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7

Predatorhaze said:
Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7
Click to expand...
Click to collapse
boy ter here rediscovering the wonders of encryption and dm-verity check

New build being uploaded, another regular LOS repo sync, should be done in about an hour
--
Predatorhaze said:
Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7
Click to expand...
Click to collapse
I'm not sure why that's happening either. Can you replicate this on official LOS? If you can, I'd suggest you try asking on their thread, they might know more.

Good ROM for a while, why not update it? Is there a new kernel upgrade for the top post?

[armitage] said:
As nobody really posted here, I just wanted to say that this is working really well.
I had huge gps problems with the last 15.1 unofficial, but it works perfectly in this one and it has some very nice additions as well and is 100% stable for me even with xposed and magisk.
@admicos Thank you very much and I really hope that, if you have the time, you continue making these.
Click to expand...
Click to collapse
What version of Xposed are you using? I've always wanted to try this ROM, but thought there wasn't an official Xposed yet. The others I knew at the time were reportedly shady.

Sorry for the long wait (kinda forgot about this existing :/), and sorry for the bad news;
As I am planning to switch to another phone, I cannot continue making this anymore.
I might continue this as a GSI or something, but I really don't know if that will happen, as Android source is a big mess that I don't think I, and my (reasonably fast) CPU are prepared to handle. (Any pointers to dealing with this are greatly appreciated)
It was a fun two years lurking around.
(ps: The source link is completely borked (and all my sources are gone). I probably should stop trying to be fancy and use a public Git server like a normal person the next time)

If your build env is on Docker, I can easily stage a build server for you. It won't be fast, but you can leave it running all night long if you need, and free up your computer.
Also, if you're not using Docker, I can help you set it up, so anyone else can easily build by themselves if they choose to do so.

Can I upgrade the kernel?
[9.0/8.1] Updated LOS Kernel [Version 3.18.136]

@admicos THREAD CLOSED!
In the OP, the mandatory link tp source code provides a HTTP 404 error.
Please advise the moderators' team if you want the thread to be re-opened and to update the link.

[UNOFFICIAL] LineageOS 15.1 for ZTE Axon 7 [Baddar-Kernel] [Final Build:03.08.20]

This is nothing big and I'm not a Developer.
This Thread is just for Unoffical LineageOS Builds that I do from time to time.
The Builds are done with Udev's Device Tree and Vendor Files and Offical LineageOS Sources.
I might make some changes at some point, but don't hold your breath.
So far all this is, is Udev's fixes and updated Lineage Sources (fixes) and monthly Security Patches.
I post updates whenever something interesting happens (which is now hardly ever with Lineage 15.1), or when there's a new security patch.
The only reason I'm making a new Thread for this, is because I don't want to post these updates in Ordenkrieger's/Udev's Official Thread.
Oh and the Disclaimer from the Original Thread.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Any failure in this process could lead to an unrecoverable bricked device.
Click to expand...
Click to collapse
With that out of the way, here is the Link to my latest Build:
https://mega.nz/file/eIEWFSAS#cmU62oG5IARruOPcYwAaSqnZKGvB3qdemJwnZt9SM_I
Thanks to:
OrdenKrieger, Unjustified Dev, king1990, DrakenFX, tdm and tprfd
ROM OS Version: 8.x Oreo
Based On: LineageOS ( Source ) ( Vendor )
Kernel version: 3.18.140-Baddar-RC1.2 ( Source )
Version Information
Status: Stable
Created: 12-04-2019
Last Updated: 03-08-2020

Changelog:
03.08.20
https://www.lineageoslog.com/15.1
20.04.19
Initial Release

Just in case...

Running great so far! Gcam FCing for me, but maybe it's just bad opengapps nightly. No battery stuck bug after changing battery.

Updated Version with latest LineageOS Fixes and latest Android Security Update, linked in the first Post.
The Build was made without Udev's latest Commits ( click ) as I don't know if he wants them in a public ROM yet ( and it says WIP anyway).

thanks!! you awesome. the previous April20 build has been great. -GA
[armitage] said:
Updated Version with latest LineageOS Fixes and latest Android Security Update, linked in the first Post.
The Build was made without Udev's latest Commits ( click ) as I don't know if he wants them in a public ROM yet ( and it says WIP anyway).
Click to expand...
Click to collapse

i am using this rom right now with baddar rc 1.1 kernel.Anyone got dolby atmos working?

I don't think that there is a way to get it working on newer non-stock Roms. I've given up on that quite a while ago.

i tried some zips,none works...i also give it up lol.The vendor really need updates also i think.Play store not certified even with fp props module.More heat on the phone,cpu load very high

Must be something on your side. No problems here whatsoever.
Play store works fine, no heat, low discharge rate, no high cpu usage.
I mean my battery is pretty much "trash", after two years of not treating it too kindly and I still get almost 5h SOT, which is not too bad I guess.
Oh and there's not really much I can do about the vendor and haven't tried that kernel yet. Using stock lineage kernel here.

i used it for some hours now,and i think i agree with you.Idle is really great,power consumption alsnly thing playstore not certified.
Thank you for these builds!!

Just uploaded the probably last update based on Lineage 15.1, as the the Axon 7 has been removed and (as you can read here) is no longer maintained.
Maybe it'll be back with Lineage 16 one day.

[armitage said:
;79596505]Just uploaded the probably last update based on Lineage 15.1, as the the Axon 7 has been removed and (as you can read here) is no longer maintained.
Maybe it'll be back with Lineage 16 one day.
Click to expand...
Click to collapse
It hasn't been maintained in months and months. I am pretty sure this only means that lineage will no longer provide an 'official' build. You can still build yours the way you're doing it.

So what you're saying is that there will still be some fixes and security patches added but I won't see a device specific changelog for the axon7 and there won't be any automated builds?
So I'd just have to check another device's changes to see when a for example a security patch was added and this will still be included when I check out and build for the axon?

[armitage] said:
So what you're saying is that there will still be some fixes and security patches added but I won't see a device specific changelog for the axon7 and there won't be any automated builds?
So I'd just have to check another device's changes to see when a for example a security patch was added and this will still be included when I check out and build for the axon?
Click to expand...
Click to collapse
No more automated builds for official. There hasn't been device specific changes for many months. The changelog you see on lineageoslog for axon7 includes the non-device specific changes and has the other device specific changes filtered out.
You can look here for the full changelog for 15.1 here:
https://www.lineageoslog.com/15.1
I can see the security bump was merged on the 17th.
It should be business as usual for your builds that you're providing here... I hope.

thanks for the ongoing efforts to update the builds!! much appreciated. do you have option to buy you a beer?? -GA
tprfd said:
No more automated builds for official. There hasn't been device specific changes for many months. The changelog you see on lineageoslog for axon7 includes the non-device specific changes and has the other device specific changes filtered out.
You can look here for the full changelog for 15.1 here:
https://www.lineageoslog.com/15.1
I can see the security bump was merged on the 17th.
It should be business as usual for your builds that you're providing here... I hope.
Click to expand...
Click to collapse

gads1 said:
thanks for the ongoing efforts to update the builds!! much appreciated. do you have option to buy you a beer?? -GA
Click to expand...
Click to collapse
Not me you should ask!
armitage is the one hosting/building these... and of course all of the work put in initially from the devs.

whoops!! thanks for correction. I wasn't paying attention... lazy! beers for everyone....
tprfd said:
Not me you should ask!
armitage is the one ....
Click to expand...
Click to collapse

I wasn't really thinking of that at all, as I don't really consider what I'm doing that important, but as I'm in the process of moving and a money will be tight over the next couple of months, sure... a beer would be appreciated.
But just to make sure... this will never be a necessity. I will probably build these as long as people need them, even if I don't have the device anymore, as it is not that hard to do and doesn't take a lot of time, once everything is set up.
Anyway, I added my paypal url to my profile.

It's not clear in this thread but is this build treble or not? Thanks

Forking and Developing Magisk

Back in May when topjohnwu joined Google, he was told he's not allowed to maintain Magisk anymore:
https://imgur.com/ozGMFbU
. For some reason, this information wasn't broadcasted widely.
Because of this, the Magisk GitHub has gone dry: https://github.com/topjohnwu/Magisk/
Today, I can root my OnePlus 8 running LineageOS 18.1 (or Android 11 in general) with Magisk and pass SafetyNet. Maybe we'll have some root with Android 12. But come Android 13, or even 12 if something changes, what will we do if Magisk isn't maintained?
I propose we fork Magisk and continue developing it from there. This thread exists mainly as a discussion about a possible fork.
Sadly, I don't know much about Android development myself. I've only gone as far as making a flashable ZIP (if even that) for a Moto Z2 Force Sprint APN fix back in 2018. Well, maybe it's time for me to learn (Full disclaimer: I am a FreeBSD committer/developer, more packaging work but some kernel/driver stuff also, but then Android is based off Linux not BSD).
To mods: Sorry for making another thread. I wanted to edit the title of my previous thread, but couldn't.

MOD ACTION:
Thread closed since another earlier thread on the same subject already exists: https://forum.xda-developers.com/t/all-hands-on-deck.4303129/
Please search before posting.