[ROM][12.1][UNOFFICIAL] PixysOS [PL2] - Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe

[ROM][12.1][UNOFFICIAL] PixysOS [PL2] - Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe

Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!

Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!

I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)

Just tell me about the experience you had with the Rom. is it smooth or not

Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.

Gcam not working fix it

Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)

Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.

Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)

OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.

Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)

I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.

Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.

New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!

Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)

Is anyone able to check if Duo Mobile 2fa is working?

I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.

Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.

Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.

Related

[ROM] [marlin] [8.1] [LOS-based] crDroidOMS**v4.7 (10/12/18)

ROM thread text:
This is crDroid for 5.5" Pixel XL [marlin]
crDroid Website: https://crdroid.net/
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
Vendor image for current build - OPM4 July vendor image - DOWNLOAD VENDOR
GAPPS: For now, open gapps unofficial, also courtsey @razorloves - DOWNLOAD GAPPS
OpenGapps: Not Supported anymore, use @razorloves gapps.
First time installing crDroid to your PixelXL, or coming from another ROM:
**NOTE** As you probably know by now, marlin (and sailfish) is weird. You must be on TWRP 3.2.0.0 to install this! 3.2.1.0 does not allow ROM installation. 3.2.0.0 does not encrypt properly, so you must remove your PIN/password before booting to and / or installing it. These installation instructions will assume you already know and have done that.
**NOTE** You are also able to use 3.2.1.-2 (3.2.0.0 or 3.2.1.-2)(Nothing in between)
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip & vendor img to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
5) Flash TWRP ***If you do not do this, you will lose TWRP!***
6) Reboot back into TWRP
7) Flash vendor image
7a) Mount vendor partition, navigate to vendor/overlay and delete that folder
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk 16.2
If you like music like I do and want to make it better, see post #3 for instructions on installing ViPER4Android.
Instructional Video
I Apologize about video quality, but this will help get you an idea of the steps involved.
Steps are the same for Marlin and Sailfish. Use corresponding files for device.
https://youtu.be/mmxIrp7BiRk
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
None yet, If you find something that is consistently reproducible, do so and pull a log. Without logs, we cannot fix the bugs. Please report any that you run into, assuming you have tested on a clean install. :good:
NOTE ON SUBSTRATUM
We currently do not have substratum commits in the ROM because they have not updated their repos on git for Oreo. As such, if you want to use Substratum, you will be doing so by allowing root and using legacy mode. you -must- make sure whatever theme you try supports 8.1. Even some that say they support Oreo may only work with 8.0, not 8.1. I'd recommend the following:
Suggestion: whenever installing themes, remove your pin/password so you can get TWRP to mount data.
If you get in a FC/bootloop situation, boot to TWRP, mount data and remove the file /data/system/overlays.xml.
That should allow you to boot and uninstall the overlays without reinstalling anything.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- @razorloves - Without his device tree and kernel bringup to work from, crDroid for marlin would not be possible at all. Apart from the ROM development itself (for which @neobuddy89 bears the largest burden, in addition to the great developers of LineageOS itself), credit for this ROM being able to even build goes to razorloves.
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
Source Code:
Device tree: https://github.com/razorloves/android_device_google_marlin
Kernel tree: https://github.com/razorloves/android_kernel_google_marlin
Vendor tree: https://github.com/razorloves/proprietary_vendor_google
Credit for all of those trees goes to @razorloves , without whose work crDroid for marlin would be a shell of itself!
XDA:DevDB Information
[ROM] [marlin] [8.1] [LOS-based] **crDroid**v4.7, ROM for the Google Pixel XL
Contributors
hokiealumnus, neobuddy89, BHermes21, razorloves
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Current Stable Version: v4.0
Stable Release Date: 2018-03-23
Beta Release Date: 2018-01-19
Created 2018-01-09
Last Updated 2018-10-12

I already said it in my post above, but feel it needs repeating. HUGE thanks to @razorloves , without whose marlin bring-up this ROM would still not be built.

