Database Users

[Q] Fastboot Recovery/Remotely enable USB debugging

SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.

Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory

EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.

Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!

So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.

I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.

So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key​11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process

Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!

Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key​11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance

not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen

Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?

usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:

almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:

bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.

*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!

HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!

HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL

npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?

jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.

[Q] How to solve the adb devices unauthorized

Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~

YouthTeam said:
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you

also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.

I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?

problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?

unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.

Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!

are that problem was solved?
how?

What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.

No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.

emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?

same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.

Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.

for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.

I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot

No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.

jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks

abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?

bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone

my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet

[Q] N4 Broken Screen, Desperate, Kit Kat 4.4.2, Stock Everything, No USB Debugger

Hello,
I just came back from my honeymoon and all of my pictures are on my N4. Of course before I pull the pictures, I drop the phone is the screen is cracked and the touch does not work anymore.
I'm really desperate to get these pictures. I've read all over online but my problems are this with all of the help out there:
My phone is the latest 4.4.2 on T Mobile.
It has stock EVERYTHING (bought straight form google), and the USB debugger is not enabled. (next phone I get this is the first thing I'm enabling.
I've been trying to follow instructions online but a lot of items have changed between last year and Kit Kat now and some steps such as unlocking the bootloader seems to wipe out everything on my phone.
I've been trying to use ADB and Freeboot but really havent gotten anymore.
I've also read that I can maybe use a usb mouse to substitute and unlock my phone? USB OTG? How do I know if my nexus has that enabled?
I'm even considering getting a new screen so I can try to replace the current one and get my photos. I dont care what happens to the phone but the pictures are priceless to me.
Is there any thread or guide that incorporates 4.4.2? the more detail the better of course.
Much thanks in advance.

have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...

Shubhamqweasd said:
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Click to expand...
Click to collapse
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.

zhanism said:
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
Click to expand...
Click to collapse
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652

Shubhamqweasd said:
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Click to expand...
Click to collapse
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.

zhanism said:
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
Click to expand...
Click to collapse
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.

acejavelin said:
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
Click to expand...
Click to collapse
I have same problem with broken screen, i bought for 56$ full kit on ebay, no need separate glass from screen. took me 1h20min, never done before but what a relief seeing everything working

You do not need USB debugging to transfer files. On windows, open file explorer and with your nexus 4 connected it should appear on the left side as Nexus 4. Or if you have osx use http://www.android.com/filetransfer/.

[Q] Screen cracked and unresponsive but display still visible. Need help getting data

Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.

The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.

oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.

jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site

[Q] I9505 Help Needed ADB

Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked

What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).

Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.

Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want

Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.

If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed

bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.