[ROM][OFFICIAL][kebab][11] LineageOS 18.1

[the00guy]

I found how to root: download official magisk from github. Rename .apk to .zip. Flash it in TWRP.
The issue is that I am not sure of how to handle slot A and B with root and updates.

And another question: which geolocation service shall I activate/install for those who use microG?

Recovery and bootloader are part of the same /boot partition on A/B devices so when you flash a recovery you need to reflash any boot related stuff like Magisk. There is a boot_a and a boot_b for each slot, so normally you'd have to switch slots and reflash to flash the opposite slot but Magisk takes care of this for you (not sure if TWRP does nowadays, used to have to flash TWRP, then Magisk, then switch slots and repeat).

 

[BillGoss]

Recovery and bootloader are part of the same /boot partition on A/B devices so when you flash a recovery you need to reflash any boot related stuff like Magisk. There is a boot_a and a boot_b for each slot, so normally you'd have to switch slots and reflash to flash the opposite slot but Magisk takes care of this for you (not sure if TWRP does nowadays, used to have to flash TWRP, then Magisk, then switch slots and repeat).

On the 8T, recovery and boot are physically separate partitions, even though the 8T is an A/B device.

 

[the00guy]

On the 8T, recovery and boot are physically separate partitions, even though the 8T is an A/B device.

Thanks for clarifying that, I was not aware. That's a better way to handle the recovery and bootloader, IMO.

 

[TheArt.]

Recovery and bootloader are part of the same /boot partition on A/B devices so when you flash a recovery you need to reflash any boot related stuff like Magisk. There is a boot_a and a boot_b for each slot, so normally you'd have to switch slots and reflash to flash the opposite slot but Magisk takes care of this for you (not sure if TWRP does nowadays, used to have to flash TWRP, then Magisk, then switch slots and repeat).

On the 8T, recovery and boot are physically separate partitions, even though the 8T is an A/B device.

Thank you both, but still I am unsure of how to handle the 8T partitions, could you help me with these questions?:

1. Do I have to install TWRP on both slots? (I used fastboot flash recovery twrp.img the first time)

2. So the slots are like multiboot?

3. Can I have two different ROMs and use them both?

4. And what about kernels, do they have two slots too?

5. I had latest stock rom installed and I used copy_partition.zip before and after installing LineageOS. It bootlooped then I flashed LineageOS again and it worked. Now I am booting from slot_a. What happens if I now try to boot from slot_b? I mean, my data is shared between slots and only the system files are in two different slots or what?

6. Is there a step-by-step guide of how to update Lineage-OS while keeping twrp and magisk?

 

[BillGoss]

Thank you both, but still I am unsure of how to handle the 8T partitions, could you help me with these questions?:

1. Do I have to install TWRP on both slots? (I used fastboot flash recovery twrp.img the first time)

2. So the slots are like multiboot?

3. Can I have two different ROMs and use them both?

4. And what about kernels, do they have two slots too?

5. I had latest stock rom installed and I used copy_partition.zip before and after installing LineageOS. It bootlooped then I flashed LineageOS again and it worked. Now I am booting from slot_a. What happens if I now try to boot from slot_b? I mean, my data is shared between slots and only the system files are in two different slots or what?

6. Is there a step-by-step guide of how to update Lineage-OS while keeping twrp and magisk?

1. Not necessary, but see 6.
2. No. They are there solely to cater for seamless updates while the system is still running.
3. No. There's only one data partition and one super partition (it contains the "system" partitions).
4. Kernel = boot, so A and B
5. Try it - best way to learn. You can always swap slots again.
6. I don't use Los on my 8T, but: if Los supports addon.d then Magisk should stick. You will have to flash TWRP to the inactive slot (Los installs it's own recovery) when updating Los. Or you can use @osm0sis's TWRP retention module.

 

[TheArt.]

Basic Updating Instructions (with ROOT)

Prerequisites:
- Already in the LineageOS Official Nightly
- MindTheGApps installed
- Rooted by Magisk via patched boot.img method

