Fastboot version 30.0.4-6686687
Trying to temporarily boot TWRP recovery image twrp-3.4.0-0-lake.img on my unlocked Motorola Moto G7 Plus.
Phone is connected via USB Type-C to Type-C cord from the box to my laptop running Linux (Manjaro 20.0.3) Live USB system.
When I run ./fastboot boot twrp-3.4.0-0-lake.img or ./fastboot boot boot.img (same file, renamed) with and without sudo, it always gets stuck at Sending 'boot.img' (30080 KB) doing nothing.
Bootloader logs section of fastboot mode shows only cmd: download:01d60000.
The PC I use now is the only PC that helped me to actually unlock the bootloader. Other PCs I have were not able to send correct fastboot commands (for example, oem help transformed into oem helpersion, and oem get_unlock_data cut to oem get_unlock). Those PCs had regular USB Type-A 3.0 ports, so I had connected them to my phone with corresponding 3rd-party cable. It might've been of insufficient quality though.
All files are located near to the root of extrenal SSD connected to another Type-C port, so the absolute paths to TWRP image and fastboot executable should not be too long.
Type-C cords I'm using now are new and OK.
Motorola doesn't distribute Linux drivers for their devices.
What else could be wrong here? Please help. Any advice is appreciated.
Will update this post later with my own findings as well for people who could stumble a similar problem.
Update 1
Tried fastboot boot boot.img on another PC. It is also running Linux (Ubuntu 20.04). Connection is from Type-A to Type-C. Wire is good. No noticeable changes. Main issue persists.
What does "fastboot devices" say? Try running the commands with root and with a different USB cable.
Edit: It should work. I just bootet TWRP 3.4.0-0 several times. I used Fedora Linux with android-tools-20180828gitc7815d675-4.fc31.x86_64 which includes fastboot. BL on device is MBM-3.0-lake_retail-38523c9-200214
Any further update on that ?
Same happens with my device (motorola one power).
The bootloader logs shows "cmd: download:<8 letter hash/code>"
And cancelling the operation doesn't do any harm, just your next command will fail with
"FAILED (remote: 'unknown command')", and bootloader logs will print an empty line starting from cmd:.
Did it work later on, what change did it require if you remember a bit ?
Update: The OP has put the question on reddit:
https://www.reddit.com/r/MotoG/comments/iwcx2v
The solution that worked for him was using windows... dont get angry sometimes we have to use the unused : )
SOLUTION: connect the phone using a USB hub
When plugin the G7 Plus, functioning MTP and ADB, but fastboot “Sending 'boot.img'” dont worked properly
The HUB worked for me, even in the same port
Regards
Hello!
I came here, just to say that I had the same issue with my Moto Z3 Play (beckham), when trying to fastboot boot. It was stuck in "Sending 'boot.img'".
Doesn't make any sense, but when I tried the solution of USB Hub, it worked. Command was accepted and loaded as it was normal as usual.
Thank you very much for this tip!
Best regards
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Hii. you go to device manager. find your phone in unknown device. Update the driver using i have a disk option. Then try again. it will work.
Disable windows 10 Driver signature and install Fastboot USB drivers again.
I can't get my Z3 Play to do much of anything through ADB, Fastboot, or other tools. It won't even allow me to install anything. Recovery comes up as "No Command" and after trying for hours I finally got it to display options, but nothing works. I tried getting my Unlock data to send to Moto but yet again, another error.
Here is the CMD output;
C:\Program Files\MotoTool\platform-tools>fastboot devices ???????????? fastboot ZY2252ZX7Z fastboot C:\Program Files\MotoTool\platform-tools>fastboot oem get_unlock_data FAILED (Write to device failed (Unknown error)) fastboot: error: Command failed
Did you install the drivers? Try that one: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/89879/p/10396
After install reboot your PC.
Try other USB cable, I do have one here that works fine for charging even in turbo power but fail to connect to PC.
I changed the USB cable and moved it to another port and it still was being difficult but I finally got it.
Thanks for your help.
This guide supports the following devices: SD-8501F, SD-X701B, SD-X501F
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB C cable
2. You will need fastboot drivers on your PC
3. Unplug the power cable from your device
4. Remove the silicone cover from the bottom right of your device (Might be hard it has adhesive on the back)
5. Plug the USB C cable into the now revealed USB-C port
6. Hold the volume - button and plug in the power cord keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot) Smart plugs or switches help so you don't damage the ports by replugging them constantly.
7. Keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot)
8. Once the device shows up on your computer in a terminal run the following command:
Code:
fastboot flashing unlock
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Word of warning doing this causes the stock OS not to boot fully.
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB unlock zip
2. Run either the avb-unlock.bat or this command in a terminal
Code:
at_auth_unlock.exe creds\
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command or the Avb_lock.bat:
Code:
fastboot oem at-lock-vboot!
Now that you are AVB unlocked you can flash the firmware/partitions from fastboot using the flash-all scripts located in the firmware zips.
Blueberry 10" Firmware:
Spoiler
Stock Debug firmware (Allows you to OTA to latest firmware if on the user slot and avb locked, but adb is unauthorized so you can't edit files on this one. ADB is intact on the other slot if you change over to it)
Android 8.1 Debug Firmware (Do not AVB lock on this firmware it uses different keys but you can fastboot/edl flash other firmware to recover if you do):
Android 7.0 Debug firmware (Select the Legacy unlock option if avb unlocking)
Amber 8" Firmware:
Spoiler
UNTESTED FLASH AT YOUR OWN RISK (But should be fine report back if it works)
Stock Debug Firmware
Unified 8" and 10" Debug/Development firmware (Only tested on Blueberry/10" but these should work on Amber/8" as well)
Spoiler
Android 8.1 Debug Firmware (Do not AVB lock on this firmware it uses different keys but you can fastboot/edl flash other firmware to recover if you do):
Android 7.0 Debug firmware (Select the Legacy unlock option if avb unlocking):
AVB Unlock tool:
Here
Amber and Blueberry EDL Firehose:
Here
The firmware provided allows you to have adb and adb root on either debug or user. But the downside is with avb off the device can't access its Tee keys so the user firmware will not finish setup. But you can still install other apps and use root which allows you to fully turn off the security restrictions to allow you to edit files on the device. The commands you need to run are these:
Spoiler
Code:
adb root
adb disable-verity
adb reboot
adb root
adb remount
adb shell setenforce 0
Disable-verity will last until you factory reset or run adb enable-verity
Useful adb and android things commands:
Spoiler
Brings up the default launcher selector screen (If a launcher you try opens and then closes it is not supported by Android Things. You will need one that does not have Widget support. Like KISS Launcher)
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
Lists installed app package names
Code:
adb shell pm list packages
Change the -p to whichever package name you want to launch it emulates clicking the apps icon in launcher so some system apps don't support it.
Code:
adb shell monkey -p PACKAGE_NAME -c android.intent.category.LAUNCHER 1
Will launch the android things settings page
Code:
adb shell monkey -p com.android.iotlauncher -c android.intent.category.HOME 1
This will launch the google setupwizard/launcher
Code:
adb shell monkey -p com.google.assistant.core -c android.intent.category.LAUNCHER 1
Seems to soft reboot the android things system, but not actually reboot the device proper
Code:
adb shell monkey -p com.google.android.apps.quartz -c android.intent.category.LAUNCHER 1
Launches camera app
Code:
adb shell am start -n com.android.camera2/com.android.camera.CameraActivity
Various Screenshots:
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there another forum, or talk about what exactly we can do with this fw?? Thanks. Also my comp not seeing the device in fastboot. Yes I have adb and fastboot tools.
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
agentdr8 said:
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
Click to expand...
Click to collapse
I can see other phones in fastboot, just not this smart display. WTF? I think this is a BS thread.
bs3pro said:
Is there another forum, or talk about what exactly we can do with this fw?? Thanks. Also my comp not seeing the device in fastboot. Yes I have adb and fastboot tools.
Click to expand...
Click to collapse
agentdr8 said:
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
Click to expand...
Click to collapse
bs3pro said:
I can see other phones in fastboot, just not this smart display. WTF? I think this is a BS thread.
Click to expand...
Click to collapse
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
deadman96385 said:
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
Click to expand...
Click to collapse
Will give it another go. Thanks for the reply.
deadman96385 said:
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
Click to expand...
Click to collapse
ok, im in fastboot!
AND....I get this. ugh
C:\Users\Owner>fastboot flashing unlock FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed
bs3pro said:
ok, im in fastboot!
AND....I get this. ugh
C:\Users\Owner>fastboot flashing unlock FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed
Click to expand...
Click to collapse
Try and just doing the avb part, it seems on some newer firmware's its tied into avb unlock/lock so when that is unlocked it unlocks the BL.
deadman96385 said:
If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device.
Click to expand...
Click to collapse
Holding Vol- makes a QUSB_BULK (VID 05C6, PID 9008) device show up in Device Manager, which I think is EDL mode and not bootloader? I tried changing it to the Android Bootloader Interface driver but fastboot never seems to find it.
Holding Vol+ makes it boot to what seems to be a missing recovery mode, with the "dead" Android and the red exclamation point icon, but that doesn't lead to any USB devices being seen.
Any thoughts?
agentdr8 said:
Holding Vol- makes a QUSB_BULK (VID 05C6, PID 9008) device show up in Device Manager, which I think is EDL mode and not bootloader? I tried changing it to the Android Bootloader Interface driver but fastboot never seems to find it.
Holding Vol+ makes it boot to what seems to be a missing recovery mode, with the "dead" Android and the red exclamation point icon, but that doesn't lead to any USB devices being seen.
Any thoughts?
Click to expand...
Click to collapse
You don't have bootloader drivers installed
i unlocked, and flashed the universal fw to my 8inch. Now i just have black screen. It always just reboots to fastboot.
EDIT!! The flashall.bat file is corrupt!!!!!!! Need to edit out the format userdata line, otherwise the flash fails!!!
When try to flash the firmware fail with error mke2fs: invalid option -- 'b'
Error: Unknown option ?
If I coment the lines:
#if [[ "${WIPE_USER_DATA}" = true ]]; then
# ARGS+=( format userdata )
#fi
Don't fail, apparently it works fine, I can set it up, connect to google home app.
After this, the update screen appears, when it reaches 100% it restarts and starts the update screen again. And this in an infinite loop.
Any idea how I can fix it? Or just install any linux ?
Can I perform this on Linux PC? I guess not since it requires running .exe file.
I have SD8501F I was able to get it into fastboot mode on both linux and windows pc, but that's about it.
On linux it was recognized right away, on windows I had to manually install google android bootloader driver once it popped in device manager.
It failed to unlock.
fastboot devices return this:
HUA0777K fastboot
--------------------------------------
fastboot flashing unlock:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.012s
----------------------------------------------------
at_auth_unlock.exe creds\
...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
Command 'fastboot oem at-get-vboot-unlock-challenge' returned non-zero exit status 1
No matter what I try, I can't get to the fastboot from neither linux nor windows. I have fastboot drivers installed on windows, I also used fastboot on linux recently with other device. I can get to that broken bootloader while holding vol up without an issue. But holding vol down does not do anything, it just boots to system as usual
CatBug said:
No matter what I try, I can't get to the fastboot from neither linux nor windows. I have fastboot drivers installed on windows, I also used fastboot on linux recently with other device. I can get to that broken bootloader while holding vol up without an issue. But holding vol down does not do anything, it just boots to system as usual
Click to expand...
Click to collapse
I figured at least on my device 10-15sec holding vol down is too much it goes into recovery and leaves it and continue normal boot.
Screen is complete black in fastboot mode, so it's hard to tell when it in.
It's easier on windows as you can see sound when usb is recognized. Then you release vol down.
Basically connecting usb cable hold vol down and plug power, in 2-5sec you will hear usb recognized on windows. Release vol down. And now on windows i had to go to device manager and install driver. On linux it just worked.
Trick is to not hold vol down for too long
bg.stefan90 said:
I figured at least on my device 10-15sec holding vol down is too much it goes into recovery and leaves it and continue normal boot.
Screen is complete black in fastboot mode, so it's hard to tell when it in.
It's easier on windows as you can see sound when usb is recognized. Then you release vol down.
Basically connecting usb cable hold vol down and plug power, in 2-5sec you will hear usb recognized on windows. Release vol down. And now on windows i had to go to device manager and install driver. On linux it just worked.
Trick is to not hold vol down for too long
Click to expand...
Click to collapse
That was a perfect advice, mate, thx a lot!
As for other people, fastboot flashing unlock failed but I managed to run at_auth_unlock.exe creds\ successfuly. Then I commented that format user data line and ran the flash all script.
Now the device boots to fastboot everytime. What should I do now?
Hello, I've flashed firmware with "success" but my device (SmartDisplay 10'') is not reconized by the command adb devices... I'm stuck there after many tries !
I use fastboot and ADB with linuxMint.
Any ideas ?
Axh3ll said:
Hello, I've flashed firmware with "success" but my device (SmartDisplay 10'') is not reconized by the command adb devices... I'm stuck there after many tries !
I use fastboot and ADB with linuxMint.
Any ideas ?
Click to expand...
Click to collapse
Does it get recognized by "fastboot devices"? If so then your device is booting to bootloader after flashing the firmware. Just like mine.
CatBug said:
Does it get recognized by "fastboot devices"? If so then your device is booting to bootloader after flashing the firmware. Just like mine.
Click to expand...
Click to collapse
Yes it is reconized in fastboot devices, I never success to have it in ADB...