I have a Huawei p20 with a broken screen and the touch does not work, after research I discovered that the only solution to get all my data back is via adb (and perhaps also fastboot), only that when I connect it to the pc it gives access, it recognizes the but the device is unauthorized instead in recovery mode it does not recognize it, but if I try it in fastboot mode it recognizes it as fastboot, how can I use adb?
Noristay said:
(...) when I connect it to the pc it gives access, it recognizes the but the device is unauthorized instead in recovery mode (...)
Click to expand...
Click to collapse
Maybe you will find something interesting in the thread:
Bypass secure USB debugging prompt on phone with broken screen
Hello everyone, I have a Samsung Galaxy S II (I9100) with Cyanogenmod 11 (Snapshot M12) installed. Recently I dropped my phone and the screen was completely shattered. The display does not work, neither does the touch. However, the phone works...
forum.xda-developers.com
ze7zez said:
Maybe you will find something interesting in the thread:
Bypass secure USB debugging prompt on phone with broken screen
Hello everyone, I have a Samsung Galaxy S II (I9100) with Cyanogenmod 11 (Snapshot M12) installed. Recently I dropped my phone and the screen was completely shattered. The display does not work, neither does the touch. However, the phone works...
forum.xda-developers.com
Click to expand...
Click to collapse
unfortunately this post doesn't help me, as it tells them how to activate usb debugging, my problem is that when i'm in recovery it doesn't show me that my device when i type adb devices command
Looks USB is OK, because Fastboot works. But I guess that ADB isn't properly installed, especially ADB Verification failed. So you can't successfully run ADB, neither when phone is in normal mode nor when in recovery mode
Related
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
HI,
i was replacing the screen and suddenly my phone went in coma the sreen has been changed but no recovery or fast boot is accessible and even my pc is detecting it as mtp device and in adb cmd it says unauthorized or offline i need your help or my brother will kill me:crying::crying::crying: please help asap
i tried the hardbrick method but the driver installation dint succeed and the phone is still recognized as android device or mtp device.
MTP device and adb recognizes it means the phone is running fine! Check the display it sounds like it's issue.. And also when connected to PC try holding down power button and see if mtp device indication goes away (hold it for like 10 secs)
Transmitted via BACON
Hello,
my problem is that I´ve got a Nexus 4 Smartfon and the sceen is broken, so I´m not able to enter my pattern. because of this I also am not able to save my data because without entering the pattern, my computer doesn´t alowe the access to the memory.
I tried two different ways to get access to memory by using ADB:
1) I tried to delet the pattern (gesture.key) file.
I tride this first with my rooted Samsung Galaxy S3 mini and it worked perfectly. it also has USB debugging turnt on.
But my Nexus 4 hasn´t USB debugging turn on. I tried in on my S3 mini with and without and without USB debbuging it also didn´t work out.
Also my Nexus 4 isn´t even recognized as an ADB device, only in sideload mode or fastboot mode. I also think this is because of the not turnt on USB debbuging.
2)i tried to turn on the USB debbuging, so my device will be detected as an ADB device, or i can you a programm to mirror my smartphone on my computer and insert the pattern via computer.
I´ve found a pretty good tutorial on the internet but this didn´t work out. Also on my S3 mini it did´t work
So my last idea is, to us a little programm/application which i can transfer via sideload to my device and which will delete the pattern on the phone. my problem is that I´m not a programmer so I can´t do this myself.
so i would like to ask what do you think about my idea, if you could help me or do you have any other suggestions what i can do to save my data.
i´m ver thankful for any help :good:
Kaktus! :angel:
Kaktus621311 said:
Hello,
my problem is that I´ve got a Nexus 4 Smartfon and the sceen is broken, so I´m not able to enter my pattern. because of this I also am not able to save my data because without entering the pattern, my computer doesn´t alowe the access to the memory.
I tried two different ways to get access to memory by using ADB:
1) I tried to delet the pattern (gesture.key) file.
I tride this first with my rooted Samsung Galaxy S3 mini and it worked perfectly. it also has USB debugging turnt on.
But my Nexus 4 hasn´t USB debugging turn on. I tried in on my S3 mini with and without and without USB debbuging it also didn´t work out.
Also my Nexus 4 isn´t even recognized as an ADB device, only in sideload mode or fastboot mode. I also think this is because of the not turnt on USB debbuging.
2)i tried to turn on the USB debbuging, so my device will be detected as an ADB device, or i can you a programm to mirror my smartphone on my computer and insert the pattern via computer.
I´ve found a pretty good tutorial on the internet but this didn´t work out. Also on my S3 mini it did´t work
So my last idea is, to us a little programm/application which i can transfer via sideload to my device and which will delete the pattern on the phone. my problem is that I´m not a programmer so I can´t do this myself.
so i would like to ask what do you think about my idea, if you could help me or do you have any other suggestions what i can do to save my data.
i´m ver thankful for any help :good:
Kaktus! :angel:
Click to expand...
Click to collapse
Hello,
Try one of the methods stated here https://forum.xda-developers.com/showthread.php?t=2620456
Regards
Vatsal,
Forum Moderator.
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
anonimazu said:
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
Click to expand...
Click to collapse
Not sure what you expected?
ADB requires the adb binary to be run at boot via the kernel ramdisk.
Neither FASTBOOT(which isn't supported on Samsung devices) nor ODIN(download mode) run the kernel.
In short ADB does not function in download mode.
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Add Samsung A9 2018 SM-A920F to this thread's title thus mainly owners of such device get addressed.
Lucvdkant said:
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Click to expand...
Click to collapse
What does
Code:
adb devices
return?
jwoegerbauer said:
What does
Code:
adb devices
return?
Click to expand...
Click to collapse
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Lucvdkant said:
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Click to expand...
Click to collapse
You have to switch phone's USB mode to ADB.
jwoegerbauer said:
You have to switch phone's USB mode to ADB.
Click to expand...
Click to collapse
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Lucvdkant said:
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Click to expand...
Click to collapse
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
jwoegerbauer said:
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
Click to expand...
Click to collapse
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Lucvdkant said:
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Click to expand...
Click to collapse
Enabling OEM Unlock and/or USB Debugging simply sets an allowance flag, nothing else. It doesn't configure phone's USB mode.
I tried it on the laptop from work and there the phone is recognized in adb. But sadly I don't have administrator rights on that laptop to open Smalipatcher. Is there an alternative or work around available?