*** NOTE - We cannot actively support audio (or any other) mods. I'm posting this because it works for me and I use it personally. This is not supported by our ROM team. Only the ROM / vendor / gapps and nothing else is supported by the crDroid development team. ***
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!

Sweet thanks

Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.

hokiealumnus said:
This is crDroid for 5.5" Pixel XL [marlin]
If you're looking for the 5" Pixel [sailfish], it is not built yet; sorry.
Click to expand...
Click to collapse
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!

Awesome thank you. Flashing now

Akomack said:
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
Click to expand...
Click to collapse
It -says- it does in Photos. However, it said it did in Nougat, but never did actually work in any LOS / LOS-based ROM. It took up storage space even though the Photos app said back up all you want with Pixel. Therefore I can't promise full functionality. The app does say it works though.
thebigdonny said:
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Click to expand...
Click to collapse
No promises on a time frame though I'm sorry to say!

hokiealumnus said:
No promises on a time frame though I'm sorry to say!
Click to expand...
Click to collapse
Soon TM

Added instructions for using Viper4Android in the 3rd post while they're still working on a functioning ARISE.

Works very good only one force close which I just uninstalled and reinstalled anyway been running du 12.0 nice change thanks

hokiealumnus said:
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Click to expand...
Click to collapse
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1

kingbri said:
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
Click to expand...
Click to collapse
Why would I give you credit? I've never even seen that post.

Are there any custom kernels that will work with this ROM right now?
Sent from my Pixel XL using Tapatalk

@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.

Thanks so much, Hokie! Packed with features, really appreciate all of the detailed instructions! Thank you!

Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yes that is normal

Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yep normal.
Reboot recovery. Flash gapps/vendor reboot.
Giving this a whirl. Thanks OP!!!

Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Click to expand...
Click to collapse
Aye, that is normal. It just means you don't have vendor installed, which you can't do until rebooting back to TWRP (so it switches slots).
Factory reset does not wipe system partition. If you are coming from a different ROM, when you switch slots, you are leaving a different ROM on your inactive slot. Not a huge deal, but I don't recommend it.
Edit - The best way to avoid stressing about that is to allow the reboot, but interrupt boot (pwr + vol down), and go right to recovery from the bootloader.

BHermes211 said:
Are there any custom kernels that will work with this ROM right now?
Click to expand...
Click to collapse
Maybe? I haven't tried installing one yet. ElementalX has always worked well in the past, indeed I always built nougat crDroid with it. Just haven't tried it on Oreo.
If you want to try installing it, worst it will do is bootloop. Just dirty flash (wipe only cache/system, leave data, repeat normal install) back to the included kernel.

[9.0][EXPERIMENTAL]Resurrection Remix v7.0 [blueline]

Warning: This is an untested unoffical build for the Pixel 3 (blueline), so please take caution in flashing and make a backup.
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
I am not a developer, I only build this ROM and it reflects the the current status of LineageOS / Resurrection Remix. If there are any device specific things missing or not working. I suggest to contact the LineageOS team, they are the real developers here and deserve all the credits.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process, so make sure you make a backup if needed.
In order to make the right startbase for the ROM you have to install the latest stock Pixel 3 image from Google found here.
Place the ROM and optionally the TWRP zip, a kernel and root on the phone and reboot to recovery by using the command line (fastboot boot twrp.img) or hold the VOL DOWN key while rebooting the phone.
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe or use the slider in TWRP for a factory reset. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip, kernel and root and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM on the phone and reboot or fastboot flash to the TWRP recovery
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when Resurrection Remix has also adapted to the latest monthly sources, you will have to do an extra step:
Download the latest Resurrection Remix ROM and place it on the internal storage
Download the latest image from the Google Factory Images site, extract the bootloader, radio and vendor images and flash them in the bootloader to both slots
From here go to TWRP recovery and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
ROM Download
GApps are already included in the ROM
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
- Active Edge
- Now playing
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

turbolukex5 said:
Warning..
Click to expand...
Click to collapse
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?

xFirefly93 said:
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?
Click to expand...
Click to collapse
It features the gapps that come with the Dirty Unicorns ROM.