Updating to the latest Nightly:
- Go to Magisk and click Uninstall Magisk, then click "Restore Images".
- Go to Settings/System/Updater check updates and download.
- Install the downloaded update.
- Once installed (DO NOT CLICK REBOOT)
- Go to Magisk and click "INSTALL", choose "Install to Inactive Slot (After OTA) and Flash then click "REBOOT" Botton in the lower right of the magisk.
- Wait for the optimization till it reboots.
- Done and Enjoy!


FAQ:
Q. Why I'm getting bootloop after updating via updater?
A. You're not using GApp package that are not addon.d v3 compliant
Q. Why I'm getting error from updating via adb sideload?
A. You're not rooted as stated to the above method. Flashed magisk zip can ends to bootloop!
Q. What is the best GApps package for Lineage?
A. MindTheGApps why? Because it's updateable.

Q. I don't want MindTheApps because it's huge and bloatty.
A. You may debloat the zip by removing or deleting this packages inside:
• AndroidAutoStubPrebuilt
• AndroidMigrateStubPrebuilt
• GoogleTTS
• PrebuiltExchange3Google
• talkback
• Velvet

Hi @Nixsuki , is this still valid? I am looking for a guide to update LOS while keeping twrp and root. Los updates include LOS recovery which will overwrite the TWRP. So do I have to flash the TWRP A/B retention script by osm0sis somewhere in the middle of your steps?

Basically I have 4 possible files to flash:

1. lineageos latest version zip (or install with the lineage updater app, not sure)
2. magisk.zip,
3. copy_partitions.zip
4. twrp_retention script zip

Which is the order of flashing those and how to proceed?

 

[hotrodwinston]

Current release wifi calling does not work on Visible/Verizon.
First custom rom I have flashed since droid turbo so don't know about prev versions.
Everything I tested worked great but decided to test other ROMs to see if I can find one with vowifi.
Continuing to test ROMs.

 

[fiepi]

$ getprop ro.product.model
KB2003
$ getprop ro.boot.rf_version
11

The model is not displayed correctly, my model is actually KB2000. You can refer to this code for correction.

device_oneplus_sm8250-common/init_sm8250.cpp at eleven · PixelExperience-Devices/device_oneplus_sm8250-common

Dependency of OnePlus 8 (instantnoodle), OnePlus 8 Pro (instantnoodlep), OnePlus 8T (kebab) - device_oneplus_sm8250-common/init_sm8250.cpp at eleven · PixelExperience-Devices/device_oneplus_sm8250-...

github.com

 

[LuK1337]

$ getprop ro.product.model
KB2003
$ getprop ro.boot.rf_version
11

The model is not displayed correctly, my model is actually KB2000. You can refer to this code for correction.

device_oneplus_sm8250-common/init_sm8250.cpp at eleven · PixelExperience-Devices/device_oneplus_sm8250-common

Dependency of OnePlus 8 (instantnoodle), OnePlus 8 Pro (instantnoodlep), OnePlus 8T (kebab) - device_oneplus_sm8250-common/init_sm8250.cpp at eleven · PixelExperience-Devices/device_oneplus_sm8250-...

github.com

Not interested in displaying correct model number.

 

[enapah]

Is the copy-partitions-20210323_1922.zip referenced in the installation tutorial still available to download from the official LOS servers? I've searched the Extras and the 8T/kebab folder without success.

Tangentially related to that script, if I understand this correctly, the LOS ROM does not ship with the matching vendor firmware. Therefore, in order to keep it updated (or even compatible with LOS), I'll need to regularly check for any OxygenOS updates, extract the individual firmware images from the official ROM, and fastboot flash each image to both slots?

 

[Dr. Mario]

Not interested in displaying correct model number.

Of course, KB200x models are more generalized for the OnePlus 8T phone, so I wouldn't sweat it. At least CPU-Z app still identifies it as OnePlus 8T (KB2003 and T-Mobile KB2007 which I have are the same hardware for all practical intentions).

 

[Dr. Mario]

Is the copy-partitions-20210323_1922.zip referenced in the installation tutorial still available to download from the official LOS servers? I've searched the Extras and the 8T/kebab folder without success.

Tangentially related to that script, if I understand this correctly, the LOS ROM does not ship with the matching vendor firmware. Therefore, in order to keep it updated (or even compatible with LOS), I'll need to regularly check for any OxygenOS updates, extract the individual firmware images from the official ROM, and fastboot flash each image to both slots?

