Database Users

To update... Or not to update... That is the question.

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

Need Advise Before Sending Back To Samsung

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

Grouper bricked after latest 4.3 OTA, no recovery

Heya...
On my 16GB Grouper I had installed the stock rooted 4.3 rom. Yesterday a system OTA update message appeared on my screen - 1.7 MB. I let it download and install over night and just went to bed. Came back in the morning to a boot loop where the device got stuck with the four colorful thingies animation. I can access the bootloader, but the recovery seems to be broken. Can't remember if I had anything other than the stock one... Anyways, now I'm strugling to get this thing going again. I am a zero at ADB but willing to learn whatever is necessary to get me started with a working recovery at least. No tool root box will do anything really for me...
Thanks for your help in advance

Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app

hettige677 said:
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah. It would be dumb to actually learn what you are doing to your device. You should totally use a toolkit.
/s
Sent from my Galaxy Nexus

Honestly, I'm just showing the user one way, I anticipated him of being a newbie. For the record, it shows you all the process's happening.
Sent from my Nexus 7 using xda app-developers app

Thank you guys. You might not believe it, but I'm not a newb to Android or flashing. It's just that I've always been playing around with Samsung devices and there you'd normaly turn to Odin in case something went wrong. Here it's different.
Anyways, with this comprehensive guide I've been able to reflash a recovery image and my old rom. Unfortunately losing all of my data in the process, but there was no way to save it.
http://www.androidupdate.us/recover-bricked-device-fastboot/
In case this happens to anybody else.
Cheers

D801 bricked. No download mode.

Short version: phone won't boot, won't go into download mode, won't properly do a factory reset (tries but doesn't do it), need help.
Finally bricked my phone after tampering with it too much.
I was on the stock KK rom released by LG themselves, no root. Reverted back to the 10c firmware, OTA to 10g, rooted and installed TWRP - flashed a Vodaphone Germany KK ROM for the LG G2 because I heard it had minimal bloatware and no bluetooth wakelock unlike the KK version I was on for T-Mobile (my carrier). It had the touchscreen issue which I never experienced before. Tried multiple times to go back to any T-Mobile LG G2 ROM using the LG Mobile Support Tool - no dice. Uninstalled and reinstalled everything twice. So I figured, oh hey, I probably need to use the Vodaphone Germany JB.kdz file, root that, install TWRP, then flash back to the T-Mobile KK version that I had before. Seemed fool proof in theory. Used the LG Tool to do such, it finished smoothly and now my phone won't boot. It won't do a factory reset (it enters the factory reset mode and it attempts to do one but just reboots). It won't enter download mode either. I think I'm screwed here. Any advice?
I found 2 guides, but to even begin to do the first one I need my phone to enter fastboot mode and I can't find out how to do that anywhere.

you say Won't go into download mode? What happens when you try?

It just shows the first screen as it tries to enter download mode, with the blue dots. The screen that comes after that doesn't happen anymore. It used to switch to it after a few seconds and then the LG Mobile Support Tool could connect to the phone, but it can't anymore.
Sent from my SGH-T989 using xda app-developers app

your phone may be was hard brick, can't do anything

Mine did that once. I complely powered it off and left it alone for 20 minutes and it suddenly worked. Freaked me out

This is what you need http://forum.xda-developers.com/showthread.php?t=2582142

Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1

I'm nervous to try that. I have no experience with ubuntu. But I'll give it a go tonight
Sent from my SGH-T989 using xda app-developers app

CHlCKEN said:
Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1
Click to expand...
Click to collapse
would you PLEASE fix your posts so the signature is at the bottom?

The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk

Gonna try what offenberg suggested in a few hours. Fingers crossed
Sent from my SGH-T989 using xda app-developers app

uToTMeH8 said:
The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over $10 a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app

ducidni said:
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
So did they fix it for you under warranty?
or they figure out that you root it and play with it !?
because I'm having the same problem with my f320k and I'm thinking to send it back to Korea

Same is the case with me, my phone is dead for more than 20 days.
here are the details if any one can help?

[Q] cant resolve boot loop

