[OFFICIAL/UNOFFICIAL] LineageOS 20 for Amlogic GXL/GXM/G12*/SM1/NE Family Devices

Search This thread
By:
Advanced…
Functioner

Functioner

Senior Member
Jan 16, 2023
237
111
ali387 said:
I get error at: update.exe 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]Err:bulkInReply=[]
ERR: AmlUsbBulkCmd failed!
Click to expand...
Click to collapse

That response is the expected response to "update bulkcmd fastboot". After running the command, check if the usb connection has actually successfully changed to a fastboot connection.

fastboot devices

If the fastboot device is not shown, try immediately executing "update bulkcmd fastboot" again. Sometimes it takes another try. If the fastboot device is shown, proceed on to whatever fastboot commands.
 
  • Like
Reactions: ali387
A

ali387

Member
Dec 3, 2018
29
9
ali387 said:
I missed one key warning in the instructions. I used my device right out of the box without updating it. I only powered it up to set the USB debugging on and went my merry way to install LOS 20.

The instructions say that i need to update my device up to android 12.

I have found the original factory image here on another thread. I have reverted back to original image and now running through update process.

I will retry installing LOS 20 after updates are done.
Click to expand...
Click to collapse
I retried the LOS 20 install steps after upgrading to latest patches on the device. Same result .
 
A

ali387

Member
Dec 3, 2018
29
9
Functioner said:
That response is the expected response to "update bulkcmd fastboot". After running the command, check if the usb connection has actually successfully changed to a fastboot connection.

fastboot devices

If the fastboot device is not shown, try immediately executing "update bulkcmd fastboot" again. Sometimes it takes another try. If the fastboot device is shown, proceed on to whatever fastboot commands.
Click to expand...
Click to collapse
Thanks. Will give it a try.
 
A

ali387

Member
Dec 3, 2018
29
9
tried running multiple times immediately but still same result.

Is the firmware version shown by update.exe identify right?
 

Attachments

  • wade_3.JPG
    wade_3.JPG
    97.1 KB · Views: 37
M

mmortal03

Senior Member
Apr 15, 2014
443
97
Just FYI, the previous Onn device just got a new maintenance release on stock. (February 5, 2023 security patch)
 
  • Like
Reactions: BTK19
S1ngl3-x

S1ngl3-x

Member
Jun 10, 2022
26
15
talksickisil said:
It’s been a bit since I’ve downloaded a build or even used “wade” one thing that has came in my absence maybe: but how do I reboot after holding down the power key? I get the 3 circles now. (Power off, restart, and screenshot) I can’t figure out how to make a selection. I’m sure I’m missing something obvious here? Is it an issue using the onn remote with the dynalink box now? I prefer the full Bluetooth of the white onn remote and haven’t had this issue previously. I have a wireless keyboard and mouse plugged into the OTG but it would be nice to use the remote for power cycling. Thanks in advance for setting me straight
Click to expand...
Click to collapse
Is this still broken only on our wade devices or is the issue relevant for everybody?
 
N

npjohnson

Recognized Developer
May 3, 2014
4,464
4,953
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
mmortal03 said:
Just FYI, the previous Onn device just got a new maintenance release on stock. (February 5, 2023 security patch)
Click to expand...
Click to collapse
everyone - won't give this advice out often, but for stock updates for these devices, pls @ me, I want to get these merged as quick as possible.

Want to avoid the "wade got 12 and I didn't know for 3 months" issue haha

dopinder update is integrated for the next build. Thx for the heads up.
 
  • Like
Reactions: mmortal03 and BTK19
A

ali387

Member
Dec 3, 2018
29
9
npjohnson said:
try this on a USB2.0 HUB or a diff cable/port.
Click to expand...
Click to collapse
I tried different cables and another PC with USB 2.0 port but no success.
What helped me move along was your suggestion on reddit to another person with similar issue: on wade.

update bulkcmd "reboot bootloader"

After that I ran:
fastboot flash recovery recovery.img
fastboot boot recovery.img

Now I can reboot to recovery but it has uncovered couple of issues with my device:

1. tapping on side button does not move to next menu item on recovery screen, I have to use remote to move the selection to factory reset.

2. once 'factory reset' is selected then I long press the side button. It turns the 'factory reset' to green/teal but no prompt comes up to format data. or any response from the recovery screen.

Has anyone run into this problem? Any suggestions to try?


PS: I have previously followed these instructions successfully to install LineageOS on to Onn device. (of course different image files)


