So, for a long time, my Nexus 7 never worked, because the charging port was too loose. So I decided to order one. It came in the mail today. Installation was easy. It started charging, but no charging icon appeared. The only thing that happend was the screen back light turning on slightly. So I let it charge more. The Nexus turned on!... But got stuck on the Google screen. So I try and use fastboot and starting it from there. "Boot failed". So, maybe no OS? Try using ADB to flash stock android onto the device. "Failed (Bootloader locked)". Ok, ill just unlock the bootloader. "Unlock failed (unknown error)" . Maybe flashing a new recovery will work? Nope, has to be unlocked. So far, nothing has worked. Spent 2 hours trying to flash, unlock and factory reset, and nothing but "failed" has come up. The device can't even go into recovery mode. When connected to adb, The list of adb devices is blank. It knows the device is connected, but it doesn't show the name or model.
Anyone know what to do?? (I have never tried to flash anything previous from today on this tablet.)
Related
My Nexus 7 isn't restarting, or booting, or responding at all. Dead. Screen won't even turn on. Blank.
It was my first time trying to root it. Should be simple with Toolkit 2.0, right? No. After successfully unlocking it, I proceeded to Root it. The Toolkit told me to wait till it restarts in Fastboot Mode. So the tablet automatically reboots, but to normal Android. Nothing's happening. So I decide to power it off and on maybe it'll boot in Fastboot mode when that happens. Aaand it's gone now. Windows cannot recognize it when I plug it in, but there's a response (as if it know 'something' was connected to it).
Please help. It's my first time doing that, and I haven't had the Nexus 7 for more than a few hours. I only did that so I can use my USB OTG.... Thanks.
UPDATE: Scratch that. Everything works now. I plugged it in the charger for a while (even though it was 49% to begin with) and then tried powering it up and it worked. I got it rooted too. Delete this thread if you want!
great to see you got it working!
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.
EyebrowZing said:
After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.
Click to expand...
Click to collapse
ADB needs a booted up android to work, it wont work in bootloader mode. Another requirement is that usb debugging must be enabled in dev options. Fastboot works only in bootloader mode and doesnt need usb debugging.
Download wugfresh toolkit.. Use it to restore your device and DISABLE FORCE FLASH
Sent from my Nexus 4 using XDA Free mobile app
Hey . i recently tried Lollirock
which i didnt like so wanted to go back to stock
I tried following https://developers.google.com/android/nexus/images
seemed that it went fine, how ever it left me with a Google Screen and it wont boot
then i tried this ,
https://support.google.com/androidtv.../6121450?hl=en
which also went fine and did a factory reset ,
but still only the Google Screen,
any ideas on what to do next
this is resolved
http://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3043711
Three Nexus Players stuck at Google loading screen
I have had 3 different Nexus Players get stuck at the Google loading screen in the past week. Recovery mode from the bootloader doesn't work. Has anyone else seen this? Any work around?
I am also experiencing the same symptoms. Factory reset results in the same Google screen.
I’m getting the same thing starting this week. Factory reset has done nothing. I’m running stock everything, unrooted Oreo. Someone help!
I was wondering if anyone else has any ideas on this issue. If I plug in my nexus player, it takes around a minute to get up to the white google logo. I have tried holding the bottom button as I plug the player in, but I am unable to get to get any result out of it. I never get to the point where the droid is on his back. I am just stuck on a loop with a white google logo on a black background.
I wonder what happened that Google broke all our players. Mine is doing the same thing - stuck at the black and white 'Google' screen. Has anyone been able to recover and reboot?
MallCop said:
Has anyone been able to recover and reboot?
Click to expand...
Click to collapse
A good number of people have been reporting that they were able to flash back (either to stock or other options), but there haven't been a lot of details on if they were already unlocked. I haven't been able to get fastboot or ADB to identify my Nexus Player from Linux, and I wasn't unlocked and hadn't enabled USB debugging before this happened.
I left my player unlocked and I can't remember if I enabled usb debugging. My problem is I can't even get into the recovery. Holding the bottom button down has yielded me nothing.
erehwon6811 said:
I left my player unlocked and I can't remember if I enabled usb debugging. My problem is I can't even get into the recovery. Holding the bottom button down has yielded me nothing.
Click to expand...
Click to collapse
Getting to the recovery (android on his back ) screen yields NOTHING. I was in the same loop and just had to be patient. Hold the button, wait until the GOOGLE screen goes away, then it will come back and eventually for me, I got to the screen with the android on his back (took like 5 minutes). Problem is that when I did a factory reset, I am still have the same problem. I did not think Google was updating these anymore. I have 6 of these and 2 are bricks now. Unplugged the rest until I can tell what is going on.
Best Buy has a offer where you can get a $30 coupon off of a nvidia shield for recycling a streaming media player. I'm tempted to see if they'd take the player in that condition. I hesitate since I haven't been able to clear my data from it. I just wonder if this a permanent brick.
Mine just randomly restarted as I was navigating the menu and now I'm stuck on the boot animation as well. I never rooted the thing. I guess I'll start going through the recovery options. Hopefully it didn't die on me.
I was in the same boat...last week got the corrupt data message so I factory reset...seemed to work fine for a couple of days and then got stuck on the Google screen...factory reset didn't help this time..
I installed TWRP and loaded lineage 15...looks like I am back in business...
I just had the Google black screen as well. I did the following, as I was running into the same errors as everyone else here stating that the reset hadn't worked.
I started by using the button into the recovery and reset - didn't work.
I then went into fastboot, and tried manually flashing the latest image from google and didn't work.
I typed fastboot oem unlock (forgot it wasn't unlocked).
I then sent the flash all script and everything went great. Now working.
Hopefully that helps others.
Well today, it rebooted into the boot splash again. I guess this thing is cooked...
Man we are all experiencing a very similar thing. This is too strange to be coincidence. I turned on my TV, saw the Nexus Player interface, then when I tried to interact the screen went black. I restarted the nexus player, and it went into the stuck on Google loop. It has been rooted / lineage rom in the past, but i have been running stock Android factory images on it for over a year now. I enabled debugging, so I connected it to my pc and checked that it was unlocked.... heres where it gets weird....
The unified android toolkit says it is locked, but when it tries to unlock it, it says its already unlocked. So i ran fastboot oem unlock manually and it says already unlocked, as does the bootloader screen. OK. Flash factory imaging using flash-all.bat, everything goes fine, then it sticks on Google screen again. I am going to try an older factory image then im going to try lineage brb...
just had the same result with 7.1.2 and 7.1.1 and 7.0.0 factory images.
flashed twrp, booted into recovery, and flashed latest lineage.
stuck on lineage logo for 10 minutes now....
seems like google bricked out Nexus Players. I am pissed.
jessehclark said:
Man we are all experiencing a very similar thing. This is too strange to be coincidence. I turned on my TV, saw the Nexus Player interface, then when I tried to interact the screen went black. I restarted the nexus player, and it went into the stuck on Google loop. It has been rooted / lineage rom in the past, but i have been running stock Android factory images on it for over a year now. I enabled debugging, so I connected it to my pc and checked that it was unlocked.... heres where it gets weird....
The unified android toolkit says it is locked, but when it tries to unlock it, it says its already unlocked. So i ran fastboot oem unlock manually and it says already unlocked, as does the bootloader screen. OK. Flash factory imaging using flash-all.bat, everything goes fine, then it sticks on Google screen again. I am going to try an older factory image then im going to try lineage brb...
Click to expand...
Click to collapse
That's pretty much exactly what happened to me. I was navigating around the menu, got the black screen and when I restarted it, I got stuck on the Google screen. It's the only Android device I have that I never rooted so it's completely stock. To say that this is frustrating is an understatement. Although it's old, it gets used heavily by the kids.
I keep having a similar issue but I've been able to flash back to 7.0. Nexus auto updates and within a week I'm back in the same boat having to reflash...
i also just had two nexus players die this weekend. something is up.
Yes, something seems to be up, mine died earlier today, too many people to just be coincidence. I was casting to it and it just rebooted and is stuck on the google startup animation. Stock, never unlocked or rooted, been rock solid up until now. I use it as a DVR so I figured maybe my external hard drive had crapped out and was causing a hangup since the light isn't on anymore, but same symptoms when unplugging it and trying to reboot.
I replaced my GNEX10 battery last january. Aside from the battery calibration being off... (which eventually corrected itself!) it's been working fine. As of late it had rebooted itself while I was using it a few times. A few days ago, it had enough battery such that I left it on overnight. I picked it up the next morning and the notification lamp was flashing so I knew it was still on. I tried to wake it up without success. Usually a quick tap on the power button should do it. Nothing. So I rebooted... and on the google logo it stuck. I knew that a factory reset was probably in order since I didn't do it when I replaced the batter... I got it into the recovery screen... but I could not get the menu. I likely didn't press the right volume rocker. Then I tried again... booted to the bootloader, and selected recovery. This time, and since, only the google logo comes up. No andy on his back with "no command". It just tries to boot into something. I can't do a factory reset this way.
I tried the Nexus Root Toolkit. I can only get it to recognize the device if it's in the bootloader... when I try to use it to boot to recovery, same thing and the NRT says waiting for device... and gets no further. I tried to use it to flash (stock?) recovery but the N10 just sits there on the twrp logo screen and nothing more after temporarily booting into twrp. Just keeps saying "waiting for device"
Anyone have any suggestions! Getting seriously bummed!
So one more data point... I manually rebooted into the bootloader after trying to flash the stock recovery using the NRT. Then it appeared to flash the recovery image.... here is the bit of the log where it ended up:
Checking Fastboot Connectivity
fastboot devices
R32CB04GHGT fastboot
+ Fastboot Device Connected
Flashing Stock Recovery to RECOVERY partition...
fastboot flash recovery "C:\usr\NRT\data\Recovery_Stock\recovery_stock_mantaray_5.1.1_LMY49J.img"
Temporarily Booting TWRP...
fastboot boot "C:\usr\NRT\data\Recovery_Custom\TWRP\twrp-3.0.2-0-manta.img"
Flashing 'undo-perm-recovery-signed.zip'...
Waiting for your device...
That's where it ended up... not getting any further. Once again, attempting to boot into recovery gets it stuck on the Google logo.
How screwed am I? Is there a thread somewhere in the forum anyone can point me at?
Well, in spite of the crickets... I understand. I've managed to resurrect my Nexus 10. Alas there are no good contemporary replacements. The last so-called nexus table google put out there was too damn expensive in the first place and they seem to have abandoned the tablet market to others.
So the key question here: So long as I can get this tablet into the bootloader is it generally possible to reflash a stock image? I'd like to know of any types of caveats etc. The mystery I have still though is: How or why did my N10 get into this state (of of only being able to get to the Google screen) in the first place? I didn't have any questionable apps installed etc. I was totally on stock. One thing that did happen a week or two prior to my tablet going belly up... was somehow the thing lost my google account info and gmail had none of my accounts in place... it was very odd.
I did have to wipe the system because evidently you can't flash anything onto a locked bootloader (the Nexus Root Toolkit by wugfresh is up to date so far as the N10 is concerned at least). I know I could have resorted to using fastboot.exe and the adb directly but this was a touch easier. Alas the backup options for it say you need an unlocked bootloader which seems to be a chicken/egg issue if you've always been on stock.... so it goes.