Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Woops, I just realized you haven't unlocked the tablet. Sorry, everything I wrote below won't work because the bootloader won't let you boot into an unsigned recovery image and if you try to unlock now the process will force a wipe. The only thing I can suggest is try booting into safe mode. Sometimes you can get the MTP device to show up even if the system isn't totally started. There is a link in the stuff below for that. I guess you could also try the adb backup again, now knowing what is going on with adb and recovery.
[Info] Guide to entering safe mode, bootloader, stock recovery
[GUIDE] Full Phone Backup without Unlock or Root
====
Almost TLDR.
Anyway, I don't know why you get the System UIDs inconsistent. Probably some corruption somewhere, but who knows the cause. There are sporadic reports of it on this tablet and actually other brand tablets as well, but it doesn't seem like the more widespread issues. Personally I think it would be worth it to exchange it to see if that helps.
Regarding your ADB issues, there are multiple:
First, in stock recovery, adb isn't running until you select sideload, that is why you don't see it under adb devices.
Second, the adb in stock recovery (ie adb sideload option) is restricted in its functions. It basically only supports sideloading.
You don't seem to have this issue, but the regular Google USB drivers won't work for adb under recovery because the USB IDs change and the device usually shows up as an unknown device "Flo". If you are afflicted by that issue, see this post for drivers that will work under both android and recovery:
[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)
Hope is not lost though, you can boot into TWRP recovery, which does support a full adb and you should be able to "adb pull" all your files off the sdcard. Just don't do any wipes or formats by accident until you get the files off.
Download TWRP from here: http://techerrata.com/browse/twrp2/flo
Place the file in the same directory as your adb/fastboot executables
Boot into bootloader using Power+VolDown, see this post if you have trouble
[Info] Guide to entering safe mode, bootloader, stock recovery
connect the USB cable to a USB2.0 port on your computer
you should see some indication that the android bootloader device got recognized
in your adb directory enter (I renamed the downloaded TWRP image for convenience)
fastboot boot twrp.imgafter maybe 5 seconds of seemingly nothing going on, TWRP will start up
your PC may ask you for drivers, if so, see the link above where I provided drivers
after that you should have full adb available to pull your files
After you are sure you have everything pulled off, try the factory image restore from google.
1. This may or may not help you but have you manually installed the adb drivers on the laptop? If not, check here. It also includes instructions on how to disable driver signature enforcement on your brother's Window 8 laptop. Now, I'm not sure if he updated that driver for flo, or if he even has to, but if that driver doesn't work, download the sdk. A driver comes in it that'll work. I know it'll be painful to wait for the whole thing to download, but it might be your best option. It's in ...\sdk\extras\google\usb_driver\
2. It's up to you whether to return it or not. I, personally, hate dealing with the return process, even if it's in-store, so I usually make-do until a fix is found, or in this situation with a Nexus device, I would try to troubleshoot it. I, too am a software developer by profession (mainly .NET; I develop on Android as kind of a hobby) and I enjoy working out issues myself. But that's just my opinion, it's completely up to you. I doubt it's any apps, I doubt it's any games. I would probably try installing factory images back onto the device and see if that helps.
Thanks for the replies, guys.
I just got home late last night, and while I was too exhausted yesterday to do anything with it, I brought the Nexus 7 with me to work today, so I'll see what I can do with it here. I thought I had the Android SDK installed on my work computer, but I don't. Fortunately, now that I'm back from holidays, I have access to fast internet connections.
My regular desktop at home and my work computer are both running Windows 7, so I shouldn't run into the driver enforcement issues that people experience with Windows 8.
I tried booting it into safe mode once, but I didn't have the USB connected. Even with safe mode, it was just frozen at the 'X' screen, but I'll try it again with the USB connected.
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It does look like progress. Try booting your phone up into recovery mode, connecting it to the computer, then installing those drivers for the phone again. Mine comes up as "Google Galaxy Nexus ADB Interface" in recovery after installing the drivers, but I think if you can get it to come up as "MTP USB Device", you might be able to use adb commands. I'm not 100% sure, but if you can get it back to recognized as an MTP device again, try quickly switching over to the command prompt and trying the "adb devices" command and see if it shows up. Of course, if you install the drivers and it comes up as an ADB interface device, you should just be able to run adb commands and not need to see if MTP will work.
The computer doesn't recognize the device at all when I start Recovery Mode. On the tablet, all I see is an Android laying down with a red exclamation mark saying "No command."
The only way I can get it to even pop up in Device Manager is if I hit "Apply update from ADB", which enables the adb sideload command, but NOTHING ELSE. If I try to run ANY other ADB command, I get "error: closed".
Remember, the device is COMPLETELY stock, not rooted, and the bootloader is locked. I had to do a wipe the last time this happened, driving down to the States at the beginning of my vacation. So even though I had USB debugging enabled before, I never re-enabled it after doing the wipe. Then I took a bunch of photos, and after rebooting the device for the first time after that one wipe, it again no longer boots up.
I would love to fix the damn thing by just doing another factory reset. But I don't want to do that, because I need to recover the photos that I've taken this past weekend.
I might call Google support and see if they know of any solution.
Stealth22 said:
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Click to expand...
Click to collapse
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
The only thing you might want to try is the adb backup command, which I've never tried from stock recovery, so there is a remote possibilty it might work, but probably not.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It would have been huge progress if you got the MTP device recognized as you could drag and drop files.
You can try spending some time figuring out whether it is a driver issue or the unit hasn't booted up far enough to response to MTP requests by removing drivers and let it reinstall with known good ones.
The ADB backup command was the first thing that I tried, it didn't work. I can't do ANYTHING with ADB in recovery mode because the computer doesn't even recognize that the tablet is connected until I select "Apply update from ADB", at which point I can only run the sideload command. Any other ADB command (backup included) brings up "error: closed".
I guess my last hope will be the MTP option, if I can get the driver working. I think I'm going to have to call Google on this one.
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Click to expand...
Click to collapse
I would take it back, if you haven't rooted it, unlocked the bootloader then you probably got a lemon. Just return it, not worth the hassle. Even if you fix it yourself you shouldn't have too. My recommendation is to return it.
sfhub said:
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
Click to expand...
Click to collapse
Ah, I stand corrected. I don't have much experience with the stock recovery; one of the first things I did when I got this phone was install CWM, and I haven't flashed a stock recovery image since.
So, back to OP:
Try getting MTP to work in recovery, then you can manually bring the files over through Explorer.
Wait, why not install a custom recovery? go here, download the fastboot file, and put it in your platform-tools folder. Might want to rename it to "recovery.img" if it isn't already named that. Now:
1. Boot into the bootloader (power off, hold Power and Volume down until it vibrates and goes to a screen with an Android on his back and his chest open)
2. Once there, see if adb will recognize your device. If not, try installing the drivers again.
3. If adb sees your device, issue this command (assuming the CWM recovery.img file is in your platform-tools folder)
Code:
fastboot flash recovery recovery.img
Once that's done, boot up into your new custom recovery. From there, make a nandroid (optional, that nandroid will contain your pictures if you want to do a factory reset or accidentally hit something). Now if you can get adb to recognize your phone while in this recovery, you can issue adb commands such as adb pull. I would do:
Code:
adb pull /sdcard/ \sdcard\
That will pull the entire contents of your sdcard to a folder called \sdcard\ under platform-tools.
EDIT:
Slight revision to the command I gave you to pull your pictures. If you just want the pictures taken by your camera, run
Code:
adb pull /sdcard/DCIM/Camera/ camera\
That will pull the pictures and place it into a folder called 'camera' inside of your platform-tools folder. The previous code I gave you would put the entire contents of you sdcard in a folder called 'sdcard' on the root of the C:\ drive because I put a back-slash ahead of the folder name. My mistake.
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Stealth22 said:
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Click to expand...
Click to collapse
Oh yeah, I'm sorry. I keep forgetting you have your bootloader locked, whoops.
Hey, I just thought of something else. Are you planning on flashing those images one by one, following a guide similar to this one? If so, if you don't flash userdata.img, it should preserve your data, including contents of /sdcard/. He touches on it a bit in the guide:
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Click to expand...
Click to collapse
2) This note is NOT for n00bs. There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
Click to expand...
Click to collapse
Might want to note that the guide I posted was for the Nexus 4, but the process should be the same. Try not flashing userdata.img when flashing the stock image.
If the bootloader was unlocked to begin with, yeah, that would work. The guide for the N7 has a similar note about preserving user data.
I've gone ahead with the factory reset. Next time, I'll be sure to have automatic backups to Dropbox or Google+.
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
joecap5 said:
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
Click to expand...
Click to collapse
I don't know if you can edit that script to pull a backup, I'm not really an expert on that subject. But from the amount of time and effort I spent, my guess would be that you (like I was) are unfortunately SOL.
I know it's been 3 weeks since you posted, but I thought I'd reply anyway, in case this ever happens to anyone else. Long story short, I was never able to recover anything, and was forced to do a reset.
I had called Google and tried to see if they could work out a solution. I was willing to ship the tablet to them, have them pull the data off, do a reset, and ship it back, but obviously, they said they couldn't do that.
In the end, I accepted that the photos were gone, and did a factory reset. Then I downloaded the stock image from Google, and reinstalled the stock OS from scratch, because of the issues I was having. I just figured that because this was the third time I was doing a factory reset, that something was screwed up with the factory image that was on the device, and that it wouldn't hurt to do a fresh install.
The very first thing I did was install Dropbox and set up the automatic sync function for photos.
I haven't rebooted my N7 very much since then (for fear of this happening again!), but whenever I've had to, it's started up with no issues. Now, I'm careful about what apps I install from Google Play, and any time I have to do a reboot or if Google sends out an update, I do a full backup first. In fact, I hadn't done a backup in a while, so I just pulled a backup, and restarted the tablet because my BT keyboard wouldn't connect. No issues this time either.
From now on though, any time I go on vacation, I don't care if I'm using a real camera or if I forget the camera and have to use my phone or N7. The laptop comes with me on the trip, and photos/videos taken get backed up at the end of each day. Copied to the laptop, to my USB passport drive, Dropbox, the whole 9 yards. I learned that lesson the hard way, and I'm a programmer for a living, so I definitely should have known better.
Moral of the story...if it's important to you, don't be lazy like I was. BACK IT UP.
Try this:
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance‼
Click to expand...
Click to collapse
Ok, first of all, have you tried to - simply let it on the Charger!??
Then press and hold the power button
If it doesn't work: Has the device ever taken a kind of damage because of heat/water/drop/whatever?
Try to replace the battery.
Try to hold the so►called „KEÝ4" inside of the device- for exactly 16.0 to 16.2 seconds. Then you smoehow can manage and check the hardware health+status+whatever. Efficient application. Also works with 0,1% battery charge.☺☻☺
I'm so sorry for you.
Which Nexus is it? (2012/2013? How many GB? Which Android Version? Because KitKat is bogus.))
I know a Galaxy S3 Mini, fell into water for 3 Seconds.
Then everything worked perfectly fine but... even if the device was turned off and connected to the charger: the device actually did recogniƶe the Charger but then:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
►Turned into►►→→
‼‼
I hope, that i could help.
All the best for you and your Nexus.