[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

[rczrider]

I still don't have the device to test this my own and very wonder if the Magisk root is preserved during OTA like in the good old days before Android 8.0, or if we want to enjoy the benefits of root, we must be prepared to patch the boot.img manually with every OS update? Has anyone checked?

Are you referring to OTA for LineageOS or OTA for stock (after bootloader unlock and root with Magisk)?

Another user answered for the former, so I'll answer for the latter (for dopinder, the ONN device): yes, with each OTA you will need to re-root with Magisk. This can be done either by flashing the Magisk APK (replace the .apk extension with .zip) by booting (not flashing) Lineage recovery (and requires a micro USB OTG Y cable so you can use a keyboard, as the hardware button won't work), or by extracting boot.img from the factory image zip and patching using Magisk once booted.

AFAIK, the second way doesn't really work right now because (again, AFAIK) no one has captured the OTA file for boot.img to be extracted. You can't set up a new ONN device without completing the setup wizard, which downloads the OTA before completion. Since you can't enable USB debugging (for doing a logcat and capturing the OTA URL) until after setup completes, it would take someone whose device is setup, has not received the OTA, and can do a logcat while the device updates in order to grab the OTA.

That leaves us with the first option of using a micro USB OTG Y-cable and Lineage recovery.

Something I don't know (which perhaps @npjohnson can comment on) is whether a stock OTA can re-lock the bootloader and and either brick the device (due to modifications that were done using root) or at the very least prevent us from unlocking again.

 

[Big Dumb Object]

Are you referring to OTA for LineageOS or OTA for stock (after bootloader unlock and root with Magisk)?

The first one.

Any LineageOS ROM will have it

Correct me if I'm wrong, but all modern devices with A-only and A/B partition scheme tend to rewrite the volumes that are essential to preserving Magisk during OTA. My Xiaomi Mix 2S (polaris) acts exactly that way, and it is very annoying. Here is a note in the official Magisk guide: https://topjohnwu.github.io/Magisk/ota.html

 

[JoshuaDoes]

The first one.

Correct me if I'm wrong, but all modern devices with A-only and A/B partition scheme tend to rewrite the volumes that are essential to preserving Magisk during OTA. My Xiaomi Mix 2S (polaris) acts exactly that way, and it is very annoying. Here is a note in the official Magisk guide: https://topjohnwu.github.io/Magisk/ota.html

You're right, but that's the purpose of the init.d extension. When Magisk patches a boot image and detects init.d support, it installs its init.d script and magiskboot to the boot image's ramdisk so that access to /data isn't needed to repatch after the OTA. And because Lineage Recovery also has init.d support, it knows to copy out the init.d scripts before replacing the boot image with the new unpatched one.

 

[Big Dumb Object]

You're right, but that's the purpose of the init.d extension. When Magisk patches a boot image and detects init.d support, it installs its init.d script and magiskboot to the boot image's ramdisk so that access to /data isn't needed to repatch after the OTA. And because Lineage Recovery also has init.d support, it knows to copy out the init.d scripts before replacing the boot image with the new unpatched one.

This is strange and contradicts my own experience, since I only found out about this issue because my polaris (A-only device), which has been running solely on official LineageOS or LOS for MicroG since the first day, inevitably removes root after OTA, while the presence of init.d support is confirmed by AFWall+ firewall app.

So, if anyone has any real success updating the flashed dopinder/sabrina/wade with Magisk — that would be the best answer to my query.

 

[JoshuaDoes]

This is strange and contradicts my own experience, since I only found out about this issue because my polaris (A-only device), which has been running solely on official LineageOS or LOS for MicroG since the first day, inevitably removes root after OTA, while the presence of init.d support is confirmed by AFWall+ firewall app.

So, if anyone has any real success updating the flashed dopinder/sabrina/wade with Magisk — that would be the best answer to my query.

I can't say why that's the case for you, but it should be working on those devices and sounds more like a bug. Regardless, I forgot to directly state it but it does successfully repatch the boot image with Magisk when I run an OTA on my dopinder box (one of the first things I tested when I bought it), both with np's builds as well as my own local builds.

 

[Big Dumb Object]

it does successfully repatch the boot image with Magisk when I run an OTA on my dopinder box (one of the first things I tested when I bought it), both with np's builds as well as my own local builds.

Thank you! It seems like a fairly unproblematic device. Can't wait for the work to be finished so I can make the purchase with confidence (want to buy a batch of dopinders at once for all my home screens).

 

[npjohnson]

So, per device it's different:

deadpool/dopinder/wade: you can't update while you're rooted or have any sort of modification to system, it breaks. Breaks AVB, now. If you just have a magisk patched boot image, that should be fine I think, Magisk has OTA handling.

Sabrina: Don't update anything ever, this device will re-lock itself and probably brick itself if you do, once the exploit is run, you're unlocked and should leave it. As such, you can flash back to stock like the thread details, but beyond that, which will mean you can never unlock again, don't do anything like that.

 

[rczrider]

deadpool/dopinder/wade: you can't update while you're rooted or have any sort of modification to system, it breaks. Breaks AVB, now. If you just have a magisk patched boot image, that should be fine I think, Magisk has OTA handling.

Is this in reference to LineageOS or stock? I assume the former ("breaks AVB") refers to LineageOS, while the latter ("Magisk patched boot image") refers to stock?

Unrelated: thank you for being so active in this thread, and for all the work you and others do to bring LineageOS to those who mostly just ask dumb questions or complain

 

[npjohnson]

Is this in reference to LineageOS or stock? I assume the former ("breaks AVB") refers to LineageOS, while the latter ("Magisk patched boot image") refers to stock?

Unrelated: thank you for being so active in this thread, and for all the work you and others do to bring LineageOS to those who mostly just ask dumb questions or complain

All of that was in reference to stock.

Lineage can be safely updated after pretty much any modification as it flashes a full OTA, and disables AVB. Will persist magisk through OTAs

 

[Broman400]

This might be off topic but does anyone know if it’s possible to get the Fire Stick remote microphone to work with any of the listed Android TVs. All the buttons work, but the microphone doesn’t detect any voice or sound

 

[lessslanted]

In case this helps anyone, this is how I've been getting USB debugging on without a google account and without updates.

Turn device on...
-connect remote control
-select language
-skip phone setup
-hit settings key on remote "cog-wheel"
-go to "apps" > "see all apps"
-select "update" and force stop
-select "show system apps"
-select "dynamic system updates" and force stop
-select and disable (or force stop):
*(it probably doesn't need to be all of these but I got sick and tired of narrowing it down)
google
google one time init
google partner setup
google play services
google services framework
market feedback agent
second screen setup auth bridge
settings suggestions
setup wizard (force stop)
setupcustomizer

-back out, back out, back out, until...
-setup remote again
-select language again

!!! - Pay attention directly after the next step. If you see anything other than "successfully connected to internet" then you missed something and it's going to download the update - hit settings button and wifi off

-sign in to network (It should say "checking connection" "successfully connected to internet")
-as soon as you see the screen with a black background and "updating apps" message
-hit settings button on remote
-turn off WiFi

Now developer options can be enabled and USB debugging turned on.

 

[npjohnson]

This might be off topic but does anyone know if it’s possible to get the Fire Stick remote microphone to work with any of the listed Android TVs. All the buttons work, but the microphone doesn’t detect any voice or sound

Nope - proprietary software receiver app/Audio HAL tie-ins.

In case this helps anyone, this is how I've been getting USB debugging on without a google account and without updates.

Turn device on...
-connect remote control
-select language
-skip phone setup
-hit settings key on remote "cog-wheel"
-go to "apps" > "see all apps"
-select "update" and force stop
-select "show system apps"
-select "dynamic system updates" and force stop
-select and disable (or force stop):
*(it probably doesn't need to be all of these but I got sick and tired of narrowing it down)
google
google one time init
google partner setup
google play services
google services framework
market feedback agent
second screen setup auth bridge
settings suggestions
setup wizard (force stop)
setupcustomizer

-back out, back out, back out, until...
-setup remote again
-select language again

!!! - Pay attention directly after the next step. If you see anything other than "successfully connected to internet" then you missed something and it's going to download the update - hit settings button and wifi off

-sign in to network (It should say "checking connection" "successfully connected to internet")
-as soon as you see the screen with a black background and "updating apps" message
-hit settings button on remote
-turn off WiFi

Now developer options can be enabled and USB debugging turned on.

Don't do this... You want the update. On dopinder/wade/deadpool you should absolutely take the OTA it recommends before starting.

 

[ferbulous]

Hi guys, I'm using walmart onn 4k with sony receiver.
I can use the onn remote to control the receiver volume but it failed to power on/off the receiver (tried all 9 attempts but none worked during power setup)
I had no problems to control both volume/power with my firetv stick 4k.

Is there a way I can configure the remote to learn IR for the power control?

 

[UnionBlvd]

Don't do this... You want the update. On dopinder/wade/deadpool you should absolutely take the OTA it recommends before starting.

Not on wade, at least not anymore. As someone else mentioned, the latest Dynalink update disables unlocking, and even after using the recovery tool to flash the older factory ROM I could no longer unlock mine.

 

[npjohnson]

Not on wade, at least not anymore. As someone else mentioned, the latest Dynalink update disables unlocking, and even after using the recovery tool to flash the older factory ROM I could no longer unlock mine.

I'm really doubtful here.

Especially considering you don't even need to toggle the switch, and you can always use brin mode to unlock by hand... I just really don't believe that.

 

[Big Dumb Object]

Not on wade, at least not anymore. As someone else mentioned, the latest Dynalink update disables unlocking, and even after using the recovery tool to flash the older factory ROM I could no longer unlock mine.

It's alarming! If the Walmart has declared war on this thread, we may soon be left with no cheap options for purchase. Can you clarify the release date of the nasty update? Apparently, all Dynalinks (and possibly Onns) manufactured later that date can be left in the store with calm. (But confirmation still needed.)

 

[UnionBlvd]

I'm really doubtful here.

Especially considering you don't even need to toggle the switch, and you can always use brin mode to unlock by hand... I just really don't believe that.

What is brin mode? I cannot find a reference to this anywhere else.

 

[npjohnson]

What is brin mode? I cannot find a reference to this anywhere else.

* burn mode.

 

[UnionBlvd]

It's alarming! If the Walmart has declared war on this thread, we may soon be left with no cheap options for purchase. Can you clarify the release date of the nasty update? Apparently, all Dynalinks (and possibly Onns) manufactured later that date can be left in the store with calm. (But confirmation still needed.)

I think the update was released in late Sep, I just got it last week after returning my Dynalink to stock. I had flashed a self-built Lineage image and the device wouldn't boot, flashing it back to stock was the only thing that got it going again.

 

[npjohnson]

I think the update was released in late Sep, I just got it last week after returning my Dynalink to stock. I had flashed a self-built Lineage image and the device wouldn't boot, flashing it back to stock was the only thing that got it going again

Okay, so if you can flash things, the bootloader is already unlocked, and as I suspected, that's not the worry.

Self built lineage wouldn't boot until about a month ago, as selinux policy wasn't done.