Related
A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app
A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue
I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.
Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers app
Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks
socjdqcer said:
Hey Guy,
Need some quick advise. So I bought my N10 back when it launched and its been pretty great! I use it for watching videos, playing games, and teaching (Im a science teacher). Anyways, I use my tablet Daily... a lot... and its never given me any issues at all really. Well about a month ago I noticed it responding a little slow and really laggy for about 2-3 minutes, then it restarted itself. I figured it was no big deal cuz its done that before. Well this time it never turned back on and it just stayed at the Google boot up screen. So I restarted it manually and then it just stayed on the "X" screen forever... Never left either of these screens until the battery would die.
I reinstalled android using the Nexus Root Toolkit and it does the job every time. It works GREAT...but.... only for about 10 minutes, then it starts to get really laggy and then restarts again and gets stuck in the bootloop.
I have it under warranty through staples and they are telling me since its a software issue they want me to send it back to Samsung. If it was a physical issue like broken screen, they would have replaced it by now.
The Tablet isnt rooted. I always root my devices, but since this was a nexus I didnt think it was necessary...for me at least.
Thanks
Click to expand...
Click to collapse
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Smash the screen and get the replacement lol. Anyways I don't see now its a software issue when you flashed the factory image and nothing changed. Try downloading the new 4.3 factory image from Google and flash it manually instead of with the toolkit. If you still have the problem then I'm pretty sure its something to do with the hardware though I don't know how the hardware would affect it getting stuck at boot screen. This is a confusing problem. Anyways according to most people Samsung won't be much of a help and you'll get you're tablet back a week or two later in the same condition. Some people have had good luck with them and got a fixed device back so I guess if your out of options you might as well give it a shot
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.
socjdqcer said:
Thanks a lot man. I just finished downloading the factory image now,but .... Noobie Question of the Day ... drum roll please ... how do I flash it manually? I transferred it to the device manually and then I opened up the bootloader then went to recovery mode then got into the stock recovery and the only options were Clear Cache...Clear Data... and ADB. Do I use ADB, If so Ill have to look that process up, I have never done that before. Sorry, Im not new to android or flashing or rooting, just new to Nexus I guess. My Samsung phones have corrupted me haha.
Click to expand...
Click to collapse
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.
Username invalid said:
No, you don't use ADB to flash image files. Stay in bootloader where you see it say "Fastboot enabled". Extract the system, userdata, recovery and boot image from the package to C:\Program Files\WugFresh Development\data.
Click to expand...
Click to collapse
Thanks man, Ill give it a shot!
socjdqcer said:
Thanks man, Ill give it a shot!
Click to expand...
Click to collapse
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices
Username invalid said:
After that open the toolkit > Advanced Options > Launch CMD.
Your computer should recognize your device by entering
Code:
fastboot devices
Click to expand...
Click to collapse
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!
socjdqcer said:
Well, I manually updated and it worked like a charm...for about 10 minutes. Then it restarted and is stuck at the boot "Google" page! This blows!!!!!!!!!
Click to expand...
Click to collapse
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.
Username invalid said:
Rebooting into recovery and wiping the cache/dalvik cache usually works for me when it hangs on the loading screen.
Click to expand...
Click to collapse
Yeah man, thats what I thought, so I have tried it a few times and whenever I go to wipe cache....The tablet doesnt really do anything and then all of a sudden it restarts. What would cause that?
try to use the toolkit to flash a factory image of 4.2.2 (mind it formats all data, files, music etc). See if it works fine. then unlock, root the device and install a custom recovery (all with the toolkit). If everything works you will have a rooted 4.2.2. Try the tablet and the recovery to see if everything works. If it does you can upgrade to 4.3
Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Well if your still having issues then just send it to Samsung and when it comes back if its still not working take it to staples and tell them Samsung said its a hardware issue or something. I'm pretty sure they'll replace it. I've always had good support with staples
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Sounds good man! Thanks for the help!
Thanks EVERYONE! I tried everyone of your suggestions and the original issue still keeps happening. I can get the tablet to work for a little while, but the its back to bootloop.
Thanks
Hey can't really figure this issue out. I gave my girlfriend my old Nexus 4 when I purchased the Nexus 5 and it was running perfect... stock but unlocked and rooted. Recently she was letting her little cousin play with it, it somehow went into airplane mode and she restarted it and now it just gets stuck at in a boot loop at the Nexus logo. It will sit there for HOURs. I've now flashed it to stock twice, once using the .bat file and the other time just doing it with adb commands and still nothing. WTF happened?
Eclipsed830 said:
Hey can't really figure this issue out. I gave my girlfriend my old Nexus 4 when I purchased the Nexus 5 and it was running perfect... stock but unlocked and rooted. Recently she was letting her little cousin play with it, it somehow went into airplane mode and she restarted it and now it just gets stuck at in a boot loop at the Nexus logo. It will sit there for HOURs. I've now flashed it to stock twice, once using the .bat file and the other time just doing it with adb commands and still nothing. WTF happened?
Click to expand...
Click to collapse
Are your erasing the cache and flashing all 6 img files?
audit13 said:
Are your erasing the cache and flashing all 6 img files?
Click to expand...
Click to collapse
Yep. Might try to install clockwork with a custom ROM next and see if that does anything but I really want stock Android on it.
Eclipsed830 said:
Yep. Might try to install clockwork with a custom ROM next and see if that does anything but I really want stock Android on it.
Click to expand...
Click to collapse
Personally, I like TWRP on the N4. I've never had any problems flashing custom ROMs with it.
Personally, I would use fastboot and follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312
Mesmurized said:
Personally, I would use fastboot and follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Yep did that step by step and still the same thing.
Per Droid-Life:
http://www.droid-life.com/2014/12/02/android-5-0-1-headed-to-aosp-as-build-lrx22c/
I'm ready!
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
I laughed way to hard for that.
SilkyJohnson said:
I've got five candles lit and Kenny G on in the background, plus I'm wearing my fancy silk robe.
So yeah, I'm ready ☺
Click to expand...
Click to collapse
Lmao!
This is why we get "Nexus". We are the bleeding edge
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.
tee00max said:
I just get my device today and then rooted it immediately to find out there is an update coming out. I wonder how the OTA is going to do when I'm rooted????
Click to expand...
Click to collapse
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6
Looks like factory images are starting to go up:
"Update: *And just like that, Android 5.0.1 factory images have gone live for a handful of devices, including the Nexus 9, Nexus 7 (2013) WiFi, and Nexus 10. Basically, we are looking at the WiFi devices. *You can grab individual image fileshere."
-per Droid-Life
SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?
iboj007 said:
Can we only flash boot.img and System.img? would this fix root and replace any modded system files?
Click to expand...
Click to collapse
Hey, I'd give it a try! In theory I'd say it could.
SilkyJohnson said:
P.S. I think any proper Nexus owner should always have the latest stock image downloaded to their computer. If you ever need to save your ass it's just a click away. Plus, come downgrade time you're ready to go when you get off work ?
P.P.S. use Google Remote Desktop and leave your home computer on the developer page. That's what I did on the N5 when our images got released. That puppy was downloaded and ready to go the second I walked in the door.
Click to expand...
Click to collapse
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.
crashercarlton said:
For Sureeee. It seems i have had a few more issues with this phone in which having the factory images and fastboot have been a godsend.
Click to expand...
Click to collapse
Agreed.
I can't get ADB to work after unlocking, but fastboot works like a champ and that's all I really use. I use ADB to reboot into BL ? I haven't cared or missed it enough to troubleshoot and fix.
Just refreshed the Dev page and it seems everything recent has been updated, minus the N5/6.
I have faith ?
jbdan said:
Lmao!
This is why we get "Nexus". We are the bleeding edge
Click to expand...
Click to collapse
Yup. I feel like I did when I first got my Galaxy Nexus and updates were fat and furious.
Sent from my Nexus 6
SilkyJohnson said:
Lollipop checks to see if ANY system files are modified. If yes, it fails. Before, you could just put stock recovery back on and pretty much call it a day. I will just flash the factory image, boot up and take the OTA - then immediately go back into fastboot and put recovery, root and an unencrypted kernel right back on. Lollipop's app restore functionality I kind of like, so I can be back up and running pretty quick.
Or you could try to restore only data through recovery, but that's risky when jumping versions. I won't do it.
Click to expand...
Click to collapse
rlh445 said:
If you have a custom recovery you'll have to do a system wipe before you can flash the OTA.
Sent from my Nexus 6
Click to expand...
Click to collapse
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.
I'll wait for a TWRP flashable zip :fingerscrossed:
tee00max said:
Right now I am running stock recovery. All I have is the bootloader unlocked and have root access.
Click to expand...
Click to collapse
It'll fail with root now.
looks like they're posting wifi only for now
indianajonze said:
looks like they're posting wifi only for now
Click to expand...
Click to collapse
Typical Googs.
Hey guys,
So the other day i was flashing my nexus to stock, and that all went fine, but when i went to OEM Relock it, my Nexus came to the Google boot stage, and wont go past that at all, i could leave it there for 8 hours, and nothing would happen. It is no longer rooted, and when i try to boot it in to recovery mode, there is an android symbol with an exclaimation mark. Though, i can boot it in to the Bootloader. Can anyone give me a hand? i'll be willing to do anything since this is my last attempt at salvaging my Nexus.
I don't actually need help, I'm merely ****posting so I can post in the thread I want to post in.
RubberDucky_EN said:
Hey guys,
So the other day i was flashing my nexus to stock, and that all went fine, but when i went to OEM Relock it, my Nexus came to the Google boot stage, and wont go past that at all, i could leave it there for 8 hours, and nothing would happen. It is no longer rooted, and when i try to boot it in to recovery mode, there is an android symbol with an exclaimation mark. Though, i can boot it in to the Bootloader. Can anyone give me a hand? i'll be willing to do anything since this is my last attempt at salvaging my Nexus.
Click to expand...
Click to collapse
Have you tried using the Nexus Root Toolkit?
Fobos531 said:
Have you tried using the Nexus Root Toolkit?
Click to expand...
Click to collapse
Yes, that is exactly what i used.. :/