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

[npjohnson]

the link is not working

Try again

 

[instylz]

Can anyone tell if the discussed devices have any problems with chargers more powerful than recommended 1000mA?
The power supply for dopinder is piece of garbage, but nowadays it's not too easy to find a high-quality replacement with equal power, so I would like to power it with 2.4A, but still afraid to burn something.

Not sure why nobody replied to this. It's completely safe. Your device will downregulate it's charge to match what it was designed to accept.

 

[kennkanniff]

Not sure why nobody replied to this. It's completely safe. Your device will downregulate it's charge to match what it was designed to accept.

You replied... Thanks for the info, good to know.

 

[Big Dumb Object]

Not sure why nobody replied to this. It's completely safe. Your device will downregulate it's charge to match what it was designed to accept.

Thank you! I really still waited for any response, but was afraid to force my inquiry too much. Now I can burn upgrade my Onn with more confidence.

 

[Deleted member 11959327]

After reading #853, and @kennkanniff 's advice, I was able to upload 18.1 recovery again without error. Going to order a usb-c adapter, to boot ubuntu and try to dd the factory recovery.

./update partition recovery lineage-18.1-20220324-recovery-sabrina.img

Flashed recovery without errors.

You can flash any recovery partition image with the update utility. You can use it instead of dd to flash the factory recovery.

Had to use the Exploit from here to be able to flash again. But maybe just bad luck.

Even after flashing 18.1 again, still stuck at bootloop and no working fastboot.

Yeah! Thanks for your help. Seemed to work, but still bootloop and not able to enter fastboot.

With the exploit that you reference above, you can also use the update utility to start bootloader fastboot directly.

./update bulkcmd fastboot

You could try erasing the data and cache partitions (using bootloader fastboot) to see if the 18.1 recovery (that is already flashed) will then be able to load. That has worked for me before.

Or, describe the state that your device was in before things went wrong. Did it have a previous version of los or the factory os installed?

 

[espchl]

thanks for your help @goapy

You can flash any recovery partition image with the update utility. You can use it instead of dd to flash the factory recovery.

That makes sense. Good to know.

With the exploit that you reference above, you can also use the update utility to start bootloader fastboot directly.

./update bulkcmd fastboot

You could try erasing the data and cache partitions (using bootloader fastboot) to see if the 18.1 recovery (that is already flashed) will then be able to load. That has worked for me before.

When in USB Burnmode, I get errors while trying to use fastboot;

./update bulkcmd fastboot
AmlUsbBulkCmd[fastboot]
[AmlUsbRom]Inf:bulkInReply failed:
ERR: AmlUsbBulkCmd failed!

when in bootloader-mode(?) (holding button while powering device), the fastboot command just times out:

./update bulkcmd fastboot
AmlUsbBulkCmd[fastboot]
AM_REQ_BULK_CMD_Handler ret=-110,blkcmd=fastboot error_msg=error sending control message: Connection timed out
[AmlUsbRom]Err:rettemp = 0 buffer = [fastboot]
ERR: AmlUsbBulkCmd failed!

Or, describe the state that your device was in before things went wrong. Did it have a previous version of los or the factory os installed?

Device was new out of box (MFG 09/2020) with factory os installed.

Edit:
Is it somehow possible, to flash the factory image with "update" and start from scratch?

Edit2:
Oh dear, I'm sorry... After reading the instructions again, I realized that I missed

fastboot oem unlock

.

 

[Deleted member 11959327]

When in USB Burnmode, I get errors while trying to use fastboot;

./update bulkcmd fastboot
AmlUsbBulkCmd[fastboot]
[AmlUsbRom]Inf:bulkInReply failed:
ERR: AmlUsbBulkCmd failed!

That is the expected normal response when "./update bulkcmd fastboot" is executed successfully, the "failed!" notice notwithstanding.

After executing the above, you should immediately be able to use bootloader fastboot, without doing anything else at all whatsoever. You just use it right then, after the result above is displayed, without touching the device or rebooting.

Edit2:
Oh dear, I'm sorry... After reading the instructions again, I realized that I missed

fastboot oem unlock

.

That part of the instructions is sort of a generic instruction that doesn't really apply to sabrina or any of the supported devices.

The device may have already been unlocked if you previously ran the original exploit script. You can check it at any time with;
fastboot getvar unlocked
or
fastboot getvar all

 

[espchl]

That is the expected normal response when "./update bulkcmd fastboot" is executed successfully, the "failed!" notice notwithstanding.

After executing the above, you should immediately be able to use bootloader fastboot, without doing anything else at all whatsoever. You just use it right then, after the result above is displayed, without touching the device or rebooting.

Even though it's not possible to execute any fastboot commads. You talk about executing them through "bulkcmd fastboot" right?
All I get is this same error. For example:

./update bulkcmd  fastboot getvar unlocked
AmlUsbBulkCmd[unlocked]
[AmlUsbRom]Inf:bulkInReply failed:
ERR: AmlUsbBulkCmd failed!

The same goes for using the fastboot commands in quotation marks.

Using fastboot on my computer doesn't detect the device at all.

The device may have already been unlocked if you previously ran the original exploit script. You can check it at any time with;
fastboot getvar unlocked
or
fastboot getvar all

Thank you. Yes. I'm pretty sure the exploit worked and the device was successfully unlocked. I flashed Lineage 19.1 using adb through Lineage recovery.

It's maybe time to stop flooding this thread and open a new one...