During the last two days I overcome the problem of mass boot loop on nexus 4 without success.
The device enters bootloop after regular restart that was done because I lost service.
Before that I had a problem that during a call the screen would turn off.
I did not root or any other manipulation device. Since I bought it (two weeks ago), he was upgraded to 4.4 OTA
I went through the posts on this forum and also online.
I've by fastboot, Flash of recovery; boot; system; radio; userdata. Well also downgraded to versions 4.2
I changed the recovery to CWM still no success.
How ever in the CWM recovery I was able to flash Hellfire (HF) ROM via "adb sideload"
after i did the wipe I restarted, the boot animaton has changed to the one of HF and a message stating that Android is upgrading: optimizing apps and then starting apps. at this point the device was stuck.
after a restart I am stuck again in the bootloop.
how should you proceed now?
thanks

Try to boot into recovery and wipe everything. Then flash rom. Let me now how it goes! Had the same problem last week...
Hit thanks if I helped you

Already tried that
might try a different ROM

If you unlock the bootloader in fastboot and then reboot the device back into the bootloader does the bootloader stay unlocked or does it lock again?
Sent from my Nexus 4 using XDA Free mobile app

lolcakes203 said:
If you unlock the bootloader in fastboot and then reboot the device back into the bootloader does the bootloader stay unlocked or does it lock again?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader remains unlocked. when I run "Fastboot oem unlock" the return line indicates that it was already unlocked.
also the lock state is unlocked (red line on the bottom)

Okay, thank you this was a test for a bad emmc (memory chip). I'll see if I can think of something else you haven't tried.
Sent from my Nexus 4 using XDA Free mobile app

Flash the factory image and then after, boot into the stock recovery and do a factory reset
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image and then after, boot into the stock recovery and do a factory reset
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that, No GO

laly76 said:
Done that, No GO
Click to expand...
Click to collapse
Looks like you've every everything you can. Are you still under warranty?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Looks like you've every everything you can. Are you still under warranty?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Bought it on Ebay, about 3 weeks ago.
not sure about warranty and how do I approach about it.. Google? LG?

laly76 said:
Bought it on Ebay, about 3 weeks ago.
not sure about warranty and how do I approach about it.. Google? LG?
Click to expand...
Click to collapse
You'll probably have to go thru LG. I know a guy who's a guru at this type of thing on the n5. Maybe he can help on the n4 @bitdomo They're very similar devices
Sent from my Nexus 5 using XDA Free mobile app

laly76 said:
Bought it on Ebay, about 3 weeks ago.
not sure about warranty and how do I approach about it.. Google? LG?
Click to expand...
Click to collapse
I only can speak warranty in the EU. It maybe different in the other parts of the world.
If the phone is originaly from google playstore you have to talk with google. If the phone does not come from google plastore originaly then you have to talk with LG. To take your phone to LG to repair your phone under warranty you will need the original receipt with the imei number printed on it from the store it was bought. Also keep in mind if the phone comes from GSM shop or then those GSM shops does not give you LG warranty just shop warranty which means that the phone have to be taken back to the original store with the original receipt. These stores sells phones only with 1 year warranty.
I forgot to mention, if the phone is from google playstore originaly then the warranty is only valid in that country's google playstore which the phone comes from.

bitdomo said:
I only can speak warranty in the EU. It maybe different in the other parts of the world.
If the phone is originaly from google playstore you have to talk with google. If the phone does not come from google plastore originaly then you have to talk with LG. To take your phone to LG to repair your phone under warranty you will need the original receipt with the imei number printed on it from the store it was bought. Also keep in mind if the phone comes from GSM shop or then those GSM shops does not give you LG warranty just shop warranty which means that the phone have to be taken back to the original store with the original receipt. These stores sells phones only with 1 year warranty.
Click to expand...
Click to collapse
Can you help him with the boot loop issue? He's flashed the factory image, fine a factory reset,etc
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Can you help him with the boot loop issue? He's flashed the factory image, fine a factory reset,etc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
He could try this if he has patience and determination. This wipes everything and rebuilds the partitions.

Update
Tried everything, no success, more over when I came back to try and work some more on the nexus 4 I noticed the screen was broken (haven't touched it the last 2 days...) finally gave up.
I got a full refund from the Ebay supplier
Still very disappointing, Ill chuck it all up to a faulty device