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
Related
I originally posted this question in XDA Assist yesterday. I was directed to this forum, and after reading more here, have added a few more questions/concerns with ***___**** that came after digging through the forum stickies. I know this has become a huge post, so apologies in advance.
I'm having some trouble mounting a Kindle Fire HD 7 Gen2 (Tate) in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
******* After reading the Faq here, I am concerned that even if Fastboot were to detect the device, that simply using it to load the FireFireFire bootloader directly onto the device would cause the problem of the wall of fire because of the M-Shield issue. Seems I would have to follow these steps here or here to load FireFireFire as a 2nd bootloader (including downgrading the OS to v7.2.3), is that correct? Also one of those pages says not to use automated tools like FireFireFire... which I thought was a bootloader, so what bootloader should I use to get around the low battery cycle startup problem that FireFireFire specifically addresses with it's startup battery check *******
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus.
******In one of the pages linked above, it makes a passing reference to some fastboot cables not putting the device in Fastboot. Since I cannot connect to the device in the first place when it is in "fastboot", I cannot use their method to confirm fastboot is working. When bootup with my fastboot cable, the "image" on the device does change from orange & flashing "Kinde Fire" to the orange "Kindle Fastboot" pic, so I'd to know if I can rule out the cable as part of my problem... *****
Here is the error from Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I found a tutorial on Ubuntu forums for getting MTP to work that involved using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However that didn't work. It seems that in Fastboot I actually might not MTP to handle the device...
OTOH, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command....
***** Since yesterday, I back and compared the vendor and product codes reported in lsusb and noticed that they are the same regardless of whether I connect the device using a regular cable (when it mounts correctly) and the fastboot cable (when the screen says fastboot, and I get the "raw device" failure to mount. My understanding is that the hardware ID should be different if the device is in fastboot mode vs "normal" mode. Is that correct? How do I deal with this behavior if the device is supposed to load different drivers when in different modes?*****
However, it seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
***** The other thing I tried was using the modprobe command to manually start the usb-storage driver as explained here. However the step to confirm the driver was unsuccessful because the /var/log/messages file was not found by the tail command. Even though that is really an ubuntu / linux question, perhaps someone here can help with some guidance on confirming the mass storage driver as well?*****
Can anybody help with this problem please?
Thank you
Additional detail
In case it's helpful to diagnose the issue, I am now experiencing an odd behavior where the device starts out in Fastboot (using the fastboot cable), and then after about 30+ seconds, it automatically switches to the "swipe" screen as though it was in normal mode.
This happened after I went and rem'd out all references to this device in the MTP rules files. The first time I plugged it in, Ubuntu popup asked how it should handle the device. I didn't see "mass storage" so I hit cancel. At that point, it started to flop over from fastboot into normal automatically even though it is plugged into a fastboot cable.
My understanding was that a fastboot cable forced it into fastboot mode (or else was somehow device in-compatible with certain Kindles). I don't understand how the host OS could do this without issuing an ADB / shell command?
I just purchased by OnePlus 3T and in the process of trying to unlock the bootloader. I have ADB while in stock oxygen os 4.0.2 but when entering fastboot to unlock the bootloader I no longer have access to the device. As per some searching I switched to a USB 2.0 port and still no luck. In device manager it shows my phone under "Other devices -> Android." I'm pretty sure i'm missing a driver for ADB, but can't figure out what is missing. Any help would be greatly appreciated!
http://www.androidusbdrivers.com/oneplus-3t-usb-drivers
Install, restart.
Specifically in folder you have adb files, hold Shift+Right Click, open command prompt.
fastboot devices to confirm connection
fastboot oem unlock to get started.
Search for the one plus 3t toolkit. It has the original one plus drivers.
Then install minimal adb and fastboot.
And it should work. If it doesn't, try on another pc.
Well it's been a while since my last new phone totally forgot to install USB drivers all good to go, newb mistake thank you!
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Jo_Jo_2000 said:
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Click to expand...
Click to collapse
After having my phone since Monday, I just now noticed that emulated drive when I had to nuke it earlier today, lol.
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
Does it work with
Different cable
Different port
Different pc
Different OS like linux
?
If I remember correctly I had issues with windows drivers.
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
ambitiousButRubbish said:
Tried different ports, same issue, not tried a different cable, but I know this cable works as I use it for fastboot on my mi mix 3.
I'll try Linux though, a few posts seem to say it works
Click to expand...
Click to collapse
I use Linux Mint Cinnamon for development
I am still happy with it
ambitiousButRubbish said:
I just got hold of an xz2 for a bit of development work, and am trying to unlock the bootloader (yes, it's allowed, I've checked)
I'm connected to a usb2 port (same one I use for my mi mix 3 because that doesn't like usb3 for fastboot)
ADB works perfectly, however, fastboot lists no devices, and executing a command just causes <waiting for device> to show.
I've installed the drivers supplied by sony, though, the installation reported they installed but could not start.
I've never experienced this before, so, tell me if I'm doing something wrong.
Click to expand...
Click to collapse
my same issue adb working but not fastboot on windows 10.
i solved using ubuntu on virtual machine. on windows i can't use fastboot but with ubuntu on oracle virtualbox all is work perfectly
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
ambitiousButRubbish said:
yep, worked with linux, well, i just connected it to my mi mix 3, installed the adb/fastboot binaries in magisk and ran the commands from the terminal, looks like all my fastboot work is being done from another android device
Click to expand...
Click to collapse
is it possible to install adb and fastboot from magisk and do it from another android device?
is it possible to do it with a 32 bit device? i have a galaxy note 4 as a second phone with snapdragon 805 32 bit
MartinX3 said:
I use Linux Mint Cinnamon for development
I am still happy with it
Click to expand...
Click to collapse
Arch linux only ?
Don't see why not, the binaries are just compiled for ARM, don't think they are architecture specific.
My mi mix 3 is ARMv8 (64 bit) sd845, and it worked fine, not sure about ARMv7, but as I say, I think the binaries are ARMv7 anyway.
So long as the device can host a USB connection it will work.
For anyone having problems with the,"Waiting for Device" in windows,
USB debugging enabled on the phone.
Connected to PC through USB data cable and Phone screen unlocked and File Transfers enabled.
In windows> Device Manager> Android device(or your device/phone) >ADB driver or similar > Properties> Driver> Update Driver > Browse Computer > Let me pick from a list of devices and Un-tick the show compatible devices and find one that works.
I've had to keep this general as there are quite a few variables with different phones makes/models but the problem is caused by Window's Device Mangler not getting the correct ADB driver installed/chosen and or too many varied ADB driver packages installed
HTH
First hit in google... so let me explain it again. (Yeah... fresh windows install ****ed me over... )
You need ADB/Fastboot.
Sony Drivers?: https://developer.sony.com/file/download/xperia-xz2-driver/
Google USB Drivers: https://developer.android.com/studio/run/win-usb
If you can't install it. Disable Driver signature enforcement (Hold Shift while you press the restart button with the mouse)
When ADB works but fastboot isn't recognized reboot into bootloader "ADB reboot bootloader" and then in Device Manager find the "Android!" device and manually select the Android Bootloader as driver.
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
hi folks I am trying to unlock the bootloader on a Motorola E4 plus running 7.1.1 but I'm having a lot of trouble. Firstly when I boot the device into bootloader mode by pressing and holding the power and volume down buttons and plug it into my windows 10 pc it says 'transfer mode: cable not connected'. I have tried different cables and usb ports but the issue persists. Moreover, when I try to get the unlock data using the 'fastboot oem get_unlock_data' command it says '(remote: 'unknown command')'. Oddly however adb works and the phone is shown when I type 'fastboot devices'.
So far I've tried:
using my mac
factory resetting the phone
wiping the system cache
ensuring security is set to none on the phone
different usb cables
different usb ports
installing the android SDK and running the cmd window from it
minimal adb and fast boot
platform tools based adb
restarting the computer
installing motorola's own drivers
ensuring oem unlocking and usb debigging are turned on in developer options
ensuring the MTP driver is installed and updating the driver in device manager
restarting the phone
I would be grateful for any help anybody could please offer. Thanks all!