Related
Code:
*** Disclaimer ***
This is provided free of charge and does not come with a warranty.
If your device fails to comply with your standards of what you consider functioning, I am not liable.
You do so at your own risk and take the responsibility upon yourself.
Introduction
Since official builds have been dropped, looking for an easy solution to keep updated by latest security patches and other updates from LOS-15.1.
Follow these steps
Installation instructions
A) download this latest mako lineage-15.1 ROM ( signed using own release-keys; to be flashed in TWRP)
B) migrating official LOS-15.1 release-keys to this ROM's release-keys by script provided
( to be done only once before flashing first time this ROM in TWRP, can be done fully in reverse also )
I also put a brief text file "Using script migration.txt" for explanation there.
Flashing Instruction
1. Backup all your data before you start ( I never needed my backups, all went smooth
2. Migrate keys by script. ( to be done only once before flashing first time this ROM)
3. Flash the ROM.
4. Reboot.
Result
all Apps and App-data are preserved ( including calling history, SMS, . . .; no need to reinstall Apps or to wipe /data partition )
as easy and smooth as to update an official mako lineage-15.1 ( except step B)
Click to expand...
Click to collapse
Downloads:
ROM: drive.google.com
ROM second source for downloading: androidfilehost.com
Sources:
Migration script: migration_RZ.sh
(Please see brief text file "Using script migration.txt" for explanation there.)
Credits:
- LineageOS team.
- @voron00 for his great work.
- If I forgot someone, please tell me.
Source Code: https://github.com/LineageOS
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][LOS-15.1] [MAKO], ROM for the Google Nexus 4
Contributors
roland3939
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: LineageOS-15.1
Version Information
Status: Stable
Stable Release Date: 2019-07-13
Current Stable Version: lineage-15.1-20211018-UNOFFICIAL-mako-signed
second source for download: androidfilehost.com
Created 2019-07-13
Last Updated 2021-10-20
reserved
Thank you very much for this ROM.
How long do you plan to support updating this ROM? As fas as I understand, OTA updates will be disabled when switching?!
Crongar said:
Thank you very much for this ROM.
How long do you plan to support updating this ROM? As fas as I understand, OTA updates will be disabled when switching?!
Click to expand...
Click to collapse
my goal is to keep this ROM updated until EOL of LOS-15.1 or EOL of my MAKO-device (depending on which one will come earlier
This ROM (and its updates) cannot be installed using the LOS-15.1 system's updater app ( I didn't modify the URL defined by the updater_server_url resource )
you have to do these few steps manually:
Flashing Instruction when switching from OFFICIAL ROM LOS-15.1
1. Backup all your data before you start ( I never needed my backups, all went smooth
1 a. download ROM ( zip-file) to the device or do adb push ROM ( zip-file) (which ever is more convenient to you)
2. Migrate keys by script. ( to be done only once before flashing very first time this ROM )
3. Boot to TWRP recovery
3 a. Flash the this ROM ( latest build)
4. Reboot to System
have fun
Hi, did you do anything special for this build or did you just follow the build instructions https://wiki.lineageos.org/devices/mako/build
rdorsch said:
Hi, did you do anything special for this build or did you just follow the build instructions https://wiki.lineageos.org/devices/mako/build
Click to expand...
Click to collapse
Nothing special, only true LOS 15.1 repository. Build is signed and keys for migration are provided. Thus seamless switch by dirty flashing from official LOS 15.1 is easy and smooth.
Interesting, my build compiled, but did not boot :-/
Do you know https://forum.xda-developers.com/showpost.php?p=79938551&postcount=346
?
Seems to be a similar effort (or is this yours?).
rdorsch said:
Interesting, my build compiled, but did not boot :-/
Click to expand...
Click to collapse
what's wrong with your build? did you do any debugging already ?
rdorsch said:
Do you know https://forum.xda-developers.com/showpost.php?p=79938551&postcount=346
?
Seems to be a similar effort (or is this yours?).
Click to expand...
Click to collapse
No, that's in No case my build. For differences, as i know so far, please see my post
https://forum.xda-developers.com/showpost.php?p=79957738&postcount=348
Thx for the instructions! But how do I technically do step "2. Migrate keys by script" ?
I managed to install LOS one year ago on my nexus4 but have no glue how to run a script on my mobile device.
Sorry for asking stupid questions !?!
next4 said:
Thx for the instructions! But how do I technically do step "2. Migrate keys by script" ?
I managed to install LOS one year ago on my nexus4 but have no glue how to run a script on my mobile device.
Sorry for asking stupid questions !?!
Click to expand...
Click to collapse
step "2. Migrate keys by script" is explained here ( to be found in the ROM's download folder):
Using script migration.txt
for any further questions, please ask
thx again for sharing, maintaining and providing the data and your knowledge. :good:
at the moment i am doing the backup. afterwards i will follow the txt for migrating the script.
as far as i can tell, you provided the unofficial ROM and uploaded it to google drive but where will the unofficial updates be found in the future?
---------- Post added at 12:46 PM ---------- Previous post was at 12:21 PM ----------
:victory:
everything went smooth. security updates 5.july 2019 !THXroland3939!
next4 said:
(---cut---)
as far as i can tell, you provided the unofficial ROM and uploaded it to google drive but where will the unofficial updates be found in the future?
---------- Post added at 12:46 PM ---------- Previous post was at 12:21 PM ----------
:victory:
everything went smooth. security updates 5.july 2019 !THXroland3939!
Click to expand...
Click to collapse
thanks for your feedback
I'm going to share next updates of this ROM ( incl. security patches August 2019) using the same google drive folder.
hold on!
New build with august security paches uploaded:
lineage-15.1-20190810-UNOFFICIAL-mako-signed
Bist super. Merci!
Frank aka Next4
lineage-15.1-20190906-UNOFFICIAL-mako-signed
New build with september security paches uploaded:
lineage-15.1-20190906-UNOFFICIAL-mako-signed
Hi,
first I want to thank you for providing this. You saved my phone because my self build let me stuck at the Google screen.
I followed the instructions from the official guide for mako. The first time the command source build/envsetup.sh && breakfast mako did not succeed as expected. I then connected my phone to my pc that had the latest official LineageOS build installed, it was already a few weeks old as it was already no longer official maintained. I rerun the command and it finished successful and proceeded with the guide. However, when sideloading my self built image I got stuck at the Google screen.
Do you have any idea what may have gone wrong?
How have you extracted the proprietary blobs? Is it enough to run source build/envsetup.sh && breakfast mako or do I need to extract the propriety blobs in an extra step as the command finishes successful when the phone is connected.
thacoon said:
(---cut---)
How have you extracted the proprietary blobs? Is it enough to run source build/envsetup.sh && breakfast mako or do I need to extract the propriety blobs in an extra step as the command finishes successful when the phone is connected.
Click to expand...
Click to collapse
hi,
proprietary blobs are extracted by running the extract-files.sh script while Nexus 4 device is connected to your computer with ADB and root enabled:
Code:
./extract-files.sh
did this step succeed without errors ?
check if all files listed in "~/android/lineage/device/lge/mako/proprietary-blobs.txt" are to be found in sub-folders of "~/android/lineage/vendor/lge/mako/proprietary/vendor/"
roland3939 said:
hi,
proprietary blobs are extracted by running the extract-files.sh script while Nexus 4 device is connected to your computer with ADB and root enabled:
Code:
./extract-files.sh
did this step succeed without errors ?
check if all files listed in "~/android/lineage/device/lge/mako/proprietary-blobs.txt" are to be found in sub-folders of "~/android/lineage/vendor/lge/mako/proprietary/vendor/"
Click to expand...
Click to collapse
There were not files, I now run
Code:
./extract-files.sh
and it extracted the files. I wonder why
Code:
source build/envsetup.sh && breakfast mako
succeeded as soon as my phone was connected although there were no vendor files. That's why I assumed that it run
Code:
./extract-files.sh
automatically. However, if I have some time I'll redo the build and check if it now works.
Thanks for helping :good:
1st time flashing
My nexus 4 device isn't working anymore. I can't get to settings and it keeps popping up an error of 'Google play store service has stopped working" in unending loop. I tried to do a factory reset but it says, "no command" or something like that. Well all that doesn't matter. Wondering if you could point me to instruction for flashing this for the 1st time? Can I still follow the ones from the old lineage website or go the current site and just follow some from another phone?
Just found this, can I use these instructions for this package ? lineageosroms.com/nexus-4-mako/
Thanks in advance for the help,
nyrel said:
My nexus 4 device isn't working anymore. I can't get to settings and it keeps popping up an error of 'Google play store service has stopped working" in unending loop. I tried to do a factory reset but it says, "no command" or something like that. Well all that doesn't matter. Wondering if you could point me to instruction for flashing this for the 1st time? Can I still follow the ones from the old lineage website or go the current site and just follow some from another phone?
Just found this, can I use these instructions for this package ? lineageosroms.com/nexus-4-mako/
Thanks in advance for the help,
Click to expand...
Click to collapse
hi,
for first time (clean !) flashing this rom lineage-15.1-20190906-UNOFFICIAL-mako-signed,
the instructions you mentioned are fully OK
or follow these instructions https://wiki.lineageos.org/devices/mako/install, whichever is more convenient to you
note: you don't have to migrate keys by script ( as you already did a full wipe of data, cache and system partitions )
NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery, ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0
Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13+).
- No changes to device-specific files.
Known issues:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)
Looking forward on this one, thank you for the effort!
Hopefully android auto and face unlock are working. Thanks in advance.
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
Can't say anything about Android Auto, but Face Unlock works just fine!
MaWalla99 said:
Can't say anything about Android Auto, but Face Unlock works just fine!
Click to expand...
Click to collapse
Great, will test and report about the android auto and overall Rom. Thanks again.
DC dimming seems to be missing
Welcome back team with a11...even with initial build rom is so stable , like this rom simplicity with so many customisations thankyou
Screenshot ???
vindipi said:
Screenshot ???
Click to expand...
Click to collapse
This Rom has latest Android security patch of January and for screenshots open and scroll down this website
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
what gapps
DRAKOITYU said:
what gapps
Click to expand...
Click to collapse
I personally used nikgapps...may be all are compatible
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
After running the Rom for 5 days now I can confirm that it's very stable and has tons of customization. Unfortunately though android auto is not working. face unlocking, camera, etc works fine. Would appreciate it if you could fix the android auto issue in the future build.
Anyone else having issues with GPay? I'm using Magisk, hidden, and GPay still won't work.
Is it possible to update crDroid from 6.13 to 7.2 without data formatting (keeping application and data)?
MaWalla99 said:
Download ROM
TWRP (use 3.5.0 or higher)
Magisk (use 21.2 or higher)
Click to expand...
Click to collapse
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
mahroze said:
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
Click to expand...
Click to collapse
Twrp 3.3 should work fine with the rom. You can keep using it if you want to. However, there is no extra step to use 3.5 vs 3.3. You have to flash twrp after flashing the rom so you can upgrade to 3.5 by just flashing it instead of 3.3.
Quick questions, this rom have smart charging feature?
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
not_the_droid_ur_lookin4 said:
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
Click to expand...
Click to collapse
You have been positing this in more than one thread. This has nothing to do with any rom, and is related to what you are doing with your phone or the phone itself. Telephony is flowless on every Android 11 custom rom for Oneplus 6. And so is GPS, which literally connects in seconds.
First thing you should do is: disable wifi calling, because if your provider doesn't have the feature (or you are not provisioned for it), that could cause your problems. Next, uninstall any mode you might have. Try calling without Gapps.
Also, if you ever used Syberia Rom, you got custom /vendor, which would not work with other custom roms that use stock /vendor. So, you need to re-flash full stock rom onto both slots, which is a pre-requisite for flashing most custom roms. Then follow directions for installing a custom rom.
First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19
How's the battery life?
works offline charge?
Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life
Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi
pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.
Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok
In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?
Never mind! I went ahead and installed it following the instruction . It works, thanks!
bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?
Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.
betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?
Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.
Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 ROM
* 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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on A/B Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
Open the updater app, download the update, then press install, press reboot when prompted, you will be taken to TWRP, there isn't any need to flash GApps separately
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_google_redbull
Device tree source:
https://github.com/AICP/device_google_barbet
Vendor source:
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
@Siluxsept
Information:
ROM OS Version: 11.x
Kernel: Linux 4.19.160
ROM {Firmware|Vendor} required: 11
Status: SUPERCEEDED
Release Date: 03-03-2022
You want to see a "normal" night at the "DEV office", click here!!
AICP Android 12.1 release candidate for Google Pixel 5a
ROM - https://www.androidfilehost.com/?fid=14655340768118475742
BOOT.IMG - https://www.androidfilehost.com/?fid=14655340768118475907
Screenshots here
Reserved
Nice nice for when I get me a pixel 5a. God bless fam.
Thank you for making a ROM for the 5a. Waiting for mine to arrive so I can start testing
Dumb question: does this support substratum?
grandpajiver said:
Dumb question: does this support substratum?
Click to expand...
Click to collapse
Not sure tbh. I never tried Substratum on AICP. We have advanced theming options in AICP Extras replacing it pretty well.
Nice
Why are there weekly updates?
Can I make the back button on the right?
ALWA7SH6 said:
Nice
Why are there weekly updates?
Can I make the back button on the right?
Click to expand...
Click to collapse
Updating hosts for integrated adblock and security patches on 11.
Yes, check AICP Extras -> Onscreen navigation options -> Invert layout
hmm the phone seems to think it's got airplane mode on when it isnt. trying the latest weekly with a t-mobile esim and it wont use the mobile network. im using mindthegapps linked in the post
nvm ignore that. seems ubreakifix broke something inside. it isnt working on stock either.
Hey Sil, quick question. Does your rom include the option to add the cursor arrows to the navigation bar?
Locklear308 said:
Hey Sil, quick question. Does your rom include the option to add the cursor arrows to the navigation bar?
Click to expand...
Click to collapse
Okay never mind. My P5a came in today and somehow I was able to load the ROM without any issues ON MY FIRST TRY. Wow talk about luck on my part... haha.
Anyway, I found the cursor arrows for the navigation drawer...but I found a problem. Or, at least I think it is a bug? When you invert the back and resents button it inverts the arrows as well. Is this intentional? If so... by chance do you think the option to not invert the cursor arrows is possible?
Other than that I love the ROM so far. Tomorrow will be the first test run of the phone and the ROM!
Locklear308 said:
Okay never mind. My P5a came in today and somehow I was able to load the ROM without any issues ON MY FIRST TRY. Wow talk about luck on my part... haha.
Anyway, I found the cursor arrows for the navigation drawer...but I found a problem. Or, at least I think it is a bug? When you invert the back and resents button it inverts the arrows as well. Is this intentional? If so... by chance do you think the option to not invert the cursor arrows is possible?
Other than that I love the ROM so far. Tomorrow will be the first test run of the phone and the ROM!
Click to expand...
Click to collapse
Hmm working okay for me with AOSP keyboard. Are you using GBoard or any other keyboard app?
Siluxsept said:
Hmm working okay for me with AOSP keyboard. Are you using GBoard or any other keyboard app?
Click to expand...
Click to collapse
It's the AOSP keyboard. I can grab some screenshots if that helps. Basically if you leave the navigation bar where the back buttons on the left, the cursor arrows look normal, but if you hit that invert switch to move the back button to the right it also swaps the cursor arrows. It's not just visual though, they work swapped as well.
finally got my phone back from google. flashed the rom per the instructions in the op. i let it restore my apps during setup as it says that should be fine. i cant download anything. the storage permissions seem to be messed up. i grabbed a logcat using the extras app. i tried the reset app pref and it didnt help. the only app i was able to fix was solid explorer, i removed it's access and then regranted it. i tried that with a few more apps but it didnt work.
pbanj said:
finally got my phone back from google. flashed the rom per the instructions in the op. i let it restore my apps during setup as it says that should be fine. i cant download anything. the storage permissions seem to be messed up. i grabbed a logcat using the extras app. i tried the reset app pref and it didnt help. the only app i was able to fix was solid explorer, i removed it's access and then regranted it. i tried that with a few more apps but it didnt work.
Click to expand...
Click to collapse
Sounds like it did not setup data partition correctly. Try this:
- Format data and reboot into recovery
- Flash / sideload ROM and fully reboot into system. Setup PIN or password in security settings. This should initialize and encrypt data.
- Reboot to recovery. Back in TWRP go to Mount -> Decrypt Data to make storage available. Sideload or flash Gapps package, Magisk, etc without wiping
- Boot system and start restoring your apps (3rd party apps like Titanium might cause trouble, refer to respective app devs then)
Hope that helps.
Siluxsept said:
Sounds like it did not setup data partition correctly. Try this:
- Format data and reboot into recovery
- Flash / sideload ROM and fully reboot into system. Setup PIN or password in security settings. This should initialize and encrypt data.
- Reboot to recovery. Back in TWRP go to Mount -> Decrypt Data to make storage available. Sideload or flash Gapps package, Magisk, etc without wiping
- Boot system and start restoring your apps (3rd party apps like Titanium might cause trouble, refer to respective app devs then)
Hope that helps.
Click to expand...
Click to collapse
alright, ill give that a try. i stopped using backup apps a while ago and just use the google backup stuff. ill let you know how it goes. other than this issue the rom is really nice.
got it working, what i did was
- formatted data and reboot to recovery
- flash rom and reboot to recovery
- installed gapps and magisk
- booted and went through setup without setting a pin or anything
- set pin
im not sure if not setting the lockscreen up in setup mattered at all as it defaults to swipe and encrypted. what you said to do also worked but wouldn't let me restore from google
the camera that comes with the rom seems to crash once at every reboot. https://haste.aicp-rom.com/omagewutig other than that, everything is perfect.
side note. i love all the log grabbing stuff built into the rom
Hello, do you plan to update ROM up to Android 12?
pbanj said:
got it working, what i did was
- formatted data and reboot to recovery
- flash rom and reboot to recovery
- installed gapps and magisk
- booted and went through setup without setting a pin or anything
- set pin
im not sure if not setting the lockscreen up in setup mattered at all as it defaults to swipe and encrypted. what you said to do also worked but wouldn't let me restore from google
the camera that comes with the rom seems to crash once at every reboot. https://haste.aicp-rom.com/omagewutig other than that, everything is perfect.
side note. i love all the log grabbing stuff built into the rom
Click to expand...
Click to collapse
Thanks for your report. For camera - need to double-check perms. Probably not to be fixed on R releases anymore. Android 12 around the corner.
I've managed to successfully install LineageOS 19.1 on my Zenfone 8 but I didn't realise you needed an entirely different release to use MicroG.
So I am now trying to install the LineageOS for MicroG release but I'm running into problems:
The MicroG release is a few weeks older than the LineageOS one. When I tried installing it I got an error "SPL is considered a downgrade" and it wouldn't let me install it.
The MicroG release doesn't provide a `vendor_boot.img` file which is required according to the LineageOS instructions. I tried using the file from the regular LineageOS release and it seemed to work the first time but now it won't boot into the recovery mode at all; it just boots into the bootloader menu.
I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files.
I saw posts in the development thread that people are having similar struggles so I'm not sure how to proceed.
Ultimately, my request is: can someone please outline an easy-to-follow approach on how to install LineageOS with MicroG on the Zenfone 8?
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd
bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd
Click to expand...
Click to collapse
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
hawkins22 said:
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
Click to expand...
Click to collapse
I would prefer to stick with LineageOS because of the larger community.
Click to expand...
Click to collapse
Understand
But for the records:
Signature-spoofing is only required to use all features of MicroG , e.g. to use the patched Playstore. If you don't need that you can ignore this.
The best method (IMHO) to install NanoDroid is:
- install Magisk into the booot partition
- install the ZIP file with NanoDroid using TWRP
Nanodroid will then install MicroG as Magisk Module .
regards
Bernd
Hello,
The issue is due to the fact that LOS+MicroG has a long delay in releases (at the time of this message, the latest LOS version is 2023-02-03 and the latest LOS+MicroG 2022-12-22). I think it is an issue because the main site announces a build every two weeks, and there are some tickets in their Git repository about this.
Anyway, I had the same issue few weeks ago and I managed to install LOS+MicroG using an old vendor_boot image; indeed you have to use the one provided by the LineageOS wiki, but you have to use one older than the LOS+MicroG release to avoid the SPL issue.
Unfortunately, I had a look and the previous version was deleted on their website since I installed my phone and I can't provide the one I used because I removed the file...
So I'm afraid you have to wait a new LOS+MicroG build or find a old vendor_boot.img to proceed.
But I agree with you: it's a shame that there is no straightforward way to install LOS+MicroG. It was easy in the time, but now it's more complicated to manage due to phones specification (I guess, I'm not a ROM dev) - but yes I think that discourage a lot of people to use it.
Good luck.
bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Click to expand...
Click to collapse
Yeah, that's why "LineageOS for microG" exists in the first place. It is a fork of LineageOS where signature spoofing was enabled. So, there is no issue using LineageOS for microG. Please educate yourself before posting things like this.
"I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files."
Click to expand...
Click to collapse
There are (or at least in the past were) indeed some files missing from "LineageOS for MicroG" for the Asus Zenfone 8. It is/was a bug confirmed by the developers. I reported it to them, maybe they fixed it in the meantime. This would be good news! I haven't checked for a while.
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
I managed to install it successfully using TWRP instead of Lineage's own recovery image. Maybe TWRP simply doesn't care if you're "downgrading" and lets you flash anyway?
The final step-by-step process I used was something like this:
Unlock the phone's bootloader using the official ASUS unlocking tool APK.
Restore the phone to its stock Android 12 state using the ASUS "raw" image (instructions):
https://dlcdnets.asus.com/pub/ASUS/...KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Flash the "vendor_boot.img" file from the regular LineageOS release as detailed in the instructions.
Install TWRP recovery instead of the LineageOS recovery image.
Use TWRP recovery to flash the LineageOS-MicroG ROM.
Mario545 said:
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
Click to expand...
Click to collapse
The vendor_boot.img is required according to the LineageOS installation instructions and is provided as a separate download on the same page.
However after extracting both the LineageOS and the LineageOS-MicroG releases, I believe the vendor_boot.img files are actually identical (same filesize) so you can probably use them interchangably anyway.
I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
Mario545 said:
I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
Click to expand...
Click to collapse
AFAIK the vendor_boot.img is also required by the LineageOS recovery image necessary to install the LineageOS image.
Therefor it must be installed before booting the LineageOS recovery.
regards
Bernd