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

[bumerc]

Any way to persist this across reboots?

1. # BoardConfig.mk
BOARD_KERNEL_CMDLINE += hdr_policy=1

2. # recompile kernel
m bootimage

 

[npjohnson]

Is this something that makes sense to put in official builds?

Any way to persist this across reboots?

1. # BoardConfig.mk
BOARD_KERNEL_CMDLINE += hdr_policy=1

2. # recompile kernel
m bootimage

 

[apropper]

Try "burn mode". Obtain worldcup drivers and command line "update" program for your OS.

Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;

update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"

Then reboot and see if fastboot works for flashing. Don't repeat the oem commands in the quote above. If you have trouble getting a fastboot connection, use "burn mode" again to start a fastboot connection:

update bulkcmd "fastboot"

Note that changing the lock variable value often requires doing a factory reset. The recovery "rescueparty" menu will prompt you if this is necessary.

Hi, I'm having a hard time trying to flash. I keep getting the device locked message in cmd when trying the "fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock" step in the instructions. I saw the quote above and...

I've got the worldcup drivers and I have my dynalink box recognized by amlogic usb burning tool. But I don't know what you mean by using "update program for worldcup. Please help.

 

[apropper]

Boot to burn mod using the button on the side and plugging in, then use amlogic update tool to run "update bulkcmd 'setenv lock 10101000;save'"

Also what do you mean by amlogic update tool? I found Amlogic USB Burning Tool from websearch, not sure if it's the same thing.

 

[npjohnson]

Also what do you mean by amlogic update tool? I found Amlogic USB Burning Tool from websearch, not sure if it's the same thing.

same thing

 

[apropper]

same thing

Ok, how would I run a command from that program?

 

[npjohnson]

Ok, how would I run a command from that program?

there's a tool called update in that burn tools package, run `update bulkcmd 'setenv lock 10101000;save`

 

[apropper]

there's a tool called update in that burn tools package, run `update bulkcmd 'setenv lock 10101000;save`

Damn, I don't see that option anywhere. Is this the right program? I'm sorry if I'm being ignorant but all I need to do is unlock the bootloader and I'm at a wall right now.

 

[npjohnson]

Damn, I don't see that option anywhere. Is this the right program? I'm sorry if I'm being ignorant but all I need to do is unlock the bootloader and I'm at a wall right now.
View attachment 5926471

no, use this https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/windows

 

[apropper]

no, use this https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/windows

How do I use this? I dl'd all those files into one folder. Nothing happens when I click "aml packer" or "update.exe". Please explain further. I've installed lineage on my phone before and that was a piece of cake. This, not so much. I feel so dumb trying to figure this out.

 

[npjohnson]

How do I use this? I dl'd all those files into one folder. Nothing happens when I click "aml packer" or "update.exe". Please explain further. I've installed lineage on my phone before and that was a piece of cake. This, not so much. I feel so dumb trying to figure this out.

it's a command line tool. Why are you doing this again?

You can run this from the boot loader instead - just use cmd not powershell

 

[apropper]

it's a command line tool. Why are you doing this again?

I was following the regular instructions from the wiki and couldn't get past the oem unlocking step to unlock the bootloader. Kept throwing "FAILED (remote: locked device)" at me.

