Hello.
I am trying to install LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip
I followed the instructions from LineageOS (main) https://wiki.lineageos.org/devices/lemonadep/install
but, of course, using the LineageOS for Microg recovery lineage-19.1-20220607-microG-lemonadep-recovery.img and zip.
I installed the dtbo.img and vendor_boot.img from the latest LineageOS repo - https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220628/
All good - until I flash the zip in recovery.
The I get:
E: Current SPL: 2022-06-05 Target SPL: 2022-05-05 this is considered a downgrade
E: Denying OTA because it's a SPL downgrade
How can I remedy the SPL error and flash successfully LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip?
{
"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"
}
anarchotaoist said:
Hello.
I am trying to install LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip
I followed the instructions from LineageOS (main) https://wiki.lineageos.org/devices/lemonadep/install
but, of course, using the LineageOS for Microg recovery lineage-19.1-20220607-microG-lemonadep-recovery.img and zip.
I installed the dtbo.img and vendor_boot.img from the latest LineageOS repo - https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220628/
All good - until I flash the zip in recovery.
The I get:
E: Current SPL: 2022-06-05 Target SPL: 2022-05-05 this is considered a downgrade
E: Denying OTA because it's a SPL downgrade
How can I remedy the SPL error and flash successfully LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip?View attachment 5650677
Click to expand...
Click to collapse
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.
razercortex said:
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.
Click to expand...
Click to collapse
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!
anarchotaoist said:
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!
Click to expand...
Click to collapse
I recommend 0607 only because the build date is closer to the LOS+microG version you are trying to flash.
anarchotaoist said:
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!
Click to expand...
Click to collapse
I also double checked and the two builds I mentioned are indeed the earliest versions of LOS 19.1 for the OnePlus 9 Pro.
razercortex said:
I recommend 0607 only because the build date is closer to the LOS+microG version you are trying to flash.
Click to expand...
Click to collapse
Yes! I stupidly thought the LOS4microg build would have been based off the earliest LOS build - and it is, but that repo holds the 18 version also!
I see what you mean that it is the closest build now after checking https://download.lineageos.org/lemonadep
SOLUTION: The 0607 files did indeed fix the issue. LOS4microg now installed.
Having the same issue here, and the link :https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ is no longer available, tried looking for it in the WayBackMachine but they only stored the page not the file itself, guess because of its size, can't find it anywhere else, can anyone who downloaded it re-upload it again to solve the same issue @anarchotaoist ?
Waited for the MicroG team to update their builds, but they still did not.
Droid_Player said:
Having the same issue here, and the link :https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ is no longer available, tried looking for it in the WayBackMachine but they only stored the page not the file itself, guess because of its size, can't find it anywhere else, can anyone who downloaded it re-upload it again to solve the same issue @anarchotaoist ?
Waited for the MicroG team to update their builds, but they still did not.
Click to expand...
Click to collapse
You should use dtbo, vendor_boot and boot images latest from may
or you can dump the rom's payload.bin and use those already included in the rom
you can try crDrod or stagOs (they both suport sign-spoofing) with spare microG
razercortex said:
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.
Click to expand...
Click to collapse
Same problem, this solution worked
I went onto lineage downloads and grabbed the oldest files (about a month old) and since I had the newest microg image it accepted it.
I did older dtbo, vendor_boot, and recovery. idk if that is excactly what was required but since it covered everything in the lineage instructions I went that route and it worked. I later realized that microg has a specific recovery, but never used it because the aforementioned flow worked.
Psk.It said:
or you can dump the rom's payload.bin and use those already included in the rom
Click to expand...
Click to collapse
Circling back here again, because believe it or not, I ran it to this on an additional phone. My previous post is the easy way, find the right dates, if possible. If the microg files are older then the other method is to dump the payload, as quoted. For anyone like me, not knowing how to do that,
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
You're going to need to have python install, you need an update as per the instructions there, and there is one more problem, the requirements.txt needs to be modified because it will throw an error, follow the error message and you will get there, eventually. I did, but it was a headache. I hope this helps anyone who has run into this problem but is not familiar with payload dumper.
I just want to thank you @Psk.It for suggesting crDroid. It has been running on the One Plus 9 Pro pretty smoothly, and after 6 months it is just as snappy as it was in the beginning. Great helpful community in the Telegram group as well. Your reply was the reason I considered an alternative to LineageOS, as it was giving me many problems because of no support of spoofing, so again your comment is much appreciated along with all the all the community.
Related
{
"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"
}
For instructions about installing or building for toro, see the wiki: http://wiki.lineageos.org/toro_info.html.
Builds can be found at https://download.lineageos.org/toro.
Bugs:
- No data out of airplane mode; reboot to fix.
- Initiating a new sim may not work; install a kitkat or older ROM to initiate sim.
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico. Please note that only the pico version will fit, unless you have changed your partitions sizes.
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs, Ziyan
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-04-19
Last Updated 2017-03-25
After over a year and a half, we once again have official CyanogenMod builds.
Official builds have been bumped up to cm-13.0. A cm-12.1 snapshot is available on get.cm.
thanks much. going to wait for the august patches to get merged in before moving over from your previous unofficial build.
error (failed) flashing cm13
My Nexus (maguro) was bricked (my own fault).
I put back the original android 4.3 with fastboot. That went well. Now I want to put it cm13. It fails. Flashing with recovery ter 8.7.0 failed, also "fastboot -w update ....zip" went wrong "cannot load ...zip". Nexus is rooted.
Then I tried to flash a different zip namely Euphoria 5.1 for maguro. I used to flash the recovery. That went okay. But I prefer CyanogenMod.
So now I real want to flash the latest cm13, but I can not. I get a failed.
Also fastboot -w update "cm13....zip" does not work.
What am I doing wrong?
greeting Lucas
lucascaw said:
My Nexus (maguro) was bricked (my own fault).
I put back the original android 4.3 with fastboot. That went well. Now I want to put it cm13. It fails. Flashing with recovery ter 8.7.0 failed, also "fastboot -w update ....zip" went wrong "cannot load ...zip". Nexus is rooted.
Then I tried to flash a different zip namely Euphoria 5.1 for maguro. I used to flash the recovery. That went okay. But I prefer CyanogenMod.
So now I real want to flash the latest cm13, but I can not. I get a failed.
Also fastboot -w update "cm13....zip" does not work.
What am I doing wrong?
greeting Lucas
Click to expand...
Click to collapse
Are you trying to flash this TORO build to your MAGURO device?
That may be your first problem.
phonetool said:
Are you trying to flash this TORO build to your MAGURO device?
That may be your first problem.
Click to expand...
Click to collapse
I do not think so.
I tried cm-13.0-20160731-NIGHTLY-maguro.zip and other dates. that's maguro and not toro, I think, I hope.
greeting Lucas
lucascaw said:
I do not think so.
I tried cm-13.0-20160731-NIGHTLY-maguro.zip and other dates. that's maguro and not toro, I think, I hope.
greeting Lucas
Click to expand...
Click to collapse
Yes, that is for maguro. This is the toro thread, though. The maguro thread is here.
My first guess is that your recovery is too old to flash cm13.0 Try this build of TWRP.
musical_chairs said:
Yes, that is for maguro. This is the toro thread, though. The maguro thread is here.
My first guess is that your recovery is too old to flash cm13.0 Try this build of TWRP.
Click to expand...
Click to collapse
Thank You, I'll try.
Lucas
Would the latest nightly (08/06) include the full August security patches outlined in https://source.android.com/security/bulletin/2016-08-01.html ?
AceNJ said:
Would the latest nightly (08/06) include the full August security patches outlined in https://source.android.com/security/bulletin/2016-08-01.html ?
Click to expand...
Click to collapse
Yes, it should, the patches were merged several days ago.
musical_chairs said:
Yes, it should, the patches were merged several days ago.
Click to expand...
Click to collapse
thanks for confirming. i've been wanting to do a clean reflash so if this has all the patches as of 08-05 then it's a good time
I am having occasional WiFi drops. Always happens with screen off. Wake up the screen and WiFi is off and no data. I read recently of a similar problem on the Galaxy Note Pro forum and some believe it to be a CM glitch.
http://forum.xda-developers.com/showthread.php?p=68754215
Anybody else having this problem?
My wifi does drop very frequently, even during use. In-fact I really only notice it while using the phone. Interestingly for me, I don't think it's a ROM specific issue but can't really confirm it. Even more odd is that I NEVER drop when connected to an iPhone hot spot, it's only when connecting to actual wifi routers. I thought it might be band based but I struggle with both 2.4 and 5ghz. I just kind of have learned to live with it at this point; spent way too many hours trying to resolve.
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
eric2112 said:
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
Click to expand...
Click to collapse
Things keep growing and nano gapps no longer fit either. You need to use the pico gapps. I corrected the instructions in the OP.
Thank you.
If any users on Page Plus (and maybe Straight Talk) have lost mobile data, here is a flashable zip that should fix it. Do not flash this if you're on Verizon, and do not flash it if your data is currently working. This fix should work on pretty much any ROM KitKat or newer.
Page Plus has made some changes to their APNs and it breaks data for us. Stock ROMs should be able to load the updated settings themselves, but that doesn't seem to work for this ROM. It's a minor change really; the APN needs to change from VZWINTERNET to TRACFONE.VZWENTP for data to work.
eric2112 said:
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
Click to expand...
Click to collapse
There is a note on the very first page of this thread (and in the CM wiki) that the NANO GApps (especially the Open sort) may well be too big - heed it! I used the pico Open GApps without trouble on my own GNex (inherited from my mom as she moved to a Galaxy J3; I'm taking the GNex to Tracfone once I get a SIM kit - replacing an existing Tracfone feature phone). In a word - smirk, smirk, smirk....
will there be no further development on this in 2017?
{
"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 a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
To flash this rom you need TWRP 3.2.0-0 or newer. https://twrp.me/huawei/huaweinexus6p.html
Make sure you have the radio & bootloader img's installed from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
radio & bootloader img's: https://androidfilehost.com/?w=files&flid=286833
Those img's can be flashed with fastboot command.
Note: There's an issue happening to some angler users on custom oreo roms. The first boot after flashing rom your sim card might not be detected. It's easy to fix. Just go to lockscreen security settings and change it to 'none' and then reboot. Then you can change it back to whatever you want. This only happens one time when you first flash oreo.
Download Links
rom: https://download.lineageos.org/angler
Note: LineageOS servers no longer make 15.1 builds for any devices. You can use my unofficial builds here. My older builds are here.
Note#2: if you want to switch from an official build to my unofficial builds, follow instructions here.
google apps (optional): https://wiki.lineageos.org/gapps.html (Use arm64 / 8.1)
root su addon (optional): https://download.lineageos.org/extras Note: Use arm64 15.1 zip. After installing the su addon, you can enable root in developer options.
Instructions
If updating from old unofficial to newer unofficial, follow the steps below:
1. if you don't already have them installed, flash the newest radio and bootloader img's linked above.
2. boot into twrp and flash the rom zip.
Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
NOTE2: if you want to switch from an official build to my unofficial builds, follow instructions here.
If coming from a different rom:
1. if you don't already have them installed, flash the newest radio & bootloader img's linked above. also make sure you have the newest twrp, linked above.
2. boot into twrp and wipe system & data & cache.
3. flash rom & gapps & su addon zips (gapps & su zips are optional).
Reboot & enjoy.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://download.lineageos.org/extras
Grab the one for version 16.0. It also works with 15.1.
Note: You'll need an api key from OpenWeather.
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
LineageOS device maintainers:
sam3000, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_huawei_angler/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_huawei_angler/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_huawei/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.10.73
Wooh! First!
Sent from my Nexus 6P using XDA Labs
Hey Razor. I used to be on your builds a couple of years ago in the old hammerhead and looking forward to flash your work again when 15.1 is out, this time on angler. Cheers! :fingers-crossed:
Any bugs? Is it suitable for daily driver? Just tired to wait for official build and want to flash as fast as possible. )
Thanks Razorl!!!!!
Error 7 -- make sure to flash the new twrp recovery if you face this issue!!
i42o said:
ERROR 7
Click to expand...
Click to collapse
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
razorloves said:
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
Click to expand...
Click to collapse
haha. Yeah my bad bro, my bad. got it tho, thanks!
Says no SIM card
Clean flash following instructions, TWRP 3.2, latest bootloader/radio/vendor, flashed vendor -> rom -> gapps. Otherwise no errors.
Any suggestions?
telefantastik said:
Says no SIM card
Click to expand...
Click to collapse
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
It's weird though. I have unlock protection and got no issue when flashing this.
Can it also be related to your carrier or something?
ChemoNL said:
I have unlock protection and got no issue
Click to expand...
Click to collapse
Its not just caused by unlock protection. I posted details on the issue in my 14.1 thread about a month ago.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
Awesome, it worked! Thanks
For those interested...
Another new version of twrp came out yesterday. 3.2.1-0
Here's the changelog for it https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
You can download it here: https://twrp.me/huawei/huaweinexus6p.html
Here's the changelog for 3.2.0-0 that came out last week, incase you missed it.
https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html
Thank you for new thread and ROM.
:fingers-crossed::fingers-crossed::fingers-crossed:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
domacikolaci said:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
Click to expand...
Click to collapse
Hi, once a month you need to flash the new vendor for security updates
Google release them once a month (usually the first tuesday of the month)
However when you flash an update that does not require new vendor, you don't need to flash it
edit: just realised you're also from Melbourne, hi
Just have installed the last unofficial in my Angler, coming from another custom rom ( with Nougat). All good. Plan to stay here. Thanks !
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Apoena said:
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Click to expand...
Click to collapse
Have you been living under a rock for the past year? Lol jk. But see here http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
tldr; blame Google and Huawei. And get yourself a free replacement or free upgrade.
http://www.androidpolice.com/2017/0...exus-6p-owners-pixel-xl-warranty-replacement/
{
"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 a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
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
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. 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 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 and reboot of flash to TWRP
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 LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list
{
"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"
}
Google Pixel 3a
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a .
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
sargo - Official builds
sargo - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
I was able to successfully download the unoffical and able to get the rom running. I could not get mindthegapps to stick though...Error 1 I think (not enough space). I tried another gapps packet to no avail. Not sure of the issue so I'm just putting this out out there for others.
mmead1143 said:
I was able to successfully download the unoffical and able to get the rom running. I could not get mindthegapps to stick though...Error 1 I think (not enough space). I tried another gapps packet to no avail. Not sure of the issue so I'm just putting this out out there for others.
Click to expand...
Click to collapse
Because the unofficial includes GApps - and a lot of them at that - look at the OP note
npjohnson said:
Because the unofficial includes GApps - and a lot of them at that - look at the OP note
Click to expand...
Click to collapse
Well I feel like an idiot haha! Okay I'll give it another go Thanks a ton!
Okay so I'm up and running on the Unofficial haha! Thanks for the help above. Install was quick and easy...not sure what I missed yesterday but it was the same downloaded file so I nixed something up.
I was getting this "android system intelligence keeps stopping" while on the rom for the first hour - as I added all my normal apps to the phone, it went away. Not sure why - don't care now Everything seems to work but I'll keep you in the loop.
Stupid question: from 18.1 to 19.1, do i need to flash the A12 mindthegapps package too?
I am currently running LOS 18.1 with the A11 version of mindthegapps package....
Fentadroid said:
Stupid question: from 18.1 to 19.1, do i need to flash the A12 mindthegapps package too?
I am currently running LOS 18.1 with the A11 version of mindthegapps package....
Click to expand...
Click to collapse
If you download the unoffical rom...it comes with gapps included with it.
Not sure about the official rom.
I installed it, and seems to be working really well. Here are some pictures, for anyone who wants to see.
Fentadroid said:
Stupid question: from 18.1 to 19.1, do i need to flash the A12 mindthegapps package too?
I am currently running LOS 18.1 with the A11 version of mindthegapps package....
Click to expand...
Click to collapse
I just installed the official one today. You do have to install MindTheGapps on it, even if you had it on 18.1. it also has to be installed right after you sideload the Lineage OS installation zip file, before you boot to android.
mmead1143 said:
Okay so I'm up and running on the Unofficial haha! Thanks for the help above. Install was quick and easy...not sure what I missed yesterday but it was the same downloaded file so I nixed something up.
I was getting this "android system intelligence keeps stopping" while on the rom for the first hour - as I added all my normal apps to the phone, it went away. Not sure why - don't care now Everything seems to work but I'll keep you in the loop.
Click to expand...
Click to collapse
its out of date, next build will have it fixed.
Apart from a few A11 to 12 things I'll get used to (personal nitpicks, lol) everything's running well. I do miss the old 18.1 blue accent, are there plans to add other color accents to the ROM itself? Currently I'm using tulsadiver's color mod. Either way, thank you for helping keep our devices alive.
Mokura3rd said:
Apart from a few A11 to 12 things I'll get used to (personal nitpicks, lol) everything's running well. I do miss the old 18.1 blue accent, are there plans to add other color accents to the ROM itself? Currently I'm using tulsadiver's color mod. Either way, thank you for helping keep our devices alive.
Click to expand...
Click to collapse
I can confirm. The update went well and everything is working fine. Well done.
Same here - both the unofficial and official work flawlessly. I've gone back n forth haha!
Mokura3rd said:
Apart from a few A11 to 12 things I'll get used to (personal nitpicks, lol) everything's running well. I do miss the old 18.1 blue accent, are there plans to add other color accents to the ROM itself? Currently I'm using tulsadiver's color mod. Either way, thank you for helping keep our devices alive.
Click to expand...
Click to collapse
On officials, no, it's all monet.
On unofficial, hold Home Screen down, select "wallpaper and styles", then pick a color!
Upgraded from LOS 18.1 to 19.1 and flashed mindthegapps12 and magisk. Everything seems to work fine until I tried making bluetooth call. My favorite bluetooth earpiece is extremely quiet. But another one works just fine. Looked in dev options and saw that all codecs are greyed out. Can anyone confirm this is happening on a clean install?
batp said:
Upgraded from LOS 18.1 to 19.1 and flashed mindthegapps12 and magisk. Everything seems to work fine until I tried making bluetooth call. My favorite bluetooth earpiece is extremely quiet. But another one works just fine. Looked in dev options and saw that all codecs are greyed out. Can anyone confirm this is happening on a clean install?
View attachment 5601803
Click to expand...
Click to collapse
Not here - Clean install and all my blu tooth devices are working properly. GL
Just to be sure, if I'm currently running the official LOS 18 builds with MindtheGapps, all I need to do is flash official LOS 19 and MindtheGapps again, and that's it? No need to flash firmware or anything? And it won't wipe user data?
Also, any chance the rounded corners got fixed in LOS 19?
Don't need any changes on firmware side to flash Lineage 19.1? Slot a is on april patch, slot b on mai patch. That can keep, right?
Thanks for bringing up LineageOS 19 officially @npjohnson and keeping the Pixel 3a alive after google's decision to drop it after this May! I searched a lot but I couldn't find a good answer: is it possible to relock the bootloader after the installation? Is LineageOS (enough) signed to pass the boot procedure?
indrekh said:
Just to be sure, if I'm currently running the official LOS 18 builds with MindtheGapps, all I need to do is flash official LOS 19 and MindtheGapps again, and that's it? No need to flash firmware or anything? And it won't wipe user data?
...
Click to expand...
Click to collapse
All Yes
{
"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"
}
Google Pixel 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.[/CENTER]
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
walleye - Official builds
walleye - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
hi Downloads: link no20,only 19.1
github-wang said:
hi Downloads: link no20,only 19.1
Click to expand...
Click to collapse
yup, minor issues, rebuilding tonight
Thank you for keeping my old device up to date.
The recovery image does not seem to work. Flashes fine onto the device. Fastboot output:
Code:
target reported max download size of 536870912 bytes
sending 'boot_b' (32768 KB)...
OKAY [ 0.091s]
writing 'boot_b'...
OKAY [ 0.161s]
finished. total time: 0.253s
But when I reboot the device, it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.
lineage-20.0-20221109-recovery-walleye,the boot damage ,But when I reboot the recovery， it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.
try booting into the recovery rather than flashing. same issue on PE13 just booting into it worked out fine
DrupadSachania said:
try booting into the recovery rather than flashing. same issue on PE13 just booting into it worked out fine
Click to expand...
Click to collapse
good i try thanks
Hi @npjohnson , I've just downloaded your latest build for lineageos 20.
I'm getting the same Error BootLinux error.
When i follow the guide, it won't allow me to boot into the latest '....20' recovery.
Thankyou for all your work.
I even tried installing your latest 19.1 and following the upgrade guide. ADB reboot sideload, adb sideload package ....20.
I had the error about downgrading, but after installation, same error at bootloader
Hawkeye77 said:
Hi @npjohnson , I've just downloaded your latest build for lineageos 20.
I'm getting the same Error BootLinux error.
When i follow the guide, it won't allow me to boot into the latest '....20' recovery.
Thankyou for all your work.
I even tried installing your latest 19.1 and following the upgrade guide. ADB reboot sideload, adb sideload package ....20.
I had the error about downgrading, but after installation, same error at bootloader
Click to expand...
Click to collapse
Working on it, should be an easy fix.
taimen works fine
Thankyou @npjohnson , just installed the Latest unofficial LOS 20 13th.
It ran faultless.
You are a magician.
Edit: only thing I've found so far is it's not passing safety net. Play store is not certified and wallet won't allow bank card.
Will this, or can this be fixed in future updates? Or do you suggest the Magisk route?
Hawkeye77 said:
Thankyou @npjohnson , just installed the Latest unofficial LOS 20 13th.
It ran faultless.
You are a magician.
Edit: only thing I've found so far is it's not passing safety net. Play store is not certified and wallet won't allow bank card.
Will this, or can this be fixed in future updates? Or do you suggest the Magisk route?
Click to expand...
Click to collapse
Aware, this build as "Get it out there for feedback" the next several will tune all that stuff.
Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.
tblr0ne said:
Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.
Click to expand...
Click to collapse
It's published. Download newest.
npjohnson said:
It's published. Download newest.
Click to expand...
Click to collapse
I meant the code, so that Magisk could be fixed as well.
tblr0ne said:
I meant the code, so that Magisk could be fixed as well.
Click to expand...
Click to collapse
it's not code, I included too many things lol - our boot image is too small.
npjohnson said:
it's not code, I included too many things lol - our boot image is too small.
Click to expand...
Click to collapse
Hm, do you see a possibility on your side to get root working? That would be great.
(Magisk installs fine, but afterwards there is this "bad buffer size" boot error again.)
tblr0ne said:
Hm, do you see a possibility on your side to get root working? That would be great.
(Magisk installs fine, but afterwards there is this "bad buffer size" boot error again.)
Click to expand...
Click to collapse
Likely no. I can look.
tblr0ne said:
非常感谢 @npjohnson 继续使用这台旧设备进行工作。
您能否分享您对这个“缓冲区大小错误”引导错误的更改。Magisk 也有同样的问题。谢谢。
Click to expand...
Click to collapse
tblr0ne said:
I meant the code, so that Magisk could be fixed as well.
Click to expand...
Click to collapse
tblr0ne said:
Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.
Click to expand...
Click to collapse
Hello, you can try this, with magisk can be rooted，i use it on lineages os 20-11.13 ，can boot ，it for tg groups
Google Pixel 2/XL | Chat，Of course, I still hope that sir can fix it
Thanks, but since LOS is shipping with its own recovery this might lead to update issues.
And more important, please don't be offended, I won't recommend installing (pre-rooted) images from untrusted sources!
tblr0ne said:
Thanks, but since LOS is shipping with its own recovery this might lead to update issues.
And more important, please don't be offended, I won't recommend installing (pre-rooted) images from untrusted sources!
Click to expand...
Click to collapse
yes,I still hope that sir can fix it