Hiya everyone,
I unlocked bootloader couple of days ago and checking it shows unlocked status. When I get to the part to root it and use command fastboot boot patched_boot.img device either shows a message Press any button to shutdown (via CMD terminal) or stays on Sending boot.img (Powershell terminal). I used all USB 3.0 and 2.0 ports my PC has, tried on a laptop that I own - also no luck and same messages are present.
What could be the solution to this?
PC Specs are: Ryzen 2600x, 32gigs of ram and Vega 64
Laptop specs: Intel I5, 8gigs of ram and intel integrated solution.
Any advice would be helpful.
Just to note I am using this guide here with all the files necessary to perform enabling Gcam: https://forum.xda-developers.com/mi...am-android-t3868766/post79123738#post79123738
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.
Hello all! Im scyyie and ive been a long time lurker on XDA for maybe 5 years or so.
Its been a while since ive rooted an android but im having some trouble in the process once i use cmd to flash the patched .img file. Let me explain and hopefully someone can eli5 lol.
information on my situation:
Razer Phone 2
android ver 9
kernel ver 4.9.112
build P-MR2-RC001-RZR-190914.3123
security update is Sept 25th 2019 i believe.
debugging is enabled.
OEM is unlocked.
I followed the user guide on xda to where I successfully unlocked bootloader, used magisk to patch an .img file matching my exact build (listed above). seems all good right? just flash the patched file i think? Well, my issue is when i turn off my phone, then hold volume down + power, i come to the bootloader/fastboot menu (i think its called?). I start adb shell with CMD prompt, with my patched .img in the same directory, and type "fastboot flash boot_a patched.img" but it hangs there and gives me this: Sending 'boot_a' (20780 KB) FAILED (Write to device failed (Unknown error)) fastboot: error: Command failed
When my phone is on, i used adb shell to use the command "adb devices" and my phone is listed with its serial. The issue (i think?) is when i put my phone into fastboot, adb doesnt detect it. I have installed the appropriate drivers i believe?
Yes i have searched for other guides on this issue but it seems none of these solutions will help. I have also tried installing samsung drivers as well. Im not tech illiterate but hopefully the issue isnt too much of a mystery to the knowledgeable people here.
Thank you all for reading and I hope something can happen here.
solved.
after more research it seems AMD cpus dont agree with this process involving ADB along with usb 3.0 causing an issue as well. I used a usb 2.0 on an intel laptop and the process worked as normal.
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
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Audoghast said:
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Click to expand...
Click to collapse
While your phone is in fastboot and connected to your laptop; How is it shown in device manager?
Good evening.
I found the solution to unbrick my Oneplus Nord CE 5G and here it is.
Status: - normal start leading to Qualcomm Crash Dump screen
- Recovery mode into TWRP possible but no transfer of files to/from phone
- No Fastboot possible
Procedure:
Install Qualcomm USB Drivers from
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
You may have to launch the command prompt as admin and type:
bcdedit /set testsigning on
I did not have to do it because the Qualcomm Driver installation did it for me.
After restart you will see the following message in the lower right side of your PC:
Testmode Windows 10 Pro + build number
To get rid of end at the very end type:
bcdedit -set testsigning off
Download the following package:
Europe: https://onepluscommunityserver.com/...BA/R/OnePlus_Nord_CE_EU_OxygenOS_11.0.9.9.zip
India:
https://onepluscommunityserver.com/...R/OnePlus_Nord_CE_India_OxygenOS_11.0.4.4.zip
These packages contain the MSM Download Tool and the respective files. Beware that you have to get the correct bundle for your phone. Other bundles contain MSM Download Tool too but will not be compatible and the tool generates a failure message.
Launch MSM and type OTHER at login.
Target was EU in my case.
Then click on start.
Now your phone needs to boot into EDL mode. It worked for me from the TWRP Reboot screen but supposedly starting the phone by holding the volume up and down buttons for 45 seconds does the same.
The screen will be totally black, no beep, no vibration, no feedback.
Then connect the USB cable and MSM will start working. After about 5 minutes the phone should be back to normal.
ADB commands worked again too (phone was being recognized as USB device under device manager). However, fastboot did not work. The device was listed as other device in the manager.
After updating the driver using the following files everything worked:
https://drive.google.com/drive/folders/1D96njoYn-n3alu3ggaK3Kw8hMGLKhJVg
Now I am back to rooting and will report about that too.
Good luck