So excited to finally see RR on my pixel 3. Been a long wait
Thank you ?

Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?

retr0gr4d3 said:
Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?
Click to expand...
Click to collapse
You can do both.

I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.

Spider_Pig27 said:
I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.
Click to expand...
Click to collapse
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.

retr0gr4d3 said:
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.
Click to expand...
Click to collapse
I flashed it with a custom kernel & still didn't boot for me. I flashed it like I've been flashing other rooms. Didn't really do anything different or special with this one.

All is running well for most trying it out and that's why it is so quiet ??

Doesn't work, installed latest factory image, installed the ROM, TWRP, and Magisk (no custom kernel). Image fails to boot, stuck at boot image for about 10 minutes and then it kicks me back out to TWRP.

I'm also stuck on the start screen with the loading icon. Just installed RR and TWRP, nothing too special. Everything went perfectly until I attempted to boot. Is there anything I'm missing?

Sad to report same issue here..

To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.

Portgas D. Ace said:
To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.
Click to expand...
Click to collapse
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.

Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.

eezdva said:
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.
Click to expand...
Click to collapse
tjcalhoun1221 1 said:
Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.
Click to expand...
Click to collapse
I know the dev, he doesn't know how to fix this.
However, you can flash the RR 7.x.x GSI if you want. I'll leave detailed steps.
Do not I am not some sort of Pixel dev. I did these steps myself with help from a friend in the Proton Kernel team.
1) Boot to your TWRP
2) Flash avbctdisable.zip. It acts like a dm-verity disable afaik, however I can't remember where I found it. I think it's on the internet, I'll edit when I find it, or if I post it myself.
3) Boot to fastboot
4) Flash the stock boot.img from the latest P OTA (fastboot flash boot boot.img)
5) Flash your GSI (fastboot flash system system.img)
6) Flash TWRP temporarily (fastboot boot twrp.img)
7) Wipe your /data (wipe > advanced wipe > data > type "yes") but do NOT reboot yet
8) Flash TWRP installer (blueline/crosshatch respectively, then reboot back to TWRP)
9) Flash your GApps, Magisk and/or kernel
9.1) If this doesn't work (/system isn't big enough) then put "resize2fs /dev/block/by-name/system$(getprop ro.boot.slot_suffix)" into adb shell. It will make /system bigger for GApps.
10) Reboot and you should have RR 7.x.x GSI working.

[ROM][UNOFFICIAL][10.0] AICP w GAPPS [MOTO G7 POWER]

{
"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 with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. 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
And all the other Developers, Testers, Donators and Users.
@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!!
If you wanna donate to me, @Electimon my paypal link is here: paypal.me/ciphermtm
Latest Stable Release Version 15.0
Download link: https://1pwn.tk/android/ocean/AicpQ/aicp-4172020.zip
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
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:
Included
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. No
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
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 the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. 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 preform 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 loose 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 loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
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. and 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 in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. 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 Zipfile.
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!)
Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > 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!
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 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.
If you want to contribute to AICP, or want 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/electimon/android_kernel_motorola_sdm632-1
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:
@Electimon
@SyberHexen
@Jleeblanch
@erfanoabdi
ROM OS Version: 10.0.x
Kernel: Linux 4.9.y
Version Information:
Status: When ever I want to release an update
Release Date: 4-15-2020
April 17 2020
- Fixed Daydream.
- Fixed Stereo Audio.
- Fixed Wifi Calling.
- Fixed Some radio issues.
- Replace stock clock app with google clock app.
- Fixed some battery issues.
- Fixed audio bugs.
You want to see a "normal" night at the "DEV office", click here!!

Anyone knows if this will work with Verizon sim with SMS working and data?

zfk110 said:
Anyone knows if this will work with Verizon sim with SMS working and data?
Click to expand...
Click to collapse
Why wouldn't it work? Or why would you have such issues. Have you swapped out your apn config file yet? You may have better luck typing Verizon's current apns in and can get data/sms working that way then just save your xml for a future swap in case you need it on another rom install on down the road. Unless im not aware of some new strange Verizon issue if you get your apns right then everything should work fine. And make sure your other settings in the roms settings/network's and internet/ are good and setup right..