Personally, I just skip copy-partition zip file and run OxygenOS updater app twice to flash the same OS update zip on both boot slots prior to flashing LineageOS on it. Zero issues so far.

 

[imusorka]

A few questions if I may.

1. Is there a trick with fingerprints? I've only managed to register one. Others fail about half way through when no more attempts are given.
2. Is it possible to have the lockscreen light up with new app notifications without touching the screen? AOD is a good option but not ideal battery-wise.
3. On my old OP3 I configured Tasker to change a bunch of settings for each of the notification slider positions. I see that LOS has something similar with System Profiles (albeit not that deep) but is there a way to tie this to the notification slider?
4. What kernel would be best for this marriage?
5. Gcam version suggestions?

 

[fabrifabrifabrifabri]

someone has tried to pass safetynet?

I have tried to use this thread below...

Universal SafetyNet Fix 1.1.0​

MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0

Universal SafetyNet Fix Magisk module This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12...

forum.xda-developers.com

but no way to pass it... can you suggest some way?

 

[Dior DNA]

Hi all, (yes/no Question below)
First of all congrats with and thanks for LOS [11] on 1+8T.
Yesterday I installed it for the first time via 'adb sideload' from recovery
(together with 'gapps' and 'root'). It ended up in slot B. All goes well.
I have also updated firmware to latest OOS 11.0.12.12 in both slots.

I would like to maintain exact same ROM in *both* slots.
*but*: no 'root' in one slot.

That's because every now and then (seldom) I need to run an app that detects 'root' and it does not help to be hidden by Magisk: the app detects root.

I used same strategy on stock OOS with success.
I temprarily changed slot when I (seldom) needed to run the app.

Question: Suppose I 'adb sideload' exact same' ZIP from recovery.
Would it (yes/no) flash onto A (i.e. onto the other slot)? I *think* it will, i.e.: flash *other* slot (because to flash additional ZIP packages one first needs to reboot to recocery). But, unfortunately, I do not remember which slot was active right *before* I installed LOS. I *think* it was A. Thing is : both A and B were boot looping (after I made some mistakes) so I changed slot few times and decided to go for LOS. Thanks for help.

 

[enapah]

someone has tried to pass safetynet?

I have tried to use this thread below...

Universal SafetyNet Fix 1.1.0​

MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0

Universal SafetyNet Fix Magisk module This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12...

forum.xda-developers.com

but no way to pass it... can you suggest some way?

You should look into this module:

[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2

MagiskHide Props Config v6.1.2 Note: For some time I have been extremely busy IRL. I simply have to prioritise things outside the Android modding world... I will get back to updating the fingerprints list and providing support as soon as I can...

forum.xda-developers.com

 

[Dior DNA]

[...] Question: Suppose I 'adb sideload' exact same' ZIP from recovery.
Would it (yes/no) flash onto A (i.e. onto the other slot)? [...]

Someone knows if it is yes or no ? I notice there is a TWRP img so I may try flashing other slot from TWRP

 

[fabrifabrifabrifabri]

You should look into this module:

[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2

MagiskHide Props Config v6.1.2 Note: For some time I have been extremely busy IRL. I simply have to prioritise things outside the Android modding world... I will get back to updating the fingerprints list and providing support as soon as I can...

forum.xda-developers.com

Great! it worked.
for other noobs like me: just select the fingerprint option (1 and f) and follow the model. That's it! easy.

Thanks my friend! happy new year.

 

[Dior DNA]

Someone knows if it is yes or no ? I notice there is a TWRP img so I may try flashing other slot from TWRP

I figured out : adb sideload flashes lineageos in inactive slot. So basically one can flash it identically twice, once with and once without root. And one can (every now and then if needed) run without root.

 

[Raketow]

I am not able to install LineageOS updates with LineageOS updater any more. Download works but when I hit install, it just gives me "Install error" with no further information. The updater worked until I did some modifications to the device which might cause that error:

1. Installed TWRP.
2. Installed Aurora Services as system app using adb root, remount and push.
3. Installed vendor firmware update as described here.

I went back to Lineage Recovery and was able to install an update of LineageOS through recovery but the LineageOS updater is still corrupt. I use LineageOS for microG. Any ideas how to get the LineageOS updater working again?