I think the android-dls wiki is wrong, because it suggests you should run adb in FASTBOOT mode.
There is no ADB in FASTBOOT mode.
Commands involving ADB need to be run from your computer while the phone is fully booted.
Commands involving FASTBOOT need to be run from your computer while the phone is in FASTBOOT mode (hold down back+power when the phone is off).
I don't really want to mess with the wiki, but I suggest the owner should make that more obvious.
Hope this helps.
Spot on - caused me alot of grief this morning!
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!
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
joeyism said:
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
Click to expand...
Click to collapse
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Renosh said:
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yea I was trying to flash it, but I read from http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that another trick is to do
Code:
fastboot boot <path/name of the recovery twrp img>
So I thought I'd try it. But now my computer can't even detect my phone :/ Would there be a reason why my phone no longer communicates with my computer?
Hi, i have tf101g b90 sbk2,
went into soft brick because I installed first CWM recovery and then TWRP not corrected. The shell must be reinstalled. adb works well and read the device with your correct serial number. . The problem is fastboot, i write fastboot device in prompt and I see nothing. When I give a command, I read 'waiting for any device. I think . I think the drivers are installed well with nacked drivers,
when it is in adb mode i have installed driver asus transformer adb interface, when in fastboot mode i have installed driver asus fastboot interface. To go to fastboot mode I press both volume buttons and the serial number of device becomes 1111111111111111111, thinking that this is the correct serial for fastboot mode. At this point I think the problems are: either I need the root (which I can not do), or the drivers are installed badly (even if I do not think), or I do not go correctly in fastboot mode. The strange thing is that in adb I go well but in fastboot no. In the end I would like to run the fastboot flashall command. Thank you
I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?
If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.
Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?
Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.
So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app
OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Then obviously USB Debugging didn't get enabled in Android's Developer Options.
Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.