[ROM][OFFICIAL][sunfish] LineageOS 18.1

Search This thread

Lada333

Senior Member
Feb 7, 2016
1,251
400
22
Budapest
OnePlus 3T
Google Pixel 4a
I hope it's ok to ask here...
I'm planning to upgrade to LOS19. I was going to try the instructions here:
https://wiki.lineageos.org/devices/sunfish/upgrade
Has anyone done this?
I have a question about this:
"Run adb sideload /path/to/zip (inserting the path to your LineageOS package)."
If I run that command, will it also update my recovery?
When I've done a "clean install", I flashed the recovery img file to boot partition first.
Will the recovery be updated when I run the "adb sideload LOS19.zip" command?

Thanks for your time.

I'm not 100% sure on this, but I think boot.img contains the recovery as well?
I think you can also just reboot to bootloader, use "fastboot flash --slot all boot boot.img", then reboot to recovery, go to Apply update -> Apply via adb, then use the adb sideload command.

(Keep in mind though that I've never installed LOS on my 4a, but the above mentioned install path has worked for me on several custom ROMs)
 
  • Like
Reactions: mangokm40

mangokm40

Senior Member
Jan 13, 2019
162
89
Just sideload via adb and look at the messages. It will patch the img.

And you have to do it just once. When getting an OTA it will reinstall Magisk for you.
Thanks for this.
Since someone always does, I will remind us that this method is no longer supported.
You can see the install instructions here.
Of course, when I've needed Magisk, I've done it as you describe. :)
 

Lada333

Senior Member
Feb 7, 2016
1,251
400
22
Budapest
OnePlus 3T
Google Pixel 4a
Just sideload via adb and look at the messages. It will patch the img.

And you have to do it just once. When getting an OTA it will reinstall Magisk for you.

Since I use custom ROMs, I'll have to patch the boot.img of whatever ROM I'm planning on flashing, and then if the ROM has an updater, the patched boot image will save me the hassle of having to manually sideload Magisk?
 

mangokm40

Senior Member
Jan 13, 2019
162
89
I'd like to thank @fbievan for providing log information for the VVM error.

I'd like to thank @razorloves for working on a fix. Razorloves has already provided the work to the Android project. Let's hope all goes well. All of razorloves' work is greatly appreciated. :)

Razorloves was kind enough to let me try the fix on my phone. Since it's working for me, I asked if I could share it here. I thought others who have stayed on LOS18 might want it.

NOTE: I updated to the Apr 14 2022 build of LOS18.1 before trying the Dialer.apk. This was so we could see VVM work on Mar 10 build, then fail on Apr 14 build, then work after updating Dialer.apk.

I've attached "Dialer.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.

To try this fix....

Enable USB debugging in your phone.
Enable ADB root in your phone.
Use these adb commands....
'adb root'
'adb remount'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is from 2008
'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is now from 2022

reboot your phone.



If you find their work useful, don't forget to support all their work. :)
https://paypal.me/LineageOS
https://patreon.com/LineageOS
 

Attachments

  • Dialer.zip
    6.4 MB · Views: 12
  • Like
Reactions: fbievan

icantlogin

Senior Member
Aug 23, 2017
58
31
Anyone planning on building this ROM themselves, now lineageos.org has moved to 19.1? I don't care much for Android 12 myself, I plan on staying on 11 for now. I've build LineageOS in the past for another device, I might give it a go again.

If I build it myself and want to share it, would I post it in this thread or create a new one? It wouldn't be an official build anymore, would it?

Anyone else planning on staying on LineageOS 18.1?
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,375
6,332
Sydney
Anyone planning on building this ROM themselves, now lineageos.org has moved to 19.1? I don't care much for Android 12 myself, I plan on staying on 11 for now. I've build LineageOS in the past for another device, I might give it a go again.

If I build it myself and want to share it, would I post it in this thread or create a new one? It wouldn't be an official build anymore, would it?

Anyone else planning on staying on LineageOS 18.1?
The thread title would be in opposition to your build, so you would definitely need to start a new thread. Also, most important details and links to new builds are posted in the OP, which you would not be able to edit unless its your own thread. And its just respectful to the orig dev.

I dont use LOS on this device or plan to. I am tempted to stick with A11. I am still running the stock A11, I too have built multiple ROMs for my previous devices (oreo being the last), but am hesitant at building for this device in case there are any "gotcha's" after spending hours building the env/source etc. I would be interested in following how you go (y) . I havent seen too many details published for building ROMs for this device. Actually, I just realised I have not checked LOS web site, previously they had pretty thorough steps details on building their ROMs for official devices.
 
  • Like
Reactions: kkjb

mangokm40

Senior Member
Jan 13, 2019
162
89
Updating to LOS19...Signature verification failed

I tried to update from LOS18 (04-14 build) to LOS19 by following directions here:
I got a long list of errors about reading certain bytes.
Then it said signature verification failed.

I was wondering if anyone could shed some light on the problem. Thanks.


These are the steps I took:

.Downloaded lineage-19.1-20220602-nightly-sunfish-signed.zip &
lineage-19.1-20220602-nightly-sunfish-signed.zip.sha256
from https://download.lineageos.org/sunfish

."sha256sum -c lineage-19.1-20220602-nightly-sunfish-signed.zip.sha256"
--It passed with "OK"

.Plugged phone to PC

.Enabled USB debugging in Settings->System->Developer Options

."adb devices"
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0445199C201DEW unauthorized
--On the phone, clicked on popup to authorize.