This is what happened when I was in burn mode

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd 'setenv lock 10101000;save'
AmlUsbBulkCmd[10101000;save']
[AmlUsbRom]Inf:bulkInReply failed:
ERR: AmlUsbBulkCmd failed!

This happened when I restarted the device and did the reboot bootloader command

C:\Users\user\Downloads\aml-flash-tool>adb devices
List of devices attached
WUSA2301003863 device

C:\Users\user\Downloads\aml-flash-tool>adb reboot bootloader

C:\Users\user\Downloads\aml-flash-tool>fastboot devices
WUSA2301003863 fastboot

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd 'setenv lock 10101000;save'
[update]:No [WorldCup Device] device after scan
[update]ERR(L1094):can not find device

I have world cup drivers installed, btw.

 

[apropper]

Okay, I followed Functioner's instructions and was able to run both "setenv lock 10100000" and update bulkcmd "saveenv" successfully. But now I rebooted and see a recovery error screen saying can't load android system. So I factory reset. Tried unlock bootloader command in fastboot and got this,

C:\Users\user\Downloads\aml-flash-tool>fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock
...
OKAY [ 0.038s]
finished. total time: 0.039s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s

Rebooted, same recovery error screen telling me to factory reset. I don't mean to use you as my personal tech support, but what am I doing wrong here?

 

[apropper]

I'm pulling my hair out over this. Factory reset a couple of times, tried Functioner's instructions again. Here's what happens:

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd "setenv lock 10100000"
AmlUsbBulkCmd[setenv lock 10100000]
[AmlUsbRom]Inf:bulkInReply success

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd "saveenv"
AmlUsbBulkCmd[saveenv]
[AmlUsbRom]Inf:bulkInReply success

C:\Users\user\Downloads\aml-flash-tool>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!

I get this error every time and have to factory reset. And I still can't unlock the bootloader through the wiki instructions either. I'm new here, so please don't accuse me of spamming, but I'm genuinely stuck and don't know what to do. It seems easy enough for everyone else to get this running. Ugh! Why can't I figure this out?!

 

[Functioner]

but what am I doing wrong here?

Your mistake was doing this:

So I factory reset. Tried unlock bootloader command in fastboot and got this,

C:\Users\user\Downloads\aml-flash-tool>fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

after you had already unlocked the bootloader doing this:

Okay, I followed Functioner's instructions and was able to run both "setenv lock 10100000" and update bulkcmd "saveenv" successfully.

You're relocking the bootloader by doing "fastboot oem 'setenv lock 10101000;save'" after you unlocked the bootloader using burn mode.

It's okay to do the factory reset after you unlock the bootloader using burn mode, as you did here:

But now I rebooted and see a recovery error screen saying can't load android system. So I factory reset.

The factory reset is required, as I explained in the post because unlocking the bootloader using burn mode is a non-standard way to do it, and it does not erase the data partition as part of the unlocking process (like fastboot does when it works to unlock properly), so a manual clearing of the data partition is required.

Repeat the burn mode unlock process, and the factory reset process, but then don't do any of this:

C:\Users\user\Downloads\aml-flash-tool>fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

 

[Functioner]

C:\Users\user\Downloads\aml-flash-tool>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!

Did you check for a fastboot connection after doing:

update bulkcmd "fastboot"

by running the command:

fastboot devices

Some of the error messages you see from the burn mode client reflect the change in connection type over usb from world cup connection (burn mode) to fastboot connection (using android drivers).

Check for a fastboot connection after running
update bulkcmd "fastboot"

using the command
fastboot devices

Just don't run any "fastboot oem" commands after that.

 

[apropper]

@Functioner thanks for the reply. So I installed the dbt and dbto files, then flashed recovery. I can't boot into recovery, and I'm stuck at the dynalink screen no matter if the cable is plugged into my computer or into the wall. I don't get any result at all when I type fastboot devices into cmd. Do I need to flash the stock firmware and if so, how to I do that?

 

[apropper]

So I did some looking around and found this from @npjohnson

https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-85425773

and put the device in burn mode and tried running the command `update.exe bulkcmd fastboot` and got this:

C:\Users\user\Downloads\aml-flash-tool>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]Inf:bulkInReply
ERR: AmlUsbBulkCmd failed!

I do have worldcup drivers installed, it shows through device manager but after I run this command, I get a yellow triangle over the worldcup device in device manager. Please help, I'm trying to unbrick this thing.

 

[Functioner]

I do have worldcup drivers installed, it shows through device manager but after I run this command, I get a yellow triangle over the worldcup device in device manager. Please help, I'm trying to unbrick this thing.

You're not able to get a burn mode connection anymore? I'm not sure that I know what state your device is in.

If you can't get a fastboot connection, forget about fastboot for the time being. If you are still able to get a burn mode connection, maybe try restoring the original dtb/dtbo/recovery using burn mode, like described at the top of this post.

Of course, you'd use the image files for your device, not the image files mentioned in the post.

 

[npjohnson]

So I did some looking around and found this from @npjohnson

https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-85425773

and put the device in burn mode and tried running the command `update.exe bulkcmd fastboot` and got this:

C:\Users\user\Downloads\aml-flash-tool>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]Inf:bulkInReply
ERR: AmlUsbBulkCmd failed!

I do have worldcup drivers installed, it shows through device manager but after I run this command, I get a yellow triangle over the worldcup device in device manager. Please help, I'm trying to unbrick this thing.

different USB port or USB2 hub