yashsingh1/xdaforums huggingface dataset:
[Google TV General] bumerc:
Write the dtb.img to the EMMC for now and try again. According to the burning log, dtb has not been written..

dtb file contains a new partition table and must be brought forward as the first step when upgrading to a newer Android version.
[Google TV General] Beyond-It:
Seems like that helped!

Getting an "Android TV" logo on the screen now, but been like this for 20 min now and not much more happening.

Not sure what I should look for in the UART to debug further on this.
[Google TV General] npjohnson:
fastboot flashing unlock, u-boot is often locked by default when built targeting android
[Google TV General] Beyond-It:
Hmm.. Didn't seem to do much. Tried with both fastboot flashing unlock and unlock_critical.

Still seems stock on Android TV
[Google TV General] npjohnson:
Get a uart log for me
[Google TV General] Beyond-It:
Fresh UART :D

Could not attach file for some reason?! - https://pastebin.com/raw/sE0PKK4L
[Google TV General] bumerc:
Try adding the root device to the kernel cmdline explicitly. e.g.

BOARD_KERNEL_CMDLINE += root=/dev/mmcblk0p18 and recompile the kernel. Or do it in u-boot bootargs
[Google TV General] npjohnson:
Yeah was about to say, I had to decommonize that recently. You just need that and it should boot further.
[Google TV General] Beyond-It:
Thank you bumerc and npjohnson. This fixed the last bit to get it to start-up.

Time to play around with it 🥳
[Google TV General] eagledipesh:
Greetings @npjohnson, please excuse me if you have tried this already this.

There is a ROM @superceleron which extracts the L1 certificates and was able to re-use it custom rom, the L1 only work as long as the device had L1 support originally by the manufacturer, I am not sure that this will work for LOS, but I thought its worth looking at.

Note : Posted a link to forum in xda to avoid being report, but the link below will guide you to the ROM by @superceleron

https://xdaforums.com/t/rom-aidan-r...le-play-certified-atv-9.4199287/post-85476745
[Google TV General] npjohnson:
Extracting and reusing L1 cert is fine in practice but very not legal lol.

Lineage can't do it
[Google TV General] eagledipesh:
Ohh ok, I didn't know that, thanks for the revert.
[Google TV General] superceleron:
Actually im not reusing the certs, im using legit blobs direct from amlogic.

Now the issue is you actually getting them from amlogic!

But still im not really sure even if you get them, how legal it is for Lineage to use them.
[Google TV General] npjohnson:
which blobs are you using, and how are you getting them?
[Google TV General] superceleron:
Well, the blobs im using is the ones used to make the OS secure(needed for L1) at build time, uboot and system itself of course.

How did i get them, well i dont want(and i wont) to talk about it, sorry!
[Google TV General] npjohnson:
if you just dumped liboemcrypto from an aml devkit, not too secret that one can do that lol.
[Google TV General] superceleron:
Nop, and yes anyone can do that! like i said above i used original legit stuff and not any dumps.

Also that is not nearly enough for make it work, you can try how much you can with dumped liboemcrypto!

Anyway good luck to your project, i like it :)
[Google TV General] rsotaal:
i have onn. dopinder , i unlocked the bootloadee, installed magisk, but i have not got full root, cannot mount r/w, i cannot delete home apk ,disney etc..

its latest ota firmware... not installing Los due to L1, can anibody help
[Google TV General] madhatt:
Many thanks for this contribution npjohnson, I recently bought an odroid c4 card with an android emmc and I'm having trouble understanding some things.

The first step would be to flash the firmware using the amc-flash-tool. I created a vm for this on macOS. But where I get stuck is when it comes to burn mode, it is a recovery mode? There is no button on my card...

Not finding the right mode I get the error:

Amlogic device not found

Thanks for your help
[Google TV General] zoomer296:
Y'all still need one? I'd be happy to grab one and send it to whoever.
[Google TV General] npjohnson:
I personally don't but I can definitely get the device to someone who would work on it!
[Google TV General] Big Dumb Object:
Sorry if replying too late. This issue was introduced a few years ago with a major Magisk update, when patching boot.img became the main installation method. It's also a problem of the LineageOS recovery, which doesn't support decryption of /data and thus prevents the survival script from working. Both problems on A-only devices are solved by Lygisk.
[Google TV General] zoomer296:
By the way, can someone point me towards instructions to reinstall stock on my 2023 Onn UHD Box, if they're available?
[Google TV General] npjohnson:
We don't support it - if someone donates one I will send it to a developer to bring up, thought.
[Google TV General] zoomer296:
I'm aware. I tried to flash it like an idiot. 😅

