yashsingh1/xdaforums huggingface dataset:
[Google TV General] skippyd:
I have uploaded my unbricking tool to my google drive.... Link is in my signature. It's made to be ran on Windows so you will need to install the ADB drivers for your device. If you have used Windows with your device in the past, then you already have the drivers. This should work with all 4 devices to bring them back to factory. Even if you have 18.1 or 19.1 it should take the device back to factory. Its big (7 parts) due to all the factory images.
[Google TV General] UltimateSuperstar:
I've tried everything i could but obviously it is impossible to unlock bootloader on my device.
[Google TV General] activadroid:
It would be helpful if you mentioned what device you are trying to unlock
[Google TV General] npjohnson:
Or what he tried lol
[Google TV General] :
Everything is a lot of things to try.
[Google TV General] tenfox:
Hey is it within the scope for Lineage to bake in cifs filesystem support? Would be great to have on a media center device.

Very happy with wade!
[Google TV General] S1ngl3-x:
Does anyone know what has happened to wade official support?
[Google TV General] tenfox:
If you're looking for the builds, they're still up.
[Google TV General] npjohnson:
Sure, I'll look into it

Technical issue, but DTB.img isn't making it to the signing server so wifi is broken. I can't yet figure out how to get it transfered correctly basically. Hopefully I figure it out soon as it is just an infrastructure issue. Unofficial work fine.

Yeah they're broken though :/
[Google TV General] S1ngl3-x:
So official builds are "unmaintained" just temporarily until the wifi issue is fixed? Great news, thank you for your great work.
[Google TV General] npjohnson:
Correct.
[Google TV General] UltimateSuperstar:
Sorry l was just whining. I am really bored with the same advices and useless adb commands etc. Can you offer stg, new?

it's walmart's onn. 4k box by the way.
[Google TV General] npjohnson:
"Useless ADB commands" - that's how you install it.

Follow the wiki. It works.
[Google TV General] activadroid:
Could you post how far you got in the installation process and what response you saw on your screen ?

Using Linux or Windows to try the install ?

I have followed the standard instructions for LineageOS on Google Pixel, Pixel XL (3 different ones), Walmart Onn4K TV and Dynalink devices, and in all cases the Bootloader Unlock process was NOT the problem. (had other issue later in the sequence of steps, that I am not sure if I am the only one who had the problem).
[Google TV General] activadroid:
HELP: 'Free up storage' problem during install.

Running Dopinder with 2GB adopted USB flash stick.

I tried to install Termux from Play store, and it kept jumping to 'Free up storage' page, but it shows 651MB of 4.4GB used, & (now) NO app installed yet. [ I previously transferred (1 at a time) all (4) previously downloaded functional apps to the adopted stick - STILL have the problem ] [ edit: same problem in Play Store app trying to apply updates to 7 apps already on the device.]

Only option allowed is 'cancel'.

What am I doing wrong ?

[BTW: what I really want at the moment is to install Armbian onto Dynalink or Onn 4K box, because I am trying to see how close I can get to usable Linux PC for $20 or $40. I installed Google Chrome via APKM installer on Dopinder & works OK, except I can't get it to print (installed HP print services, but that did not solve it). I have Armbian on old Tronsmart S905 2GB/8GB box - on SD card - and I thought that might run Chrome & work with printer. Problem with that system is no DRM / Widevine, which is why I recently bought the Onn & Dynalink boxes. Other problem is developer (Balbes ?) for Armbian on Tronsmart ended support 2 years ago. I would consider a Radxa Zero, but I am not sure if Widevine runs on that yet, and already own RasPi 4b 4GB (audible fan), where Widevine runs fine. Would have bought more RasPi's, but not available ! ]

Any suggestions ?
[Google TV General] MrPlayboy22:
Hello everone, you are my last chance 😇

I am currently trying to unlock my Wade device, yet do struggle already getting an ADB (and FASTBOOT) connection to the device.

- Normally, there should be an RSA approval window popping up (see a sample as picture attached) when putting the device in Developer settings into MTP/ PTP mode. Yet, this does NOT happen. USB debugging is naturally activated. Resetting previously granted authorizations does not change anything. Different USB cables and ports do not change the behavior.

- At the same time, I do NOT see any device in the Windows 7/10 Device Manager (not even hidden or with an exclamation mark!).

- If I put the Wade device into recovery mode (long pressing the side button during startup), I also do NOT get any ADB or Fastboot connection.

As a result, I need some community help:

- Are there any particular Wade specific USB drivers (note: Tried universal drivers, drivers from Google, etc.)?

