Boot locked Galaxy A51 not responding to ADB - Android Q&A, Help & Troubleshooting

Hello, I am new to this forum, I have a boot looped Samsung A51. That has been water damaged.
And when I try to use ADB and type "fastboot oem unlock" the cmd says waiting for device. Or when I type root in ADB, the cmd says unable to connect for root: closed.
So I have a boot locked phone that does not respond to ADB commands. I am wondering if the hardware is damaged? Any advice is appreciated. Thank You.

If I type adb devices, my device shows up. It just doesn't respond to any commands and I can't push any files...

Related

need root help, probably adb help

I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>

Problems while removing screen lock using ADB on QTAB v7

I want to unlock my cousin's tab who recently passed away and no one knows the passcode so after some googling i found that you can do it via ADB.
(https://forum.xda-developers.com/showthread.php?t=2620456)
The device successfully connects with my pc but when I execute "adb devices" it shows;
.......................... unauthorized
and running adb shell shows;
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
With the device locked Im unable to authorize my computer so I decided to search something for that too and found this article where it tells u to pull keys from another device and push it into your locked one while in recovery mode and this is where Im stuck. Whenever Im in recovery mode, adb devices shows nothing so if someone of you could help me would be awesome.

[Help] My phone does not show any confirmation on oem unlock request!

Hi everyone.
I apologize if this was already asked.
I own a Symphony H50. I am trying to install windows via change my software but it shows device too slow or protected by manufacturer.
So googled it and found that i need to unlock my boot loader.
So I installed adb,fastboot,drivers including bootloader interface driver. And booted into fastboot mode. And typed "fastboot oem get_unlock_data" and the command prompt shows 3 dots (...) And the cursor keeps flashing. And no confirmation message shows up on my phone.
It only shows "FASTBOOT mode".
Another thing i found out while installing adb drivers that it listed my phone manufacturer as HTC.
So is the problem with my phone?
And how do i fix it?
It may be a problem with driver, uninstall the previous one and install Koush universal adb driver from kaushikdatta.com
Use the link given below for a thorough tutorial to replace drivers.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Thanks for reply,
I'll try the drivers.
Though my adb drivers are working fine. My issue is with fastboot.
When i boot into fastboot mode it shows "FASTBOOT mode" on a black screen.
But i would try with the
That black screen with fastboot mode written at the bottom comes up on every phone when you boot into bootloader.
Please read the whole guide before proceeding.
You may skip the driver and adb installation part if u have already taken the measures I stated before.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.

Galaxy S4: ADB recognizes device when normal. Although not recognized in bootloader

Hello everyone!
I am currently having issues with my Galaxy S4. I am attempting to install twrp onto it although I am having issues. I have not made any modifications to it, it is running the stock rom and it is not rooted.
I am following this guide: https://www.xda-developers.com/how-to-install-twrp/
I installed adb and fastboot using: https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I have not gotten any errors.
I type into command prompt:
adb devices
I then get my devices id.
I then type adb reboot bootloader
Once it finishes going into bootloader.
I type adb devices and then get nothing.
I also tried typing fastboot devices and also got nothing.
When I use flashboot flash recovery it gives: <waiting for device>
Could anyone help? I am a newbie at this.
Thank you!

OPPO F15 not rebooting into Fastboot mode.

Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Those are the proper commands
([emoji88]Havoc GSI[emoji88])
Venomiest said:
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
Click to expand...
Click to collapse
The bootloader is blocked by code combination. If you try to see more attentive you'll notice the tiny message on the black screen while rebooting.
Not Working
Alien object

Categories

Resources