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

Lost my galaxy nexus waiting on my Nexus 4

I had a question meanwhile so I am able to better protect my nexus 4. I had ceberus installed on my galaxy nexus, but really for anyone that has half a brain he would just flash the phone back from the boot menu. Is there a way to protect your phone from being flashed if stolen? Can you put a pass to even get into the boot menu? :crying:

ludeboye said:
I had a question meanwhile so I am able to better protect my nexus 4. I had ceberus installed on my galaxy nexus, but really for anyone that has half a brain he would just flash the phone back from the boot menu. Is there a way to protect your phone from being flashed if stolen? Can you put a pass to even get into the boot menu? :crying:
Click to expand...
Click to collapse
If you install cerberus via CWM (a system apk) it can survive a factory reset... And people who are about to steal your phone have no idea what CWM is... so you it should work!
Edit: I actually remove my CWM entirely and go back to stock recovery. Makes it even harder for them to get at it.

elliot.newnham said:
If you install cerberus via CWM (a system apk) it can survive a factory reset... And people who are about to steal your phone have no idea what CWM is... so you it should work!
Edit: I actually remove my CWM entirely and go back to stock recovery. Makes it even harder for them to get at it.
Click to expand...
Click to collapse
Thanks but wouldnt that mess with future ota updates?

There is hope?
ludeboye said:
I had a question meanwhile so I am able to better protect my nexus 4. I had ceberus installed on my galaxy nexus, but really for anyone that has half a brain he would just flash the phone back from the boot menu. Is there a way to protect your phone from being flashed if stolen? Can you put a pass to even get into the boot menu? :crying:
Click to expand...
Click to collapse
It sucks that you lost your GNex.
If you are lucky enough you can still find it and recover it using AndroidLost:good:.
Its on the Play App store. This app can locate your phone, and take pictures of who ever is holding it and/or using it. You can lock your phone with it but any android power user can flash your phone from the boot menu. The idea is to get to your phone before anyone attempts to flash it in the first place, by locating it in 2 minutes using AndroidLost or any respectable Find My Device kind of apps. Worse case it will delete everything on your phone if you cannot locate it, as to keep preying eyes away from your data.
www.AndroidLost.com
Let me know if you need help with the App, I use it daily for almost a year now.

ludeboye said:
Thanks but wouldnt that mess with future ota updates?
Click to expand...
Click to collapse
No...All you need to do is copy the cerberus.apk to the system/app folder. OTA don't uninstall the app. If you are concerned, after an OTA update, check the folder and see if the cerberus apk is there. If it is, you are good to go, if not, just copy it back.

Id recommend downloading hidden version of Cerberus .... Found on their webpage
Sent from my Nexus 4 using xda premium

[Q] hard bricked and SOL it seems

I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
Can you get into the bootloader?

DaanJordaan said:
Can you get into the bootloader?
Click to expand...
Click to collapse
No. it's really gone. Just spoke with google and getting a replacement. I really can't do jack....bleep...with it.
all this for changing a font with Rom toolbox.

Yeah, bricked, but I'll buy it for 30

So it's permanently stuck on the Google logo and you can't access recovery or bootloader? No boot animation?
I wonder why something so trivial as a font change caused this... I've had font changes cause bootloops but never a bricked device.
Sent from my Nexus 7 using XDA Premium HD app

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
You aren't alone.
That app is made by the ROM Toolbox dev, lotsa complaining in the reviews about it bricking. You did connect it to your PC via USB and tried pushing the needed bits and starting from scratch didn't you? I'd even try one of the toolkits available for rooting and recovery.

After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks

As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.

I'm glad I was able to fix it. My computer was not able to recognize the device while I was on the fastboot screen (android laying down.) THe only other screen I ever was able to get was the bootlooping screen. By chance I realized the computer was connected to the device only if it was on the bootloop screen. When I saw that, then I was cooking with fire.

Sounds like you should install your fast boot drivers
Sent from my Galaxy Nexus

I've only just got my nexus (first tablet) had it for two weeks, decided to root mainly because I hate adverts popping up everywhere, anyway I digress. I purchased toolbox pro for my hox ages ago and even though I haven't installed it, for the last few days I've been thinking of it so cheers buddy for bringing this to my attention
Sent from my Nexus 7 using xda premium

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
Best. Idea. Ever.
Also, with a Nexus device at least that was a shot. Many others would keel over and die for good if that sort of stuff happened.

neiander said:
After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks
Click to expand...
Click to collapse
Cool, and agreed with the above. If you can see stuff on the screen, it's technically not bricked.
Bricked an N7 once, it was stuck in APX mode, the lowest recovery mode for tegra chips I believe.
At the time there was no way recovering from it using NVFlash, maybe there is now though.
Mind telling us how you got yours back to life? Just curious
Cheers

all nowellel
Was really luck. I was working on trying to get the computer to sees the device. Trying to load drivers. Anything I could do. The computer kept saying no adb device plugged in. Finally after deleting drivers and reloading drivers, I plugged in the device while it was bootlooping and heard the correct "connected" sound and saw the device in device manager. Then with toolbox, was finally able to reboot into recovery and wipe and reinstall rom. Didn't lose anything in the process.

Oh, the thing that was really the biggest mind blower was that there were 2 screens I could get to, bootlooping screen and what appeared to be the correct fadtboot screen, the computer would not recognize the device when I was on the fastboot screen. That was why I thought I was SOL.

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
What is this NVedit tool? I cant seem to find that anywhere. I'm working on my buddy's N7 32GB Wifi, he tried to revert to stock from having CWR and CM10.1 using the Nexus Root Toolkit and now there is that problem happening you mentioned, backlight wont light up and computer doesnt recognize the device and I cant get into the bootloader either. Already checked the Screen itself and it works (disassemble and connected to my N7) and the battery has power, just no luck.

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

Need help, bootloop..

I installed LCD Density app from the market. Changed settings from 320 to 300 and it said to reboot phone. This put my phone into bootloop with LG logo and led flashing. My phone is Verizon, rooted with TWRP installed. I can get into TWRP but hadn't made a backup yet. Any ideas? I tried wiping will in TWRP and then rebooting but still got the bootloop. If it matters, I have a Mac. Thanks for any help...

Factory reset in twrp. Then install the rom again should work. Changing dpi can have adverse effects ☺
Sent from my LG-D800 using Tapatalk 4

How can I get the Rom onto my phone? I have a Mac?

did you delete the rom from the sdcard? if it isnt there anymore then you will need to adb push it. I dont have a mac so cant be of help on that side of it.

I was running stock Rom. Only mod was black notification bar. I hadn't downloaded any roms yet. Don't think I can get adb to recognize my phone as I can't select Ethernet connection. Any ideas?

I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app

Yeah I have always made a back up in the past. I'm so annoyed at myself for not doing it. Any suggestion on how I can either get a rom onto my phone or edit the build.prop back to stock?

Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.

black05x5 said:
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
Click to expand...
Click to collapse
Excellent.
Thanks Devs. From my VZW G2.

trickster2369 said:
I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
It amazes me when people don't create a backup.