- And how can I (manually) force the RSA authorization popup to occur granting access?

Thanks ahead!
[Google TV General] npjohnson:
the wiki describes how to install drivers and get connected to the device, but this device doesn't need adb to install at all beyond sideloading the stuff in recovery - but that has no auth window.
[Google TV General] tenfox:
Stock, Lineage-Unoffical or Lineage-Official? New out of the box, or have you already flashed something on it before?

If your problem is on stock or Lineage-Unoffical, and if you have drivers properly installed, I'd suspect the problem is a bad or charge-only cable(s) even though you said you tried other cables already. Make sure you can connect to a different device. You could try an amlogic update utility to see if it connects. You could try wireless. You could start soldering things.

If your problem is on Lineage-Official, it's the dtb issue. Flash the unoffical dtb or wait till official is fixed.

Those are my best guesses, hope it helps.
[Google TV General] j_smolka:
What I've ran into on Dopinder and on Wade was right after flashing recovery and then trying to reboot into it using the same data cable and linux pc I just had used both ADB and fastboot on to get to that point thus far, I would then no longer get fastboot to seem to respond and trying to get boot into recovery the button method plugging in was a no-go at all before getting the ROM loaded when using the same cable directly to the pc. Charge only cable would allow access this standard method to boot into recovery. Located a powered USB hub I had laying around with the original data cable to access recovery without the hub plugged into the pc and then once in recovery, connected to the pc.....still no ADB yet for sideload to work after selecting recovery's enable ADB option until about 30 seconds after entering "apply update from adb" usb connection re-initialized and 'adb devices" showed device appropriately while in sideload, ROM and Magisk loaded fine and booting back into recovery no longer has no issues
[Google TV General] MrPlayboy22:
Thanks @npjohnson - means your proposal is not even utilizing the option of granting the RSA authorization on screen, but only using the hardware button during startup to enter the original device recovery and then utilizing the options provided (enable ADB) that @j_smolka below mentioned? Maybe this was mentioned in the guide, I at least did not understand it in this way, as the hardware button was not/ is not mentioned in the wiki like this ;-) But thanks for the hint, will try it like this as well....

Drivers - according to the wiki - were installed, yet the device was still not recognized. But I ordered another, different USB cable (see below), maybe this will solve the topic together with the hardware button.

Thanks @tenfox - still on stock (as I was not yet able to flash the Linage unofficial). I now ordered another, brand new usb cable with a focus on data transfer (rather than charging). Will try over the weekend with this one and then also start looking into the AMlogic update utility or the wireless option (if needed).

Thanks @j_smolka - good hint! So maybe the ADB does not work, as there is not enough energy provided to the device for running it properly and at the same time using it for data transfers via the same, standard equipped and provided usb cable. So a powered USB is now also on the bucket list!
[Google TV General] MrPlayboy22:
Dear all, just a quick update:

- With a new notebook and a different cable, I was able to unlock the bootloader, flash the dtb and the dtbo partition, install the recovery and sideload LinageOS! So far, so good - thanks for all you support.

BUT....

- Yet, as I did not read properly (my fault!), I did

not

replace the dtbo img from the unofficial version and hence my LinageOs does not work properly (wifi broken).

- I

cannot

jump over the i

nitial internet setting

and then enable the developer settings and USB debugging, hence currently cannot run any ADB/ fastboot commands.

- I

tried

to push the

hardware side button

and then power the device up to boot into recovery, yet this for whatever reason does not work (any hints?)

- Is there a remote control button combination that boots the device into recovery mode? If so, which one?

Any hints, that would give me a chance to either

a) restart the process after the bootloader unlocking or

b) how to get into the Linage Recovery, so that I can wipe the system, connect via ADB and then start again from the partitioning?

