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

[Deleted member 11959327]

Caveat: I won't follow up on any questions. Do this at your own risk. You don't need an OTG cable.

If you can't boot into fastboot mode:

• run `./update partition boot <boot.img>` as root
• run `./update bulkcmd "reset"` (including quotes) as root
• You should now be in fastboot mode

The first step in the quote above flashes boot.img to the boot partition on the emmc.
The second step reboots the device.

This probably won't result in rebooting to fastboot (the bootloader version of fastboot).

Instead of:
update bulkcmd "reset"

Using this command:
update bulkcmd "fastboot"

would immediately load bootloader fastboot (without even rebooting).
And it isn't necessary to flash the boot partition first in order for this to happen.

Notice that there are no questions in this reply, so you won't have to violate your pledge not to follow up on any questions.

 

[Deleted member 12243335]

The first step in the quote above flashes boot.img to the boot partition on the emmc.
The second step reboots the device.

This probably won't result in rebooting to fastboot (the bootloader version of fastboot).

Instead of:
update bulkcmd "reset"

Using this command:
update bulkcmd "fastboot"

would immediately load bootloader fastboot (without even rebooting).
And it isn't necessary to flash the boot partition first in order for this to happen.

Notice that there are no questions in this reply, so you won't have to violate your pledge not to follow up on any questions.

I think you were so obsessed with the first line, you missed this part

For some reason (probably due to earlier experimentation with the mainline kernel) I couldn't boot into recovery without flashing all the images first, so YMMV

 

[Deleted member 11959327]

I think you were so obsessed with the first line, you missed this part

For some reason (probably due to earlier experimentation with the mainline kernel) I couldn't boot into recovery without flashing all the images first, so YMMV

Booting into recovery is one thing, booting (or loading) bootloader fastboot is another.

Whatever is true about your earlier experimentation and the results it produced or the remediation that it required afterwards, it is still the case that the usb burn mode command:

update bulkcmd "reset"

only reboots the device. While the usb burn mode command:

update bulkcmd "fastboot"

immediately loads bootloader fastboot.

You listed a series of steps to get into "fastmode mode". I was merely pointing out, for others reading this thread, that these steps may be incorrect, in so far as using the update utility with the reset command in order to achieve that limited end.

 

[Deleted member 12243335]

Booting into recovery is one thing, booting (or loading) bootloader fastboot is another.

Whatever is true about your earlier experimentation and the results it produced or the remediation that it required afterwards, it is still the case that the usb burn mode command:

update bulkcmd "reset"

only reboots the device. While the usb burn mode command:

update bulkcmd "fastboot"

immediately loads bootloader fastboot.

You listed a series of steps to get into "fastmode mode". I was merely pointing out, for others reading this thread, that these steps may be incorrect, in so far as using the update utility with the reset command in order to achieve that limited end.

You're absolutely right. I should have probably explained how bulkcmd fastboot didn't initially work for me, how I spent an entire evening trying numerous other things to resolve the exact same problem the commenter I replied to was having, and how the only solution that ended up working was very hacky and dumb, that it warranted me making an xda-dev account to post a comment. I realize now the error of my ways.

 

[js8call]

I have bricked my Onn TV box..it only shows the Onn screen..I tried to unbrick with the linux method but no luck..
Im not clear how to run these commands:
"./update xxx"..do I type sh before or just ./update xxx within the terminal?
Also theres an 650mb update and it seems its obliged to update before doing anything further..should I update before the Lineage process or how it can be bypassed?

 

[Deleted member 11959327]

You're absolutely right. I should have probably explained how bulkcmd fastboot didn't initially work for me, how I spent an entire evening trying numerous other things to resolve the exact same problem the commenter I replied to was having, and how the only solution that ended up working was very hacky and dumb, that it warranted me making an xda-dev account to post a comment. I realize now the error of my ways.

Well, if what you described worked, I won't argue with that.

It is difficult to understand how bulkcmd fastboot could fail to work though, as long as there is a burn mode connection. Because it executes directly in uboot instantaneously, without any reboot. This is easiest to see if a uart connection is also available while doing all of these operations. That is the best way to learn what is going on behind the scenes.

Anyway, if anyone wants to try using bulkcmd reset instead of bulkcmd fastboot, it will cause no harm to try.

 

[Deleted member 11959327]

I have bricked my Onn TV box..it only shows the Onn screen..

Also theres an 650mb update and it seems its obliged to update before doing anything further..should I update before the Lineage process or how it can be bypassed?

If it is bricked, how could the update install?

 

[js8call]

Yes..Im sorry for the miswording...
When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..then I added my account and turned on developer mode..there was no oem unlock option..I read the web guide for Windows...I got to boot to the stock recovery..I tried to upload the dot files but it gave me an error..I skipped that step and proceeded to flash the Lineage recovery image..it took it but it shutdown..now I only get the ONN screen..
But in linux I ran lsusb and its listed as a Amlogic device...any help?

If it is bricked, how could the update install

 

[BTK19]

