Develop Bugs

Need urgent help accessing data on my rooted t989 with broken screen

My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.

So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk

CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.

I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.

slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.

CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium

try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.

To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.

THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.

Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.

Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.

soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.

[Q] recovery mode on stock rom?

Ok, a friend of mine dropped my Epic 4G Touch and cracked the screen. Screen is totally black and as far as i can tell, the touch interface doesnt work. The phone turns on fine and i can hear it boot up and receive email, etc, but i cant figure out how to access its internal memory. I know that you have to turn on storage mode to get the usb mount option to work and i have adb installed on my mac, but it never sees the device. I was told I could start the phone in recovery mode by holding the volume up button, then hitting the power button, but it doesnt seem to make a difference and it just boots regularly. Am i missing something? Is there even a recovery mode with the stock firmware/rom from Sprint?
Any help is appreciated. Thanks!

If it is already rooted and usb debugging is enabled. You should be able to use program such as Android Commander to pull the files from the phone. Another option is to odin into an ICS rom, I believe on those MTP is enabled by default on ICS builds and the phone should mount as a drive immediately when you plug it in. It should be possible to odin with just using the power and volume keys.

As i mentioned, its stock, so its not rooted and its using gingerbread since ICS isnt out from Sprint yet for it (not OTA at least). What does ODIN mean? Am i doing the keys wrong to get into recovery mode? I mentioned the method with the volume up key and power and not getting anywhere with that. Did you actually read my entire post?

First off, wrong section but anyways there is a recovery mode when running stock which you can access by 1. Turn off phone 2. Hold volume up and power button at the same time probably for about 5-10 seconds.
Sent from my SPH-D710 using Tapatalk

Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!

MACscr said:
Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!
Click to expand...
Click to collapse
No problem, glad I could help.
Sent from my SPH-D710 using Tapatalk

Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!

MACscr said:
Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!
Click to expand...
Click to collapse
You probably can using some commands in adb but a bit too much for what I know. I'd suggest going to the e4gt irc channel. Go to webchat.freenode.net channel is #ics-dev-e4gt hopefully a dev is in the channel and can help you out or someone can stop by this thread before then.
Edit: try the command "su" then enter and then "adb devices" see if that helps with anything.
Sent from my SPH-D710 using Tapatalk

Simply odin just the el26cwm kernel only that should be enough to allow root commands since it's an rooted "insecure" kernel. It should not touch your data.

FML I think I bricked my phone

Ok so long story short, I accidentally wiped the system when in recovery and now my phone only boots to the google logo and hangs. I cant get into boot loader because it seems the volume up button doesnt work. Does anyone have any ideas on how I can my phone back up and running or is it just shot at this point?

You hold both volume buttons down to get into fastboot.

adb

I cant hold the volume up button for anything, it doesnt work anymore.

samcraig said:
I cant hold the volume up button for anything, it doesnt work anymore.
Click to expand...
Click to collapse
Oh- you're saying the physical volume up button is broken?

sickopsycho said:
Oh- you're saying the physical volume up button is broken?
Click to expand...
Click to collapse
yes
right now im using the nexus root toolkit, flash stock/unroot because of softbrick, to see if that works then i can reflash.
the whole reason this nightmare started is because i flashed to team oes nightlies rom and there was no google play store lol. i let gooim update and it kept looping saying android cant start, so i figured id clear the cache and oops pushed the wrong button

If you can use USB debugging adb reboot bootloader should do the trick

Sdobron said:
If you can use USB debugging adb reboot bootloader should do the trick
Click to expand...
Click to collapse
thanks I'll try that if this doesnt work. I do have another question, Im trying to get my kyocera jax info onto my nexus, ya ya ya I know "obama phone", but the way I see it is Im in wifi at work and home so the only time I need an actual service is when Im driving or out because the rest of the time I can use google voice which = 0 bill . so what all info is needed just to get talk and text mms working?

Fix that volume up key, its your best shot. That should be your main concern.
Sent from my i9250

1. Connect your phone to your computer
2. Type "adb wait-for-device reboot recovery" at your command prompt/terminal(at your computer)
3. Flash your ROM
4. Done
If you don't have a backup of your ROM at your internal sdcard, then either mount it at recovery, and if the mounting fails, use this:
"adb push rom.zip /sdcard/rom.zip" (replace rom.zip with the name of your rom)
And, get the volume button fixed, you won't always be with your computer when trouble passes by

[Q] Help desperately needed - Galaxy Nexus not booting after installing Jelly Belly!

I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?

bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
the proper term to use here is bootloop
ur phone bootlooped and u need to flash back the stock firware via odin
go back in the dev section and find somethng relatd to odin
remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod
u must have done something wrng while flashng jellybean mod...take the steps crrctly
EDIT:- http://forum.xda-developers.com/showthread.php?t=1827685
heres the link to fix ur phone
properly take the steps plzz

bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
Are u able to boot into CWM recovery, Power and both volume up and down?

garner said:
Are u able to boot into CWM recovery, Power and both volume up and down?
Click to expand...
Click to collapse
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?

bluroot said:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
Click to expand...
Click to collapse
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone

Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?

press and hold both ends of the volume button and the power button... its really not that hard.

Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?

Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?

bluroot said:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
Click to expand...
Click to collapse
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?

bluroot said:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
Click to expand...
Click to collapse
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?
What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.
On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.

good lord... you have a device ID so just use the fastboot commands... start at part D

Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I said much the same myself.
For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?
"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.
I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?
I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.
Thanks.

Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.
Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement
Device: Portable Devices
Manufacturer: Generic-
Location: on UMBus Enumerator
I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?
I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above

garner said:
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
Click to expand...
Click to collapse
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!

Oh, no, now I can't connect with the server!
Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?
Some standard apps are missing too, including the Play Store app!

[Q] Unable to boot beyond google screen

Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?

standardman said:
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
Click to expand...
Click to collapse
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?

charesa39 said:
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.

standardman said:
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
Click to expand...
Click to collapse
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.

charesa39 said:
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
Click to expand...
Click to collapse
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.

standardman said:
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.

charesa39 said:
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
Click to expand...
Click to collapse
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!

standardman said:
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
Click to expand...
Click to collapse
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.

charesa39 said:
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
Click to expand...
Click to collapse
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?

standardman said:
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
Click to expand...
Click to collapse
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.

charesa39 said:
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
Click to expand...
Click to collapse
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?

standardman said:
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
Click to expand...
Click to collapse
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.

charesa39 said:
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
Click to expand...
Click to collapse
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:

standardman said:
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
Click to expand...
Click to collapse
Haha! I don't know about all that. Just glad I could help. :highfive: Hope it all works our for you. :good: