I was following this tutorial
https://forum.xda-developers.com/showthread.php?t=3859565
And my phone ended like this, It seems to be something with the screen
https://imgur.com/a/qY2PGjn
The only different step I made was install usb drivers for windows manually
I still enter to fastboot and when I type fastboot devices in the adb command shell it appers
Please help
Related
I cant seem to ADB from the bootloader. It works fine when the Xoom is on but when i enter "adb reboot bootloader" it reboots in to boot loader and stops working.
I have the necessary drivers as its showing "Mot Single ADB Interface" under device manager.
When i enter adb devices its saying "list of devices attached" but there is no device under it.
When i enter "adb get-state" it comes back with "UNKNOWN"
Please help
When you say that it stops working, are you trying to enter other ADB commands or are you using fastboot? I've just tried all of the same commands as you have entered and I get the exact same results. It seems to me (and I'm by no means an expert in adb having just learnt the basics so far) that in bootloader the standard ADB commands do not work. Once in bootloader it seems that you need to use the fastboot commands to flash an img file.
Also, in bootloader mode the xoom is no longer recognised by the pc, just press vol up + popwer and it should reboot, or I guess you could also enter fastboot reboot to do the same thing.
I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!
did you reboot your xoom into bootloader mode? (adb reboot bootloader)
does it show any devices when you type
adb devices
Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..
usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )
well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.
Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!
Hey there
(info: Windows 7, LG optimus 4X HD, 4.0.3 ICS, debugging mode is ON)
So i've installed the SDK, ADB & fastboot + drivers
to try to unlock my bootloader.
First i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2224020
When I type this command in the prompt: adb reboot oem-unlock
My device is just rebooting as normal.
But when i try to do fastboot commands it tells me
Waiting for device.....
So fastboot isn't seeing my phone
Does anyone have an idea what's going on?
Ryan.
ryantju said:
Hey there
(info: Windows 7, LG optimus 4X HD, 4.0.3 ICS, debugging mode is ON)
So i've installed the SDK, ADB & fastboot + drivers
to try to unlock my bootloader.
First i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2224020
When I type this command in the prompt: adb reboot oem-unlock
My device is just rebooting as normal.
But when i try to do fastboot commands it tells me
Waiting for device.....
So fastboot isn't seeing my phone
Does anyone have an idea what's going on?
Ryan.
Click to expand...
Click to collapse
your phone must be booted in bootloader mode to use fastboot commands unlike adb commands that are used when booted in the OS
Hello, I need to use fastboot commands, but when I type in fastboot devices I get a blank space in my command prompt. I have the latest drivers for my phone, which is the Samsung Galaxy S9 (G960U1) (Qualcomm/US model). ADB commands do work; when I use the command adb devices, I do get the device. I do have OEM Unlocking on, as well as USB Debugging. I have been following the instructions from https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-snapdragon-roms-kernels-recoveries--other-development/root-t4041815/post81608559#post81608559 for rooting this model of phone, however I am trying to install an Android 11 beta.
Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!