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

[MrPlayboy22]

I have had my WiFi broken by updates many times, and what worked for me every time was to flash previous known-good DTB and DTBO. Use aml-flash-tool as described here. You don't need to follow all the steps, for me it was enough to:

1. Turn on wade while holding the side button (to enter AMLogic burn mode)
2. ./update bulkcmd fastboot
3. fastboot flash dtb dtb.img
4. fastboot flash dtbo dtbo.img
5. fastboot reboot

The DTB/DTBO files I use are from lineage-19.1-20221023-nightly-wade-signed.zip

Thanks @sjustinas - much appreciated and sorry for getting back so late to you (I was on a business trip).
I tried now to get the DTB(O) files according to your description (which seems to be for Linux, including the tool). Very sadly, I only have Windows (10) available. Would you mind guiding me to a tool (and respective commands) for Windows? Thanks a lot in advance for your kind support again to get my box working again - very much appreciated!

 

[sjustinas]

Thanks @sjustinas - much appreciated and sorry for getting back so late to you (I was on a business trip).
I tried now to get the DTB(O) files according to your description (which seems to be for Linux, including the tool). Very sadly, I only have Windows (10) available. Would you mind guiding me to a tool (and respective commands) for Windows? Thanks a lot in advance for your kind support again to get my box working again - very much appreciated!

Yeah, it seems like aml-flash-tool is only available for Linux. I am not sure what the equivalent for Windows is. If you are at all comfortable with Linux, you could boot a live USB of Ubuntu and use that.

 

[MrPlayboy22]

Yeah, it seems like aml-flash-tool is only available for Linux. I am not sure what the equivalent for Windows is. If you are at all comfortable with Linux, you could boot a live USB of Ubuntu and use that.

Thanks @sjustinas - will try to get a USB stick up and running. A pitty, it is not available for Windows.
@npjohnson - would you potentially have a Windows (10) working solution to the issue, as this might happen to other users as well? Thanks ahead

 

[npjohnson]

Thanks @sjustinas - will try to get a USB stick up and running. A pitty, it is not available for Windows.
@npjohnson - would you potentially have a Windows (10) working solution to the issue, as this might happen to other users as well? Thanks ahead

There is a flash-tool but I know nothing about it. AML Burning Tool

 

[itchydroid]

Thanks @sjustinas - will try to get a USB stick up and running. A pitty, it is not available for Windows.
@npjohnson - would you potentially have a Windows (10) working solution to the issue, as this might happen to other users as well? Thanks ahead

After soft-bricking my ONN devices I was able to recover on windows 10 using the method above but I used the windows flash tool from https://github.com/osmc/aml-flash-tool. There is a download for the Windows tool under https://github.com/osmc/aml-flash-tool/tree/master/tools/windows. You will need to ensure you have the right drivers installed first which you can get from https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view

Make sure that you connect the hdmi to tv and the other to pc/laptop so that if it boots into the bootloader gui, you can navigate it.

On some occasions I got a blank screen or just the ONN logo but no fastboot. In this case i issued the 'update bulkcmd fastboot' command and was able to enter into fastboot mode.

EDIT: Also you might need to run fastboot as administrator on the windows console. Im not 100% sure as I am a linux guy . I just use a windows laptop to do device/firmware flash and recoveries because a lot of the these tools are usually windows.

 

[endera]

So anyone have this working on a radxa zero ?

 

[MrPlayboy22]

After soft-bricking my ONN devices I was able to recover on windows 10 using the method above but I used the windows flash tool from https://github.com/osmc/aml-flash-tool. There is a download for the Windows tool under https://github.com/osmc/aml-flash-tool/tree/master/tools/windows. You will need to ensure you have the right drivers installed first which you can get from https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view

Make sure that you connect the hdmi to tv and the other to pc/laptop so that if it boots into the bootloader gui, you can navigate it.

On some occasions I got a blank screen or just the ONN logo but no fastboot. In this case i issued the 'update bulkcmd fastboot' command and was able to enter into fastboot mode.

