I am trying to unlock bootloader on my Samsung A40 with Android software tools. I have installed software tools through Android SDK Manager in Android Studio.
Adb lists devices:
However when I enter bootloader by typing adb reboot bootloader my device doesn't show with command fastboot devices:
I have tried installing drivers from Samsung site and through Android Studio Google drivers but neither worked. I installed drivers manually through device manager too.
I tried doing same commands in VM with Debian 10 but with same result.
I have tried flashing TWRP with Odin too but I got error: custom binary (vbmeta) blocked by oem lock.
I tried different USB ports too and a different cable.
Related
I wanted to install a custom rom on my Xiaomi Mi A3, so I had to install the twrp. I enabled oem unlock from the developer settings of the phone and rebooted into bootloader mode, but when I ran the command "fastboot oem unlock" it gave me as a result
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(this on linux)
Then I tried on windows, but fastboot did not recognize my device, while windows and adb yes.
Any solution?
You have to use Xiaomi's unlock tool, not fastboot. After 7 days you'll be able to unlock. If your xiaomi is not recognized on windows, download an older xiaomi unlock tool (on their website there are lots on the faq), it will have a driver installer, then your xiaomi is going to get recognized so you can unlock.
As Guerlando OCs said, you will need to use Xiaomi's unlock tool to unlock your Xiaomi device (Windows only). Also, you can use XiaoMiTool V2 if you are on Mac or Linux (on Windows will also work).
fastboot oem unlock will not work, because OEMs set their own fastboot oem commands. Xiaomi unlock tool uses a modified version of fastboot which adds a command: fastboot flashing unlock_bootloader [UNLOCK_CODE], that unlocks the bootloader of the device after obtaining the code from Xiaomi's servers.
If you need to install drivers, download MiFlash from here and install the device drivers from there.
I want to flash a special disk image onto an Android Emulator (Google Pixel 2) using adb and fastboot. The virtual device can only be detected by adb but not by fastboot. I already tried (cmd as an administrator):
C:\windows\system32>adb devices
List of devices attached
emulator-5554 device
C:\windows\system32>adb reboot bootloader
C:\windows\system32>fastboot devices
C:\windows\system32>
I am using Android Studio (Android SDK and Google USB drivers are installed properly, i also enabled USB debugging in the emulator) on Windows 10. Is it possible (in principle) to use fastboot together with an emulator? If yes, do you have an idea why it does not work here?
No, you can't use fastboot with Android Studio emulator. AVD does not have a bootloader, it just boots the system and ramdisk images.
If you want to use fastboot, you'll need a real device that supports it (mostly everyone but Samsung's).
You may find more information in this post: how to reboot the emulator into recovery mode
I've been trying to install TWRP custom recovery on my galaxy s8 and haven't had much luck getting past this particular issue. After looking on several forums and watching pretty much all of the solutions on youtube I've resorted to posting my problem.
So, after enabling usb debugging and OEM unlocking I open up platform-tools in cmd prompt and type in the following:
adb devices - this is showing me that my device has been detected by my pc
adb reboot bootloader - this then takes me to the bootloader mode
fastboot flash recovery recovery.img - which presents me with "waiting for any device"
All the solutions that I've seen have something to do with the drivers but I believe mine is up to date after installing it manually from C:\Users\"My Name"\AppData\Local\Android\Sdk\extras\google\usb_driver
Any help would be much appreciated. Thanks
I have run into exactly the same issue on a Mi 11.
A working solution has been provided by Shendai on the GrapheneOS Discussion Forum (https://discuss.grapheneos.org/d/2753-trouble-installing-google-usb-drivers-w-fastboot-onto-windows-10/2).
For this, the usb/fastboot drivers for your phone need to be downloaded onto your computer.
To fix this, execute set devmgr_show_nonpresent_devices=1 in an administrator command prompt, then unplug the phone from the computer.
Next go to the Device Management on Windows and uninstall all drivers related to the phone. Connect the phone to the computer again, find the now unknown device in the device manager and install the drivers by browsing the computer for drivers and selecting the corresponding files.
After this, you can run adb reboot bootloader to enter the bootloader and fastboot devices to verify, that the phone is being detected.
Worked in Windows 11 with disabled driver signature enforcement.
So I have USB Debugging enabled on the device and its plugged in via USB. Currently, executing adb devices lists nothing in Android Studio terminal. I've checked Device Manager and the device is successfully showing up under "Portable Devices" as "Venue 8 7840". The Dell website doesnt list any drivers for this device.
Using Update Driver Software in Device Manager says the device driver is up to date and lists MTP USB Device.
I've found threads like this one and even though my device is listed in the Device Manager I tried editing the android_winusb.inf anyway, but the issue persists.
Running Win 7, AS 1.3.
Any insight into this issue is appreciate, thanks!
Here is the solution Dell Venue 7/8 Unlocked Bootloader
A quick search on your device says it runs Android 4.2.2.
If this is the Android version on your Dell Venue, then you should have received a dialog on your Android device, asking whether to accept an RSA key that allows debugging through your computer. Acknowledging this dialog should then unlock the Android device and allow debugging.
Did you receive the security dialog?
If not, it also requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
You can run "adb version" (without the quotes) on a your terminal/command prompt to get the adb version you're running.
See Android Developer website on Enabling ADB:
Enabling adb Debugging
I found Android XDA has universal adb drivers for Dell Android devices.
Dell ADB Universal Drivers
Hope this helps.
I know I'm late, but this tool should help you: http://adbdriver.com/
Open it, click Install and follow the instructions. Good luck!
I have a Samsung Galaxy S4 that I would like to deploy my app to using eclipse. However the device simply does not appear on the list of devices to deploy to.
I am using Windows 7 64-bit.
The phone appears as a drive when plugged in, allowing me to transfer files to and from the device.
The phone has developer mode and USB debugging switched on.
In the Android SDK Manager, the Google USB Driver appears as installed.
I have manually installed the usb driver located at \extras\google\usb_driver\.
This same device has been recognised and deployed to on other computers.
I have tried restarting the adb server in command prompt using adb kill-server and then typing adb start-server.
I have tried restarting both the phone and the computer.
My deployment screen simply thinks there is no android device:
Any ideas? Is there perhaps something I am missing here that is required for my android device to be properly recognised by eclipse?
First, is your device id showing up when you use adb devices
If it is, it's just a matter of restarting eclipse. Another cause could be that you're using the Google USB driver, whereas you should be using Samsung's Android USB driver, which can be found here:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Get the drivers for your Galaxy S4 here:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
P.S. ya better got Nexus 5
You should install Samsung KIES, that have included some USB Drivers and something more, then you will able the possibility to eclipse sdk recognize your Phone, i was with the same problem, after i installed KIES everything worked fine, trust me.
KIES Download:
http://www.samsung.com/us/kies/