All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?
with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered
Check this command
adb devices
does it even show up on the list?
Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again
darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm
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.
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.
Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯
I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.
have we even seen a bricked device yet?
twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.