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.
Related
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
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 guys, I have an Samsung Galaxy SIII mini GT-I8190 and i have a lot of problems on it! I was on services but the man told me that he cannot do anything!
1. I can't connect my phone to the PC, i activate USB debugging, i have tried differents PC's, i tried 5-6 USB cables and nothing. My device it's only charging, i have installed and Kies and drivers. Nothing!
2. I cannot acces the camera, sais: Camera failed, i have deconect and reconnect pins of the camera and nothing. I tried and hard resets.
3. The biggest problem: I put simcard in the device morning and in the evening my device keeps restarting while i don't remove my sim card. After 1 hour i can to put the simcard at the place to make a call.
4. I can't root my device with any apps who says that he root my device whitout PC, because i have said i cannot connect my device to PC to root him with the PC!
Help me please!
SfantuAteu said:
Hi guys, I have an Samsung Galaxy SIII mini GT-I8190 and i have a lot of problems on it! I was on services but the man told me that he cannot do anything!
1. I can't connect my phone to the PC, i activate USB debugging, i have tried differents PC's, i tried 5-6 USB cables and nothing. My device it's only charging, i have installed and Kies and drivers. Nothing!
2. I cannot acces the camera, sais: Camera failed, i have deconect and reconnect pins of the camera and nothing. I tried and hard resets.
3. The biggest problem: I put simcard in the device morning and in the evening my device keeps restarting while i don't remove my sim card. After 1 hour i can to put the simcard at the place to make a call.
4. I can't root my device with any apps who says that he root my device whitout PC, because i have said i cannot connect my device to PC to root him with the PC!
Help me please!
Click to expand...
Click to collapse
Hello, thank you for using XDA Assist!
For the best answers, please post your question here:
http://forum.xda-developers.com/galaxy-s3-mini/help
Your device experts are located there and will be able to help.
Good luck!
I was recently trying to root my Samsung Galaxy Alpha (and it is the first time I root a device), and as I plugged the phone into the computer it doesn't recognize. At first I thought of the drivers, so I went on google and searched for usb and adb/fastboot drivers, but it still didn't recognized. I took a look at the rooting guide I was following, and I saw that it said to turn on OEM Unlock, but I saw that the toggle wasn't there. I searched here on XDA Forums, and even on Google but I didn't find anything. If anyone had this issue or knows how to solve it please respond ASAP.
Is the phone connected to the internet? Sometimes that brings up the OEM unlock toggle in the developer options. There's a related article for the Galaxy S8 and S9 which might be relevant to your situation: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
If using a Windows computer, you should be able to install Samsung Galaxy drivers. Enable USB debugging on your phone and you should be able to use adb commands in a terminal. Odin software is needed for performing tasks while the phone is in 'Download' mode.
adb can be installed on your computer by searching for ' platform-tools '
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