Development [ROM][OFFICIAL][sake][11] LineageOS 18.1

[roomanus]

What boot.img are you refering to?
I tried flashing vendor boot (fastboot flash vendor_boot .\sake_vendor_boot.img) like stated here and than booting into twrp (fastboot boot .\twrp.img) like stated here. But after reboot it stucks at ASUS logo, till I hardrestartet it. Happens everytime. booting to TWRP without flashing vendor results in the same outcome.
Btw. I had the same outcome even bevor flashing LOS recovery and LOS.

Any ideas?

Hey there,
so you havn't seen TWRP at all, right? Didn't boot, stuck immediatly?

 

[roomanus]

In my case, if i remember it right (it has been a while and a lot of trial and error trials):
1. Extract vendor_boot.img and boot.img from the latest official Asus release (in my case: UL-I006D-ASUS-30.12.112.72-1.1.31)
2. Flash both of them.
3. Sideload Lineage (and Gapps if you want them)
4. Start lineage and do first quick setup.
5. Reboot to bootloader
6. Again, do step 2.
7. then boot to twrp via fastboot boot
8. do the alternate Installation Method: Advanced>Install recovery Ramdisk.
9. Reboot Recovery, hopefully comes back.

Hope i remember right and it helps, tell me if you stuck somewhere, i'll try to help...
Cheers..

 

[chrisrevoltes]

Hey there,
so you havn't seen TWRP at all, right? Didn't boot, stuck immediatly?

Correct. It stuck at ASUS logo after fastboot boot twrp.

In my case, if i remember it right (it has been a while and a lot of trial and error trials):
1. Extract vendor_boot.img and boot.img from the latest official Asus release (in my case: UL-I006D-ASUS-30.12.112.72-1.1.31)
2. Flash both of them.
3. Sideload Lineage (and Gapps if you want them)
4. Start lineage and do first quick setup.
5. Reboot to bootloader
6. Again, do step 2.
7. then boot to twrp via
8. do the alternate Installation Method: Advanced>Install recovery Ramdisk.
9. Reboot Recovery, hopefully comes back.

Hope i remember right and it helps, tell me if you stuck somewhere, i'll try to help...
Cheers..

Interesting but strange.
Did you temp boot to TWRP via fastboot boot?

Edit: how did you get the vendor_boot and boot images? I cant extract them from the payload. Tried zip and some tools I found. But non worked.

 

[roomanus]

yes, sorry, Step 7. boot to TWRP via fastboot boot.
try this: https://github.com/ssut/payload-dumper-go
Fingers crossed...

 

[chrisrevoltes]

So first of all the payload dumper worked great. But unfortunatly that didn't helped much.

The main problem is, to flash everything to the correct partitions. But I have managed to flash TWRP directly to the boot partition like captain_throwback proposed:

EDIT: Does TWRP work if it's flashed directly to the device rather than fastboot booted?

But I'm still not sure if i flashed it correctly, because after switching the A/B partitions TWRP is gone again. On the other hand, as already written in the other thread, I have no idea how this works with A/B.

For the record:

fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB)                   OKAY [  2.380s]
Writing 'vendor_boot'                              OKAY [  0.224s]

fastboot flash boot .\twrp.img
Sending 'boot_b' (98304 KB)                        OKAY [  2.238s]
Writing 'boot_b'

As seen TWRP is always written to one partition only. But adb sideloading inside TWRP writes LOS to the other partition (as thought for an update) Btw. I tried the original vendor and the LOS vendor. Ill try again tomorow....

 

[chrisrevoltes]

I got it running. After a lot of try and error that's what I found:

Currently (Jan. 22) the LOS vendor image is NOT compatible with TWRP! If you first flash the vendor image and then ether flash or boot TWRP it will just stuck an the ASUS logo.

I don't know if that's could be a issue in future but for now, I reflashed the original vendor extracted from an update unsing this payload dumper. And then followed the TWRP instructions.

Here my steps:
With unlocked BL, booting to BL already done and working adb/fastboot drivers

1. (Reflashing original vendor (only needed on non stock devices))
   • fastboot flash vendor_boot vendor_boot.img
2. Booting TWRP:
   • fastboot boot <TWRP Image>.img
3. (Doing a faktory reset if needed)
4. Sideloading LOS (TWRP flashes it to the inactiveslot)
   • In TWRP: Advanced -> ADB Sideload -> Swipe to Start Sideload
   • On PC: adb sideload <LOS Image>.zip
5. Let TWRP flash itself
   • In TWRP: Advanced -> "Flash current TWRP"
6. If further packages are needed (like gapps oder magisk)
   1. Change slot (In TWRP: Reboot -> Slot x) or reboot to recovery
   2. Either sideload them oder adb push them to sdcard and use TWRPs install method.
      • Sideload: see 4.
      • ADB Push: adb push <package> \sdcard
7. Reboot to system.

For reference: My images

• LOS: 18.1-20220121 lineage-18.1-20220121-nightly-sake-signed.zip
• TWRP: v3.6.0_11 twrp-3.6.0_11-0-I006D.img
• Stock Rom: Version WW-30.12.112.72 from 2021/12/17

I believe the with every LOS update its required to let TWRP reflash itselve, otherwise the original LOS recovery will be used. I read somewhere that TWRP does this by itself when flashing, but I am not sure if this is really the case.

But as stated, I'm not sure if that's the correct way. Unfortunately didn't get answers till now.

-------
Edit: Format, links and commands

 

[Winnie_LD]

Vibration is now working, guess it was the last update from Friday, Feb 04?
Thank you anyway, @ZVNexus ! Great Work!

 

[ZVNexus]

I got it running. After a lot of try and error that's what I found:

Currently (Jan. 22) the LOS vendor image is NOT compatible with TWRP! If you first flash the vendor image and then ether flash or boot TWRP it will just stuck an the ASUS logo.

I don't know if that's could be a issue in future but for now, I reflashed the original vendor extracted from an update unsing this payload dumper. And then followed the TWRP instructions.

Here my steps:
With unlocked BL, booting to BL already done and working adb/fastboot drivers

1. (Reflashing original vendor (only needed on non stock devices))
   • fastboot flash vendor_boot vendor_boot.img
2. Booting TWRP:
   • fastboot boot <TWRP Image>.img
3. (Doing a faktory reset if needed)
4. Sideloading LOS (TWRP flashes it to the inactiveslot)
   • In TWRP: Advanced -> ADB Sideload -> Swipe to Start Sideload
   • On PC: adb sideload <LOS Image>.zip
5. Let TWRP flash itself
   • In TWRP: Advanced -> "Flash current TWRP"
6. If further packages are needed (like gapps oder magisk)
   1. Change slot (In TWRP: Reboot -> Slot x) or reboot to recovery
   2. Either sideload them oder adb push them to sdcard and use TWRPs install method.
      • Sideload: see 4.
      • ADB Push: adb push <package> \sdcard
7. Reboot to system.

For reference: My images

• LOS: 18.1-20220121 lineage-18.1-20220121-nightly-sake-signed.zip
• TWRP: v3.6.0_11 twrp-3.6.0_11-0-I006D.img
• Stock Rom: Version WW-30.12.112.72 from 2021/12/17

I believe the with every LOS update its required to let TWRP reflash itselve, otherwise the original LOS recovery will be used. I read somewhere that TWRP does this by itself when flashing, but I am not sure if this is really the case.

But as stated, I'm not sure if that's the correct way. Unfortunately didn't get answers till now.

-------
Edit: Format, links and commands

Like I said earlier in the thread, just keep in mind I don't support or endorse using TWRP for LOS.

 

[chrisrevoltes]

Like I said earlier in the thread, just keep in mind I don't support or endorse using TWRP for LOS.

Totally okay. Could you perhaps explain what the difference is between the (your?) LOS vendor boot image and the stock vendor?
Could it be that some functionalities did not work?
Does it make sense if I (and others of course) still give feedback, or does it not help you anymore?

 

[ZVNexus]

Totally okay. Could you perhaps explain what the difference is between the (your?) LOS vendor boot image and the stock vendor?
Could it be that some functionalities did not work?
Does it make sense if I (and others of course) still give feedback, or does it not help you anymore?

The vendor boot image is completely different from the vendor image, vendor_boot is for fstab in first stage ramdisk and recovery modules.

 

[igor47]

using this as my daily driver and loving it so far! main bugs that are affecting me:
* the full-screen flash when unlocking with fingerprint reader, which ZVNexus mentioned is unlikely to be fixed
* when I turn on Night Light nothing happens, same for any of the Color setting modes (natural/boosted/adaptive), or Reading Mode
* I have AccA installed with the ACC daemon, root through Magisk. the app reports that everything works fine, but charging control doesn't happen and the phone always charges to 100% when it's plugged in

i would love to get the second two issues fixed, let me know if i can help somehow -- beta-tester? contributing to a bounty?

 

[ZVNexus]

using this as my daily driver and loving it so far! main bugs that are affecting me:
* the full-screen flash when unlocking with fingerprint reader, which ZVNexus mentioned is unlikely to be fixed
* when I turn on Night Light nothing happens, same for any of the Color setting modes (natural/boosted/adaptive), or Reading Mode
* I have AccA installed with the ACC daemon, root through Magisk. the app reports that everything works fine, but charging control doesn't happen and the phone always charges to 100% when it's plugged in

i would love to get the second two issues fixed, let me know if i can help somehow -- beta-tester? contributing to a bounty?

Night light was addressed in Lineage 19, the fix was backported in the build last Thursday.

 

[igor47]

Night light was addressed in Lineage 19, the fix was backported in the build last Thursday.

i'm running the build from Feb 4th, and nightlight continues to be broken. is there anything i can do to prod it? maybe a hack like the toggle-always-show-time-to-fix-DTW one?