Good stable rom here. Always like AICP.

Thanks for the ROM, I really like it, but I have a G7 Power with NFC, and the NFC doesn't work, do you know how to make it work? Thank you

Great Rom!?
Thanks for this hidden gem.
I was looking for a stable 10 rom for my power due to the Aosp extended rom had a few bugs later on after use.
1.Data stopped working
2.Unable to use swap.
But when I flashed this rom, I'm pleased to say this rom should be OFFICIAL!!
Only minor gripe., since gapps is pre-installed there was only 16mb of /system space.
I had to use root file browser to delete most of the Google apps in /system/product/app,,,and /system/product/priv-app.
That gave me 789mb of free space back.
Swap works, custom kernel very good, great battery life.
Thanks again O.P for this diamond in the rough!!

Saying thanks again for the ROMs for the g7power.
As of tomorrow I'll be the on the Moto G power thread.s.
Hope you guys get the new Moto g power as well and port some roms.
Love y'all stay safe guys..

I've installed AICP pie in my mido device! This is the best rom that I've got till date! But musicfx doesn't work more than half of the times! Though it does work sometimes. I'm using youtube music to stream music. Can somebody suggest me a solution for this?

Cant seem to pass safety net checks with this rom - specifically the ctsProfile is showing as False. SElinux is set to Permissive - should I try to change this? Anyone else have this issue?
PS - ROM itself is great! My favorite so far. If I can get safetynet to pass, I am keeping this one on here

timba123 said:
I used magisk module MagiskHide Props Config to edit fingerprint... it lists Motorola g7 power.
Click to expand...
Click to collapse
U use terminal emulator type su at prompt till I get # then I in su mode props hit enter then 1 enter then f enter then 15 enter then 15 wait till it's done then reboot

Thank you guys, got it working.
I am really impressed with this ROM! I have tried every single other rom for this device and none is on the same level as AICP (in my opinion). I'm really just shocked at how much smoother and clearly better it is over Stock especially. Thank you devs so much for this!!! Still testing but.....man, this is something else.

Seeing the responses from other users I really want to try out this ROM, my problem though are the Gapps..
- Do you think you would do a build without them?
- Is it possible or rather easy to remove them from the source and build it myself?
- Do you think it is enough to remove gapps installed in system- and priv-apps or are they going "deeper". I think I once read that also some apps are replaced on Gapps installation.
Thanks for your work!