I'm wondering if anyone could point me towards finding and reinstalling the original firmware.
[Google TV General] BTK19:
Here is a link to the firmware. Post in thread 'Walmart ONN Google TV' https://xdaforums.com/t/walmart-onn-google-tv.4586587/post-88539531
[Google TV General] smu44:
Hi!

First of all, graceful thanks to all nice people here, having LOS 20 on these devices is awesome!

I managed to build for Banana M5 (m5_tab variant), if anyone is interested in testing the build is available here: https://androidfilehost.com/?fid=10620683726822077890.

I may have a couple of questions, I'd be very grateful if someone had any clue:

- where does the u-boot.img, available here, come from? Is there any way to rebuild from source?

- I had to modify vendor/lineage/config/common.mk to enable adb (see below). Is there a better/proper way to achieve that?

(from line #16 to #25)

#ifeq ($(TARGET_BUILD_VARIANT),eng)
# Disable ADB authentication
PRODUCT_SYSTEM_DEFAULT_PROPERTIES += ro.adb.secure=0
#else
# Enable ADB authentication
#PRODUCT_SYSTEM_DEFAULT_PROPERTIES += ro.adb.secure=1

# Disable extra StrictMode features on all non-engineering builds
#PRODUCT_SYSTEM_DEFAULT_PROPERTIES += persist.sys.strictmode.disable=true
#endif

Wish you all a nice day :)
[Google TV General] apropper:
Hi, I just updated my dynalink to the newest sept 10 update and now I don't see anything onscreen. I see the androidtv logo, the lineageos logo, then black. I have a signal coming from the box, otherwise my tv would say "no signal", and if I hold the power button on the remote I can see the advanced power menu. Rebooting doesn't do anything. Can someone please help me?
[Google TV General] w00cash:
I had the same problem yesterday. I didn't have time to think it over so I have just rolled back to last working update and device booted normally.
[Google TV General] darkvoid:
In order to support the onn. Google TV 4K Streaming Box 2023 (Codename Yoc), I've ordered 2 of them and sent them off to @npjohnson.

He should be able to use them to enable LineageOS developers to get their hands on these and hopefully start on initial support.
[Google TV General] npjohnson:
I got them!

Like I mentioned, I am moving but I will get them to relevant devs by the end of the month!

Thanks.
[Google TV General] ramuka:
Something about the lineage-20.0-20230910-nightly knocked my wade (dynalink) out of commission. It froze right after the linneage OS animation. I had to go through fastboot and downgrade to an august release to get it working again. I tried upgrading again to the same nightly and same result.
[Google TV General] npjohnson:
We are pulling this weeks builds for all devices, and re-pushing them for officials.

For unofficial they are all rebuilding now.

Sorry about that.
[Google TV General] npjohnson:
Alright, new unofficial are posted and new officials are building - may be like 12 hours before officials all post.
[Google TV General] bretto_aus:
When you say downgrade you mean just flashing previous build right? For the life of me I can remember how to get into fastboot with button combo etc as since sept10th build device is unresponsive so cant exactly turn on adb debugging to run adb commands to get into fastboot...
[Google TV General] npjohnson:
Hold side button, then use AML update tool to run `update bulkcmd fastboot` then flash whatever you want via fastboot and boot recovery.
[Google TV General] bretto_aus:
Edit: Found a solution as noted here: https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-87982245
[Google TV General] npjohnson:
Tablet variant builds for _only_ the devkits are uploading on the unofficial side.

Enjoy!
[Google TV General] matrix200200:
What is the reason for 3 consecutive updates this month? (For dopinder).

Especially strange two that were released within 2 days.
[Google TV General] npjohnson:
There was an SELinux bug in the first one, the second one I messed up the build config, the 3rd is correct.
[Google TV General] matrix200200:
Wow, I installed all 3 of them.

Luckily, none bricked my device, or had any other ill effects :)

Perhaps its a good strategy to wait a few updates, before installing updates.

Also, any reason why all these updates (going back to July I believe), are still available in the updater?

It would be nice, if it only showed either the latest one, or maybe two updates, so people could revert if the need arises.
[Google TV General] npjohnson:
They get cleared out every 6 months by me.
[Google TV General] ChriMo:
what might be available or the best option in the EU for Q4 or Q1/2024 to flash?
[Google TV General] npjohnson:
Not sure yet, haven't even played with my s905X4 box yet.
[Google TV General] npjohnson:
Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

