Jump to content

LineageOS 20.0 Official Release for Pro1


Recommended Posts

10 hours ago, claude0001 said:

The official LineageOS tool to extract them is extract.py, but there are others ...

FYI, some Linux distributions (like Debian Bullseye) name the prerequisite package  "python3-protobuf", and you may need to set "PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python" to get the script to work.

  • Thanks 2
Link to post
Share on other sites
  • Replies 61
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This is where that second hexadecimal number in each keymap rule is useful. It allows you to specify an alternate Linux event code plus any combination of Shift, Alt, AltGr, Ctrl, or Fn. F(x)tec moved

Split the above from the 19.1 thread Link for rom: https://download.lineageos.org/pro1 Just attempted a dirty flash from Lin 19.1 MTG12 to 20.0 MTG 13 arm64 (Android security update 2022-12-0

There is another layer, the .kcm file. For Scandic models of the Pro1-X I made this key character map:  https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1x/+/348323/5/AsantiKeypad/

Posted Images

5 hours ago, Sean McCreary said:

you may need to set "PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python"

Seemed to work without this on my Bullseye. Thanks anyway for the hint.

Link to post
Share on other sites
12 hours ago, EskeRahn said:

So not that easy to extract after all

Well, it is really easy for those who have a lineage build environment up and running anyway. Extracting some previous payload.bin is a required step in making your own ROM.

For those who are not running on Linux (and thus have no preinstalled Python), people have made stand-alone extractor programs (like this one or that one). Please note that I haven't tested those, and think twice before running your phone's boot partition through some random tool from the internet.

  • Thanks 1
Link to post
Share on other sites

 

3 hours ago, claude0001 said:

Well, it is really easy for those who have a lineage build environment up and running anyway.

But I think the point for us "civilians" is we don't have to extract those files because those files are provided.  😄   If you are flashing for the first time, you need to fastboot flash those files in order to be able to boot into Lineage recovery so you can sideload the zip (which, yes, also contains those files).  Used to get it as one image file which also was labeled with the date.  But you only have to flash those files once so you have access to recovery for ADB sideload.  After that, you only do ADB sideload or use OTA (when official).

  • Like 1
Link to post
Share on other sites
3 hours ago, Hook said:

After that, you only do ADB sideload or use OTA (when official).

Yes, normal users need to fastboot-flash the boot.img only once, and can then sideload-away for years to come.  

But I believe @EskeRahn specifically wants to backup previous Lineage versions, to be able to jump back to them in case regressions were to be introduced in the OTAs. In such a scenario, he would indeed have to first flash the boot.img matching the timestamp of the *.zip. This is because, to my knowledge, Lineage recovery does not allow downgrading itself via sideload (at least in 16.0 it didn't).

So my only point was that it is not necessary for him to figure out a scheme to keep track of all his boot.img-versions. If needed, he could always extract the right one from the *.zip itself, which -- I think -- is an acceptable inconvenience in such an advanced use-case.

Edited by claude0001
  • Thanks 1
Link to post
Share on other sites
6 hours ago, claude0001 said:

Yes, normal users need to fastboot-flash the boot.img only once, and can then sideload-away for years to come.

As can be seen even on the hash of the last four, the boot.img is not identical, and I know from AICP, that a flash can be quite picky on the bootloader selected matching the zip.

So at the least when changing major version, I think you should flash the boot-loader first. For LOS I always flash the matching bootloader before booting into the recovery and sideloading the main zip.

It might be a superfluous step in general. but I believe @tdm did the same thing in the guide he originally provided for v16, so I just followed that since...

  • Like 1
Link to post
Share on other sites
28 minutes ago, EskeRahn said:

As can be seen even on the hash of the last four, the boot.img is not identical [...]

Well, as the timestamp updates, I do not see how the hash could stay identical, even if there are no functional changes. That said, there probably is a reason why LOS recovery does not allow downgrading via sideload ...

Link to post
Share on other sites
13 minutes ago, claude0001 said:

Well, as the timestamp updates, I do not see how the hash could stay identical, even if there are no functional changes. That said, there probably is a reason why LOS recovery does not allow downgrading via sideload ...

When I have experimented with downgrading a good while back, and  it works fine - though you will (almost) always need to wipe the user data in the process, and I always flashed the boot image as well.

Link to post
Share on other sites

(lineage-20.0-20230313-nightly-pro1-signed.zip on February 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Terms