EDIT: Also you might need to run fastboot as administrator on the windows console. Im not 100% sure as I am a linux guy . I just use a windows laptop to do device/firmware flash and recoveries because a lot of the these tools are usually windows.

Dear @itchydroid - thanks for your detailed help and sorry for coming back again to you.... I still struggle slightly ;-)

What I have done (on Windows 10):
- Installed the drivers as per your link
- Installed the windows files of the AML-flash-tool as per your link
- Connected via HDMI to the TV and via USB (with a proper USB cable) to the laptop
- Running the console with local Admin rights (see below)

Where is the issue
- When running the console, I get the following error message:
Microsoft Windows [Version 10.0.19045.2486] (c) Microsoft Corporation. All rights reserved. C:\Windows\system32>cd C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9 C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>update bulkcmd fastboot AmlUsbBulkCmd[fastboot] usbReadFile len=512,ret=-5 error_msg=libusb0-dll:err [submit_async] submitting request failed, win error: A device attached to the system is not functioning. [AmlUsbRom]Err:return len=-1 < strLenBusy 11 [AmlUsbRom]Inf:bulkInReply ERR: AmlUsbBulkCmd failed! C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>


I feel like I am not too far away - yet still too far away to get my Wifi issues sorted :-(
By the way: With the AMLogic USB Burning Tool, I see the device connected. So the burning mode seems to be "correct".

Could you please guide me/ help me? Thanks a lot!!!


Screenshots of the setting:
- Driver

- Console:

 

[itchydroid]

Dear @itchydroid - thanks for your detailed help and sorry for coming back again to you.... I still struggle slightly ;-)

What I have done (on Windows 10):
- Installed the drivers as per your link
- Installed the windows files of the AML-flash-tool as per your link
- Connected via HDMI to the TV and via USB (with a proper USB cable) to the laptop
- Running the console with local Admin rights (see below)

Where is the issue
- When running the console, I get the following error message:
Microsoft Windows [Version 10.0.19045.2486] (c) Microsoft Corporation. All rights reserved. C:\Windows\system32>cd C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9 C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>update bulkcmd fastboot AmlUsbBulkCmd[fastboot] usbReadFile len=512,ret=-5 error_msg=libusb0-dll:err [submit_async] submitting request failed, win error: A device attached to the system is not functioning. [AmlUsbRom]Err:return len=-1 < strLenBusy 11 [AmlUsbRom]Inf:bulkInReply ERR: AmlUsbBulkCmd failed! C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>