Thanks, see you on the other side!
[Google TV General] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[Google TV General] _Fidor_:
Hi,

First of all thanks for the hard work porting Lineageos to BananaPi M5.

However I've notice two issues with instruction posted on LineageOS wiki:

- "Press and hold the SW5 button on the board, and plug into your PC." - there is no SW5 on M5 board. SW4 should be used and keeping this button pressed gets me into burn mode (so it is most likely a typo in Wiki)

- This brings me to second problem: There is no way to navigate in LineageOS recovery:

- - USB ports on M5 provides no power so keyboard,mouse are out of the question.

- - there is no "input" binary in the image so "adb shell input keyevent ..." does not work

- - SW3 and SW4 does nothing. SW1 pressed shortly reboots the device (apparently it just selects highlighted option on screen), SW1 pressed for longer makes selection green and after release the device is rebooted.

Lack of navigation was reported previously in this topic, with a promise of quick fix but as for today this hasn't happened yet :(
[Google TV General] _Fidor_:
By my own stupidy I connected 12V USB-C power supply. Aside from distinctive smell of burning electronics, the device is getting hot however the USB ports started to work :D . I'll get new Banana Pi M5 on Tuesday but since I was able to get keyboard working, I moved forward w/ recovery.

However the official LineageOS sideload ends w/ error:

[ 133.223467] ERROR: recovery: [liblp]Logical partition metadata has invalid geometry magic signature.
[ 133.316185] ERROR: recovery: [liblp]Logical partition metadata has invalid geometry magic signature.
[ 133.412848] ERROR: recovery: Could not read partition table.

The device is still operational as I was able to flash Banana Android 9 before this error (but after the 12V incident) and it was working.

Full log is here: https://gist.github.com/adam-kulagowski/7b738dce467fab1542d4a560987b13b5
[Google TV General] _Fidor_:
After attempting to format system partition (from recovery) which throws the error:

The sideload error changed:

Full error log here:

M5 failure after system format

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
[Google TV General] _Fidor_:
Got a tiny bit forward:

1. ./aml-flash-tool.sh ../../Pobrane/aml_install_package.img

2. Cycle power

3. Booted to recovery

4. Factory Reset -> Format data/factory reset

5. Advanced -> Enter Fastboot

6. # fastboot wipe-super super_empty.img

7. Reboot to recovery

8. #adb sideload /home/fidor/Downloads/lineage-20.0-20230930-nightly-m5-signed.zip

Success!

But at this point any reboot that I can do, gets me back to recovery.I've tried:

- System reboot after sideload

- power off/ power on (using dedicated power supply)

- reboot from console / fastboot

I'm attaching console output. What seems curious, there are no errors, no crashes, it looks like, the machine each time boots directly to recovery image.

M5 reboots recovery

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
[Google TV General] snackematician:
I have a similar problem on wade where the remote won't wake up the device after it's been off ~1 or 2 hours.

The remote works again if I remove the battery and put it back, same as reported by @jacob12345. HDMI-CEC also works to turn the TV on in this state.

As a workaround, I've sideloaded the Wakelock Revamp app to prevent the CPU from going into standby/low-power mode.
[Google TV General] npjohnson:
sooo, the issue is that you need to flash the bootloader image: https://github.com/TheMuppets/proprietary_vendor_amlogic/blob/lineage-19.1/m5/radio/bootloader.img

I am not sure why the wrong one lookalike it's being included..... in the "patching" list you see in recovery was bootloader one of them?

If you flash that bootloader image it will just boot.
[Google TV General] _Fidor_:
Redone whole process (adding flashing bootloader.img):

[Marvin-PC aml-flash-tool]# ./aml-flash-tool.sh ../../Pobrane/aml_install_package.img
Unpacking image [OK]
Initializing ddr ........[OK]
Running u-boot ........[OK]
Create partitions [OK]
Writing device tree [OK]
Writing bootloader [OK]
Wiping data partition [OK]
Wiping cache partition [OK]
Writing boot partition [OK]
Writing dtbo partition [OK]
Writing logo partition [OK]
Writing recovery partition [OK]
Writing super partition [OK]
Writing vbmeta partition [OK]
Resetting board [OK]

...Factory reset from recovery and -> fastboot...

