[Google TV General] AiM2LeaRn:
INSTRUCTIONS FOR WADE ( DYNALINK ) ANDROID BOX

IF Bootlooped (SOFT-BRICKED) or installing linage or getting bootloader locked message:

FAILED (remote: 'unlock_ability is 0, can not unlock')

fastboot: error: Command failed

when trying the old method of unlocking the bootloader or you if you are bootlooped in a bootloop with just the Dynalink logo which some people think is bricked then

Heres how to un-bootloop, unlock bootloader, and install linage 20

Files Needed:

1) "World Cup" (libusb-win32 usb) Driver (Driver is often included with the "BURN TOOL" zip file )

2) aml-flash-tool (that includes Update.exe)

3)LATEST platform tools and android driver (latest as of this time is platform-tools_r34.0.4-windows... use the latest most recent version or you will get errors in ADB)... let me repeat: USE THE LATEST NEWEST VERSION

4)IMG files (Andorid/Linage rom files like recovery,dtbo,dtb, system linage image and whatever else)

ENTERING BURN MODE:

NOTE: After the latest update there is now a quick "timeout" if no command is sent it will quickly go into burn mode then proceed to the regular boot process where before it would stay in burn mode.

Install the "World Cup" (libusb-win32 usb) Driver (some people may have to manually install)

Then Enter "Burn Mode" by making sure the USB cable is not plugged into the dynalink box. then press and hold down the Dynalink BOX's device's circle button located on the side of the Dynalink box and while holding down the button you have to plug in the USB cable thats plugged into the computer making it a PC to Dynalink usb cable data connection , let go of the Dynalink button after a few seconds, should see LIBUSB-WIN32 in device manager, if you have speakers you will also hear windows make a hardware device detected sound. if it goes past the DYNALINK logo then you have went to far and have to try again. this is the trickiest and hardest part of the entire flashing process.

Hint for those having problems: for some reason i had to keep running the

update bulkcmd "saveenv"

HINT: for it to "catch and enter" burn mode.... right after i made the PC to phone connection with the USB cable i immediately in Windows 10 QUICKLY hit the UP ARROW button on the computer keyboard which brings up the previous command and then I hit ENTER button a bunch of times as fast as i could until i seen it detected in device manager as "libusb-win32 usb"... you will also get a "success" message meaning the command worked meaning you are in burn mode. (so to sum that up right after i plugged in the USB cable i repeatedly hit the UP and Enter as fast as i could until it said success and was shown in device manager)

UNLOCK BOOTLOADER

once in Burn Mode then go to the aml-flash-tool folder and run:

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

Power off for changes to take effect and Enter Burnmode again

INTALLING RECOVERY AND LINAGE

once in Burn Mode then go to the aml-flash-tool folder and run:

update partition dtbo C:\Folder\dtbo.img
update partition _aml_dtb C:\Folder\dtb.img
update partition recovery C:\Folder\recovery.img

so files you just flashed take effect you have to

POWER OFF UNIT AND ENTER BURN MODE AGAIN ( yes you have to reboot into burn mode again )

when back in burn mode from the aml-flash-tool folder run the following command to force fastboot:

update bulkcmd fastboot

it will show error when trying to enter fastboot using update, but just keep repeating command a few times. it will go into fastboot even without you knowing even though it gave error.

to verify you are in fastboot go to platform-tools_r.x.x.x-windows folder and run:

fastboot devices

fastboot devices should give you some numbers and letters

once in fastboot we boot to recovery by running:

fastboot boot C:\Folder\recovery.img

(Helpful NOTE: Once in recovery use the power button on the remote control to select and choose)

inside of linage recovery choose APPLY UPDATE>APPLY UPDATE FROM ADB then run command:

adb sideload lineage_system.img

then go to "FACTORY RESET>FORMAT DATA/FACTORY RESET"

then go to "REBOOT SYSTEM NOW " and reboot into a working linage os