Thank you for your support in advance!
[Google TV General] activadroid:
One trick posted in a comment (# I can't remember) was to:

(1) with micro USB cable end plugged into device & USB-A unplugged from PC:

(2) press & HOLD the button on the device.

(3) plug the standard male USB-A end PARTIALLY in to your PC.

(4) KEEP HOLDING button in until you see LED on Device.

(5) Then push USB-A plug all the way in.

(6) Release button on device. (or maybe release button before pushing USB plug rest of the way in).

Anyway, the reason they mentioned this might be required is the device was trying to talk to the PC USB port and interrupted its normal boot mode. It does NOT do that when only connected to +5V & Ground.

I can't remember which device this applied to: Google, Wade or Dopinder (or all 3), but I used it on Wade & Dopinder and it seems to help.

It was a bit tricky to tell how far in, to initially get just the USB power and ground pins, and NOT the data pins, to make contact.

I usually pushed very slowly, and watched the light on my LCD panel change from standby color (amber) to active (white), and STOPPED pushing the USB plug in, and WAITED, at that point (for LED on device).

Tedious, but it worked well enough that I did not quite get to the point of cutting my cable open to install a switch on the data lines.
[Google TV General] :
It may be possible to just flash dtb/dtbo from the unofficial build using burn mode, leaving the rest of the present official installation in place.

Download the windows worldcup driver and update tool (see here).

After these are installed, hold the button (starting a second or so after power is applied) until you have a worldcup burn mode connection.

Then flash dtb (dt.img) ** and dtbo (dtbo.img) from the unoffical build using the update utility.

update partition _aml_dtb dt.img **
update partition dtbo dtbo.img

** Edit: amlogic ota packages typically use the filename dt.img, These builds apparently use the filename dtb.img. Use whatever filename is applicable, given the source package used.

Alternatively, you can use a burn mode connection to get a usb connection to bootloader fastboot;

update bulkcmd "fastboot"

Once you have a bootloader fastboot connection, you can also boot directly to recovery using a local image of the partition, sending it via the fastboot boot command (which uses uboot's bootm to boot the recovery image from ram).

fastboot boot path-to-recovery.img-file
[Google TV General] MrPlayboy22:
Thanks a lot, this did the trick - just "overflashing" the correct dtb.img and dtbo.img from the

un

official build.

For others, struggling with the same, the following hints:

- There was a small typo in @goapy's command. The correct one is as following (a "b" was missing:

update partition _aml_dtb dtb.img
update partition dtbo dtbo.img

- Worldcup Device drivers as proposed by @goapy: https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view

- Flash Tool for Windows from here: https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/windows

Thanks again, @goapy and naturally also @activadroid - you helped me out of a miserable situation :-)
[Google TV General] :
Sorry about that. All amlogic ota updates have the file named that way. I had forgotten the name used in these builds.
[Google TV General] MonoPro9:
Hi,

was waiting for the OTG-Cable to use the Dynalink DL-ATV36 with ethernet. Today i started to unlock the bootloader. Now i wanted to do the next step, to flash the "dbt" & "dbto" partition, like in the instruction, but i couldn't find it. The "/pub/lineageos/full/wade" folder is empty.

Is there some other link to download it?

Is the "wade"-build working properly?
[Google TV General] BTK19:
Unofficial Builds are there the dtb and dtbo are in the zip
[Google TV General] tokoam:
I already have lineage installed but when I run adb devices i get 10.0.0.236:5555 unauthorized and OUSA211XXXXX device . I need to go back to factory to update my linage i must be on a really old build but cant get past this part . I tried to adb kill-server and adb start-server but it doesn't work . still shows 10.0.0.236:5555 unauthorized . My device is a Dopinder btw .
[Google TV General] :
This seems like a pc-side issue, not an issue on the device.

Did you ever use adb to connect to a device at that address? Can you use a different pc?

Did you try;

adb disconnect all
[Google TV General] npjohnson:
deadpool an wade are official again, hopefully we got it all right this time around.

onto dopinder and Sabrina. Hoping to get those shipped soon.
[Google TV General] tokoam:
You were right I was able for it to show just the Onn device on another computer but now when I run adb reboot bootloader the device reboots . However it does not show anything when executing fastboot devices . Any idea's ? Also I might add in device manager when its in fastboot it shows unknown device which i think is why it cant see it in fastboot . Edit was able to install adb fastboot drivers and it installed the drivers . now I went ahead and flashed the the device with the following commands I found in this thread it failed to flash boot.img now the device wont power on at all no power . These are the commands I used

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

fastboot flash:raw boot boot.img

fastboot flash dtb dtb.img

fastboot flash dtbo dtbo.img

fastboot flash logo logo.img

fastboot flash recovery recovery.img

fastboot flash super super.img

fastboot flash vbmeta vbmeta.img

fastboot -w

fastboot reboot

Edit #2 thanks to all these post I was able to revive the unit in recovery mode I forced bootloader mode and reflashed boot.img then it booted to the setup screen . Now on to the last part to flash the newest build of Lineage .... Do I just run the following command after i update my stock andriod os ?

Enable ADB.

adb reboot bootloader

fastboot oem 'setenv lock 10101000;save'

fastboot reboot bootloader

fastboot flashing unlock

fastboot flash dtb lineage-dtb.img

fastboot flash dtbo lineage-dtbo.img

fastboot flash recovery lineage-recovery.img

fastboot reboot-bootloader

fastboot boot lineage-recovery.img

Use button to select "Factory Reset", "Wipe Data", once complete, "Apply Update", "From ADB" ?
[Google TV General] 0x1329029:
Will dopinder and Sabrina become official?
[Google TV General] npjohnson:
When we fix DRM yes
[Google TV General] activadroid:
On wade & dopinder I tried, ' fastboot reboot-bootloader ' did not work - so I stopped using that.

But, ' fastboot boot lineage-recovery.img ' (using actual specific name of the version just flashed) did.
[Google TV General] samsungs3neos3neos3neo:
Hi, will this take time to arrive on the Lineage wiki? The link to the installation package says

Whoops - this page doesn't exist​

This device has no available builds. Please select another device.

LineageOS Downloads

download.lineageos.org

And will the dtb and dtbo files be on the Princeton site (or changed) or packaged in the official zip?
[Google TV General] npjohnson:
On the Princeton site.

And they build respectively Sunday and Monday
[Google TV General] samsungs3neos3neos3neo:
Nice, thanks!! So WiFi works now? And are there any requirements or best practices for using external drives?
[Google TV General] npjohnson:
Yes, wifi being broken was the DTB being messed up by lineage infra.

And not really, should just work.
[Google TV General] samsungs3neos3neos3neo:
Great! Do you know if the remote's button for voice search can be repurposed on a degoogled installation (no gapps)? I'm looking at Konele
[Google TV General] samsungs3neos3neos3neo:
Releases · ewheelerinc/LocalSTT

Android Speech Recognition Service using Vosk/Kaldi and Mozilla DeepSpeech - ewheelerinc/LocalSTT

github.com

for AnySoftKeyboard or Konele
[Google TV General] npjohnson:
You can just change the key layout yeah
[Google TV General] samsungs3neos3neos3neo:
Cool, is that within the general android settings? I haven't bought the Dynalink yet
[Google TV General] npjohnson:
No, you'd have to adb root and edit the file.
[Google TV General] samsungs3neos3neos3neo:
Thanks, I'll try it.

Hello, what does the OTG adapter in the bottom picture do? Could you not connect to the hub directly with a male micro usb to male USB A?
[Google TV General] activadroid:
Does anyone have a list (I assume npjohnson does) of all the hardware differences between wade, dopinder, deadpool & sabrina ?

I found instructions (github) on how to boot ubuntu from USB on sabrina, and wondered if the schematics are close enough that the process might work on dopinder or wade ?
[Google TV General] npjohnson:
Common

- 2 GB RAM

- 8 GB eMMC

- L1 Widevine DRM

wade (the best option):

- s905y2 (g12a)

- IR Remote & IR Support

- GPIO button kicks you into Amlogic burn mode

- BCM BT/Wi-Fi

deadpool:

- s905y2 (g12a)

- BT Remote

- BCM BT/Wi-Fi

- GPIO button kicks you into Android recovery mode

dopinder

- S905x2 (g12a)

- BT Remote

- RTK BT/Wi-Fi

- GPIO button kicks you into Amlogic burn mode

- Likes to spontaneously combust in blue-smoke sometimes

sabrina:

- S905D3G (sm1)

- BT Remote

- GPIO button kicks you into Amlogic BootROM mode

- BCM BT/Wi-Fi (Slightly different version that wade/deadpool, but mostly cross compatible)

As for that ubuntu repo, you can use the ubuntu root-fs but will need a custom dtb, dtbo, and boot image for your specific device. Plus you don't need the exploit Sabrina needs, you can just boot to burn mode and boot it.
[Google TV General] skippyd:
let me know how it goes :cool: very interested in same

more info for you...

GitHub - Calmact/amlogic-s9xxx-armbian: Armbian for Amlogic s905l3a tv box. Support s905x2, s905l3a, s905l3a-b, including install to EMMC and update related functions.

Armbian for Amlogic s905l3a tv box. Support s905x2, s905l3a, s905l3a-b, including install to EMMC and update related functions. - GitHub - Calmact/amlogic-s9xxx-armbian: Armbian for Amlogic s905l3...

github.com

GitHub - Amlogic-Devlopment-PureFusion/android_device_askey_sti6140d360_TWRP-AOSP

Contribute to Amlogic-Devlopment-PureFusion/android_device_askey_sti6140d360_TWRP-AOSP development by creating an account on GitHub.

github.com

Armbian for Amlogic S905X3

I try to use image Armbian_19.11.3_Aml-g12_bionic_legacy_5.3.0_desktop_20191126.img for device with S905X3. TV box is called X96 Air. Unfortunately, I can't make multi boot. I've got error: -- Install /udisk/aml_autoscript.zip ... Verifying update package... E:footer is wrong Update package verif...

forum.armbian.com

driver for dopinder wifi/bt

GitHub - chewitt/RTL8822CS: ** USE RTW88 NOT THIS DRIVER **

** USE RTW88 NOT THIS DRIVER **. Contribute to chewitt/RTL8822CS development by creating an account on GitHub.

github.com

twrp with lots of info...

GitHub - Amlogic-Devlopment-PureFusion/android_device_askey_sti6140d360_TWRP-AOSP

Contribute to Amlogic-Devlopment-PureFusion/android_device_askey_sti6140d360_TWRP-AOSP development by creating an account on GitHub.

github.com
[Google TV General] activadroid:
skippyd - Thank you for the links !

Huge learning curve for me. my background is hardware (PC & microcontrollers), with bits of PIC & Arduino C programming.

I have a feeling that what npjohnson can do in his sleep (and his PC builds in 15 minutes) might take me weeks or months (last time I tried a Linux Mint build or Android build took my old slow PC 6 HOURS and 15 minutes) !
[Google TV General] Jann F:
On wade:

GPIO Button kicks you into Burn Mode IF USB data is connected only. If just power is connected, it will boot into recovery. :)
[Google TV General] npjohnson:
Yup yup
[Google TV General] Jann F:
Just want to make sure my hacky advice gets added to the LineageOS Wiki :P
[Google TV General] 0x1329029:
Just follow this guide to build and install lineage on my onn.