[Marvin-PC super]# fastboot wipe-super super_empty.img
Sending 'super' (264 KB) OKAY [ 0.016s]
Writing 'super' OKAY [ 0.015s]
Finished. Total time: 0.102s
[Marvin-PC super]# fastboot flash bootloader /home/fidor/Downloads/bootloader.img
Sending 'bootloader' (1290 KB) OKAY [ 0.061s]
Writing 'bootloader' OKAY [ 0.031s]
Finished. Total time: 0.193s

...Enter recovery -> sideload ...

[Marvin-PC super]# adb sideload /home/fidor/Downloads/lineage-20.0-20230930-nightly-m5-signed.zip
Total xfer: 1.00x

The following patching was done: System, Vendor, Product, odm, System_ext, dbto, vbmeta, dtb, logo

Unfortunately reboot still gets me into LOS Recovery. Console logs is here:

BPI M5 new bootloaded from 19.1

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
[Google TV General] Big Dumb Object:
Could you please recommend the best way to reliably remove GApps from your unofficial builds without issues for OTA updates? This is still a hurdle for me as I have four dopinders on my hands.
[Google TV General] npjohnson:
There really isn't one. Sorry.
[Google TV General] Big Dumb Object:
Maybe I can utilize some debloating Magisk module, manually configured against GApps. Where can I get a complete list of GApps components included in your builds?
[Google TV General] hereisjohnny:
Does this work with the MiBox 2nd Gen?

Quad-Core Cortex-A55

Just asking before I start
[Google TV General] BTK19:
No
[Google TV General] smu44:
What gives flashing aml_upgrade_package.img instead of install image, and simply booting device?
[Google TV General] _Fidor_:
While using FW from IX-22

[Marvin-PC aml-flash-tool]# ./aml-flash-tool.sh ../../aml_upgrade_package.img
Unpacking image [OK]
[...]
Initializing ddr ........[OK]
Running u-boot [KO]

[Marvin-PC aml-flash-tool]#

On RS232 console:

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:D;RCY:0;USB:0;0.0;c
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 14123948

BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz

Board ID = 1
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:D;RCY:0;USB:0;0.0;C
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 12125633

BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
DDR driver_vesion: LPDDR4_PHY_V_0_1_18 build time: Aug 28 2019 15:21:45
board id: 1
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
LPDDR4 probe
ddr clk to 792MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
Cfg max: 2, cur: 2. Board id: 255. Force loop cfg
ddr probe id done
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
LPDDR4 probe
ddr clk to 792MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
All ddr config failed...
Try next cfg
Exit data request loop...Err0x00000020
[Google TV General] smu44:
You will need to get your hands on a Windows computer or VM, then use https://wiki.banana-pi.org/Getting_Started_with_M5/M2Pro#Android.

Bash script "aml-flash-tool" has bugs, flashing full image won't work with it :/

I wrote a post about installing LOS in BPI forums: https://forum.banana-pi.org/t/keyboard-or-input-devices-do-not-work/16224/2.
[Google TV General] _Fidor_:
This will take some time but I'll check it. Thanks for the tip :) . Strange thing is that native BPI android 9.0 was flashed using this bash script without any issues.
[Google TV General] npjohnson:
Someone DMed me about bricking Deadpool, does anyone have time to walk someone through hooking up UART to get to fastboot to reflash?

I sadly don't at the moment, if anyone does let me know and I will send along the contact info
[Google TV General] ali387:
Maybe this explanation by a very knowledgeable forum member (Functioner) can get them started: https://xdaforums.com/t/guides-2023-walmart-onn-google-tv.4610749/post-88976891
[Google TV General] _Fidor_:
I've tried with windows. It appears that I'm getting the same error with aml_upgrade_package.img (from 22-IX) as I was getting with Linux. On windows flashing stops at:

[0x10303004]Romcode/Switch status/Identify/Error resuls

This error appears during uboot reading phase and stops image flashing.
[Google TV General] _Fidor_:
But with latest aml_upgrade_package.img (10-X) I'm getting to LineageOS wizard screen (so its working). Curious ... I'll investigate it in following days.
[Google TV General] npjohnson:
radxa0_tab, m5_tab, and odroidc4_tab go official next week with many bug fixes for the devkits in general!
[Google TV General] smu44:
Just tested OK with 3 "upgrade package" available on my hard drive : 230828, 230922, 231010.

Maybe your 230922 image is corrupt?