That part of the instructions is sort of a generic instruction that doesn't really apply to sabrina or any of the supported devices.

Aight. Thatnks for clarification.

 

[Deleted member 11959327]

Even though it's not possible to execute any fastboot commads. You talk about executing them through "bulkcmd fastboot" right?

No, the fastboot commands are not executed through the update utility.

They are executed using the fastboot binary directly.

What executing "./update bulkcmd fastboot" does is change the usb connection from using the worldcup drivers to using the fastboot/adb drivers.

You're done with update then, and then you run the fastboot binary directly.

If using the fastboot binary directly doesn't work, and you're sure that you have the fastboot/adb (android) driver installed, sometimes it takes a second execution of "./update bulkcmd fastboot" to make it work.

If the fastboot binary won't run directly even after one or two executions of "./update bulkcmd fastboot", then I'm at a loss and have no other ideas, except to say that you can use the update utility to do pretty much everything that bootloader fastboot can do. So, not much is lost if you can't access bootloader fastboot but can access burn mode and use the update utility.

 

[Wagmans]

Thanks! It's too bad that usb burning mode is increasingly being disabled in new model devices. The askey ASK-STI6220 (S905X4) doesn't have it. The uboot menu is missing "update - Enter v2 usbburning mode". They've replaced it with a distinct version of fastboot (different than bootloader fastboot and fastbootd). Even masking the rom brings up only this mini version of fastboot. And it is no where near as capable as usb burning mode.

I've had one of these Fios Stream TV Gen2 sitting around for a while- now that Coreelec supports S905x4 devices I'm wondering if you've gotten anywhere with it? You should at least be able to boot off a USB flashdrive- I'm not even talking about rooting it. I can't even figure out how to get into recovery mode reliably.

 

[Deleted member 11959327]

I've had one of these Fios Stream TV Gen2 sitting around for a while- now that Coreelec supports S905x4 devices I'm wondering if you've gotten anywhere with it? You should at least be able to boot off a USB flashdrive- I'm not even talking about rooting it. I can't even figure out how to get into recovery mode reliably.

This should probably be discussed in a different thread. But to answer briefly, the post to which you responded was merely about modern amlogic SoCs (such as the X4, Y4 and others) replacing "v2 usbburning mode" with "Amlogic DNL protocol". Askey's sti6220d315 (verizon stream tv v2) is one device to which this applies. I describe this slightly more thoroughly in this thread.

Whatever "factory" mode may be used to recover a device is separate and apart from other amlogic features.

The sti6220d315's bootloader is readily unlocked, and the device does not use secure boot or an encrypted bootloader. The button on the top of the device will force an adnl (Amlogic DNL protocol) connection if the usb c port is connected to a host computer, or will reboot to recovery if the usb c port is not connected to a host computer. Note that the usb a port can only be used for peripherals, not for a slave connection.

Overall, running an alternate os on the sti6220d315 should be possible and straightforward, but I haven't done it yet.

 

[npjohnson]

People who brick their Sabrina - here's a gift: https://github.com/npjohnson/sabrina-unlock/blob/main/repair.sh

This will repair pretty much any Sabrina that is broken.

 

[npjohnson]

Additionally, dopinder, wade, and Deadpool all boot now.

 

[curryrice71]

Additionally, dopinder, wade, and Deadpool all boot now.

Thank you! I see this build from 2022-05-15 lineage-19.1-20220515-UNOFFICIAL-dopinder.zip
should I wait until the next build comes out to try it on dopinder?

 

[TabascoJoe]

Latest 19.1 image and recovery are working...
It was a lot of trial and error (dont ask)
but after an hour the dopinder is working
ty

 

[RDS5]

Latest 19.1 image and recovery are working...
It was a lot of trial and error (dont ask)
but after an hour the dopinder is working
ty

how?
im on wade and ive been waiting for a way to get 19.1 working with its recovery, since i dont wanna fiddle with the 18.1 recovery.
how did you manage to do it? unless its device specific...

 

[TabascoJoe]

how?
im on wade and ive been waiting for a way to get 19.1 working with its recovery, since i dont wanna fiddle with the 18.1 recovery.
how did you manage to do it? unless its device specific...

I think it is...
The instructions talked about flashing dtb and the dtbo partition, so I did that...
Other than that, dont ask... a lot of reboots and reflashes to get to the recovery, but finally it worked
Proof attached

 

[Deleted member 11959327]

Additionally, dopinder, wade, and Deadpool all boot now.

Were the contents of the 20220515 url links for these builds changed to contain the fixes, or should we wait for url links with a later date?

 

[npjohnson]

The existing builds were 100% functional.

People weren't flashing dtb/dtbo. Absolutely necessary.

I put it in the wiki.

The only _truly_ broken one is Sabrina.

 

[curryrice71]

I'm trying this on my Walmart ONN 4K box/dopinder. I got to this point in the steps:

Run sudo ./update bulkcmd fastboot and enter your sudo password.

I'm not sure it works though, I get this:

[update]No [WorldCup Device] device after scan
[update]ERR(L1095):can not find device

I ran the steps exactly up to that point. It's not bricked and I can reboot back into Android TV. It's running 1.01.35 firmware. Is the firmware too new?

Since the output from the update bulkcmd fastboot command didn't look right I just stopped at that point.

Right before that step it says to go into burn mode. Does 'adb reboot bootloader' put it in burn mode or do i need to hold down the button or something when i power it on?

Thanks in advance for any advice.