Yes..Im sorry for the miswording...
When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..then I added my account and turned on developer mode..there was no oem unlock option..I read the web guide for Windows...I got to boot to the stock recovery..I tried to upload the dot files but it gave me an error..I skipped that step and proceeded to flash the Lineage recovery image..it took it but it shutdown..now I only get the ONN screen..
But in linux I ran lsusb and its listed as a Amlogic device...any help?

What are dot files. Post in thread '[UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices' https://xdaforums.com/t/unofficial-...-g12-sm1-family-devices.4313743/post-87029813. that is the way to flash lineage

 

[Deleted member 11959327]

When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..

It must have rebooted to install the update immediately after it downloaded.

When an automatic check for updates is made as part of the oobe/setup wizard process during the first boot of the device, it won't continue without first rebooting to install the just downloaded update.

So, if you ever got fully into the OS, the update was very likely installed before that.

 

[js8call]

I installed the Worldcup windows driver..I hold side button until Win7 registered and shows lisusb-win32 USB/Worldcup Drivers and its active . I go adb devices and no device is listed..I adb reboot bootloader and the Win 7 cmd says error : no devices found...the white tiny light on the box is off..what next?

 

[Deleted member 11959327]

When the box has a wordcup connection to your windows pc, abd/fastboot can't communicate with the box.

Use the command line update.exe utility instead.

 

[js8call]

When the box has a wordcup connection to your windows pc, abd/fastboot can't communicate with the box.

Use the command line update.exe utility instead.

GitHub - khadas/utils: Utils/Tools for development

Utils/Tools for development. Contribute to khadas/utils development by creating an account on GitHub.

github.com

this site only has the git linux version..I cant find a standalone windows version,,,anyplace I can find it?...the openlinux2 amlogic site is down

 

[Deleted member 11959327]

Khadas has a copy on github, here.

All of the dlls in the folder are required in addition to the update.exe binary.

Or, attached is a copy previously linked in a prior forum post.

 

[js8call]

Khadas has a copy on github, here.

All of the dlls in the folder are required in addition to the update.exe binary.

Or, attached is a copy previously linked in a prior forum post.

Thank you very much Goapy..I believe this box is bricked beyond repair..now Im NOT getting the ONN screen and if I press and hold the button the white led shows lit once very fast and then turns off..
On Ubuntu, dmesg says theres is a usb thing attached but USBview says a unknown thing is attached..I copied Kadas repo and ran aml-flash but says error : no devices..
Im going to assume that If I dont see the ONN screen anymore, its hardbricked..
Which is sad, 4k Youtube videos were really nice on this box..
Im going to try to exchange the box for another one..will you help me install.Lineage correctly?

 

[p0werpl]

Im going to try to exchange the box for another one..will you help me install.Lineage correctly?

I am sure goapy is the nicest human either side of the Mississippi, but please answer a couple of questions first:

You have already chalked out plans to return Onn #1 because you were unable to unbrick it. What makes you think Onn #2 will not suffer the same fate? Asked differently, what skills have you gained in the intervening time to bring about a different outcome?

Have you read the last few pages (including clear statements by the OP) about how LOS on the Onn box (dopinder) has DRM issues? Based on your request above, I think the answer is clear, but please answer anyway.

What about stock do you not like that you want to install LOS?

 

[js8call]

I am sure goapy is the nicest human either side of the Mississippi, but please answer a couple of questions first:

You have already chalked out plans to return Onn #1 because you were unable to unbrick it. What makes you think Onn #2 will not suffer the same fate? Asked differently, what skills have you gained in the intervening time to bring about a different outcome?

Have you read the last few pages (including clear statements by the OP) about how LOS on the Onn box (dopinder) has DRM issues? Based on your request above, I think the answer is clear, but please answer anyway.

What about stock do you not like that you want to install LOS?

Yes, Im sure he is a good person!
Thinking about what you proposed, I think your right..I only want the following apps installed..
Brave Browser
Flexie
Plex
Kodi
Viper4android
a noads YT app

Thats about what I like to have. I know Viper4andoid needs root SuperSu and busybox
I dont care about Netflix or Disney..I dont use them...
Any help?

 

[Deleted member 11959327]

I believe this box is bricked beyond repair..now Im NOT getting the ONN screen and if I press and hold the button the white led shows lit once very fast and then turns off..

What happened to the worldcup connection that you were getting on your windows pc just a few hours prior?

It's very difficult to brick the onn device beyond repair. It takes something like bootloader corruption or physical hardware failure to do it. Anything less than that can usually be fixed using burn mode, including problems like a recovery bootloop.

 

[js8call]

What happened to the worldcup connection that you were getting on your windows pc just a few hours prior?

It's very difficult to brick the onn device beyond repair. It takes something like bootloader corruption or physical hardware failure to do it. Anything less than that can usually be fixed using burn mode, including problems like a recovery bootloop.

the update.exe is giving a win core 12 dll error. I have updated my Win7 to SP2 and I still get the error..I can try on my win10 pc after work..but Im not getting the Onn screen anymore..I plug the box with the button pressed, I see a quick white blip and Win7 sees the worlcup device..but the Kadas update tool is not working becuase of the dll error..

 

[Deleted member 11959327]

.but the Kadas update tool is not working becuase of the dll error..

Did you also try the version of update.exe attached to forum post in amlogic.zip?