edit: i looked at the changelog for lineage-18.1-20220204-nightly-sake-signed.zip and the only relevant change seems to be this one but that still doesn't look particularly relevant. was the change you mention backported to 18.1 from 19? in any case, i grabbed a logcat from when i enable night mode. it looks like this:

02-12 23:45:23.515 1069 1216 D ColorDisplayService: NightDisplayTintController Animation cancelled: true to matrix:
02-12 23:45:23.515 1069 1216 D ColorDisplayService: 1.000000 0.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 0.000000 1.000000 min matrix coefficients:
02-12 23:45:23.515 1069 1216 D ColorDisplayService: 1.000000 0.000000 0.000000 0.000000 0.000000 0.811456 0.000000 0.000000 0.000000 0.000000 0.633580 0.000000 0.000000 0.000000 0.000000 1.000000 max matrix coefficients:
02-12 23:45:23.515 1069 1216 D ColorDisplayService: 1.000000 0.000000 0.000000 0.000000 0.000000 0.996541 0.000000 0.000000 0.000000 0.000000 0.993277 0.000000 0.000000 0.000000 0.000000 1.000000
02-12 23:45:23.523 905 1466 E SurfaceFlinger: The color transform's last row must be (0, 0, 0, 1)
02-12 23:45:23.527 854 1058 E SDM : ColorManager::ColorMgrSetColorTransform: STC interface is NULL
02-12 23:45:23.531 905 1468 E SurfaceFlinger: The color transform's last row must be (0, 0, 0, 1)
02-12 23:45:23.535 854 1058 E SDM : ColorManager::ColorMgrSetColorTransform: STC interface is NULL
0

with that last message repeating many times

 

[Sarum4n]

Fora such as this one are often full of problems and questions, and not so much the success stories (because what is there to tell, right?) So just as a counter point: three days ago I received my Zenfone 8 16/256, and I installed LOS18.1 nightly, including LOS Recovery and MindTheGApps, with no noteworthy problems. Works like a charm!

 

[Malko007]

Hello , sorry for asking but i see a lot of update on LOS ...but nothing recent on LOS4microg. Is this normal? When can we expect an update?

 

[NisseGurra]

Hello , sorry for asking but i see a lot of update on LOS ...but nothing recent on LOS4microg. Is this normal? When can we expect an update?

los4Microg has slower updates, next should be up tomorrow

 

[ZVNexus]

i'm running the build from Feb 4th, and nightlight continues to be broken. is there anything i can do to prod it? maybe a hack like the toggle-always-show-time-to-fix-DTW one?

edit: i looked at the changelog for lineage-18.1-20220204-nightly-sake-signed.zip and the only relevant change seems to be this one but that still doesn't look particularly relevant. was the change you mention backported to 18.1 from 19? in any case, i grabbed a logcat from when i enable night mode. it looks like this:




with that last message repeating many times

yeah I'm dumb I didn't backport properly, should be fixed in tomorrows build

 

[eVen123]

Hello!
The thread is mostly about discussing issues and doesn't get the praise it deserves: I've been rocking this ROM for a while now as daily driver. Very stable, no crashes. Perfectly usable.

Some facts worth considering:

1. The fingerprint sensor doesn't work while screen is off. You have to wake the phone first (key or double tap if enabled)
2. The fingerprint sensor makes the screen go full brightness.
3. The fingerprint sensor is significantly faster than on stock ROM.
4. The app switching is significantly faster than on stock ROM.
5. The audio recording is not as good as on stock ROM. I tried installing default app, but it doesn't record as well - I think stock ROM does some automatic gain control. This is a significant loss for me, but I guess irrelevant for most.
6. There is no vibration intensity control and the stock vibration is very mild. If I have phone set to vibration and carrying it in pocket, I easily miss calls.

Due to the last issue, can this be solved with some external modifications perhaps? Magisk module? Some prop edits? If anyone knows, please @ me.

 

[igor47]

yeah I'm dumb I didn't backport properly, should be fixed in tomorrows build

YES! installed the fresh build today, confirm all display features work now including night light and grayscale mode. i definitely still have to enable/disable "always show time and date" to get double-tap-to-wake enabled after every update, minor inconvenience, re-installing magisk after every update is much more annoying

 

[Winnie_LD]

missing: data roaming

Hi again! I have been in Austria for a few days and was left with no data roaming. this has been mentioned earlier in this thread, I just wanted to inform you that it is still not working - at least for me with the following predispositions:

Asus Zenfone 8, 256 GB, 8 GB
LineageOS 18.1, build 20220218-recovery-sake
vodafone callya
APN: web.vodafone.de

I called vodafone to check settings. They told me, they had no attempts from my SIM-Card to log into the Vodafone Mobile Data Net. Calls and SMS no prob, only data roaming does not work.
Obviously, the phone does not even attempt to login to the net.
Same for the second SIM Card, a prepaid data card (ALDImobile).

Do you experience the same issues? What have you tried so far? Has anyone gotten data roaming to work?

Since I am on the road quite a few times and I live near the border, getting data roaming to work would be a huge relief.
thanks all!