Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Ghuillaume said:
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Click to expand...
Click to collapse
Don't know if there is a simpler option, but this might help you:
http://forum.xda-developers.com/showthread.php?t=2433307
Not sure if adb works with usb debugging disabled though...
That has to be the Worst case scenario. Another reason I use Google drive and keep pics synced via cloud
Sent from my Nexus 4 using xda app-developers app
It's really annoying, I just need to unlock my phone but I can't !
I'm not comfortable with the idea having my pics on Google's servers, but I will find something to backup data now..
Maybe the only way is to wait the nexus to be obsolete and find a screen for a low price
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
Ghuillaume said:
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
Click to expand...
Click to collapse
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
i know with my HTC desire i run adb, when the device is turned off and connected to PC .
i think you can try it with your N4 , there are tools to do it google it .
good luck
You can try some combination of Airdroid (older version) and adb/shell command. So you'll need your device connected and older version of Airdroid - not two, because it asks for user action to accept the connection, and the older one just gives random generated password for the user to input in their browsers.
Now, you'll need to push the apk on your phone, and then just start it from your adb shell with the following command:
am start -a android.intent.action.MAIN -n com.sand.airdroid/.Splash - this should work on the old version
am start -a android.intent.action.MAIN -n com.sand.airdroid/.SplashActivity_ this works on last airdroid
At least you can try with other app that doesn't need user interaction on their display to get into the phone memory from their browsers. You can just install them from play store.
The first time that I'm writing here in Nexus forum though I am here with my 2 old DHD for about 2 years and I hope my answer could be helpful. And now I am here because of my soon to come Nexus 4
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
You don't need root access, just adb debugging.
For everything off your phone: adb pull /sdcard/
Done.
EDIT: If you just want your pics from your camera the command would be adb pull /sdcard/DCIM/Camera/
lopezk38 said:
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
Click to expand...
Click to collapse
You don't need root to use adb.
You only need to for adb to access anything beyond the sdcard.
When you first use adb there is a pop up on the device that asks if you want to allow the pc access.
He can't use the touchscreen to confirm its ok. This is the reason after I flash a Rom hook up to my pc ASAP and have it remember my computer to allow me access if this were to happen to me.
illru said:
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
Click to expand...
Click to collapse
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
studacris said:
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
Click to expand...
Click to collapse
If you flash the custom recovery immediately after unlocking (without rebooting into android in between) your data should not get wiped.
Well then... I sit here humbly corrected.
studacris said:
Well then... I sit here humbly corrected.
Click to expand...
Click to collapse
Dont worry, its not really an officially documented thing...more of just a bug with the bootloader.
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
illru said:
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
Click to expand...
Click to collapse
I dont think adb works in stock recovery. Only custom ones afaik.
Related
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.
x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.
USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.
Mind telling me what you did, im stuck in the same situation
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?
gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26
Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server
EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?
It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!
jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.
Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?
myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers
I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.
how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.
Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:
leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.
did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:
Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.
Hi folks,
yesterday my Nexus 4 hit the ground and the front glass just bursted. Touch is not working anymore and the screen is locked (only slide to unlock, no pin or gesture). I can connect it to my PC and can access the internal storage, so backing up images, music, etc. is not a problem.
I have some apps installed of which I want to transfer the app data to my new phone. Debugging is enabled so I thought, well that'll be easy just run adb backup. Thought so... As adb backup requires a user action when it comes to entering the password I'm doomed
Does anybody has an idea or experienced the same problem on how I can get adb backup to work without being able to use the touch screen?
I'm not limited to adb backup but as my phone is not rooted I assume there are not a lot possibilities besides.
Thanks a lot for your help.
calex
calex3141 said:
Hi folks,
yesterday my Nexus 4 hit the ground and the front glass just bursted. Touch is not working anymore and the screen is locked (only slide to unlock, no pin or gesture). I can connect it to my PC and can access the internal storage, so backing up images, music, etc. is not a problem.
I have some apps installed of which I want to transfer the app data to my new phone. Debugging is enabled so I thought, well that'll be easy just run adb backup. Thought so... As adb backup requires a user action when it comes to entering the password I'm doomed
Does anybody has an idea or experienced the same problem on how I can get adb backup to work without being able to use the touch screen?
I'm not limited to adb backup but as my phone is not rooted I assume there are not a lot possibilities besides.
Thanks a lot for your help.
calex
Click to expand...
Click to collapse
Do you have a custom recovery? Try flashing a non-touch one. Adb should work from within it.
abaaaabbbb63 said:
Do you have a custom recovery? Try flashing a non-touch one. Adb should work from within it.
Click to expand...
Click to collapse
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
calex3141 said:
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
Click to expand...
Click to collapse
Then you'll lose your app data.
calex3141 said:
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
Click to expand...
Click to collapse
Your outta luck it seems then... If its that important to you you could buy a replacement screen for the n4... Get your data and sell it and get the money you spent in the screen back.
Sent from my Nexus 4 using Tapatalk
If the apps that u need data are on sdcard(their datas)then u just do adb pull /sdcard c:\sdbackup with phone on.
if not then:
@calex3141 :
1ST: IM NOT RESPONSABLE FOR ANY DAMAGE / FAIL WHILE DOING THIS METHOD, I TESTED ON MY FRIEND´S N4 BUT I CANT GUARANTEE THAT WILL WORK ON EVERY NEXUS (INCLUDING YOURS), USE AT YOUR OWN RISK.
2ND: DO NOT CRY IF U CANT GET BACK THE FILES IF SOMETHING FAIL. YOU COULD JUST BUY SCREEN REPLACEMENT OR GET A JTAG DUMP
3RD: do carefuly. if you are nervous calm down b4 doing this. one single command and u can format the nand so be careful.
4TH: I hope it Works for u .
5TH: u need to have adb seted up and also drivers. if you dont know how, search google(for drivers).
for adb just install minimal adb and fastboot
6TH: its recomended to test to see if cygwin(u will know what it is in a moment) is working (do some commands on it, like cd .. (to go back)or ls (list files) )
7TH: if u have any errors contact me asap and i will try to help you
LETS GO:
unlock the bootloader: (type in cmd prompt, fastboot oem unlock, and follow instructions on phone)(DO THE MANUAL WAY, DO NOT USE TOOLKITS, KEEP READING TO KNOW WHY)(it will say that u will loose files, but it actualy dosent format, it just change the 1st´s block of userdata partition to make it unmountable normally,thats why toolkits do fastboot format userdata after unlock.and tutorials say to format data in STOCk recovery, since custom ones dosent format, just delete everything except sdcard)
(do not format anything, even on stock recovery)
flash multirom recovery:http://d-h.st/pzv (Thanks@tassadar for his great work)(the only that i use, so i cant tell others)
then do this
http://forum.xda-developers.com/showthread.php?t=1994705
(instead of doing it with phone on, just do on recovery,adb is enabled on it)
Greeting team!
I need some help to unlock and access my pic/files on my nexus 4. I have a nexus 4 that runs on stock ROM, boot loader untouched, and Developer option turned on. Unfortunately, I dropped the phone on concrete and broke my screen. The device is functioning fine, charge, screens turn on off but doesn't register touch so I can't unlocked the devices. I have pattern lock and all I really need is to pull pics and files from the devices. Is there any way I can unlock the device other than physically from the screen? I checked with a local shop to replace the screen but realistically it would cost more to replace ($160) than to get a refurbished.
Any advice is greatly appreciated and thank you!!!!
qdochemistry said:
Greeting team!
I need some help to unlock and access my pic/files on my nexus 4. I have a nexus 4 that runs on stock ROM, boot loader untouched, and Developer option turned on. Unfortunately, I dropped the phone on concrete and broke my screen. The device is functioning fine, charge, screens turn on off but doesn't register touch so I can't unlocked the devices. I have pattern lock and all I really need is to pull pics and files from the devices. Is there any way I can unlock the device other than physically from the screen? I checked with a local shop to replace the screen but realistically it would cost more to replace ($160) than to get a refurbished.
Any advice is greatly appreciated and thank you!!!!
Click to expand...
Click to collapse
Is USB debugging on? If it's on i think you might be able to get the files with adb.
Im not sure but how do I test that?
qdochemistry said:
Im not sure but how do I test that?
Click to expand...
Click to collapse
Do you have adb installed?
I don't have that installed .. Was that the only hope to get unlocked through PC?
Adb is the software on PC that is used to interact with the android device. You can still install adb on your computer using one of the many guides on xda.
Care to elaborate or can you kindly point me to a thread with step-by-step applicable to my case
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Here you go. It's not an xda thread, but I think it is good enough for you to understand and install adb. After you install this, you can send the commands through terminal to your phone. You might be able to pull the files off your device to the computer, but we'll cross that bridge when we get to it. Sorry for lack of elaboration on my previous post.
lolcakes203 said:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Here you go. It's not an xda thread, but I think it is good enough for you to understand and install adb. After you install this, you can send the commands through terminal to your phone. You might be able to pull the files off your device to the computer, but we'll cross that bridge when we get to it. Sorry for lack of elaboration on my previous post.
Click to expand...
Click to collapse
Yes - I remember now. I installed this when I was putting Android on Touchpad. But my command on Linux is incredibly limited and I managed to do so with step-by-step instructions from post. THanks for the link but I don't quite understand how to do it without detailed commands.
qdochemistry said:
Yes - I remember now. I installed this when I was putting Android on Touchpad. But my command on Linux is incredibly limited and I managed to do so with step-by-step instructions from post. THanks for the link but I don't quite understand how to do it without detailed commands.
Click to expand...
Click to collapse
Try connecting your device with an USB cable. Then use the shortcut you created when following the above guide to open the command prompt in the correct location. Then type in the command prompt: "adb devices" and press enter. If you see some numbers listed after that you can use adb to get files from your phone. If you don't I'm not aware of any way of getting access to your files.
Will test it out and thank you very much!!
Hi Guys,
This is my first message in this forum even if I read so many useful stuff here in the last few years. So first of all thanks for the many useful tips
Now I am facing a problem that probably is prohibitive even for you gurus.
This morning I broke the screen of my nexus 4, I can still boot it and the os seems to work fine. Unfortunately the touch screen is totally gone and I am not able to unlock the security pattern and access the phone. The phone is stock and not rooted.
I would like to retrieve all the data stored in the phone and access some app, so I tought I could use [email protected] Unfortunately adb tool says: device unauthorized. Please check the confirmation dialog in your device.
Of course I can't access any confirmation dialog since the touch screen is not working. Then I tought I could go in recovery mode and do something but when I reboot in bootloader and then go into recovery mode I only see the green android and a message that sounds like "no command".
What can I do? The best option would be to unlock adb and take control of the device trough [email protected] Do you guys thinks it is possible?
Just a quick update: I was able to access the recovery mode but I can't find my device in adb devices list
_Braid_ said:
Just a quick update: I was able to access the recovery mode but I can't find my device in adb devices list
Click to expand...
Click to collapse
Do you have USB debugging enabled? Is you bootloader locked or unlocked? If you boot into the bootloader, try using the command "fastboot devices" instead. You can only access adb from recovery with a custom recovery like TWRP.
theminikiller said:
Do you have USB debugging enabled? Is you bootloader locked or unlocked? If you boot into the bootloader, try using the command "fastboot devices" instead. You can only access adb from recovery with a custom recovery like TWRP.
Click to expand...
Click to collapse
USB debugging should be available but if I try to use adb while the phone is turned on I get the "unathorized" message.
What should I do after I used command "fastboot devices"? I only see: "deviceidnumber" fastboot
In the bootloader menu I see "LOCK STATE - unlocked, SECURE NOOT- enabled"
What should I do then?
Thanks for your help!
_Braid_ said:
USB debugging should be available but if I try to use adb while the phone is turned on I get the "unathorized" message.
What should I do after I used command "fastboot devices"? I only see: "deviceidnumber" fastboot
In the bootloader menu I see "LOCK STATE - unlocked, SECURE NOOT- enabled"
What should I do then?
Thanks for your help!
Click to expand...
Click to collapse
I was able to flash a custom recovery! It is the clockwork 6.0.4.7.
Now when I am inside the clockwork and I run "adb devices" I get "unauthorized". Is there a way to authorize adb through the recovery mode?
_Braid_ said:
I was able to flash a custom recovery! It is the clockwork 6.0.4.7.
Now when I am inside the clockwork and I run "adb devices" I get "unauthorized". Is there a way to authorize adb through the recovery mode?
Click to expand...
Click to collapse
Try TWRP instead of CWM. I think that will work. If it doesn't I at least know that TWRP will give you access to your sdcard so you at least can copy what's on there.
theminikiller said:
Try TWRP instead of CWM. I think that will work. If it doesn't I at least know that TWRP will give you access to your sdcard so you at least can copy what's on there.
Click to expand...
Click to collapse
If I install latest TWRP recovery will it work with volume and power button? I can't use touchscreen and I am not able to find on google a version of the TWRP which is not touch
_Braid_ said:
If I install latest TWRP recovery will it work with volume and power button? I can't use touchscreen and I am not able to find on google a version of the TWRP which is not touch
Click to expand...
Click to collapse
Oh, heh, forgot about that. Lol. Umm, don't think so unfortunately. But I don't think you actually need to touch anything. Just boot into TWRP and plug it into the computer. I might be wrong about ADB working with it though. But I'm sure you will be able to access your sdcard. Or can you access your sdcard when booting normally without entering your pattern? If so then that part is useless [emoji14]
theminikiller said:
Oh, heh, forgot about that. Lol. Umm, don't think so unfortunately. But I don't think you actually need to touch anything. Just boot into TWRP and plug it into the computer. I might be wrong about ADB working with it though. But I'm sure you will be able to access your sdcard. Or can you access your sdcard when booting normally without entering your pattern? If so then that part is useless [emoji14]
Click to expand...
Click to collapse
Just flashed TWRP and I am able to use adb!!!
Now what should I do to "authorize" my device and be able to use [email protected] when reboot?
_Braid_ said:
Just flashed TWRP and I am able to use adb!!!
Now what should I do to "authorize" my device and be able to use [email protected] when reboot?
Click to expand...
Click to collapse
I'm not sure... Bit i think you should be able to get your data from the phone via adb without an app. I was originally going to suggest using the command "adb backup" but it seems like you have to allow that from your phone which you need your screen to do. You could try it when you are booted in TWRP maybe it won't need confirmation then? No idea. The command and it's various settings are detailed here: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351. I honestly forgot about the app and just thought about how to get adb working... Sorry [emoji14]
theminikiller said:
I'm not sure... Bit i think you should be able to get your data from the phone via adb without an app. I was originally going to suggest using the command "adb backup" but it seems like you have to allow that from your phone which you need your screen to do. You could try it when you are booted in TWRP maybe it won't need confirmation then? No idea. The command and it's various settings are detailed here: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351. I honestly forgot about the app and just thought about how to get adb working... Sorry [emoji14]
Click to expand...
Click to collapse
unfortunately as soon as I was able to run [email protected] I realided that it does not allow to control the device but only mirror the screen. Do you guys know if there is an app that allows to control the screen of a device? Now my device is debug authorized, rooted and with custom recovery.
_Braid_ said:
unfortunately as soon as I was able to run [email protected] I realided that it does not allow to control the device but only mirror the screen. Do you guys know if there is an app that allows to control the screen of a device? Now my device is debug authorized, rooted and with custom recovery.
Click to expand...
Click to collapse
What exactly are you trying to backup? If you want to backup the whole device I think it is possible to make a nandroid backup remotely from a computer with TWRP, but unfortunately I'm not sure how. Did you try the adb command? That should also backup everything I think, if it works that is...
theminikiller said:
What exactly are you trying to backup? If you want to backup the whole device I think it is possible to make a nandroid backup remotely from a computer with TWRP, but unfortunately I'm not sure how. Did you try the adb command? That should also backup everything I think, if it works that is...
Click to expand...
Click to collapse
I am trying to retrieve data from one application. The application is financisto and there I saved all my expense information for years. Probably this does not make sense to you but I really want to recovere those data. I don't know if financisto save the db somewhere inside the phone so I thought that the easiest way would be to control remotely the phone access the app and do a db backup and export.
_Braid_ said:
I am trying to retrieve data from one application. The application is financisto and there I saved all my expense information for years. Probably this does not make sense to you but I really want to recovere those data. I don't know if financisto save the db somewhere inside the phone so I thought that the easiest way would be to control remotely the phone access the app and do a db backup and export.
Click to expand...
Click to collapse
Ahh i see, unfortunately I am not aware of any way to do that, but I'm not that knowledgeable about that so it is very possible there exists a very easy and obvious way.
Guys I finally did it!
I pulled the db of the app with the following command: adb pull /data/data/ru.orangesoftware.financisto
Then I installed the same application in another phone and I pushed my old db with adb push. When I started the application everything was there again :victory:
Thank you very much for your help!
_Braid_ said:
Guys I finally did it!
I pulled the db of the app with the following command: adb pull /data/data/ru.orangesoftware.financisto
Then I installed the same application in another phone and I pushed my old db with adb push. When I started the application everything was there again :victory:
Thank you very much for your help!
Click to expand...
Click to collapse
Great! I'm glad you got your data xD
elonus said:
Great! I'm glad you got your data xD
Click to expand...
Click to collapse
scrcpy should give you control as well as video.
GitHub - Genymobile/scrcpy: Display and control your Android device
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com