Unrecognized Command Flashing Unlock

[Agnella Datson]

Hasanyone successfully flashed a MR18 that has the latest up to date firmware installed?

On my device its showing "bootsh build 25-201804051805-G885d6d78-dhow-rel". Im getting to the Meraki prompt with a UART cable but whatever I type, Im greeted with "UNRECOGNIZED COMMAND LOGGED TO CLOUD SERVERS"

Ive searched everywhere but havnt found a solution yet One recommendation was to flash it using USB JTAG cable, but that costs as much as a new ac AP

Actually, I did follow method C and it did not work, no matter how I tried.

BUT, what is surprising that in not one thread about flashing MR18 with LEDE, where people encounter problems with newer firmware, no one has recommended to roll back to previous firmware! A few weeks back when I first started messing around with the MR18 and flashing LEDE, I briedly looked into the "firmware rollback" topic, but a bit Googling said that it is not possible.

Yesterday I looked into the possibility again and succesfully rolled back to an earlier firmware! 25.9 I belive.

Then after the roll back, I followed method C again, got to the Meraki prompt, commands worked and Im now succesfully running LEDE

After writing the new firmware onto it and powering off-on again, I had some trouble booting into the new initramfs kernel, but after some messing around, I got to it. Should anyone encounter problems with it, let me know, I can describe how I got into the new kernel. It involved some precise timing with powering on, unplugging/plugging in the GND pin and pressing 2.

So, problem solved, case closed.

I have been attempting to install /e/ OS on a Fairphone 4 in accordance with these instructions: and I am stuck on Step 6 of Unlocking the Bootloader. No matter what I do, I get results like this when attempting to use the fastboot flashing ... commands:

I need help!

When I am flashing Meraki Z1 into OpenWRT I can't get a Busybox prompt.

on the step 16. Build for Cisco Meraki Z1

