Hello,
I have a Shield 16gb 2017 model that I believe is bricked. It has a stock rom of 5.2 I believe and has the bootloader unlocked.
I took an OTA and forgot that I had rooted months before and am now getting stuck at the nVidia logo.
I cannot enter the stock recovery using the controller or keyboard and my PC doesn't detect the device at all.
Is there any hope?:crying:
I'm having a similar issue with my Shield TV 2017 16gb. I tried updating Lineage OS through TWRP but when I went to reboot, it'll get to the Nvidia screen then repeatidly reboot. Also whenever I plug in the controller, pressing A and B to boot to bootloader does nothing now. Does anybody have any solutions to fix this?
ThatGuy94 said:
I'm having a similar issue with my Shield TV 2017 16gb. I tried updating Lineage OS through TWRP but when I went to reboot, it'll get to the Nvidia screen then repeatidly reboot. Also whenever I plug in the controller, pressing A and B to boot to bootloader does nothing now. Does anybody have any solutions to fix this?
Click to expand...
Click to collapse
I think we are perma-bricked my friend.
Related
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.
Hello,
yesterday I tried to boot my tablet and after the logo "Lenovo" appeared on the screen, nothing happened (the screen was stuck on "Lenovo").
Tried to power off/on several times, same behaviour.
I charged it the whole night, and today when I tried to boot it, after the logo "Lenovo" appeared on the screen, the screen started flickering (random gray/green lines here and there)...
Any help?
Do you think it's a hardware or software problem?
Thanks
did you tried to do something ? any flashing/rooting attempt etc?
in any case you could try flashing a stock rom anew so at least you will know what is the problem... could be anything
(i have assumed you have an android tablet, maybe you could also post the model when asking)
ionioni said:
did you tried to do something ? any flashing/rooting attempt etc?
in any case you could try flashing a stock rom anew so at least you will know what is the problem... could be anything
(i have assumed you have an android tablet, maybe you could also post the model when asking)
Click to expand...
Click to collapse
I rooted it and flashed it a few months ago. Have been using it with multiuser feature (4 users).
Worked until yesterday.
See http://forum.xda-developers.com/showpost.php?p=59609862&postcount=172
Model:
Lenovo Yoga 10 B8000-F tablet
Android version: 4.4.2
[.::MDT::.] said:
I rooted it and flashed it a few months ago. Have been using it with multiuser feature (4 users).
Worked until yesterday.
See http://forum.xda-developers.com/showpost.php?p=59609862&postcount=172
Model:
Lenovo Yoga 10 B8000-F tablet
Android version: 4.4.2
Click to expand...
Click to collapse
so... try and flash back your stock rom
Or try to wipe data from recovery.....
StepoXX said:
Or try to wipe data from recovery.....
Click to expand...
Click to collapse
Thanks.
While booting (when the LENOVO logo appears) I kept pressing VOLUME UP button.
It entered recovery mode, where I deleted cache only (no factory reset).
After that it booted correctly.
I reckon the multiuser feature (I set up 4 users) could maybe use a lot of ram and the device gets stuck.
Not sure how to reproduce the problem, I'll maybe try a factory reset to check if the issue is still there.
Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.
Hallo,
got the same problem, how did you resolve it ??? Thanks a lot ...
Same here. I can't connect to the device by no means. How did you solve your problem?
Tallyphillips said:
Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.
Click to expand...
Click to collapse
you mention it wont connect via fastboot but you can still reboot with the pwr + vol- to get menus of some kind.. ? if the screen is backlite even just a blank screen but you can see it light up theres still hope. All i can say is try to reboot the device into fastboot an then try Nexus Root Toolkit an see if you can reset to Factory to restore the stock recovery partition along with reset the OS to which ever you select and start over .. Good Luck Flashing... the only way i can say your SOL is if when you plug it into your PC an it pops up with the error "Device Malfunctioned,....." then you SOL Good Luck Flashing :good:
EDIT: Sorry didnt notice it was resolved in the title..
Hi, hoping for some advice, I have three shield 2017's, updated 2 of 3 to 8.0.1 without issue, last one went into bootloop after the update.
The problematic one had the update pending for a long time, just never rebooted to install it, until now.
I followed the nvidia KB, and tried the the fast boot menu, recovery kernel, factory reset, still bootloop.
I contacted support over chat, they had me boot without HDMI, press A, reconnect HDMI, no difference, shield keeps rebooting even without HDMI.
Support then had me change power plugs, since I have three shields, I tested using another working shield PSU, same problem.
Support then had me boot, wait 2 mins, press home and left on dpad, wait for blue flashing, no difference, as shield keeps rebooting, waiting for anything is really pointless.
Out of frustration, and not knowing what I'm doing, I did a factory reset directly from fastboot menu, now I get a can't verify firmware, lock firmware, press A message, and then it just sits at the nvidia menu, not good.
(Btw, it took many tries to get the fastboot menu to launch, first time was lucky, but it continued rebooting before I had a chance to move the menu, then it seemed impossible to get again.
Is there a reliable way to get the fastboot menu up using the controller A+B or other method?
Given the state of the shield, can I recover the device, any advice on how, please?
if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device
zecabra said:
if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device
Click to expand...
Click to collapse
Ok, that's good news then, I'll order and A-A cable and try one of the tutorials (I was pointed to one on reddit).
Any advice on how to reliably launch the fastboot menu using the controller, I do the A+B button, power on, and it only occasionally works?
Just today I tried using my 2019 Fire HD 10 and it wouldnt display anything. So I powered off by holding the power button for 20 seconds. Turned back on and it won't get past the white Amazon Logo. So I booted into Recovery mode to reset the device and wipe the cache. When I try both options, I get nothing but errors stating that it cannot mount E:/ (which I am assuming is the internal 64gb of ram). So something got majorly corrupted. Don't know what happened as all we use this thing for is in the kitchen watching streaming shows as we cook. I can only assume that maybe an update corrupted it.
Here are the details. I did install Google Play on it when I got it back in early 2020. But it has been working very very good for close to 2 years now. I did not enable ADB Debugging...or at least I dont think I did UNLESS its required to install Google Play. I did the method of just installing in order the 4 or 5 Play files that required me to unable to install from untrusted sources. But I dont think I enable ADB Debugging.
I can boot into Recovery and Fastboot just fine. But nothing in Recovery mode works as I get the errors stating E cannot be mounted.
So my question is....is there anything I can do to get past the white Amazon Logo or anything I can do to reinstall the OS or anything I can do to install a new OS like LineageOS.
Thanks for your help guys
Here is what it looks like when I first boot into Recovery.
have exactly the same problem
i used fire toolbox a long time ago
maybe there was an update from Amazon
help from professionals here would be nice
I too have the same issue. Bone stock and never been modified. I've been reading and haven't found a solution.