Anyway, only 231010 is publicly available now, so better stick on this one ;)
[Google TV General] Slimshady997:
The version of dopinder now works correctly like the streaming applications
[Google TV General] _Fidor_:
I did some checking and:

- with full upgrade image I'm always getting LineageOS to boot

- with full upgrade image BUT reflashed later via recovery with pure LineageOS - I'm getting boot of pure LineageOS (w/o Gapps)

- regardless of my attempts (order, flashing bootloaded separately) - flashing minimal aml_install package and the flashing LineageOS on to of it - I'm always landing in recovery after reboot.

I've created GitLab ticket in LineageOS bug list: https://gitlab.com/LineageOS/issues/android/-/issues/6306
[Google TV General] npjohnson:
Netflix and such?

Which one specifically
[Google TV General] Slimshady997:
Since the last time I tried none of them work
[Google TV General] npjohnson:
What was your last message intending to say then? Your last message said that they now work lol
[Google TV General] smu44:
By the way, how could you navigate into recovery options ?

I'd like to confirm your problem here, but I can't :/
[Google TV General] Slimshady997:
I mean all of them, since none of them work, you can enter and everything but when viewing some content an error came out
[Google TV General] _Fidor_:
By my own stupidy ;)

By accident (read "being dumb") I've connected USB-C power supply that is giving fixed 12V. Something burned (that smell :D) and I've got USB-A ports online after that. I'm not recommending this "fix" - I'll try to create another bug report (as soon as I'll have some time at my hands) at LineageOS gitlab regarding lack of navigation in recovery.

Update:

Ticket created: https://gitlab.com/LineageOS/issues/android/-/issues/6343
[Google TV General] npjohnson:
Yeah, absolutely no new news, it says that in the OP
[Google TV General] UnionBlvd:
Anyone else having trouble with the official build and the Sling app? Upgraded my wade yesterday from 19.1 to 20 after wiping data, sideloaded latest mindthegapps at the same time, and the few other apps I installed seem fine. I can install Sling from the Play Store but the icon doesn't show up in the launcher, and if I launch it via Kodi it just closes immediately.

EDIT: just for giggles I manually installed the previous version of Sling from apkmirror and it worked. Not sure what happened there.
[Google TV General] _Fidor_:
I've played a bit and you can try the following:

Approach 1: does not work but the closest to LineageOS Wiki:

linux# sudo -i
##boot M5 holding SW4 switch
linux# ./aml-flash-tool.sh /tmp/aml_install_package.img
##power cycle M5 and wait for recovery
linux# adb shell
m5# mkfs.ext4 /dev/block/data
m5# mkfs.ext4 /dev/block/cache
m5# exit
linux# adb reboot fastboot
##wait for fastboot
linux# fastboot wipe-super /tmp/super_empty.img
linux# fastboot reboot
##wait for recovery
linux# adb reboot sideload
##wait for recovery sideload
linux# adb sideload /tmp/line/lineage-20.0-20231014-nightly-m5-signed.zip
linux# adb reboot

The following approach gives me LineageOS either w/ google Apps or clean (if followed by sideload) BUT USB3.0 ports are offline in both cases - which means no input:

linux# sudo -i
##boot M5 holding SW4 switch
linux# ./aml-flash-tool.sh /home/fidor/Downloads/aml_upgrade_package.img
##power cycle M5 and wait for LineageOS
linux# adb reboot recovery
##wait for recovery
linux# adb shell
m5# mkfs.ext4 /dev/block/data
m5# mkfs.ext4 /dev/block/cache
m5# exit
##wait for recovery sideload
linux# adb reboot sideload
linux# adb sideload /tmp/line/lineage-20.0-20231014-nightly-m5-signed.zip
linux# adb reboot

While You can navige by using serial console and issuing commands there:

input keyevent KEYCODE_TAB
input keyevent KEYCODE_SPACE

It seems a bit not a best user experience. I've updated the Gitlab ticket pointing that power to USB 3.0 is lacking not only in revovery but in general.
[Google TV General] truefriendcz:
Hi. I have Odroid C4_tab (official build) but after install missing Bluetooth and Wifi drivers. How i can enable Bluetooth and Wifi? (combined USB dongle fopr wifi and Bluetooth).
[Google TV General] wyldwilly:
With the latest build (lineage-20.0-20230110-UNOFFICIAL-dopinder.zip) WiFi is now automatically reconnecting when device wakes up! On device wake up, WiFi is initially disconnected but does reconnect after a few seconds. This is great news and thanks for the continued effort!