If you want to take a crack at it, here is how to install Android Oreo. We should caution, however, that the first release of any OS is often the buggiest. Alternatively, if you’re the impatient sort, you can download factory images from Google’s Android Developer page and install it manually. Google says that the Pixel and Nexus 5X/6P builds have entered carrier testing and will roll out soon, alongside the Pixel C and Nexus Player. The easiest is via an over-the-air update, which obviates the need for a computer and USB cables. It’s official: Google has released Android Oreo. After months of developer preview releases, the newest version of Google’s operating system is available in finished form for the Nexus 5X, 6P, Nexus Player, Pixel C, Pixel, and Pixel XL. Dug up my brain, found out tons of tweaks lying in a corner, and tried them all. The thing is I was constantly getting bugged with an error or two. All these three have managed to work out in my favor when everything failed. Well, all these might sound too easy to be true, yet they sometimes end up doing wonders. Case 3: USB Port, Cable and Windows Version The FAILED (remote: unknown command) Error might have been rectified by now. If you have successfully installed the above-mentioned drivers, then proceed with your ADB or Fastboot commands. If that is not the case, then refer to our detailed guide on how to get these drivers. If you face this error when your device is booted to EDL or Emergency Download Mode, then make sure that the Device Manager shows Qualcomm HS-USB QDLoader 9008, rather than the earlier QUSB_BULK.
In that case, you will be needing the drivers from Android SDK and Platform Tools installed on your PC. The Fastboot drivers will be needed, as the name suggests when your device is booted to Fastboot Mode. This is the case when you wish to execute ADB commands, as in ADB commands, your device remains in a switched-on state.
The former is needed when you connect your device to PC in a switched-on state. By USB Drivers, we mean both the OEM specific drivers as well as the Fastboot drivers. The unofficial recoveries that we share here at Droidwin are also taken from XDA as well.Īlso, keep in mind that the correct USB drivers are installed. Regarding the unofficial build, we would only suggest you search on XDA. Many sites are offering incorrect TWRP builds, which you might have flashed on your device, then the FAILED (remote: unknown command) Error is imminent. Don’t Miss: How to Boot Any Android Device to TWRP Recovery.However, the problem stems out from unofficial builds. If your device officially supports a TWRP Recover, then there is no issue as you could directly get a hold of the same from the TWRP home page. However, if you are flashing an incompatible build of TWRP, then this error is bound to occur.
As a result, you will first have to boot the img file via fastboot boot twrp.img and then flash the TWRP installer ZIP file to permanently get this custom recovery. So you no longer can directly flash the twrp file on those devices. Since the inception of A/B partition, the recovery partition has been removed. When: While Dealing with TWRP and other flashable ZIPs This phone can’t be unlocked.” Check the Build/Version of the File “You can’t unlock the bootloader on most Verizon phones. “Your phone is not unlockable as it is not on the unlock list, has a mediatek processor, and doesn’t support the unlock commands”. We have seen many users, especially from the Motorola OEMs being greeted with the following error: So if the PC successfully recognizes your device in ADB and Fastboot Mode, why this error occurs? Well here is everything you need to be aware of and the potential fixes.
In both these cases, you will get the device code as well.
Or enter fastboot devices when the device is connected in fastboot mode. For example, try executing the adb devices command when your device is connected in the ADB command. So fastboot oem unlock and fastboot boot recovery.img are the two most frequent times users face this error.įurthermore, the strange thing is that your device gets successfully recognized, even when you face the FAILED (remote: unknown command) Error. But again, these are just two of the ocean causes why this may happen. For the latter, booting a TWRP IMG file takes a major share of the blame.
In the case of former, Motorola devices seem to be the major culprit (though it’s not limited to it).