I feel like I am not too far away - yet still too far away to get my Wifi issues sorted :-(
By the way: With the AMLogic USB Burning Tool, I see the device connected. So the burning mode seems to be "correct".

Could you please guide me/ help me? Thanks a lot!!!


Screenshots of the setting:
- Driver
View attachment 5807803

- Console:
View attachment 5807805

I think you can ignore the failure. I get the same thing. After the failure, if I run "fastboot devices" the box should show up.

EDIT: After the failure, you should hear the windows usb "disconnect" sound and a short while later, the reconnect sound. This is the device switching to allow fastboot to work.

 

[MrPlayboy22]

I think you can ignore the failure. I get the same thing. After the failure, if I run "fastboot devices" the box should show up.

EDIT: After the failure, you should hear the windows usb "disconnect" sound and a short while later, the reconnect sound. This is the device switching to allow fastboot to work.

THIS DID IT! THANK YOU VERY MUCH
You are my hero!!!

 

[mediavieja]

Hi guys, its been a while since the last time i got into the forums but i need help with my Onn Tv Box.

I was following the guide from https://wiki.oddsolutions.us/devices/dopinder/install to flash lineos on my tv box, i unlocked the bootloader and then downloaded the dtb.img file only from the link, but couldnt find the dtbo.img file, it said the file didnt exists, so i flashed the lineage-19.1-20221024-dtb-dopinder.img and after that my box was no longer being recognized by windows, nor adb or fastboot and everytime i reboot the box is just sitting there at the onn. screen, is there a way to recover my box?

Edit1: i followed this guide https://forum.xda-developers.com/t/...-g12-sm1-family-devices.4313743/post-87830141 to flash all 3 images as it says, but when i do the update.exe bulkcmd fastboot i get the following error:

and heres the previous screen with all 3 imgs flashed properly

so i dont know what else to do :-(

Edit2: Fix it, i followed @itchidroid advice and ignore the error after runing the update bulkcmd fastboot command, so i tried fastboot devices and indeed it was working properly, after that i just finished the update process and everything is running now without issues

 

[mediavieja]

A question tho, how do i get back to the original firmware and all in case something is not working with LineageOS? and is there a way to run Netflix and Prime Video on this? i installed the apps from the play store but when i try to play any content, it hits me with an error :-(

Edith1: as sson as Google app gets updated, restart the deice and should go to Google TV interface

 

[activadroid]

A question tho, how do i get back to the original firmware and all in case something is not working with LineageOS? and is there a way to run Netflix and Prime Video on this? i installed the apps from the play store but when i try to play any content, it hits me with an error :-(

On the first page of all this, It is stated that 'L1' not working for dopinder and a couple others.
That means that hardware supported DRM not working.
Same problem on my Onn / dopinder.
So, on npjohnsons recommendation, I bought a Dynalink (around $40 at that time), installed wade UNofficial version of LineageOS, and it works great with DRM.

 

[mediavieja]

On the first page of all this, It is stated that 'L1' not working for dopinder and a couple others.
That means that hardware supported DRM not working.
Same problem on my Onn / dopinder.
So, on npjohnsons recommendation, I bought a Dynalink (around $40 at that time), installed wade UNofficial version of LineageOS, and it works great with DRM.

Ya hehe, after a bit more reading found out it definetly doesnt work yet :-( had to go back to stock while they manage to make it work

 

[itchydroid]

I just bought a dynalink (wade) device and trying to flash the LOS unofficial 20 on it. I followed the instructions as I have done also on 2 dopinder (ONN) devices. I can get into the LineageOS recovery fine but after following I cannot navigate using the button. I can only press and hold the button down which highlights "Reboot system now" by turning the selection green but nothing happens. Suprisingly I can use the remote control to navigate up and down on the LOS recovery, but when I hold down the circle (o) button, it does the same - just highlights the command green and thats it. So I cannot do `adb sideload` because in recovery I cannot select "Apply Update". I can only highlight it. I then tried to do the same with LOS19 recovery, but its doing the same thing. Am I missing sometime? The button appears to be working fine as it allows me to get into fastboot mode and reboot fine.

 

[BTK19]

I just bought a dynalink (wade) device and trying to flash the LOS unofficial 20 on it. I followed the instructions as I have done also on 2 dopinder (ONN) devices. I can get into the LineageOS recovery fine but after following I cannot navigate using the button. I can only press and hold the button down which highlights "Reboot system now" by turning the selection green but nothing happens. Suprisingly I can use the remote control to navigate up and down on the LOS recovery, but when I hold down the circle (o) button, it does the same - just highlights the command green and thats it. So I cannot do `adb sideload` because in recovery I cannot select "Apply Update". I can only highlight it. I then tried to do the same with LOS19 recovery, but its doing the same thing. Am I missing sometime? The button appears to be working fine as it allows me to get into fastboot mode and reboot fine.

use the power button to select stuff in recovery

 

[itchydroid]

use the power button to select stuff in recovery

Silly me and thank you @BTK19. I was using (o) button on the remote and also tried the button on the device itself (just as its done on the dopinder ONN device). All is well now.

Just wondering, if I didnt have a remote paired with the device, would I be SOL to activate the menu item?

 

[BTK19]

.

 

[General_Mayhem]

Trying to install this on Dopinder on firmware 1.01.36. adb reboot bootloader just powers it off. I can use adb reboot recovery (which shows 'No Command') and use the button on the device to select bootloader but it just powers off.

I didn't see an option in dev options for OEM unlock. Safe to assume I'm on the wrong version of the firmware?

 

[karandpr]

Thread closed as per OP request @npjohnson

- XDA Staff