Now I can't enter bootloader(stuck at androidtv logo), fastboot/recovery/system is working but device SN from "adb devices" shown "(no serial number)" and wifi can't be enabled.

Any advice to bring bootloader back?
[Google TV General] 0x1329029:
Looks like it's my fault. Fixed by force syncing repository to build a new rom and sideload again.
[Google TV General] skippyd:
i feel the same and wish he and other would teach us more ... i can do everything needed on the linux or dos side but dealing with *.dtb *.dtb0 I get lost.... if our devices didn't require this like the nexus7 i would already be running and on the mmc instead of usb...
[Google TV General] S1ngl3-x:
Can't install the official ROM for wade because the dtb link is still empty. https://mirror.math.princeton.edu/pub/lineageos/full/wade/

Does anyone know what to do?
[Google TV General] BTK19:
It's inside the rom zip file
[Google TV General] 0x1329029:
Does anyone ever try to use USB DAC on onn?

My DAC is working at 96khz on stock ROM but only showing 48khz on lineageos and no sound.
[Google TV General] S1ngl3-x:
Wade - I rebooted after flashing dtb files and now I am stuck at "dynalink" screen and can't do anything. Did I brick my device?
[Google TV General] ChriMo:
Thanks. Very useful as I'm interested in wade and dopinder. Since wade is more easily (and faster) available in Europe this is the favorite.

However I would like to ask if the IR Remote needs "to see the correct side of the Box" so that IR works? Without BT (on the remote) this seems the only possibility?
[Google TV General] npjohnson:
It has BT on the remote too
[Google TV General] RDS5:
no, with or without bluetooth it seems to be very forgiving as to where im pointing towards it, it usually works even with obstructions as long as im pointing in its relative direction.

also as npjohnson said, it has bluetooth so you might aswell just use that instead..
[Google TV General] samsungs3neos3neos3neo:
Has anyone tried the official 20221023 release for wade? I see both dtb.img and dtbo.img within the lineage zip, so no need to use the wiki's other links?
[Google TV General] npjohnson:
The wiki now has valid links to DTB.

I'm done waiting for lineage's infra to show it so I just linked my site.
[Google TV General] samsungs3neos3neos3neo:
Is there any difference between the DTB and DTBO files inside the official zip and the files at https://download.ods.ninja/Android/lineage/wade/ ?
[Google TV General] wyldwilly:
I'm currently using the following build on dopinder: lineage-19.1-20220908-UNOFFICIAL-dopinder. Except for the DRM issues, it seems to work great! I see there is a new build here: https://download.ods.ninja/Android/lineage/dopinder/

What are the preferred instructions to upgrade to this build? I'll test whatever installation/upgrade methods that are suggested. Also, is the DRM issues fixed? Thanks!