There has not been much action here for a while, so here goes!
I purchased a used Nexus 10 seven years ago, so it is probably 10 years old now, with original battery
The problem I have is that I have encountered a problem that I am unable to fix; when I boot up I receive this message
“Android is starting, optimising apps 1 of 119” (cannot understand the 119, definitely nothing like 119 apps on the device.)
The message is in a loop, and Nexus is unusable, I cannot get into safe mode, when I click on recovery mode I receive the message “no command” or get a message "download do not switch off"
Any assistance would be appreciated
So if you are in the ''no command screen'' he have to play around with the buttons so you get an menu, then select adb sideload. (with my Pixel 6 pro it's keeping the power button pressed and hit the up button a few times.)
In preparation it's an good idea to download the ota firmware files and platform tools so you can start right away once you're there.
If this all is a bit jibberis to you try finding an guide on sideloading for your device. The general idea is the same so if you can't find it for your device, look at the pixel 6 pro page under howto there are a few good guides you just have to adjust them a bit to your device. Andriod flash tool (via the google/andriod site) might be an option too, if the nexus is supported.
Thanks for reply,however I have had enough, wasted too much time , the latest is the only screen I can get up is "downloading do not turn off target.
Think I will surrender to a replacement, considering my usage I might take a punt on this at at Amazon Aus $109
Tablet 10 Inch Android 11 Tablets, 32GB ROM 512GB Expand，6000mah Battery, Quad-Core Processor 2GB RAM Tableta, 8MP Camera WiFi GPS FM 10.1'' IPS HD Touch Screen, ZZB 10IN Tabletas
Related
Just gonna throw this out there and hope that somebody will have some insight…
Right now, my Xoom won’t turn on... or atleast "all the way on".
If I hold in “Volume Up” and the power button for 3 seconds (as described on the support site), it boots, gets past the moto screen and to the honeycomb animation. The animation plays for a few minutes… yes minutes until it either goes dark/off or presents a bare-bones lock screen that doesn’t respond to touch input.
Occasionally, when it reboots, it gets to the screen that has the Motorola logo and in the upper left corner, it has the text: "Starting RSD Protocol support 0". When that happens, it just freezes there. This has only happen a couple of times and I believe it had to do with variable durations of holding down the power and volume buttons. The phrase quoted doesn’t appear in either bing or google’s indexes.
Right now, the honeycomb animation has been playing for several minutes and 2 notification sounds just played… WTF
Any help would be GREATLY appreciated.
FWIW
Whatever happen, it did so under the follwoing circumstances:
1. Sent gTalk invite
2. Changed background image
3. While it was applying the new background, gTalk popped up with an incoming call.
4. I accepted the call
5. I then saw my video image in the lower right and nothing else on the screen.
6. Approx 10-15 seconds later, the Xoom rebooted.
7. Never finished the reboot, just turned off during honeycomb animation.
8. Tried that again a few times.
9. Tried the hard reboot, where you hold in the volume and power in... no dice
Sometimes, it will play a notification sound when in the honeycomb animation.
Sometimes, it will get to a generic unlock screen that doesnt respond to touch input. When that happens, and once the screen goes to sleep, I'm back to square one.
Just got off the phone with Motorola. I explained to the lady on the phone the situation and she was confident that she could help. Unfortunately, the volume / power button combo was all she had up her sleeve. She advised me to return it to BestBuy tomorrow.
Willing to bet BestBuy wont have any tomorrow... This isnt the "experience" i was hoping to get.
Just return it and get a new one? its obviously defective...
martonikaj said:
Just return it and get a new one? its obviously defective...
Click to expand...
Click to collapse
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
gigglebox said:
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
Click to expand...
Click to collapse
The quicker you take it back, the better off you are. They'll get new stock in and you'll be better off.
If you see that it doesn't mean its defective, it means your stuck on the fastboot screen
do this:
"Holding vol up down & power does a force normal reboot"
I just returned the device to BestBuy, exchanged it for a new one… so I’m all set.
Here are my current thoughts as to what happened (and what may happen in the future):
It really seemed / behaved like an unhandled combination of circumstances exposed what might be a couple of holes in Honeycomb. Obviously, we’re still pretty early on in the life span of this thing and many things that fell through the software validation process will likely be corrected as they are found.
Best I can figure, while attempting to write a change to (what I imagine is) a config file somewhere (when changing the background image), the process was interrupted by an incoming connection (inbound gTalk video call). That, perhaps in conjunction with the set of apps that I had loaded and were likely still present in ram, somehow made Android lose its marbles.
Throughout the night, I tried lots of different ways to reboot, and lots of attempts with no luck. However, on 3 occasions, after 30-40 minutes of not touching the device, it would start to make noise. Each time, I found that the noise was that of an incoming gTalk call and the caller (that seemed to initiate the failure) appeared on the screen accompanied by the Accept, Deny buttons. The pressing of any of the on-screen buttons resulted in the powering off of the device. Whats puzzling is that the device maintained any awareness of a call, etc, hours after it was initiated and had been hard-rebooted several times. Something wasn’t getting flushed…
I assume that once folks get a solid handle on rooting and custom ROM procedures, there will be an iron-clad way out of the hole I found myself in.
Have the same problem
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
Thats the fastboot screen, you could try flashing it at your own risk. But if it was a software glitch that would fix it.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
FastBoot or not, I never succeeded in getting it out of that funk (any combo of either proscribed or "creative" button pushing). I dicked with it for about 5-6 hours before I cut my losses and went to bed. In terms of flashing it, I would imagine that it would work, but I personally wouldnt be comfortable enough yet. The process will get a hell of a lot more tested and vouched for in the near future.
The day after launch, I just called around to see what BestBuys had them in stock and drove out there to exchange it.
I hope that you guys are reporting your issues to Google...
never got it fixed
I never did get it out of that loop or what ever was going on. I am too an advanced user of android, from day one and it seem like more of a hardware or software problem then anything. Took it back to costco and they had me call up verizon. Went up a few tech levels. He tryed to help me get into the factory reset menu but no go on that. Got a replacement. I had my new xoom crash and go to the startup screen. Held my breath as it started back up.
Will send out a message to google and motorola letting them know.
All you had to do is hit sound up and power button it would have shutdown and once you power back up it will go into the regular boot
broken xoom
mine is stuck at the duo core screen with failed image lnx 0x002
starting RSD mode 2
i can hold the down volume button and put it in the fastboot protocol support. but when i plug it in and try to unlock it to run the factory reboot protocol from motorola my command prompt says waiting on device. i have the correct mot driver installed. any help out there
Try this post http://forum.xda-developers.com/showthread.php?t=973355
Sent from my HTC HD2 using XDA Premium App
This is the only forum I can find to post this to.
Got out my old nook classic and wanted to remove a soft root I did a few years ago and I flashed the wrong firmware. I flashed 1.0 and it's a newer 1005 model. Now it's stuck on the "installing software update screen" and the LCD keeps looping.
Being that it's so old I'm having trouble finding out any info. Is there anything I can do? I can't get it to mount.
I assume you tried something like this? (from here)
This will actually restore it to the same exact way you got it from the store, brand new, including with the un-updated software assuming that there have been updates since you got it. It's the Nook equivalent of restoring your computer with a fresh format and new Windows/Mac/Linux installation.
Pop out your SDCard if you have one installed, again just to be safe.
Turn off your Nook by pressing the Power Button on the top of it.
With it off, showing you the blank white screen, press and hold the power button until the screen flickers black for a second, then continue to hold it for another 12 seconds. You won't see anything happen at this point, the screen will stay white.
Repeat the above step 6 more times in a row. Yep, you read that right, 6 more times in a row. My assumption is they do this so people don't accidentally restore their Nooks during normal use.
Now press the Power Button once to turn the Nook back on.
You'll see the touch screen go black, with a sky blue progress bar, and a description of what it's doing, such as mounting the drive, formatting, etc. This takes a few minutes so be patient.
Once it does that, it'll boot up to your main screen, (it can take a while) with any previous version of the software showing, and you'll need to treat it just as you did when it was brand spanking new. i.e. re-register it, set the display name again, reload your screensavers, books and so on.
To update to the latest software version, press the "My Library" button, and make sure you're in the "My B&N Library" area; tap the "Check for new B&N content" button, it'll re-discover that it needs to be updated to the latest software, and automatically go through that process again for you. It can and often does take some time, and do some reboots, partition mounting, etc., so just be patient and let it do it's thing.
1570 6336344
I have followed that and have had no luck. It just keeps looping.
I'm thinking it's dead...
"Dead" is it will not turn on. Yours is "confused"
Seems like what is needed is a method like NookManager or CWM in which the Nook 1 boots from the external SD card and then some repairs are pushed in.
There *is* seemingly such a method, detailed on the-ebook.org, but unless your Russian is up-to-date, you'll have to see if the Google translation is clear enough to give it a try. You don't have anything to lose and everything to gain at this point.
Search on this URL in Google and choose "Translate this page": http://www.the-ebook.org/forum/viewtopic.php?t=19536&sid=8c61d40bfbb40f6f5e3dfcfaa99e5545
Hello all!
I just received a nexus 10 from someone but only because he said he hasn't used it in like 2 years as he says it's broken. It is indeed "broken". He says it may be a hardware issue.
So what's happening is that when I turn it on, the tablet vibrates, goes to the google logo, and then comes the colored dots swirling around and after a while the tablet crashes. The process then starts all over again and never actually goes to the homescreen.
The only thing I have done so far is do a factory reset from the tablet itself (holding down power + volumes) but that did not fix anything.
What can I do to get it at its default state and working properly? Do I need to update the firmware? What software do I need to download?
If anybody can help, it would be much appreciated. This thing is beautiful and I would love to use it.
Thanks
foolness said:
Hello all!
I just received a nexus 10 from someone but only because he said he hasn't used it in like 2 years as he says it's broken. It is indeed "broken". He says it may be a hardware issue.
So what's happening is that when I turn it on, the tablet vibrates, goes to the google logo, and then comes the colored dots swirling around and after a while the tablet crashes. The process then starts all over again and never actually goes to the homescreen.
The only thing I have done so far is do a factory reset from the tablet itself (holding down power + volumes) but that did not fix anything.
What can I do to get it at its default state and working properly? Do I need to update the firmware? What software do I need to download?
If anybody can help, it would be much appreciated. This thing is beautiful and I would love to use it.
Thanks
Click to expand...
Click to collapse
If this is your first Nexus device and you aren't familiar with flashing the stock images, then you will have to start from square one which is download and install the Android SDK on your computer so you have the drivers to recognize the device.
Download from here: https://developer.android.com/studio/index.html
Tutorial Video here: https://www.youtube.com/watch?v=oaNM-lt_aHw
Then you will have to download the factory image for the Nexus 10 and install them. Make sure you download the one specifically for the Nexus 10. It's codenamed Mantaray on Googles site so scroll down and find it.
Download here: https://developers.google.com/android/nexus/images
Video Tutorial here: https://www.youtube.com/watch?v=uO7HkTrRzwM (He is using a Nexus 4 but the instructions are the same for all Nexus devices)
For a visual reference, you can read this tutorial for the Nexus 7 which may fill in some gaps that the videos don't mention. Again, the instructions are the same for all Nexus devices. Just as long as you have the Nexus 10 specific factory images.
Read here: http://forum.xda-developers.com/showthread.php?t=1907796
If your issue is just a software issue, this should fix it. Good luck.
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
BrickOfNexus said:
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
Click to expand...
Click to collapse
Hi... There is no available fix for the moment. Check this thread. You are not alone
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page19
BrickOfNexus said:
... Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android....
Click to expand...
Click to collapse
Unfortunately @5.1 is right. The common denominator of the BLOD (many threads on this) is the inability to get into recovery mode by any means. ADB doesn't work unless in recovery. Without ADB you will not be able to pull anything off the phone. At least you are unlocked so you can try some tools and/or manually attempt to fastboot boot or fastboot flash a custom recovery and get ADB working, but chances are almost non-existent. Some ppl have been able to briefly get back into recovery on completely full charge, but it seems to start boot looping again shortly afterwards from recovery. Hopefully you were using Photos and synced recently. If you bought direct from Google, contact them even if out of warranty. If they won't help you or you didn't buy from Google, approach Huawei for an RMA.
I was in your situation and was able to flash the full stock image (flash-all.bat command) even though my device didn't show up on ABD--but maybe I just got lucky. I thought there was no chance it would work but it did. Some people reported getting out of the boot loop using Skipsoft's tool but most likely you will need to RMA the device if it's still under warranty from Huawei. Sorry to hear you have been added to this club. There are a lot of lemon 6Ps that die because of hardware issues (according to Google) and they clearly don't care because they never recalled the affected devices. I was hoping it was just the early generation phones but if yours is 5 months old that means the problem is persisting. None of these things might still be running in a couple years which is ridiculous for a premium phone. Makes you think twice about buying another phone from Google since they threw 6p owners under the bus rather than offering 6P owners a credit or something for their defective 6Ps. Good luck. At this point I think people need to create a class action suit against Google. That's the only way people got repairs or compensation from Apple the numerous times they pulled stuff like this with defective products. Why should Google get away with selling what they themselves admit is a defective phone?
My Shield TV Pro was working fine last night before a big wind storm took out our power for several minutes. Once power was restored, the Shield's green light was on with no video and it would not respond. Read up on XDA on how to try and recover it. I tried all the dd if this and that stuff, spent all day with nothing to show for it. The furthest I could get was it would boot with a new 500GB drive installed and prepped in Linux, but it will not get past the wizard, saying my Google username and password is incorrect, and it will not find my phone if I try that method.
I can get it into fast boot, so I tried to then flash the Nvidia recovery OS image of 9.0, it would get all the way to the last command before rebooting, then it would just die. Pressing the power button would light it up for about 2 seconds and it would shut off every time.
It seems I can get into fastboot but not recovery, and also when its in fastboot, there is no image on the screen.
Very dissapointed right now, I really do not want to buy another one of these POS'. I spent around $400 for this thing when I bought it new, granted it was a long time ago but I don't want to buy it again!!
Do I have any chance in recovering this thing? Then I read that the widevine keys are probably gone too since the OEM HD is crashed. Any help is greatly appreciated.