."adb devices"
List of devices attached
0445199C201DEW device

."adb reboot sideload"
--My phone rebooted to LOS recovery, ready to sideload.

."adb sideload lineage-19.1-20220602-nightly-sunfish-signed.zip"
--Phone gave many errors and then said
signature verification failed. Install anyway?
I said 'no'
 

mangokm40

Senior Member
Jan 13, 2019
162
89
Updating to LOS19...Success!

Hmmmm...
I ran through the process again. This time....


."adb sideload lineage-19.1-20220602-nightly-sunfish-signed.zip"
Supported API 3
Finding update package...
Verifying update package...
Update package verification took 50,5 s (result 0)
Installing update...
Step 1/2
Step 2/2

Install from ADB complete (status: 0).


.On phone, I clicked "Reboot system now"
--Phone rebooted in about a minute.
--VVM works on LOS19. (y)
 

Lada333

Senior Member
Feb 7, 2016
1,251
400
22
Budapest
OnePlus 3T
Google Pixel 4a
what did you do differently?
I remember reading it in some other thread that this "signature verification failed" can safely be ignored as long as you know what you're doing. ie: you have downloaded the correct ROM for your device, from a trusted site. Since he said that the checksum checked out (pun intended), there isn't any reason to care about the signature verification.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,375
6,332
Sydney
I remember reading it in some other thread that this "signature verification failed" can safely be ignored as long as you know what you're doing. ie: you have downloaded the correct ROM for your device, from a trusted site. Since he said that the checksum checked out (pun intended), there isn't any reason to care about the signature verification.
Yeah, I read that also, and I think you even commented once on how I said that I read that exact thing.

However, @mangokm40 actually may of detailed how to correct that in his previous post (y)
That is the first time I have seen how to do it (havent tested it yet), and i had searched the internet, and it now seems so damn obvious.:geek:

Connect the phone via USB and click the authorise on the screen. I always use adb over WiFI, which obviously is a different authorisation, and it always came up as unauthorised when I went into recovery, where there is no UI to click on an authorise pop-up.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    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. LineageOS does still include various proprietary hardware-specific code.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Notes
    • Before the initial installation, please make sure your Pixel 4a has already been updated to Android 11 official firmware so that the recovery can function correctly.
    • This ROM comes with latest firmware bundled, so after the initial flash you don't need to worry about updating firmware manually.
    • This ROM comes with source-built kernel and modules
    • eSIM functions without GAPPS, but to manage (add / erase) eSIMs you will need to have GAPPS installed
    Installation
    • Update your Pixel 4a to official Android 11
    • Download the latest boot.img and rom zip
    • Boot to bootloader
    • fastboot flash boot boot.img
    • Boot to recovery
    • Format data
    • Flash LineageOS zip
    • Optionally flash any addons:
      • Advanced > Reboot to recovery
      • Flash the addons
    • Reboot
    Updating
    • Boot to recovery
    • Flash LineageOS zip
    • Flash the same addons you had previously installed:
      • Advanced > Reboot to recovery
      • Flash the addons
    • Reboot
    Downloads

    Official: https://download.lineageos.org/sunfish

    Reporting bugs
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/* (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.

    Known Issues
    • On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
    Source Code

    6
    4a LineageOS 18.1 Update 2021-11-18 - Security Bump

    Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 18.1 sunfish build 2021-10-14 + lineage-18.1-20211014-recovery-sunfish to build 2021-11-18. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly.

    There are a bunch of changes as you can see here: https://download.lineageos.org/sunfish/changes/

    After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "November 5, 2021".
    The Vendor security patch level (just below) is now "October 1, 2021".
    The Build number at the bottom is "RQ3A.211001.001 10036888".
    This appears to be the last Vendor security patch for Android 11. The 1105 firmware is for Android 12.

    See Android Security Bulletin - November 2021 for details about the security fixes.

    I rebooted to recovery to verify that it was also updated. It now shows version "20211118" and active slot 'b'.

    Thank you to the Lineage Team, PeterCxy & cdesai for their work.
    6
    please tell us what method worked for you

    please tell us what method worked for you!
    1. extract the boot from LOS payload.bin
    2. install Magisk 22 by patching the extracted boot image
    3. hide the magisk from: google play store, play services, gpay, clear data for all these apps.
    4. install magisk module safetynet-fix-v1.1.1.zip
    5. reboot
    4
    There is no hope, the quality of the asocial media is as bad as with stock ROM.
    4
    4a LineageOS 18.1 Update 2021-05-13 - Security Bump

    Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 18.1 sunfish build 2021-05-06 + Magisk 23.0 + lineage-18.1-20210506-recovery-sunfish to build 2021-05-13. Everything went smoothly & Magisk survived the update.

    There are a bunch of changes as you can see here: https://download.lineageos.org/sunfish/changes/

    After the reboot, I went to Settings->About phone->"Android version" (see screenshots). The "Android security update" shows "May 5, 2021".
    The Vendor security patch level just below it is now "May 5, 2021".
    The Build number at the bottom changed from "RQ2A.210405.005" to "RQ2A.210505.003".

    See Android Security Bulletin - May 2021 for details about the security fixes.

    I rebooted to recovery to verify that it was also updated. It now shows version "2021-05-13" and slot 'a'.

    Thank you to the Lineage Team, @PeterCxy & @cdesai for their work.


    In a poor man's homage to @curiousrom, I have used his postings as a template for mine.
    They have been very helpful with my daily driver (S5) for a loooong time. :geek: