yashsingh1/xdaforums huggingface dataset:
[Google TV General] endera:
Hi,

I installed LineagOS 20 (aml_upgrade_package.img ) version for my "Radxa Zero" device.

It's really very successful. Well done to those who made it.

My only problem is that I can't run the "Netflix" app. Do you have any suggestions on this matter?

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)​

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja
[Google TV General] npjohnson:
You can't. The ATV app requires L1 DRM. Radxa0 has no keys.
[Google TV General] endera:
Thanks, but I'm running Netflix with a different ROM. Slimbox rom works with AdrianROM
[Google TV General] npjohnson:
On Android tv? You'll need to link me their sources if so.
[Google TV General] endera:
https://slimboxtv.ru/x96s-tv-stick/ (slimBOXtv 9)
[Google TV General] _Fidor_:
In such case - could You please update FAQ in first post. One can think that L1 and Netflix is working also on M5, Raxda, Odroid.
[Google TV General] _Fidor_:
I've debug this problem a bit further. It seems that bootloader from aml_install_package.img and aml_upgrade_package.img have different env. It seems to boil down to:

#AML INSTALL IMAGE
bootcmd=run recovery_from_flash
preboot=run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run recovery_key;bcb uboot-command;run recovery_from_flash;
reboot_mode=normal

#AML UPGRADE IMAGE
bootcmd=run storeboot
preboot=run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run recovery_key;bcb uboot-command;run switch_bootmode;
reboot_mode=factory_reset

Now if I perform

1. flashing with aml_install_package.img image,

2. install LOS

3. Enter burn mode on M5

4. change those variables to be in sync w/ those from aml_upgrade_package.img

...then I'm getting LOS to boot.

However when I get them in sync before flashing LOS (just after burning the image) then the bootloader attempts to boot LOS and fails:

[ 5.962605@0]- init: init first stage started!
[ 5.962751@0]- init: Unable to open /lib/modules, skipping module loading.
[ 5.968537@0]- init: Copied ramdisk prop to /second_stage_resources/system/etc/ramdisk/build.prop
[ 5.980279@0]- init: Using Android DT directory /proc/device-tree/firmware/android/
[ 6.016480@0]- init: AVB is not enabled, skip verity setup for '/metadata'
[ 6.018128@1]- init: [libfs_mgr]Invalid ext4 superblock on '/dev/block/metadata'
[ 6.026217@1]- init: [liblp]Logical partition metadata has invalid geometry magic signature.
[ 6.033869@1]- init: [liblp]Logical partition metadata has invalid geometry magic signature.
[ 6.041986@1]- init: Could not read logical partition metadata from /dev/block/super
[ 6.049827@1]- init: Failed to mount required partitions early ...
[...]
[ 16.458470@0]- reboot: Restarting system with command 'bootloader'
[ 16.464718@0]d reboot reason 7

Which puts me at bootloader (not recovery). Am I missing something here?
[Google TV General] npjohnson:
When you install lineage env gets reset as bootloader "upgrades".

I now have all the info I need to properly fix it.

Thanks so much!
[Google TV General] musakilic:
Use radxa zero and also install last lineageos 20 and Disney plus working but netfilix for ATV version not work but work netflix.8.59.1_build_12
[Google TV General] doe1435:
Hello everyone,

I'm using a Odroid C4 with 32GB emmc and try to install the OFFICIAL LOS build with GAPPS. I managed to flash the am_install_package and booted into the recovery. During the first attempt to install LOS.zip, the recovery threw an error that it cannot read dynamic partition tables. I then changed to fastboot and flashed all the partition files from LOS-page (.img files). Now the recovery successfully flashes the .zip files, but after reboot the C4 ends up in the recovery. Trying to re-flash does not help.

Does anyone have suggestions what to do? And does someone know how to put the C4 back into "burn/maskrom mode"?

Thanks,

doe
[Google TV General] espionage724:
I'm on Windows, and in the restore zip, I changed flash-all.sh to bat, removed the bash part, and notably had to remove the "flash:raw" part from the boot img flash so that it was just "flash" (no :raw). I also had to downgrade platform-tools to 30.0.5 due to some later flash error. The main thing I was missing was ignoring that boot.img flash failure :p

Both of those changes got my 4K box back to stock and booting!
[Google TV General] Functioner:
I was making the change after lineage was already up and running. I just typed "update" at the u-boot shell prompt in order to start a "bootloader burn mode" connection.

If I was starting from a "bootrom burn mode" connection, I may have done it like shown in the steps you've listed.