I hope this is the right place for this, I couldn't find AICP for G7 power w/o GAPPS...
Thank you for a very, very well made rom. I have a Moto G7 Power xt-1955-5 and for months I tried several other roms, but either the sim card was not recognized, or everything worked except for the phone audio (I could make and receive calls but they couldn't hear me and I couldn't hear them).
When I flashed aicp_ocean_r-16.1-WEEKLY-20220604 I was really disappointed because I still had the phone call audio issue.
However, after the June 11 update, everything works!!!!!!!!
Did you do something specifically to fix it or is it just a happy coincidence?
Three more questions. How do I turn off the camera? Can I disable the camera swipe for selfie? If I load the Pixel camera (or whatever it's called) I assume it will send data to Google, correct?
Again, thanks for your work.

Can someone please explain to me the copypartitions.zip part of this procedure? I'm not exactly sure what I am supposed to flash or do there and I'm having a lot of trouble. I've got my phone rooted and whatnot I just have not been able to flash any custom roms because I'm confused about this part

Jake81345 said:
Can someone please explain to me the copypartitions.zip part of this procedure? I'm not exactly sure what I am supposed to flash or do there and I'm having a lot of trouble. I've got my phone rooted and whatnot I just have not been able to flash any custom roms because I'm confused about this part
Click to expand...
Click to collapse
I'm not expert, but AFAIK copypartitions makes sure that both partitions (A & B) have the same thing so that if something goes wrong when you flash A, there will be a backup on B.
Again, I'm no expert, but it worked for me.

[ROM][UNOFFICIAL]LineageOS-14.1 for deb/flo | Android 7.1.2 Nougat [MAY 2023]

{
"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"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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 me for messing up your device, I will laugh at you.
*/
What's working :
Everything that worked in last OFFICIAL build.
There are NO MODIFICATIONS at all. If something didn't work in the last official LineageOS release, it wont work in this build.
Instructions :
Download build and copy it to Internal Memory
Reboot to TWRP recovery
Create TWRP Backup (Recommended)
Flash the latest build (Clean Flash if coming from any other build)
Flash Magisk/LineageSU zip (Optional)
Flash GApps/MicroG (Optional)
Reboot
Downloads :
deb
Build: lineage-14.1-20230514-UNOFFICIAL-deb.zip
MD5: 534dff964ca9c44a8ab00e6a6d3883f9
flo
Build: lineage-14.1-20230514-UNOFFICIAL-flo.zip
MD5: 66a094b14a1f1531af1d195bf787a03b
TWRP
deb: twrp-3.4.0-0-deb.img
flo: twrp-3.4.0-0-flo.img
followmsi builds: TWRP-followmsi
Root Method:
Magisk: here
LineageOS su: here
Addon (GApps/MicroG):
GApps: BiTGApps (arm 7.1.2)
MicroG (Built via FriendlyNeighborhoodShane repo): MinMicroG.zip
Source Code: https://github.com/LineageOS
Proprietary Files: TheMuppets
Kernel Source: Here
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.0
Security Patch: May 2023
Created 2021-01-12
Last Updated 2023-05-14

Older Builds
Downloads:
AFH Google Nexus 7 (2013) Root Folder (Builds older than July 2022)
SourceForge - deb
SourceForge - flo

Thank you.

Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,

aurocha said:
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Click to expand...
Click to collapse
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.

aurocha said:
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
Click to expand...
Click to collapse
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
Os_A said:
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
Click to expand...
Click to collapse
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.

M4Master96 said:
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
Click to expand...
Click to collapse
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,

aurocha said:
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Click to expand...
Click to collapse
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel

M4Master96 said:
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
Yep, that's the kernel I'm running. Mainly because of DT2W. Loads of options when flashing because of the Aroma installer and easily manageable with exkm, which I bought some years ago.

M4Master96 said:
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!

plusminus_ said:
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
Click to expand...
Click to collapse
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)

this looks great - thank you - does it work with any of the Custom Kernels?

February 2021 Security Patches
deb
Build: lineage-14.1-20210208-UNOFFICIAL-deb.zip
MD5: 7ed9473d325d20b863d1516d902602d7
flo
Build: lineage-14.1-20210208-UNOFFICIAL-flo.zip
MD5: 9a6617aa7111b4c91daf310e7bf09183
Added links in first post

M4Master96 said:
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
Click to expand...
Click to collapse
Ah I suspected this, hmm
thanks

Thanks all you guys, was looking for a decent rom for this tablet, can't live without doubletap2wake and newer roms are just too heavy for this gadget, was looking for a decent rom for it, and I have finally find it

March 2021 Security Patches
deb
Build: lineage-14.1-20210309-UNOFFICIAL-deb.zip
MD5: 6d23b5115b073a6d9a85981cb6abac11
flo
Build: lineage-14.1-20210309-UNOFFICIAL-flo.zip
MD5: 39f1a8945af9870369ffdd1deefb5e4c
Updated links in first post

First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?

sundog1 said:
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
Click to expand...
Click to collapse
I create flashable microg zip via https://github.com/WeAreFairphone/flashable-zip_microG and then flash it along with ROM, magisk and kernel. Afterwards, I use SmaliPatcher Module to patch and enable SignatureSpoofing so that MicroG works.
I had also raised Merge Request in lineageos4microg so that We can build ROM with microg without syncing repository but my MR is still open and so, Not able to build that.

April 2021 Security Patches
deb
Build: lineage-14.1-20210409-UNOFFICIAL-deb.zip
MD5: 627ce7454888bc71aec2fea10e6023ce
flo
Build: lineage-14.1-20210409-UNOFFICIAL-flo.zip
MD5: 54ac5466ae8df749a6650ee1c7b28e82
Updated links in first post

aurocha said:
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
Click to expand...
Click to collapse
Hi,
May i know which 'official image' you restored and which version of twrp was used?
I flashed LOS 18.1 before and it work but seems lag. Then I tried to flash this ROM but faced the same problem, endless looping is the screen of upwards arc w/ circle (LOS logo?) running from right to left again and again.
Thank you!
Update: Well, i just follow the link provided by @JT1510365 in https://forum.xda-developers.com/t/...oted-unmodified-6-0-mra58v-flashable.3694735/ and download the stock rom, restore to 6.0, it boot normal. Then flash twrp & this rom and it work now.
Thank you for your share of the reinstallation of 'official image'.

[DISCONTINUED][ROM][PAYTON]LineageOS 18.1

Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org

Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.

ThE_MarD said:
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
Click to expand...
Click to collapse
For wifi display we can update wfd from caf
Seems works on other roms

Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast

ThE_MarD said:
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
Click to expand...
Click to collapse
Ahh that bad
Another question is offline charging works?

Offline charging works, but the animation is broken.
Edit: Is the selinux permessive?

@dhinesh_cool oh snap, offline charging animation is broken lol... We will have to check into that then.
@Sujanth the test builds I released are selinux enforcing. I did just try testing with permissive and it still failed, so the issue lies elsewhere... I'll try some stuff and see what we need to do to solve it

Ok. I played cod and scwitch to telelgram. Then I switch back to cod. But the game loads from the beginning. In other rom it doesn't happen. I think the ram management could be impoved.

Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not

Audio from front facing video is working?

ThE_MarD said:
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Click to expand...
Click to collapse
Offline charging is working now. Thanks.I am testing the other fixes and write then back.
Edit: Hotspot with WPA2 also works with 2,4 GHz band. But with 5.0gHz band i can't find the hotspot. Need any logs?
I did also a whatsapp call, no echo or mic problems.
But volume of the speaker is low. Can you fix it?
And radio FM doesn't work.
When I want to call somebody, the telephone screen is not coming, but you hear the call tone.

How to upgrade to this ROM from Lineage 17.1? Thanks.

Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive

Heyyo, a new test build is going up! As always it is in the first post and is uploading meow so it'll be about 30 minutes. lineage-18.1-20210211-UNOFFICIAL-payton contains some perf fixes so that cpufreq also properly scales up and down.

ThE_MarD said:
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Click to expand...
Click to collapse
I haven't installed any other phone apps. So i don't think I need to select it. Same bug also present in corvus a11.

Hi, first time using Lineage OS here. After sideloading LineageOS, i am just not able to install Gapps. Tried using MindtheGapps 11, tried sideloading, flashing, nothing happened. Either the phone starts to bootloop or it boots to recovery or it boots to Lineage OS without any google apps. Can someone please tell me where i am going wrong?
Edit: I realised i was flashing the wrong GApps, so i tried flashing ARM64 Android 10 nano pack. The screen gets stuck at the LOS boot logo before booting back to TWRP.
SOS

Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.

ThE_MarD said:
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
Click to expand...
Click to collapse
First i sideload the rom zip in slot A along with TWRP and then i reboot to the recovery to set the current slot to B and then flash GApps. On flashing it, there are no errors, but on booting up the system for the first time, i get redirected to TWRP. Is something wrong with my phone?
Till now i have been using ViperOS for quite some time, until i wanted to try something new. Really wanna give LOS a try.

@warhead1721972 , just to check since you're using TWRP, when you switched ROMs are you wiping Dalvik, cache, data and system?
Also, are you reinstalling TWRP after flashing LOS? Because if you are, you must use the TWRP installer zip and not flash the TWRP image as that kernel isn't compatible with the ROM.

Better Mobile App

welcome