After the serial number is changed correctly, I am putting power off the device and hold down the s key in the serial terminal while powering on the device but no Busybox prompt (/ #) only and UNRECOGNIZED COMMAND LOGGED TO CLOUD SERVERS.

I have Meraki z1 with BusyBox v1.24.1 2018-03-26.

So you succeeded to get the odm help output before without the unrecognized command error? Than try to keep tapping S in the serial terminal. Like tap s-s-(power on)-s-s-s-s-s-s-s till you got the busybox prompt.

Just curious if anyone has been able to get this box running with OWRT - I have 2 of these (paperweights at this point as they are off licensing) and another to soon become a paperweight in less than 1 year.

6. You should now be back to a new root prompt, but with working network connectivity. At this point, you'll want to download the firmware image for the MR18 from the repo at -MR18/releases and then extract the files to the root of your local webserver. Once this is done and you have verified that the 2 images are extracted and in the webroot folder, you can download the initramfs image to the MR18 and flash it:

NOTE: In the initramfs image, you may notice wifi does not work. This is because the factory MR18 firmware does not properly populate the UBI caldata partition with the required information, but we will take care of this shortly.

8. Now that we have the initramfs build working, you'll want to browse to which should then take you to the LuCI web interface. From here, you can just press login to enter as no password is set. Now, just go to the System Upgrade tab, and select the downloaded sysupgrade image named openwrt-ar71xx-nand-mr18-squashfs-sysupgrade.tar. Once selected, de-select the save config option and then press Upgrade. Once on the confirmation page, go ahead and flash the image.

2. Hook up your MR18 to a router, and disconnect the router from the internet. DO NOT ALLOW THE MR18 TO TOUCH THE INTERNET DURING THIS PROCESS! This is important as the most reliable way to do this exploit is to have the MR18 use DHCP to get an IP on the same network as your personal computer.

Note that the above command may timeout, depending at what state your router is during the boot process. If it times out or fails, just wait 60 seconds and try again. Normally the best time to run the command is when the LED on the MR18 is green or flashing orange.

I am experiencing more and more a problem where AutoCAD stops responding and I notice the error 'unrecognized' flashing in the bottom right menu bar (see attachment). It becomes impossible to carry on working as it takes ages to action each command.

I have successfully restored the OS using adb devices / adb sideload update.zip and got back to the latest image for Android. However I still get the warning message "Bootloader is unlocked and software integrity cannot be guaranteed..." upon each boot.

There's an entire step on the Web Installer that says "relock bootloader" after you reflash stock. What is your issue? You skipped that step, so go back and don't skip it this time. Boot your phone into recovery by holding the power and volume button, connect it to your computer, and click the "Lock Bootloader" command from the Web Installer page.

caldera Then I don't know how you managed to install GOS in the first place if you cannot follow the Web Installer located on this website step by step. There is no way to make it any easier for you. Go to the web installer page and follow the directions.

Do you have platform tools installed? If not, you can relock the bootloader yourself by downloading platform tools from Google, just search for it and download it into a folder. Go to that folder in the command prompt, while your device is plugged in, and type "fastboot flashing lock".

@morapelor I went through all processes to arrive at this point or this post wouldn't exist. I simply don't see an option to erase the bootloader warning message unless reloading one is somehow an option and I scarcely find that to be one

EDIT: I have tried many fastboot options including get_lock_ability etc and all lead me to the same message along the lines of "unrecognized command" - I can post more details tomorrow when I have it back plugged in but as of writing these are my recolections

caldera I have tried many fastboot options including get_lock_ability etc and all lead me to the same message along the lines of "unrecognized command" - I can post more details tomorrow when I have it back plugged in but as of writing these are my recolections.

If providing further information, please try to provide all relevant details: which OS on your computer, which release, which version of fastboot, exactly what fastboot commands you try, and exactly the responses you get. If you are following directions from some web page or video, please say which.

Use l4t_initrd_flash.sh to flash internal or external media connected to a Jetson device. This script uses the recovery initial ramdisk to do the flashing, and can flash internal and external media using the same procedure. Because this script uses the kernel for flashing, it is generally faster than flash.sh . See Flashing with Initrd for more details.

specifies the configuration to be applied to the deviceto be flashed. Values are listed in the Jetson Modules and Configurations table in Quick Start . flash.sh gets the configuration from a configuration file named .conf .

where --storage is supported only on Jetson Xavier NX series, Jetson AGX Xavier series, Jetson AGX Orin series, and Jetson Orin NX series. It can be nvme0n1p1 for flashing to an external NVMe SSD or sda1 for flashing to an external USB storage drive.

This command stores the UUID used for the root file system partition in the file bootloader/l4t-rootfs-uuid.txt . You may specify your own UUID by writing the UUID to this file before executing the command above.

This command stores the UUID used for the root file system partition in the file bootloader/l4t-rootfs-uuid.txt_ext . You may specify your own UUID by writing the UUID to this file before executing the command above.

This step creates two copies of in the directory, a sparsed image (smaller than the original) named , and an exact copy named .raw . The time it takes to back up a partition depends on the size of the partition.

If the target board has already been flashed, reflash the clone image to the APP partition. The time it takes to back up a partition depends on the size of the partition. To back up the partition, run the following command:

If root file system of the source device for clone is resized during oem-config , the eMMC configuration file of destination device must be updated accordingly. For example, with jetson-agx-orin-devkit , root file system ( APP ) is the final partition before secondary_gpt . If the APP is resized to maximum allowed size, the allocation_attribute of APP partition in Linux_for_Tegra/bootloader/t186ref/cfg/flash_t234_qspi_sdmmc.xml must be updated from 0x8 to 0x808.

Kernel command line arguments. If this option isspecified, it overrides the default values definedfor flash.sh . If two or more arguments arespecified, they must be enclosed in quotation marksand separated by spaces.

The flash.sh script supports a usb-instance to flash a specific Jetson on a host that has multiple Jetson in recovery mode. This section provides information about how you can find out which usb-instance to use.

Jetson devices can be booted from a mass storage class USB device withbulk-only protocol, such as a flash drive. Hot plugging is notsupported; the flash drive must be attached before the Jetson device isbooted. You can manually set up a flash drive for booting as explained in To set up a flash drive manually for booting .

You can also specify as the size of the APP partition. This value is different from the total size of the external storage device, which is defined by the num_sectors field in . If you change the num_sectors field in , you have to specify a new so that it is a few GiB smaller then the total size of the external storage device to fit the APP and other partitions.

3a8082e126