Related
Android 8.0 Oreo - Now in Development
Lineage for Oppo F1 (f1f)
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform. It is the successor to the highly popular custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
Instructions
For Installing
1. Unlock root.
2. Download the latest TWRP, build, and GApps.
3. Install/unlock TWRP.
4. Reboot to TWRP recovery.
5. Wipe System, Data, Cache, and Dalvik.
6. Flash the build, and GApps respectively.
7. Flash patches if available.
8. Wipe cache and dalvik.
9. Reboot to system, and enjoy.
Note: If you have 'already installed' Lineage, and want to update your build, use the instructions below.
For Updating Build (Clean Flash)
1. Download the latest build and GApps.
2. Reboot to TWRP recovery.
3. Wipe System, Data, Cache, and Dalvik.
4. Flash the build, and GApps respectively.
5. Flash patches if available.
6. Wipe cache and dalvik.
7. Reboot to system, and enjoy.
For Updating Build (Dirty Flash)
1. Download the latest build.
2. Reboot to TWRP recovery.
3. Flash the build.
4. Flash patches if available.
5. Wipe cache and dalvik.
6. Reboot to system, and enjoy.
For Updating TWRP
1. Download the latest TWRP.
2. Reboot to TWRP recovery.
3. Flash the TWRP update.
4. Wipe cache and dalvik.
5. Reboot to system, and enjoy.
For Unlocking
1. Download magictricks.zip.
2. Go to stock recovery, then install/flash magictricks.zip
3. Reboot to fastboot, then connect phone to pc.
4. Setup adb shell in Windows.
5. Lunch CMD.
6. Install adb drivers for oppo f1f.
7. Type "cd c:\adb" then enter.
8. Type "adb devices" then enter.
9. You should see your device in the list, if not, go back to step six.
10. Put TWRP flashable zip to c:\adb (rename as twrp.img).
11. Type "fastboot oem unlock" then enter.
12. Type "fastboot flash recovery twrp.img" then press enter.
13. After, disconnect phone then reboot to TWRP.
14. Flash img/zips what you want.
Downloads
TWRP: download link
OpenGApps: download link
Unlocker: download link
ADB Installer: download link
ADB Extract: download link
For the builds, see below.
Version Information
Latest Stable Version
Build: 14.1-2017XXXX-UNOFFICIAL-f1f
Android Version: 7.1.1 Nougat
Latest Beta Version
Build: 15.0-2017XXXX-UNOFFICIAL-f1f
Android Version: Android 8.0 Oreo
OpenGApps Version
Platform: ARM64
Android: 7.1 (stable) or 8.0 (beta)
Variant: Stock (recommended)
Android 8.0 Oreo (In Development)
Downloads
Lineage 15 based on Android Oreo Source Code: Link
Notes for Android Oreo Development
Lineage 15 based on Android Oreo Source Code is the one we will need to port.
Android 7.1 Nougat (Old)
Downloads
Build: download link
Patch (Auto Rotation and Navigation Bar): download link
Patch (Kernel): download link
Add-ons
Temporary Camera: download link
Temporary Torch: download link
Known Bugs
The bugs listed here are bugs from the latest nougat build.
1. Camera crashes.
2. Torch toggle don't work.
3. Battery non-accuracy.
4. Hotspot Issue.
FAQ
Q1: What's the difference between updating build "Cleaand "Dirty Flash"?
Clean flash - removes all your files then install the update. Dirty flash - updates your build without removing your files.
Q2: When will you release the next stable build?
See "Version Information" in this thread.
Q3: Can I try the latest beta version?
Yes, if granted by developers of this thread. No, if not.
Q4: Did you already fix the bugs present in the latest stable build?
See "Known Bugs" in this thread.
Q5: What's better for updating build? Clean flash or Dirty flash?
I recommend dirty flash. Only use clean flash when you can't update build properly.
Q6: What's the difference between this thread and other threads.
This thread is for "DEVELOPMENT and FULL GUIDE for 'UNLOCKING, RECOVERIES, KERNELS, ROMS, and OPENGAPPS' for Oppo F1 (f1f)".
Credits, Sources
Developers and contributors:
@kdd998
Android 7.1 Build
@MiniBlu
Android 7.1 Kernel Patch
@khannz7
Android 7.1 Auto Rotation and Navigation Bar Patch
@Earthy
Instructions/Guides
Android 7.1 Add-ons
@ TWRP
TWRP
@ OpenGApps
OpenGApps
@ Lineage Github Repo
LineageOS 14.1
LineageOS 15.0
@ AOSP
Android Nougat Source Code
Android Oreo Source Code
and the community.
For those who want to help building builds for this rom, and for those have knowledge about building builds, just reply to this thread. We will cooperate and share knowledge with each other, so we can build a build faster, better, and more stable. Just teamwork.
Notes
Bug report:
For bug report, just reply to this thread.
Keep up-to-date here, this first thread post change info over from time to time. This thread is last updated: 00:00 PM, Mon-Sun, Jan-Dec 00 2017 (GMT+8).
Reserved 1 out of 9.
Reserved 2 out of 9.
Reserved 3 out of 9.
Reserved 4 out of 9.
Reserved 5 out of 9.
Reserved 6 out of 9.
Reserved 7 out of 9.
Reserved 8 out of 9.
Reserved 9 out of 9.
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Jamie_oppo said:
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Click to expand...
Click to collapse
Here's the Lineage 15 Source Code.
https://github.com/LineageOS/android_vendor_lineage
Earthy said:
Here's the Lineage 15 Source Code.
https://github.com/LineageOS/android_vendor_lineage
Click to expand...
Click to collapse
Yeah but you still need a los15.0 branch for the f1f device tree. Which isn't available and won't be for a long time
Jamie_oppo said:
https://github.com/LineageOS/android_device_oppo_f1f
You can't do anything until there's a cm15 branch anyway.
You can try and port to our device from another device if you want.
There's still actually no new links in this thread. Its all other peoples work. U say u have a beta but havent posted anything. Try and help the other dev fix the sound in the nougat kernel. Instead of just posting other peoples work here.
Click to expand...
Click to collapse
Jamie_oppo said:
Yeah but you still need a los15.0 branch for the f1f device tree. Which isn't available and won't be for a long time
Click to expand...
Click to collapse
We don't need to wait if we will build our own branch for the f1f device tree. And actually, we are the one should make it because we are the only who develops ROM for this. And also common sense to know that "the one who develop the ROMs should make everything needed here like kernel, branch that you're saying, etc.".
?
Earthy said:
We don't need to wait if we will build our own branch for the f1f device tree. And actually, we are the one should make it because we are the only who develops ROM for this. And also common sense to know that "the one who develop the ROMs should make everything needed here like kernel, branch that you're saying, etc.".
Click to expand...
Click to collapse
Well I have my doubt's. Prove me wrong. I would have no idea how to do this.
Also I think a group collaboration would be better. One person would just be too much work.
Good luck anyway
@MiniBlu, there's your credit. :angel:
@Earthy it is obvious none of this is your work. I personally don't see a camera fix as reason enough for you to repackage someone else's work and release it yourself. Under XDA rule:
12-3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse
Thread closed
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Quote:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
NOTE: This version of TWRP is intended to be used with the original unlock for karnak by xyz`.
If you unlocked or updated using amonet-3 it already contains an updated TWRP.
This version will still work, but it lacks support for features such as reboot to hacked BL.
Features:
amonet-aware
SDCard support
USB-OTG support
Backup/Restore support
Downgrade/Overwrite-protection for LK/PL/TZ
Autorestore of broken boot-patch
Also patches amonet-microloader when flashing images
Supports flashing stock-update bins (rename to .zip, no modification necessary )
NOTE: Your device needs to be unlocked.
NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System".
Many thanks to @Kaijones23 for testing!
Download: twrp-karnak-3.3.1-0.zip
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the Amazon Fire HD 8 and HD 10
Contributors
k4y0z, xyz`
Source Code: https://github.com/chaosmaster/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-07-17
Created 2019-07-16
Last Updated 2019-07-17
Changelog
17.07.2019:
Update TWRP to 3.3.1-0
Add support for vendor partition
16.07.2019:
Fix USB-OTG
Reserved #2
Reserved #3
Sent from my Pixel 3a XL using Tapatalk
@k4y0z @Kaijones23 good work guys!!
Great work!
Just flash from existing TWRP to update?
Michajin said:
Great work!
Just flash from existing TWRP to update?
Click to expand...
Click to collapse
Yup
Just uploaded a new build, that also fixes USB-OTG
Works great on my HD8 2018 that I just got today.
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
k4y0z said:
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
Click to expand...
Click to collapse
Wow very nice!
Does karnak has vendor partition??
Rortiz2 said:
Wow very nice!
Does karnak has vendor partition??
Click to expand...
Click to collapse
It has, but not used by stock as far as i can tell.
I added support in TWRP, so it could potentially be used by custom ROMS.
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
jibgilmon said:
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
Click to expand...
Click to collapse
Reflashing Magsik should not have been necessary if it was already installed
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
agr8lemon said:
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
Click to expand...
Click to collapse
You can do it either way, but just flashing the zip in recovery is probably the easiest way. You can reboot recovery while in TWRP to check that it flashed successfully, if you want to.
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
5442 said:
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
Click to expand...
Click to collapse
I just installed YouTube Vanced from Magisk.
nujak said:
I just installed YouTube Vanced from Magisk.
Click to expand...
Click to collapse
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
5442 said:
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
Click to expand...
Click to collapse
Flashing YT VANCED in TWRP will also work.
Notice: This is a dedicated thread for unofficial TWRP builds with msm-4.9 kernel. If you don't know why you're here, you probably want to just stick with whatever recovery you're using right now.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Disclaimer
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* I am 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 this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Redmi Note 4(X) (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-mido.img
Where x and y are version of TWRP you're going to flash.
(???) You know the rest.
Downloads
Webserver | MEGA
Known Issues
You tell me?
Special Thanks
Dees_Troy and everyone behind TWRP
Acknowledgements for msm-4.9 kernel port: https://kudnet.id/~raw/mido-4.9
Everyone on Redmi Note 4(X) community
Device Sources
TWRP repository fork
Device tree
Kernel source
Changelogstwrp-3.5.2_9-1-KudProject-mido
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated MoeSyndrome kernel in recovery
Added back Cust partition entry in fstab (umounting it also umounts Vendor partition)
twrp-3.3.1-3-KudProject-mido
Synced with TeamWin's changes up to 25 May 2020 (UTC+8)
Switched f2fs-tools to latest AOSP master
Updated prebuilt kernel to include all fixes and workarounds done in kernel
twrp-3.3.1-2-KudProject-mido
Initial TWRP build with msm-4.9 kernel in preparation for custom ROMs that ship 4.9 kernel
All other builds older than 3.3.1-2 are with msm-3.18 kernel instead.
Notes
This specific TWRP build is mandatory for flashing ROMs that ship msm-4.9 kernel and target FCM level 3. Any other recoveries (official and a number of TWRP forks) aren't supported nor will be guaranteed a successful flash.
Technical advice (although unrelated to TWRP): Never flash 3.18 kernel on 4.9 ROM or vice versa and hope everything will work. Just... don't.
Verifying released buildsThis was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.
And... I'm officially back!
We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??
ShreyYy said:
We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??
Click to expand...
Click to collapse
You can flash TWRP from TWRP itself just fine, just target right partition. And, you probably want to use 3.3.1-1 instead if you don't plan to flash any 4.9 ROM.
[Spot the device version]
Sent from my MI 9 SE using XDA Labs
It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.
Yes, look at los 16 official from Aryan Kedare, post 1167 with links.
Official TWRP 3.4.0 got released for mido.
Can we use that? Or you have to do your magic first?
speter2 said:
It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.
Click to expand...
Click to collapse
Evolution x support 4.9
Hi community,
Please, correct me if i'm wrong. If i already have installed a custom recovery, i just have to flash this and reboot to recovery and thats all? Regards.
Any update on 3.4?
lintah_darat said:
Any update on 3.4?
Click to expand...
Click to collapse
Under testing for all 3 devices so far
PS: You'll probably need updated ROMs more than recovery.
Sent from my Redmi Note 4 using XDA Labs
Hello guys, first post here I have installed the last Pixel Experience 11 Stable with the official lastest TWRP 3.4, but in the PE11 official page, they have a link to use this TWRP Custom version.
What should I do now ? Flash the custom and reinstall the PE11 ? Sorry if its a newbie question, but Im still learning about rooting and Custom ROMS. Cheers
Version 3.5.2_9-1 is now available. Release is currently available only via download server due to storage constraints on MEGA mirror. Enjoy!
does it need lazy flasher?
So no one has bothered to point out kudnet.id isn't working and the latest build is not posted on Mega.nz ?
Is this project abandoned?
Hello, I building twrp minimal manifest for teak board. In attached file what is this error?
Ouput Error:
ninja: error: '/root/_twrp/out/target/product/teak/system/bin/linker', needed by '/root/_twrp/out/target/product/teak/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin', missing and no known rule to make it
Re-post your issue here:
[HOW-TO] Building TWRP from source with goodies
I decided to put together a guide on how to build TWRP from source, having successfully built it myself and restored a few of the goodies that disappeared in the 3.3.1-0 release (e.g. install kernel). Also, marlin (Pixel XL) has had a few...
forum.xda-developers.com
stayboogy [ROM] AOSP 12L (12.1.0_r3, SPA2 5G) for Pixel 5 [redfin]
stayboogy AOSP 12L (12.1.0_r3, SPA2 5G) Redfin sources: base repo: https://android.googlesource.com/platform/manifest/+/refs/heads/android-12.1.0_r3/default.xml my work: https://github.com/stayboogy/stayboogy_Redfin this rom...
forum.xda-developers.com
1 Bug has been found so far:
Camera app will disappear from the app drawer, but it is still available from "double click power button" accessibility settings. It works out of the box if it has disappeared, but if you change the button settings it won't work any longer or be visible.
I'm working on tracking the fix.
Everything else works just as it should.
I have now uploaded a boot+recovery.img which can be used to boot into the Google Factory Recovery from adb using "adb reboot recovery"
--this is mainly useful to wipe userdata if you need to root after install, which makes rooting easier and no longer has to be done at install time since data has to be wiped.
--this recovery will be edited to install any zip without verification so that any update.zip can be applied such as open-gapps-installer.zips
I have also uploaded a root+boot.img which is patched with latest magisk already
I have also uploaded a root+boot+recovery.img which has both magisk root and Google Factory Recovery built into it.
THIS ROM ONLY AND IT'S VARIOUS BUILDS
These files are here:
stayboogy_Pixel5-Android12-AOSP/Build-1/imgs at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
Stayboogy Pixel 5 AOSP 12.0.0.r3 [straight from https://android.googlesource.com/] - stayboogy_Pixel5-Android12-AOSP/Build-1/imgs at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
github.com
Direct Links:
stayboogy_Pixel5-Android12-AOSP/direct-links at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
Stayboogy Pixel 5 AOSP 12.0.0.r3 [straight from https://android.googlesource.com/] - stayboogy_Pixel5-Android12-AOSP/direct-links at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
github.com
Direct Links have been added to everything.
I've cooked up a build of TWRP for this ROM, but I haven't had time to test it or upload it.
seriously i work heavily to i have 6 children but if u need another person to test for you im definitely down right now im trying to load corvos os or havoc just for playing
I appreciate the offer man. The only issue right now is I have very poor internet where I'm staying right now. My upload speeds are s*** so by the time I get something uploaded I've already tested it myself.
Twrp's repo for building the recovery is borked right now so I'm having lots of issues getting an image built to use for my ROM.
I will be having some more rom
releases coming soon though to be tested.
New Build coming as soon as I can get it all uploaded.
Build2 will include signed gapps [no spoofing like with CalyxOS which is terribly insecure in all ways] built inline with the rest of the system since I have yet to get a new twrp build working for 12.0.0+
Build2 will also include factory recovery already in the boot, mainly for wiping the device should you need to as installing zips still fails for some reason.
I also did not add the automotive files to either build as my main goal with these builds is a slim system without a lot of unnecessary fluff.
Other slight modifications coming soon as well.
Because Google is cracking down on distributing signed GApps directly on a device with AOSP Based Roms, you have to manually add your Google Play Store device identifier to Google's whitelist system. I'm not going to do this, and I do not suggest you do either. I have a build with signed GApps built inline with the AOSP system but it continually notifies for being "uncertified" by Google. Again this can be overcome by adding your Google Play Store device identifier to Google's whitelist. Because of this, I am not going to release a build including singed GApps.
I also will not be adding "signature spoofing" to support MicroG, OpenGApps, or any other variations of open source GApps. This is because, regardless what CalyxOS, LineageOS, and others have successfully convinced people of, signature spoofing is NOT SAFE, and it can easily be hijacked regardless of your settings in MicroG to gain unlimited background access to your device. I don't suggest it at all, and is why I don't use LineageOS or CalyxOS, but have opted to build AOSP like I have.
GApps Compatibility
stayboogy_Pixel5-Android12-AOSP/GApps_MagiskModules_direct-links at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
Stayboogy Pixel 5 AOSP 12.0.0.r3 [straight from https://android.googlesource.com/] - stayboogy_Pixel5-Android12-AOSP/GApps_MagiskModules_direct-links at main · stayboogy/stayboogy_Pixel5-Android12-...
github.com
hoping to have the camera bug fixed with the latest build, which is forthcoming, probably tomorrow sometime.
Has anybody installed this yet?? Looks like something straight out of the early Sony Xperia days
thatsupnow said:
Has anybody installed this yet?? Looks like something straight out of the early Sony Xperia days
Click to expand...
Click to collapse
it's straight AOSP, with no customization, as of yet anyway.
Build2 Uploading now!
*Camera Bug Fixed
**New Default Wallpaper
***Factory Recovery Already in boot.img
Build-2 Live, See OP for Links
Added New Info For GApps Compatibility. Several Magisk Modules Options Now.
stayboogy_Pixel5-Android12-AOSP/GApps_MagiskModules_direct-links at main · stayboogy/stayboogy_Pixel5-Android12-AOSP
Stayboogy Pixel 5 AOSP 12.0.0.r3 [straight from https://android.googlesource.com/] - stayboogy_Pixel5-Android12-AOSP/GApps_MagiskModules_direct-links at main · stayboogy/stayboogy_Pixel5-Android12-...
github.com
at 97% complete on a 12.1 build from a new development machine, based on the same code the last OTA was, vanilla though of course.
12.1 coming tonight.
should mean this build will be compatible with the working TWRP image, fingers crossed
I'll have 12.1 uploaded sometime Friday most likely--already built and working just fine, with April OTA firmware too, but still Vanilla AOSP. Currently re-working on twrp for these builds so that we have a working recovery to do whatever we need. And to make upgrading to newer builds simpler.
once I have a working twrp image that is embedded as a stock recovery option into the boot.img, I will start working on bringing features like call recording, theming, etc into the builds. those types of additions are fairly simple.
we also need twrp for better GApps options should you wish to use them. I won't be for daily use, but I intend to make this Vanilla AOSP look much better while still keeping it simple.
and for the record, you can already used xposed and magisk modules to signature spoof to use MicroG, but it will not be baked into my builds at all. I don't support it. I don't really support Google GApps either. I intend to use this vanilla once twrp is working and I get the mods I use regularly added and it looks better. All forthcoming very soon I assure you.
GOT TWRP WORKING!!! (using the working image I posted about in the Guides section 3.6.1_11-0)
Unfortunately, you must wipe your userdata and encryption must be disabled for userdata...
Here's how to have working TWRP for my AOSP ROMs for now, until I have twrp encryption support.
1) root your rom, directions are in OP
2) make sure you are actually rooted with the patched boot.img flashed
3) adb root
4) adb remount
5) adb shell rm /vendor/etc/fstab.sm7250
6) adb push fstab.sm7250 /vendor/etc/
7) Settings-->System-->Reset Options-->Erase All Data (factory reset)
8) after "Erasing" is finished immediately hold the volume down button to get into bootloader
9) fastboot boot twrp.img
10) adb push twrp.img /
11) Advanced Menu-->Install Ramdisk-->choose the twrp.img you just pushed to /
12) Backup your current boot.img only and copy to your internal sdcard and rename from ***.win to ***.img
13) reboot to system and install Magisk
14) patch the boot.img you just backed up
15) reboot to bootloader
16) fastboot flash boot last.boot.img
17) now you have twrp and root for aosp
EDIT: Looks like this may not be permanently working...ugh. This file gets overwritten on reboot for some reason, probably baked into the ramdisk. I'll have it conquered before long I assure you
Should have 12.1 up sometime today/tonight. Call recording, round icons, some hidden settings enabled, various other small changes will be in available with its release.
alright, i've got 12.1 built with gapps minimal built inline, and once your android id is put into Google you will pass play protect
however, device overlays that include lots of the mods I had planned such as call recording which i've successfully patched the dialer app for, just aren't getting copied over because of some issues in the boardconfig from google in aosp source. it took me a while to figure out what was going on, but i'm rebuilding right now.
I'm also working with the Lineage source too at the moment, going to remove signature spoofing support and release a build of it as well. Working on finding the best configuration for everything.