The following are the steps I used when I first installed lineage about 48 hours ago. This is not a guide, it's just for information.

I was running completely factory stock m5 android os:

[ro.build.expect.bootloader]: [01.01.180822.145544]
[ro.build.fingerprint]: [bpi/m5_mbox/m5_mbox:9/PPR1.180610.011/20210427:userdebug/test-keys]

While booted to the stock os*:

adb reboot fastboot

*alternatively, type "fastboot" at the u-boot shell prompt

Next, using fastboot:

fastboot flashing unlock
fastboot flash dtb dtb.img (from lineage-20.0-20231022-nightly-m5-signed.zip)
fastboot flash dtbo dtbo.img (from lineage-20.0-20231022-nightly-m5-signed.zip)
fastboot flash recovery recovery.img (from lineage-20.0-20231022-nightly-m5-signed.zip)
fastboot flash super super_empty-edit.img (file linked in post #610)
fastboot oem "reboot recovery"

The above was all with the factory original bootloader still installed, and no changes to the environment.

Once lineage recovery booted, I used the keyboard* to select factory reset (format data/factory reset). Did it twice, the second execution was free of any errors. This formats data, cache, and metadata, solving many issues that occurred with the provided amlogic-format-image installation. Likewise, the flashing of super_empty-edit.img solves the super issue.

*Usb keyboard may need to be unplugged/re-plugged in order to be recognized.

Then, while still in the same recovery session, I selected apply update (adb/sideload):

adb sideload lineage-20.0-20231022-nightly-m5-signed.zip

It completed without errors. Next, while still in the same recovery session, I selected "reboot to bootloader". After the device rebooted to fastboot (bootloader fastboot), then I flashed DDR.USB from aml_upgrade_package.img:

fastboot flashing unlock (bootloader needs to be unlocked again)
fastboot flash bootloader DDR.USB (from aml_upgrade_package.img)
fastboot reboot

Only after all of the above, and having booted several times to the os, did I make the change to the environment to include a start/re-start/reset of usb during u-boot preboot.
[Google TV General] Computeraar:
Hey,

I just stumbled upon this project and it looks very interesting! Is there any planned support for the Minix Neo U9-H in the future? (this is also a GXM/S912 box)
[Google TV General] npjohnson:
Nope. But you can likely port it.

Take the beast tree and rebrand
[Google TV General] endera:
Hello, do you have any suggestions for Netflix? Thanks. (Radxa Zero)
[Google TV General] npjohnson:
Nope. It doesn't support L1.

Unless someone shows me L1 working one radxa0 and the source for it I can't help.
[Google TV General] Computeraar:
I don't quite get what you mean by this. I don't see a beast tree anywhere. Could you elaborate?

Also, how involved is the process of porting a ROM? I've never done it but I'm willing to give it a try
[Google TV General] npjohnson:
Sorry, I sadly don't have the time to walk you through it.
[Google TV General] npjohnson:
not sure why you blankly quoted me
[Google TV General] endera:
I added a video but it wasn't sent, I don't understand why, I apologize.
[Google TV General] npjohnson:
I didn

I didn't mean send me a video L1 working lololoo.

I meant I need source code to look at.
[Google TV General] endera:
hi, as an end user, I do not know how to access the source code, but the link to the ROM I downloaded and installed is below.

4GB

Посмотреть и скачать с Яндекс Диска

disk.yandex.ru
[Google TV General] npjohnson:
Sorry, that doesn't help me
[Google TV General] endera:
Ok, since I'm not a developer, we're stuck here. There's nothing to do. Thanks anyway...

note: maybe if you create a compatible "Netflix.apk". Which eliminates the L1 requirement.
[Google TV General] npjohnson:
Lol that's not how it works, and not feasible.
[Google TV General] lukash188:
Hi guys,

I just tried to flash Lineage OS 20 into my dopinder but it seems I hit the wall during the process. Everything went okay until I tried to flash the recovery. It seems the recovery was flashed, then I tried to reboot into the recovery but nothing was happening. So I waited for around 15 minutes and then I restarted my device manually. Then the 'onn.' title appear on the screen and it got stuck there. adb/fastboot commands don't work anymore. Did I brick my device?

EDIT:

I found in another thread that it's possible to enter recovery by holding the power button and powering the device up simultaneously. That worked for me and I was able to enter recovery. From there, I was able to continue with installation. I will leave this comment here in case someone experiences the same issue.
[Google TV General] Computeraar:
I understand. However, I have since looked into it a bit more and I think I mostly understand what I need to do now. Therefore, I do hope you can answer a question I have.

Given the instructions I found in this earlier comment of yours, I have an idea of how to approach this. I am currently following the build guide for beast and will apply the steps as you described in that comment to my device. I have all the files I need, including proprietary blobs for beast, what exactly should I edit in the lineage_beast.mk file? And where exactly should the DTS file for my Minix go in the kernel directory. Should there be a certain subdirectory structure?
[Google TV General] npjohnson:
This is the part that isn't easy to explain.

Sadly none of those questions have clear answers.

You need to in short:

- Rebrand the tree to reflect relevant values for your devices everywhere (name, oem, chipset, etc.)

- Configure your wifi/BT depending on what chip it uses (see Deadpool for BCM, dopinder for RTK)

- Extract proprietary blobs from your devices stock builds or a generic one for your platform

- Configure your devices DTS in kernel and utilize the right platforms inherits
[Google TV General] CollieBabaX:
For the USB issue of the m5 in recovery mode, I did not understand, is it something that I can do without coding knowledge? Sorry guys

Thank you
[Google TV General] SuperUser008:
After an update of LOS 20 on Dynalink, the device does not boot anymore. It is stuck on the "androidtv" logo. What happened? I did updates before and it worked.

What can I do now? Can I recover my device? Or new installation?
[Google TV General] macromorgan:
Not sure, but I can confirm this happened to me too. I rolled back to the previous week and it worked fine.
[Google TV General] SuperUser008:
ok, that are good news, that the device can be recovered. How did you roll back?
[Google TV General] macromorgan:
The device was stuck in fastboot mode. I'm not entirely sure what I *should* have done, but I reflashed the DTB, DTBO, and recovery images using fastboot. Then I did fastboot boot recovery.img and did an adb sideload of the image file from 2023-10-16. Afterwards, I was back up and running even without having to clear and delete everything.
[Google TV General] rx149:
I ran into the same issue after using the LineageOS Updater in-OS with Dynalink aka Wade. Downloaded and flashed the 10/26 update and then was stuck on the androidTV boot screen.

So I attempted to reinstall from scratch, using the LineageOS install instructions, using the same build of LineageOS, not knowing it was potentially bad, including factory resetting it. This of course didn't work and now I can't get the device to be able to connect to adb. I only have fastboot access now.

Is there any way to get adb re-enabled using something like the amlogic utilities so I can flash a known good LineageOS build, or am I softbricked completely?
[Google TV General] npjohnson:
Which device?
[Google TV General] rx149:
Dynalink/Wade. Sorry, should have specified.
[Google TV General] npjohnson:
I've pulled the 1026 build, looking into why it is broken.
[Google TV General] macromorgan:
1102 build also broken, at least for me.
[Google TV General] npjohnson:
With or without gapps?
[Google TV General] macromorgan:
This is with gapps. It had the same problem as the 1026 build, basically wouldn't exit fastboot after I did an upgrade with the Updater menu option. I've used fastboot to flash the 1019 build back and it's working again.

To clarify, this is the official one not the "unofficial" one.
[Google TV General] npjohnson:
Can you please factory reset and try without gapps and see if it boots?

Will help me debug the issue.
[Google TV General] npjohnson:
sorry, forgot to quote you, see above
[Google TV General] macromorgan:
On an unrelated topic, what would it take to get this device either on a 64 bit userland or a newer version of the kernel? I'm extremely green when it comes to Android, but a seasoned veteran at Linux porting and have quite a few devices I've upstreamed under my belt for both Linux as well as U-Boot.
[Google TV General] macromorgan:
I will have to try later. It's a living room device so I don't want to upset the Mrs.
[Google TV General] npjohnson:
64-bit user space on android isn't really that feasible - no 64 bit Mali.

Not sure how other OSes would fare.

And 4.9 is where we're stuck if we want hardware backed OMX, google has 5.15 booting on this platform, but there are no OMX blobs that are compatible with it.

Look at the device/amlogic/yukawa sources on googlesource git. supports this platform (g12a) in its entirety.
[Google TV General] macromorgan:
Yeah, I was afraid something to do with media codecs would be the undoing. As for Mali, we can just use Panfrost. No Vulkan, but otherwise works fine in my limited experience. The biggest issue I imagine is that mainline may have the codecs, but they're stateless whereas Android (OMX or whatever else) probably only wants to deal with stateful. Also, something about Optee/Trustee/whatever.

I guess for now I'll leave this to you guys, as for me I'll try to get my feet wet supporting android builds for some other devices I own (looking at you Anbernic RG353P).

Thanks again.
[Google TV General] npjohnson:
well, hey now if you want to support more amlogic devices with this tree, would totally love to see it!

We have trees for all 3 major families of amlogic chip (just not gxbb), so really any /can/ be supported.
[Google TV General] doe1435:
Hello again,

I had a few questions about a week ago and after a few days of "cooldown" I tried to install LOS-231010 again without luck. I can confirm that the official installation procedure for the Odroid C4 does not work with versions 20231101, 20231025 and 20231010. The installation gets stuck at flashing the ROM. Does anyone how to fix this?

Besides this, I'd like to share some insights on the Odroid C4: Getting into the AML flash/mask mode was extremely unreliable (I don't know how many times I deleted partitions, created partitions and so on with no result... the only way that works reliable with my C4 is detaching the EMMC and every other mass storage, first powering it up "nacked" and after boot (lsusb check) attaching an empty emmc. It would have saved me hours, knowing this.

Cheers,

doe
[Google TV General] Functioner:
Since there is an error involving the metadata partition, you could try the "Factory reset" (format data/factory reset) option prior to sideloading the zip via adb, since that will format the metadata partition.

Even if that solves the error involving the metadata partition, the other error (involving dynamic_partitions_op_list) probably involves super. For this you could use advanced options in the recovery menu, and use an adb shell to fix super.

There has to be a better way than this. I have a C4, but no emmc module for it. I'll check what I can w/o the emmc module.
[Google TV General] doe1435:
I did the factory reset exactly as/when it is mentioned in the official Lineage OS installation instructions, prior to flashing the ROM.
[Google TV General] Functioner:
I was contemplating the possibility that the instructions may be wrong, or at least incomplete. If you don't want to go beyond the instructions, I certainly understand.

Regardless of whatever you had done up until the point of your screenshot, at the time of the screenshot, there was trouble with the metadata partition. I was trying to take it from there, not rewind the clock and re-write any insufficiencies in the instructions. If I had stuck with the instructions, I never would have got the m5 running.

Starting with a blank emmc means no reserved partition and therefore no partition table. Perhaps the amlogic-format image for the C4 doesn't fully account for starting in that state. But maybe it does, I don't know.

I'll back away now and leave you to the instructions.
[Google TV General] doe1435:
Edit: I read the answer again and followed the mentioned m5 steps according to odroidc4, precisely:

fastboot flashing unlock (not needed for odroidc4)

fastboot flash dtb dtb.img (does not exist)

fastboot flash dtbo dtbo.img (from lineage-20.0-20231010-nightly-odroidc4-signed.zip)

fastboot flash recovery recovery.img (from lineage-20.0-20231010-nightly-odroidc4-signed.zip)

fastboot flash super super_empty.img (from lineage-20.0-20231010-nightly-odroidc4-signed.zip)

fastboot reboot recovery

..when I'm back in the recovery and try to flash the ROM via sideload, the odroid shows the same error messages as mentioned before (post 669).

Edit2: tried everything with the Unofficial Image too with the same result. Even flashing the unofficial recovery did not help.
[Google TV General] doe1435:
@Functioner sent me a collection of all needed .img files. Thanks for your effort in helping me with this. So I did:

fastboot flash dtb dtb.img

This throws an error like: writing 'dtb'... FAILED (remote: No such file or directory)

fastboot flash bootloader DDR.USB
fastboot flash dtbo dtbo.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash super super_empty-edit.img
fastboot flash vbmeta vbmeta.img

The above commands worked successful, but:

fastboot oem "reboot recovery"

"FAILED (remote: Unknown OEM command)", so I did "fastboot reboot" worked for me.

So I did and after the factory reset, I flashed the ROM without any errors with:

Until this point I had a pretty good feeling, that this could work, but unfortunately the C4 always ends up in the recovery after a reboot. I tried to repeat the flashing procedure and flashing the latest LOS image, but always the same result. What went wring?
[Google TV General] Functioner:
The dtb.img file was present in the local directory?

Is your version of fastboot current?

How are you getting a fastboot connection in the first place? Is it by selecting "Reboot to bootloader" from the recovery menu?

Are you able to connect to the uart on the C4?

If you start with an empty emmc, the emmc might not be the selected device when you've booted by whatever other means.

I'm not sure. It might help if you listed every step you did from the very beginning of the attempted installation, before anything was installed at all.
[Google TV General] andreas__:
I do not have Gapps installed and the update 1019 -> 1109 failed as well with the device hanging in fastboot mode as a result.

In order to reduce the reports, I'd suggest to remove that download as well.

If I can test a build or get some logs for you, then I would be happy to help.
[Google TV General] npjohnson:
Please try this https://mirror.math.princeton.edu/pub/lineageos/exp/wade/20231110/
[Google TV General] andreas__:
After sideloading, the device again is stuck in fastboot mode.

With the 1109 build, it has shown the android tv logo, with this build it just stays black. I have not wiped data, though.

After flashing 1019 again, it's booting.

Best regards
[Google TV General] npjohnson:
you would need likely to wipe data to properly test that build.
[Google TV General] mitmille:
I was looking for the lastest Lineage Builds for dopinder, but I keep getting a error message on the page that had those builds. Anyone knows what happened to them?? -- Thanks
[Google TV General] npjohnson:
had space issues, this months build will go up in a few days.
[Google TV General] npjohnson:
try this pls https://mirror.math.princeton.edu/pub/lineageos/exp/wade/20231113/
[Google TV General] andreas__:
Hello,

booting fine now, without wipe! Thanks.
[Google TV General] npjohnson:
fantastic to hear - Thursday's official build will be fixed.

Thanks.
[Google TV General] macromorgan:
I can confirm Thursday's build (20231116) works for me after performing an upgrade.

If you don't mind, what was the root cause? I'm just curious as while I like to think of myself as a kernel expert I'm actually pretty clueless when it comes to userspace, specifically Android.
[Google TV General] npjohnson:
https://review.lineageos.org/c/LineageOS/android_device_amlogic_g12-common/+/374149

Mounting issues after migration to split fstab.
[Google TV General] CrysisLTU:
Since I've moved away from Netlix and don't care about Widevine L1 anymore, I'm thinking of moving over to LOS. Has the IR TV control for the remote on dopinder been implemented?
[Google TV General] npjohnson:
Dopinder itself doesn't have IR.

The remote does, but we have no configuration app to tie it to your TV.

But if you can figure it for your TV before you come from stock I think it should work.
[Google TV General] LSolrac2:
Hello! Considering that the Dynalink, ADT-3 and Onn (2021) are hard to find, are there alternatives with Lineage? Is there any progress regarding the Onn 2023 model?
[Google TV General] npjohnson:
ONN 2023 is progressing but has some road blocks like the first family. Gonna be a while sadly.
[Google TV General] Big Dumb Object:
Please don't tell me it's back to Widevine and mass self-immolations.
[Google TV General] npjohnson:
Worse, it's all the way back to hardware OMX... lol
[Google TV General] Big Dumb Object:
And here I have to ask what is the current situation with Banana M5: is it still sick or cured?
[Google TV General] Functioner:
The dynalink device (video) that's replacing wade is very nearly identical to the onn 2023 device. It's the same sdmc-designed YOC device as the '23 onn. Except the dynalink YOC device has 16gb emmc while the onn YOC has 8gb.
[Google TV General] npjohnson:
I'll probably go pick one up soon
[Google TV General] npjohnson:
I've been strapped for time sadly.
[Google TV General] LSolrac2:
Do you think it's worth getting at this time?

Pardon my ignorance; but what might this be? I remember back in LOS19 there was a codec that wasn't working
[Google TV General] npjohnson:
it wasn't _a codec_ that wasn't working.

It was all hardware support for all codecs.

Which means that nothing above 1080p will ever work and 1080p will be choppy - not great on a TV device.
[Google TV General] Big Dumb Object:
NO!

Two years ago, anticipating the official LineageOS release, I bought four Onn's 1st-gen to use them exclusively with this ROM. As a result, they are still waiting unpacked on my shelf.

That time I should have held off and then chose Dynalink, so looks like the story's repeating itself today. Don't make the same mistake I made.
[Google TV General] LSolrac2:
I mean, LOS20 is available for the 2021 model, but the L1 being broken does seem like an issue, but how big? -- I don't use Netflix, so I'm not sure how big of an impact it is.

However, there also isn't a way to get the new Dynalink, is there? -- Granted, though similar, it's still possible for one to be completed sooner than the other, no?

Sweet heck, I assume this is the OMX issue?
[Google TV General] npjohnson:
Yup.
[Google TV General] Big Dumb Object:
These are unofficial npjohnson's builds with baked-in GApps and some surprises from time to time. Not very good for my family living room.