6
[OFFICIAL][ROM][PAYTON]LineageOS 19.1 (Android 12.1)
source link: https://forum.xda-developers.com/t/official-rom-payton-lineageos-19-1-android-12-1.4432955/page-4#post-86984693
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
[OFFICIAL][ROM][PAYTON]LineageOS 19.1 (Android 12.1)
Knuxyl
Senior Member
May 20, 2009
Google Pixel 5
TWRP isnt supported by los., so if u have problems, ur on ur own.
los recovery works just fine. ive never had an issue with across many devices, but ive had a ton with twrp
los recovery works just fine. ive never had an issue with across many devices, but ive had a ton with twrp
Reactions: kcv_earner
I wasn't looking for this but happened across it and thought it worth bringing up since it mentions _b:
I have to wonder now if TWRP is or isn't the way to go in general despite the official instructions, since that answer seems pretty definitive, though this was in the 18.1 era and maybe something pertaining to this has changed since.
I followed these instructions from LOS 19.1 >> https://wiki.lineageos.org/devices/payton/install
I found no mention of TWRP in there. I just used the recovery image "lineage-19.1-20220524-recovery-payton.img" found here: >> https://download.lineageos.org/payton. So far I have no problems with this ROM.
OK, good to know, though isn't that the TWRP installer that not supported, as opposed to just using it once to get off stock? That's what the first post in this thread suggests anyway. If someone does encounter the problem mentioned at the Reddit link when they're trying to get off stock, at least the TWRP option is there, since in that situation the normal way is a roadblock. This may go back to the problem described a few days ago on this thread: differences in partitions (not everyone is starting in exactly the same place, so people can have different results even when using the same methods).TWRP isnt supported by los., so if u have problems, ur on ur own.
los recovery works just fine. ive never had an issue with across many devices, but ive had a ton with twrp
Knuxyl
Senior Member
May 20, 2009
Google Pixel 5
OK, good to know, though isn't that the TWRP installer that not supported, as opposed to just using it once to get off stock? That's what the first post in this thread suggests anyway. If someone does encounter the problem mentioned at the Reddit link when they're trying to get off stock, at least the TWRP option is there, since in that situation the normal way is a roadblock. This may go back to the problem described a few days ago on this thread: differences in partitions (not everyone is starting in exactly the same place, so people can have different results even when using the same methods).
which is why it is best to update to the latest stock before using lineage. twpr hasnt been recommwndwd for a while
Hi, at first, my stock camera app can't save to an external SD card. The secound issue i've found is in the Lineageupdater. If i want export a downloaded update, the updater crashed/closed immedialtly, be tapping "export update". May be same issue with the external SD card, simmilar in the camera app? I have no idea, hope it will fixed in future. Otherwise the rom feels good on my motox4.
The second issue i've found is in the Lineageupdater. If i want export a downloaded update, the updater crashed/closed immedialtly, be tapping "export update"
No idea if they're related, but that issue is listed in the 20220531 release, out now.
Last edited: Tuesday at 3:43 PM
With the update 20220531 from today the update export works great, thanks
Export update via linageupdater works fine since the today update 20220531. thanks for the hint
I updated from LS18.1, never had a problem. Now with 19 I'm getting all kinds of no service, dropped calls(no service), texts not sent, despite being on wifi with wifi calling/texting on. Sometimes I'll get the ! mark on the mobile signal icon.
Under the mobile data, I can't uncheck "automatically select network", says "couldn't find networks. try again".
Under the mobile data, I can't uncheck "automatically select network", says "couldn't find networks. try again".
Knuxyl
Senior Member
May 20, 2009
Google Pixel 5
I updated from LS18.1, never had a problem. Now with 19 I'm getting all kinds of no service, dropped calls(no service), texts not sent, despite being on wifi with wifi calling/texting on. Sometimes I'll get the ! mark on the mobile signal icon.
Under the mobile data, I can't uncheck "automatically select network", says "couldn't find networks. try again".
Sounds like the problem some of us were having. Try following the steps I posted above to flash it. There seems to be an issue with copy_partitions zip not correctly putting the modem firmware/driver in the second partition.
[OFFICIAL][ROM][PAYTON]LineageOS 19.1 (Android 12.1)
/* * 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...
forum.xda-developers.com
EdwinTheRed
New member
Jun 3, 2022
I upgraded from 18.1 to 19.1 using the installation instructions linked by the OTA Updater and the lastest (may-31st) build.
So far most things seem to be working, except for my in-ear-buds.
The Play/Pause buttons on my Jabra in ear headbuds stopped working - even after pairing them again. Volume buttons work fine though. This is the same for my Sony headset, but honestly, I newer used the play/pause buttons on the Sony in the first place (at least when paired with the phone). I am open to suggestions.
Also, is there any way to get back to the old 18.1-style number-buttons in the PIN-Unlock screen? I cant stand the new ones.
Same for the Clock in the Lock-screen. Is there any way to get this clock centered on the screen AND in one line again?
sincerely,
Edwin
So far most things seem to be working, except for my in-ear-buds.
The Play/Pause buttons on my Jabra in ear headbuds stopped working - even after pairing them again. Volume buttons work fine though. This is the same for my Sony headset, but honestly, I newer used the play/pause buttons on the Sony in the first place (at least when paired with the phone). I am open to suggestions.
Also, is there any way to get back to the old 18.1-style number-buttons in the PIN-Unlock screen? I cant stand the new ones.
Same for the Clock in the Lock-screen. Is there any way to get this clock centered on the screen AND in one line again?
sincerely,
Edwin
I never would have known that there was an OTA method for a version upgrade:I upgraded from 18.1 to 19.1 using the installation instructions linked by the OTA Updater and the lastest (may-31st) build.
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
I have the FI version of the phone,Sounds like the problem some of us were having. Try following the steps I posted above to flash it. There seems to be an issue with copy_partitions zip not correctly putting the modem firmware/driver in the second partition.[OFFICIAL][ROM][PAYTON]LineageOS 19.1 (Android 12.1)
/* * 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...
Would it be advisable to flash the retail firmware mentioned
or the FI version
XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Are these interchangeable?
EDIT: kinda feel like my problem might be different. if you have wifi texting on, and turn off mobile data, but are still on wifi, I don't think I should be getting 'waiting for network' ? I've always had a weak signal at my house and relied on wifi calling/texting.
Last edited: Yesterday at 2:01 AM
I never would have known that there was an OTA method for a version upgrade:Is that out of date somehow or am I misreading something?Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
These were the instructions I followed to the T, and had signal issues.
Knuxyl
Senior Member
May 20, 2009
Google Pixel 5
Fi and Retail are interchangeable, and Retail has newer firmware. I have Fi too but always flash retail.
And that sounds exactly like a driver/firmware issue. I could be wrong, but unless LOS is just broken, which it isnt for a lot of ppl, then its drivers.
And that sounds exactly like a driver/firmware issue. I could be wrong, but unless LOS is just broken, which it isnt for a lot of ppl, then its drivers.
Reactions: shar88
The irony of having a partition problem now is a bit much, but it happened.@rseiler @skiwarz
I tested flashing NON-HLOS.bin and it did not work. And I was wrong, there is no VZW variant of this phone.
However I did fix my issue. There was something wrong with the system_b or oem partition, I'm guessing it was outdated. Or there is something wrong with the copy-partitions zip that is linked in official lineageos guide. Because it's a possibility I didn't even use it because the stock firmware occupied system_b and oem.
So, I got through putting on the OEM with your fastboot batch and booted into it. All was well.
Rebooted into fastboot for the temporary recovery. Executed that command (fastboot flash boot lineage-19.1-20220531-recovery-payton.img) and got this, which may or may not be normal:
Then I did "fastboot reboot" and got:(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (25089 KB) OKAY [ 0.777s]
Writing 'boot_a' OKAY [ 0.755s]
Finished. Total time: 1.837s
I ended up in a kind of limited fastboot mode. I thought putting on the ROM beforehand was supposed to forestall this kind of thing, so I don't really get it. Were some of the commands in the batch perhaps not universally appropriate?No bootable a/b slot , failed to boot linux
falling back to fastboot
fastboot reason: fallthrough from normal boot mode
fastboot getvar all shows:
So I ran your batch again to re-flash, got back into bootloader mode (the normal one). And now it looks more normal, though why isn't the one I have highlighted in bold a YES?(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
I have to wonder if trying the next step (temp recovery) will result in the very same problem. I don't know why it wouldn't if it did the first time.(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
Last edited: Today at 7:25 AM
Knuxyl
Senior Member
May 20, 2009
Google Pixel 5
The irony of having a partition problem now is a bit much, but it happened.
So, I got through putting on the OEM with your fastboot batch and booted into it. All was well.
Rebooted into fastboot for the temporary recovery. Executed that command (fastboot flash boot lineage-19.1-20220531-recovery-payton.img) and got this, which may or may not be normal:
Then I did "fastboot reboot" and got:
I ended up in a kind of limited fastboot mode. I thought putting on the ROM beforehand was supposed to forestall this kind of thing, so I don't really get it. Were some of the commands in the batch perhaps not universally appropriate?
fastboot getvar all shows:
So I ran your batch again to re-flash, got back into bootloader mode (the normal one). And now it looks more normal, though why isn't the one I have highlighted in bold a YES?
I have to wonder if trying the next step (temp recovery) will result in the very same problem. I don't know why it wouldn't if it did the first time.
The first time you tried you flashed the recovery and tried to reboot the phone. you need to reboot the phone into recovery, either by doing fastboot reboot recovery or by selecting it in the bootloader menu.
the error you got is normal, since some phones started having a and b partitions fastboot started auto checking if the partition you're flashing is actually partition_a.
This is my fault, i forgot to pat that in between the flash lineage and perform factory reset. ill fix it, sorry!
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK