Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you say the USB flash drive doesn't work, do you mean the USB port in the phone?
MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver
I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.
There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
Related
So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize
So I had the magical luck of having my S4 fall out of my pocket while closing my car door, shattered to pieces, no touch response from the glass.
The problem is, I had the device locked with a pattern & pin, so I can't just plug in and backup all my photos and stuff that were saved with local device storage. I also can't get adb to connect to the device (with developer options enabled), I always get a "device offline" error (I've updated ADB to the current 4.2.2 version, but I cant whitelist it because I can't allow it from the phone without touch)
Now, I still have root, and I was able to blindly install CWM (the OUDHS-Recovery-jfltespr-1.0.3.3.tar) version with Odin. I'm assuming it went well because I heard the sprint chime on restart.
WHAT I NEED: Is someone to either give me some screenshots (or number of button presses) to enable internal storage to be accessible by usb in cwm (also how to get into it too). I figure if I'm able to use volume presses and the home button I can get to my internal files. Other than this option I'm at a loss before I return it. If anyone can help I would be so damn grateful.
I'll draw you a picture too.
EDIT 1: I have a picture of the main CWM screen from a youtube video here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now all i need is the mount and storage menu
So nobody can help? I didn't think a cwm menu was that hard to come by with an S4.
alexcu said:
So nobody can help? I didn't think a cwm menu was that hard to come by with an S4.
Click to expand...
Click to collapse
Were you able to connect with adb before? Was usb debugging checked in settings before the drop?
If you could get adb to connect, you could use a program like android screencast to view your phones screen on your computer.
fgr said:
Were you able to connect with adb before? Was usb debugging checked in settings before the drop?
If you could get adb to connect, you could use a program like android screencast to view your phones screen on your computer.
Click to expand...
Click to collapse
That was my first move actually.
Problem is, even though debugging was enabled, I can't whitelist my PC from my phone. This is a new 4.2.2 feature to prevent data theft ironically.
All of these options will just return an "adb: device offline" error when it's connected. Trust me, I wish it was that easy.
You can't connect while in recovery either?
It would be kind of a pain, but you could pull multiple files that way.
Look HERE
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:
Hello,
I am having problems with adb recognition on recovery mode. I did manage to contact codeworkx, but it seems it's just me, because for him it's working. The drivers are installed correctly, because adb sideload works just fine. I want to use the new adb backup function, to backup files right into my PC, but no recognition is stopping me. Has anyone ever had this problem? If so, any ideas on how to fix it are really welcome. Thanks in advance!
adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?
sk8223 said:
adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?
Click to expand...
Click to collapse
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
punpun1 said:
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
Click to expand...
Click to collapse
That's not recovery, that's simply adb.
Are you sure you're using the correct command? Read this: https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I just tried using adb backup with my device and it works fine. You're supposed to do it from within actual ROM itself, not TWRP. So boot into your ROM and try again.
Hello!
So, my Mi 9T suffered water damage recently and the screen completely stopped working. I took it to the repair shop but a new screen for it would be way too expensive to be worth repairing.
I have the device with me, and i really want to recover my data on it, it is rooted with magisk, bootloader is unlocked and TWRP recovery installed. Is there any way that i can access the data through USB debugging or something like that?
I tried intalling vysor through ADB install today but it gave the error "error: device unauthorized". It's probably asking me to allow USB debugging again but there is no way i can do that without a screen/touch working as far as i know.
I saw a youtube video telling me to use the shell command to try unlocking it and there was the error.
I also tried going to C:/User/.android and deleting adbkey and adbkey.pub, didn't solve the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only thing i want is to be able to use it through my computer so i can recover data and maybe use WhatsApp while my new phone is on the way.
Any help is deeply appreciated, thank you!
gabrielziller said:
Hello!
So, my Mi 9T suffered water damage recently and the screen completely stopped working. I took it to the repair shop but a new screen for it would be way too expensive to be worth repairing.
I have the device with me, and i really want to recover my data on it, it is rooted with magisk, bootloader is unlocked and TWRP recovery installed. Is there any way that i can access the data through USB debugging or something like that?
I tried intalling vysor through ADB install today but it gave the error "error: device unauthorized". It's probably asking me to allow USB debugging again but there is no way i can do that without a screen/touch working as far as i know.
I saw a youtube video telling me to use the shell command to try unlocking it and there was the error.
I also tried going to C:/User/.android and deleting adbkey and adbkey.pub, didn't solve the problem.
View attachment 5367511
The only thing i want is to be able to use it through my computer so i can recover data and maybe use WhatsApp while my new phone is on the way.
Any help is deeply appreciated, thank you!
Click to expand...
Click to collapse
TWRP supports Media Transfer Protocol - access Imternal memory just like in Amdroid.
However, if you set a PIN/pass/pattern, TWRP would ask you to type in when booting to TWRP (but you can't if screen not working)