Related
I dropped my N4 on the ground this past weekend and it now has both a shattered front and back glass. The digitizer does not work so I can't use the touchscreen at all.
Here's what I can share about the status of the phone:
It is still on, I can see the screen, and is fully charged receiving messages.
The power button and two volume buttons work.
The phone's storage is encrypted with the stock android encryption.
I have a 4-digit PIN enabled on the lock screen.
The phone did not have USB debugging enabled when this occurred.
I've tried to mount it to a computer to get the files, but nothing shows up as I believe I need to unlock it with the PIN before it will mount.
I can install apps remotely from the Play store.
I have the Sophos mobile app installed and configured but I don't believe there are any commands to UNLOCK the device, only to lock it and wipe it.
Honestly, I just want my data off of the phone and would rather not replace the screen and continue using it. I love the phone but it is way too fragile. Is there any way to transfer my data? I looked into connecting a mouse to the usb and using that to enter the PIN, but the N4 does not support mice. Since USB debugging was not turned on, I can't connect via ADB. Is there some sort of app I can remotely install from the play store to turn on USB debugging? Is there some sort of app I can remotely install to remotely unlock the device with my 4-digit PIN? If I let it die and then try to boot into recovery, will ADB work then? If so, how would I get the data off of the device if it is encrypted? Any guidance would be greatly appreciated.
Thanks in advance!
Is it running a custom recovery?
If yes, just go into recovery and do a nandroid, boot back into android and copy the backup.
If no, there's a thread somewhere with instructions on how to unlock your bootloader WITHOUT wiping your phone.
Unfortunately this is the only android phone I've ever owned that I haven't touched and left completely stock... No custom recovery, no custom ROM. I'll try to look for the instructions on how to unlock the bootloader without wiping the phone, but if I do a nandroid and boot back into android how will I transfer the data? I'd be stuck at the screen where I have to type in my encryption password, and even if I got past that I still can't mount the device in Windows to transfer the data?
Anyone?
Exousia said:
Unfortunately this is the only android phone I've ever owned that I haven't touched and left completely stock... No custom recovery, no custom ROM. I'll try to look for the instructions on how to unlock the bootloader without wiping the phone, but if I do a nandroid and boot back into android how will I transfer the data? I'd be stuck at the screen where I have to type in my encryption password, and even if I got past that I still can't mount the device in Windows to transfer the data?
Click to expand...
Click to collapse
The only way I can think is flash an advanced version of cwm (if it doesn't already have one) that has a file manager and make a backup, and copy the recovery to a location on the SD. Then mount USB storage and copy everything over.
Edit: actually, you could mount USB storage in cwm to copy files over, then make a backup through adb on to your computer, there's some tutorials on how to do that
Sent from my Nexus 4 using xda premium
do you have adb installed? cant you copy the files in bootloader mode to the computer? havent tried yet, and im on my work laptop right now, cant try it.
zakoo2 said:
do you have adb installed? cant you copy the files in bootloader mode to the computer? havent tried yet, and im on my work laptop right now, cant try it.
Click to expand...
Click to collapse
as far as I know no. In bootloader mode is only fastboot, not adb
Sent from Halo.
what i dont understand is how you cannot connect the phone with mtp... that should work without debugging.
EDIT: sorry, youre right, when the device is encrypted, you have to unlock it before mounting.
looks like you made pretty damn sure there is no way for you (or anyone else) to get access to the data on your device :/
although i dont know about unlocking without wiping. maybe that could work.
sent from my Nexus 4...
Google search a program called Motorobo; equivalent to what service providers use.
Sent from a neXus device
I have a Generation 1 32GB Nexus 7. It has just been Factory Reset using the Pow, Vol +. Vol - combo to enter recovery and then using the Pow, Vol + combo to get to the menu to do a factory reset. I did this because my Nexus 7 was stuck on the X screen after several months of not being used, due to purchasing a more robust tablet.
I have successfully gotten past the X screen and I am not looking at the Welcome screen to select my language. On this screen I am getting what seems to be an infinite number of pop ups stating:
Unfortunately, Currents has stopped
Unfortunately, the process com.google.process.location has stopped.
Unfortunately, Google Play services has stopped.
Unfortunately, the process com.google.process.gapps has stopped.
Not in this order, but perpetual none the less.
I am able to get them to stop after several minutes of pressing OK, and I am then able to proceed to the select WiFi screen. Here, My nexus 7 is not finding any networks, where my GS4, laptop, and desktop all find 20+ wireless networks. My network is hidden, and I have attempted to connect to it via 'Other Network..." However it instant informs me unable to connect. I have also attempted a WPS connection and instantly I am told:
WPS failed. Please try again in a few minutes.
I have since tried every couple of minutes while typing this, ensuring my router is in WPS mode as well.
I very distinctly remember there being a skip button on this screen in the past, because when i purchased it was opened it in the car and was messing around with it before I got home, however no matter what voodoo I perform, nor how many times i restart the process and come back to this screen, I am unable to continue the initial setup.
Here is what I know FOR SURE about the state of the Nexus 7 prior to All my troubles.
1. The bootloader is unlocked, as I see the unlock icon on the Google splash screen.
2. It was previously set to USB debugging mode, however i am not sure if this gets reset when factory resets are performed.
3. I have installed apps to allow the USB port to connect to a dongle to attach external storage devices, this was unsuccessful, and prompted the purchase of the new tablet.
4. I have previously installed several custom ROMs, rooted, and in general messed around with the software successfully many many times. All were working fine.
5. The last ROM was the 4.2 Stock ROM
I have since updated my Nexus Root Toolkit program that I have been using since Wugfesh released it, and I am currently unable to get past the "checking ADB status". The program itself is not detecting the Nexus 7 in any regard, nor is my PC when connecting to the cable. I have tried several cables that are working for my phone, and have tried several ports that are also all working for my phone.
I have uninstalled all the drivers, and re-installed all of the drivers, and I have ensured they are the correct ones.
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen.
The Wifi was for sure working the last time I used the Nexus 7, as I was using it to control a Chromecast in my bedroom and play games.
Any help would be greatly appreciated, as I would like to not have to concede to scrapping my Nexus 7.
tzelo said:
I have a Generation 1 32GB Nexus 7. It has just been Factory Reset using the Pow, Vol +. Vol - combo to enter recovery and then using the Pow, Vol + combo to get to the menu to do a factory reset. I did this because my Nexus 7 was stuck on the X screen after several months of not being used, due to purchasing a more robust tablet.
I have successfully gotten past the X screen and I am not looking at the Welcome screen to select my language. On this screen I am getting what seems to be an infinite number of pop ups stating:
Unfortunately, Currents has stopped
Unfortunately, the process com.google.process.location has stopped.
Unfortunately, Google Play services has stopped.
Unfortunately, the process com.google.process.gapps has stopped.
Not in this order, but perpetual none the less.
I am able to get them to stop after several minutes of pressing OK, and I am then able to proceed to the select WiFi screen. Here, My nexus 7 is not finding any networks, where my GS4, laptop, and desktop all find 20+ wireless networks. My network is hidden, and I have attempted to connect to it via 'Other Network..." However it instant informs me unable to connect. I have also attempted a WPS connection and instantly I am told:
WPS failed. Please try again in a few minutes.
I have since tried every couple of minutes while typing this, ensuring my router is in WPS mode as well.
I very distinctly remember there being a skip button on this screen in the past, because when i purchased it was opened it in the car and was messing around with it before I got home, however no matter what voodoo I perform, nor how many times i restart the process and come back to this screen, I am unable to continue the initial setup.
Here is what I know FOR SURE about the state of the Nexus 7 prior to All my troubles.
1. The bootloader is unlocked, as I see the unlock icon on the Google splash screen.
2. It was previously set to USB debugging mode, however i am not sure if this gets reset when factory resets are performed.
3. I have installed apps to allow the USB port to connect to a dongle to attach external storage devices, this was unsuccessful, and prompted the purchase of the new tablet.
4. I have previously installed several custom ROMs, rooted, and in general messed around with the software successfully many many times. All were working fine.
5. The last ROM was the 4.2 Stock ROM
I have since updated my Nexus Root Toolkit program that I have been using since Wugfesh released it, and I am currently unable to get past the "checking ADB status". The program itself is not detecting the Nexus 7 in any regard, nor is my PC when connecting to the cable. I have tried several cables that are working for my phone, and have tried several ports that are also all working for my phone.
I have uninstalled all the drivers, and re-installed all of the drivers, and I have ensured they are the correct ones.
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen.
The Wifi was for sure working the last time I used the Nexus 7, as I was using it to control a Chromecast in my bedroom and play games.
Any help would be greatly appreciated, as I would like to not have to concede to scrapping my Nexus 7.
Click to expand...
Click to collapse
If you have a twrp recovery and a otg cable
You will have a few more options
Reply if you have those
tzelo said:
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen..
Click to expand...
Click to collapse
Tapping all four corners of the screen will skip the WiFi part of setup not sure if the order you tap them in matters. Other than that boot into fastboot mode and follow the sticky for flashing a new factory image. Fastboot does not need USB debugging enabled.
Sent from my C5303 using xda app-developers app
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks
ozgurust said:
I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks
Click to expand...
Click to collapse
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/
prasanth21 said:
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Click to expand...
Click to collapse
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..
adb push will put them back, but your phone will probably mount normally and show up in 'My Computer' now so you could just do that.
ozgurust said:
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..
Click to expand...
Click to collapse
I'm glad you were able to pull off the files from the phone.
You can use the adb push command to put the data back into the phone
Try this : adb push /path/to/local/file /mnt/sdcard/path/to/file
or
adb -s [yourdeviceserialnumberhere] push /system/[whateverdirectory]
You can check out this too : http://forum.xda-developers.com/showthread.php?t=2167651
The post clearly explains multiple adb commands
Hope it helps!
Hi!
My Nexus Player was rooted, but this was messed up by a recent OTA update (not the current 7.1.1, but the last one before that I guess), after which I factory reset it. I don't really remember if I tried connecting it to my PC then or do something else. A while later I tried rerooting with Nexus Root Toolkit, but there were some issues with the ADB drivers I think, it didn't maintain a connection with the computer during fastboot. It also kept resetting the USB default to charging (I chose MTP, but it just kept switching back by itself). So I took a break for a while and now it won't connect to my computer at all except for a brief moment while booting. All during this I've tried different cables and actually two more computers, but the issue persists. The bootloader is still unlocked and factory resets don't help. Does anyone have any idea how to solve this?
Best regards,
Mikk
re enable debugging? The flip back to Charging from MTP is by design I think...as is the inability to shut off auto update. Google trying to save us from ourselves. Have you flashed twrp? I found the only way to see the player on the desktop was when booted in twrp. Otherwise, like you , it appeared the player wasn't connected. I do believe I was still connected as a fastboot device though.
I haven't bothered to re root as my SD card is supported and kodi installed from the play store removing any need to sideload or file explorer my way to install apps. I have found the 7.1.1. update to be solid/stable with no issues.