PS2:

Here is getvarall output for my device (i case if this device is different from previous ones):

[root@fireiso ~/Downloads]# fastboot getvar all
(bootloader) hw-revision:0
(bootloader) battery-voltage:4
(bootloader) is-userspace:no
(bootloader) is-logical:data:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:super:no
(bootloader) is-logical:boot:no
(bootloader) is-logical:system:yes
(bootloader) is-logical:vendor:yes
(bootloader) is-logical product:yes
(bootloader) is-logical: odm:yes
(bootloader) slot-count:0
(bootloader) max-download-size:0x08000000
(bootloader) serialno:WUSA23******
(bootloader) product:franklin
(bootloader) unlocked:yes
(bootloader) has-slot:data:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:boot:no
(bootloader) has-slot:system:no
(bootloader) has-slot:vendor:no
(bootloader) has-slot product:no
(bootloader) has-slot odm:no
(bootloader) secure:no
(bootloader) super-partition-name:super
(bootloader) version-baseband:N/A
(bootloader) version-bootloader:01.01.221216.094717
(bootloader) partition-size:boot:0000000001000000
(bootloader) partition-size:metadata:0000000001000000
(bootloader) partition-size:misc:0000000000200000
(bootloader) partition-size:super:0000000064000000
(bootloader) partition-size:data:0000000123dfc000
all: version:0.4
Finished. Total time: 2.259s
 

Attachments

  • wade_4.JPG
    wade_4.JPG
    113.7 KB · Views: 33
Last edited:
N

npjohnson

Recognized Developer
May 3, 2014
4,464
4,953
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
ali387 said:
I tried different cables and another PC with USB 2.0 port but no success.
What helped me move along was your suggestion on reddit to another person with similar issue: on wade.

update bulkcmd "reboot bootloader"

After that I ran:
fastboot flash recovery recovery.img
fastboot boot recovery.img

Now I can reboot to recovery but it has uncovered couple of issues with my device:

1. tapping on side button does not move to next menu item on recovery screen, I have to use remote to move the selection to factory reset.

2. once 'factory reset' is selected then I long press the side button. It turns the 'factory reset' to green/teal but no prompt comes up to format data. or any response from the recovery screen.

Has anyone run into this problem? Any suggestions to try?


PS: I have previously followed these instructions successfully to install LineageOS on to Onn device. (of course different image files)
Click to expand...
Click to collapse
Use the remote, use the d-pad to navigate and then the power button on the remote to select
 
  • Like
Reactions: talksickisil and ali387
N

npjohnson

Recognized Developer
May 3, 2014
4,464
4,953
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
N

npjohnson

Recognized Developer
May 3, 2014
4,464
4,953
Orlando, FL
Verizon Samsung Galaxy S4
Nexus 7 (2013)
fepij52921 said:
I was thinking of the official builds actually, are those supported by other developers?
Click to expand...
Click to collapse
Oh there's 0 chance of that.

It took the lineage infrastructure team two years to deploy the new download portal, very doubtful that something like that would be adapted, it would also require extensive wiki changes, and a much more systematic approach to changing it out.

Don't see it happening officially ever tbh.
 
You must log in or register to reply here.

Similar threads

N
  • Locked
[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices
Replies
2K
Views
248K
karandpr
karandpr
N
[RELEASE] Chromecast with Google TV Bootloader Unlock
Replies
316
Views
63K
dante_ov
dante_ov
M
How To install Google TV Launcher on Android 9 TV
Replies
19
Views
20K
m12v345
m12v345
Endex
Screen size change on Lineage OS 20 TV
Replies
2
Views
2K
X
Xibeian
ichyb3ll
Google TV file manager problem!!
Replies
59
Views
19K
v4mpi
v4mpi

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    N
    npjohnson
    darkvoid said:
    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.
    Click to expand...
    Click to collapse
    I got them!

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

    Thanks.
    View
    2
    N
    npjohnson
    apropper said:
    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?
    Click to expand...
    Click to collapse

    w00cash said:
    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.
    Click to expand...
    Click to collapse

    ramuka said:
    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.
    Click to expand...
    Click to collapse
    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.
    View
    2
    D
    darkvoid
    npjohnson said:
    We don't support it - if someone donates one I will send it to a developer to bring up, thought.
    Click to expand...
    Click to collapse
    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.
    View
    2
    BTK19
    BTK19
    zoomer296 said:
    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.
    Click to expand...
    Click to collapse
    Here is a link to the firmware. Post in thread 'Walmart ONN Google TV' https://forum.xda-developers.com/t/walmart-onn-google-tv.4586587/post-88539531
    View
    2
    zoomer296
    zoomer296
    npjohnson said:
    Really one of us just needs to get our hands on it, we already have a work in progress tree for that generation of device, I just personally haven't had time
    Click to expand...
    Click to collapse
    Y'all still need one? I'd be happy to grab one and send it to whoever.
    View
  • 10
    N
    npjohnson
    lineage-os-logo.png

    Amlogic GXL/GXM/G12*/SM1 Family Devices
    Code: 
    - Your warranty is now void.
- You have been warned.
- Use at your own risk.

    Introduction:
    This is the Official Lineage OS 20 thread for the Amlogic GXL/GXM/G12*/SM1 SoC family of devices.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:

    Official Builds:
    • deadpool - Google ADT-3
    • wade - Dynalink TV Box (4K)
    • m5 - Banana Pi M5 (Android TV)
    • odroidc4 - ODROID C4 (Android TV)
    • radxa0 - Rock Pi Radxa Zero (Android TV)

    Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.

    Unofficial Builds:
    • deadpool - Google ADT-3
    • dopinder - Walmart Onn UHD Box
    • sabrina - Chromecast with Google TV
    • wade - Dynalink TV Box (4K)
    • m5 - Banana Pi M5 (Android TV)
    • odroidc4 - ODROID C4 (Android TV)
    • radxa0 - Rock Pi Radxa Zero (Android TV)
    Additionally, with no Google apps, and no support provided, full-android builds are available for devkits:
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Recent apps/Multitasking menu doesn't launch.
    • (sabrina) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
    • (dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
    Notes:
    • GApps are baked in on the Android TV Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
    • GApps are NOT included on the following targets due to space restrictions: `m5_tab`, `odroidc4_tab`, `radxa0_tab`. No, I will not be providing tablet style builds for any device that isn't a devkit - it just doesn't make sense.
    • Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
    • On the unofficial OTA is provided the same way officials would have them.
    • Find any more on an official build? Report them according to this guide.
    FAQ:
    • Does L1 Widevine DRM break when I unlock my bootloader?

      Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.

    • Can I haz Netflix?

      Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.

    • Is this Android TV or Google TV?

      Android TV, with some of the better components of Google TV.

    • Can I go back to stock and relock the bootloader?

      Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.

    • Are these the stock codenames for these devices?

      Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.

    • Does it pass SafetyNet?

      Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.

    • Does the stock remote work?

      Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!

    • Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?

      Nope.

    • I have a very similar device! Can I install these builds and use them?

      No. Please don't do that. You will brick your device, as we include firmware and bootloader images.

      If you're a developer looking to help port to a new device, contact me.

    Kernel Source (NE): https://github.com/LineageOS/android_kernel_amlogic_linux-5.4
    Kernel Source (G12*/SM1): https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
    Kernel Source {GXL/GXM): https://github.com/LineageOS/android_kernel_amlogic_linux-4.9-pie

    Contributors:
    • npjohnson
    • bgcngm
    • stricted
    • webgeek1234
    • deadman96385
    • trautamaki
    • luca020400
    • aleasto
    • chrmhoffmann
    • highwaystar
    • mikeioannina
    View
    7
    N
    npjohnson
    Good news for all - the new ONN box and the newer generation of devices can be supported by the current tree.

    Will just need some work.

    We will 100% need the ADT-4 to be released though.
    View
    7
    N
    npjohnson
    Official builds of 20 for deadpool/wade will ship within a week!
    View
    4
    N
    npjohnson
    sjustinas said:
    I would say probably yeah. I am not an expert on those matters though - not sure if there are any drawbacks. IIRC stock ROM's "Droid Settings" app eventually gained this option (Auto-HDR depending on the source), the default "HDR always on" behavior was perhaps a bit of a mistake.
    Click to expand...
    Click to collapse
    done. Next build will have it.
    View
    3
    TTcell
    TTcell
    npjohnson said:
    Good news for all - the new ONN box and the newer generation of devices can be supported by the current tree.

    Will just need some work.

    We will 100% need the ADT-4 to be released though.
    Click to expand...
    Click to collapse
    Fingers crossed that there won't be any problems with L1 (widevine) and the 2nd generation ONN Google TV box.
    View

New posts