I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?
How are you doing this, using adb sideload with the ota zip or ?
- Sent from my US Cellular SGS3
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
There's plenty of ota zip files that are the official ota which will allow you to upgrade.
Are you 100% stock or ?
- Sent from my US Cellular SGS3
yanksrock1000 said:
I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?
Click to expand...
Click to collapse
Is the device rooted and have you modified any system files? This generally happens when the patch update system attempts to patch a file for the update but it's been modified or missing.
Cheers,
Kermee
Haven't modified a thing, its completely stock.
Sent from my Nexus 7 using xda app-developers app
Try doing a factory reset
Sent from my SGH-T959V using xda app-developers app
I'm running into the same exact situation, except I have a 16GB. Whenever I attempt to update to 4.2 I get the robot lying on its back with a red exclamation point in its belly.
Related
My nexus 7 is rooted. Is that why it can't accept the 4.1.2 update? What should I do? It keeps reminding me to install the update every 15 minutes. When I try to, it just crashes.
Sent from my Nexus 7 using xda app-developers app
You want to eat from two tables ... ? It's your choice, original or rooted ...
Sent from my Nexus 7 using xda app-developers app
I'm trying to update it while keeping root. I downloaded ota root keeper. But I keep getting the "dead Android with red exclamation mark" screen every time I try to install the OTA update. I even tried its option to temporarily un-root before performing the update, but no luck. Anyone have any ideas?
Edit - Also I tried installing it manually. Used GooManager to install TWRP and tried installing 4.1.2 through it. Still fails every time. I'm disgusted.
Sent from my Nexus 7 using xda app-developers app
I had my Nexus 7 rooted w/ the "Google Nexus 7 Toolkit" and I was able to update to 4.1.2 w/o any problems.
Sent from my Nexus 7 using xda app-developers app
Having the same issue as well..Can't root.
Sent from my GT-I9100 using xda premium
---------- Post added at 02:41 PM ---------- Previous post was at 02:25 PM ----------
Well after trying again I finally successed doing so.
Sent from my GT-I9100 using xda premium
Backup--unroot--relock--update--unlock--reroot--recover? I'm brand new to this stuff (don't even have a N7 yet), but seems like this would work.
The stock update will only install with stock recovery being root has no effect. If you have changed system apps. Like to the 4.2 apps floating around could stop the update as well. Google does not care another root or unlocked. I would say do factory reset then update then root. Or download one of the stock cwm/twelve roms and be done with it.
Sent from my Nexus 7 using Tapatalk 2
Well it happened again. The 4.2.2 update is out and I can't update to it. Every time I try, I get the dead android error icon.
It sure gets old saying this, but...
The error message is recorded in the recovery log at
/cache/recovery/recovery.log
You will find that the problem has nothing to do with root per se - generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
In general, OTAs are not meant for customized ROMs - it is unreasonable for anyone to have an expectation that they will work correctly on a customized ROM.
But I didn't install a customized rom. I just rooted/unlocked it.
You can always download the update from Google's servers and flash it through fastboot. No hassle.
Bryon15 said:
But I didn't install a customized rom. I just rooted/unlocked it.
Click to expand...
Click to collapse
the proof is in the pudding...
...and the pudding is at /cache/recovery/recovery.log
bftb0 said:
generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
Click to expand...
Click to collapse
Note that the recovery.log file gets overwritten every time you boot the recovery, so the thing you are trying to retrieve (let's say with the booted OS) will be from the immediately prior use of the recovery. So, attempt the OTA (let it fail), then boot into the OS and capture that file (using something which is root-privileged).
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?
Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.
Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.
Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app
thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app
I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.
Guys, I've been checking for system updates for a week, but JWR66Y update has never shown up. I'm running fully stock, no root or anything. Am I doing something wrong?
kzakhar said:
Guys, I've been checking for system updates for a week, but JWR66Y update has never shown up. I'm running fully stock, no root or anything. Am I doing something wrong?
Click to expand...
Click to collapse
You could flash the factory image instead of waiting for the OTA update.
You're not doing anything wrong. Just keep trying.
abaaaabbbb63 said:
You could flash the factory image instead of waiting for the OTA update.
You're not doing anything wrong. Just keep trying.
Click to expand...
Click to collapse
Many thanks for your response!
I take it, flashing the factory image would mean losing all data, and I'd rather avoid that.
I will keep trying to get the OTA update, just thought it would be available by now, it's been a week already
Try forcing the OTA update
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 05:14 AM ---------- Previous post was at 05:06 AM ----------
First you want to check for an update the traditional way:
Go into your Android device’s main Settings.
Scroll down to the bottom and tap on About Phone.
Tap on System Updates (or something along those lines).
If applicable, tap on Check Now.
If you get notified that an update is available, then your done!
If you weren’t so lucky, then follow these steps:
Go into your Android device’s main Settings.
Tap on the option for Apps (or something along those lines).
Swipe over (or change the filter) to the All tab (where you can see all the apps on your device).
Find Google Services Frame work and tap on it.
Hit Clear Data (this wipes back-end Google information that clears the update logs).
Press Force Stop to close the Google Services Framework application.
Check for an update using the traditional method outlined above.
This method works on both smartphones and tablets, but like we mentioned earlier there has to actually be an update available for your device’s specific model. As in, if you have a Verizon Galaxy S3, there has to be an update specifically for the Verizon version of the SGS3. Also, for those of you wondering, clearing the data for Google Services Framework doesn’t delete your Google accounts, contacts, calendar or anything like that from your phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
kzakhar said:
Many thanks for your response!
I take it, flashing the factory image would mean losing all data, and I'd rather avoid that.
I will keep trying to get the OTA update, just thought it would be available by now, it's been a week already
Click to expand...
Click to collapse
You're able to install the ota.zip using the stock recovery and adb sideload
Where to download the package and how to do that should be explained in the ota help thread (I guess it's the thread)
Sent from my Nexus 4 running Android 4.3
Ok i have a unrooted Nexus 7 and it received the OTA update but stopped halfway through the update. Now the device will never pass the flashing LOGO symbol. this phone was never rooted and i never turned on the debug option. I tried using fastboot and adb but when i type the "devices" command it doesn't see the tablet. Also when i try to go into recovery mode it just shows the android with the red exclamation sign and says "no command". Can anyone help? Thank you.
Ksealy03 said:
Ok i have a unrooted Nexus 7 and it received the OTA update but stopped halfway through the update. Now the device will never pass the flashing LOGO symbol. this phone was never rooted and i never turned on the debug option. I tried using fastboot and adb but when i type the "devices" command it doesn't see the tablet. Also when i try to go into recovery mode it just shows the android with the red exclamation sign and says "no command". Can anyone help? Thank you.
Click to expand...
Click to collapse
This happened to me last night except I was rooted and had CWM installed. I wound up having to restore to factory settings and then I was able to OTA from there, so I lost all of my data. Are you using Windows or OSX? There is a great Nexus 7 Toolkit from Skipsoft which will do everything for you automatically. If you are on OSX I used the one click unroot restore found here http://www.androidrootz.com/2012/12/nexus-7-one-click-toolkit-for-mac.html
danipoak said:
This happened to me last night except I was rooted and had CWM installed. I wound up having to restore to factory settings and then I was able to OTA from there, so I lost all of my data. Are you using Windows or OSX? There is a great Nexus 7 Toolkit from Skipsoft which will do everything for you automatically. If you are on OSX I used the one click unroot restore found here http://www.androidrootz.com/2012/12/nexus-7-one-click-toolkit-for-mac.html
Click to expand...
Click to collapse
I am using windows. I guess i will search to see if i can find the windows version. Thanks.
Crap so I need to factory reset this, what about root ??
Sent From My Rooted G3
mobgod said:
Crap so I need to factory reset this, what about root ??
Sent From My Rooted G3
Click to expand...
Click to collapse
I was rooted and factory reset was the only way I could get it. I know there are other people on here far smarter than I am at getting the tablet to speak with the computer so there could very well be another way. Honestly I'm glad I did the factory reset though, my tablet is smooth as butter again. I had a lot of junk on it before that was really making it laggy. Here is the website for the windows toolkit http://www.skipsoft.net/
danipoak said:
I was rooted and factory reset was the only way I could get it. I know there are other people on here far smarter than I am at getting the tablet to speak with the computer so there could very well be another way. Honestly I'm glad I did the factory reset though, my tablet is smooth as butter again. I had a lot of junk on it before that was really making it laggy. Here is the website for the windows toolkit http://www.skipsoft.net/
Click to expand...
Click to collapse
Ok so that's to root it again also correct? After I factory reset do the ota than use that site right?
Sent From My Rooted G3
Ok now I'm really stuck can't get anything to work I'm stuck at the Google logo but I can bout into recovery what do I do now ok I can get into recovery just a fyi
Sent From My Rooted G3
---------- Post added at 02:21 PM ---------- Previous post was at 02:00 PM ----------
Ok looks like there is no os what do I do now??
Sent From My Rooted G3
Ksealy03 said:
I am using windows. I guess i will search to see if i can find the windows version. Thanks.
Click to expand...
Click to collapse
There is a Nexus specific tool kit here which I have used for everything that I did to my 2012 N7 (unlock, root, reset etc.) and it couldn't have gone smoother. It's fairly intuitive and there are lots of "how-to's" anyway.
mobgod said:
Ok now I'm really stuck can't get anything to work I'm stuck at the Google logo but I can bout into recovery what do I do now ok I can get into recovery just a fyi
Sent From My Rooted G3
---------- Post added at 02:21 PM ---------- Previous post was at 02:00 PM ----------
Ok looks like there is no os what do I do now??
Sent From My Rooted G3
Click to expand...
Click to collapse
Once in recovery, you might want to just try "Wipe cache partition" first, reboot and see if THAT fixes the issue. That way, you don't have to possibly lose all your app settings.
Otherwise, if that option doesn't work, then you need to select the "Wipe Data/Factory Reset" option. This WILL wipe out all your installed apps and their settings.
Hope this helps!
While i was installing the o update, it failed and wont boot anymore, Just goes to a screen that says no command and reboots. This also happens when I try to reboot into recovery. Im trying to unlock the bootloader so I can reinstall but it ends up on the screen again.
this happened to me with android 7.1.2 , go into ADB , flash everything by cmd , but DON'T USE the comand erase cache and flash cache, that worked for me.
the co0kie said:
While i was installing the o update, it failed and wont boot anymore, Just goes to a screen that says no command and reboots. This also happens when I try to reboot into recovery. Im trying to unlock the bootloader so I can reinstall but it ends up on the screen again.
Click to expand...
Click to collapse
It failed.. how?
You can only unlock once you authenticated and ticked the gear in dev menu within the OS.
Mine does the same thing. It's not unlocked or rooted. Just stock 7.1.2 I enrolled in the Beta program, downloaded, it went to install, then I get the android guy with the red triangle that says No Command below it. It set there for about 30 sec & then it rebooted. Rebooted back into 7.1.2
I still get the system pop-up that there is an update to the Android Beta program.
Same thing happened to mine. But I am on stock Android o (OOP2.170420.017) and not rooted. It was the .019 update and when it tried to install it gave error, but just rebooted back to .017 just fine.
Never had. 017 but yes, 019 is it. Mine just rebooted back to 7.1.2
Guess I won't be testing O at the moment.
Sent from my Nexus 6P using Tapatalk
In4Life said:
Same thing happened to mine. But I am on stock Android o (OOP2.170420.017) and not rooted. It was the .019 update and when it tried to install it gave error, but just rebooted back to .017 just fine.
Click to expand...
Click to collapse
Exactly the same for me
Sent from my Nexus 6P using XDA-Developers Legacy app
Looks like just a bug with .019 at the moment. Just don't install it.
Google released a new OPP2.170420.019 image late last night. It is 1053.3 MB instead of 44.5 MB.
stevemw said:
Google released a new OPP2.170420.019 image late last night. It is 1053.3 MB instead of 44.5 MB.
Click to expand...
Click to collapse
Mines exactly the same size & same issue. I updated from 7.1.2. The 44.5 MB should be the update I believe from 017 Android O to 019.
The image you state was what has been on my phone for a few days. Nothing new yet unless that image that caused issues was fixed.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
I just rechecked updates & still the same 1053.3 MB that isn't fixed yet.
Sent from my Nexus 6P using Tapatalk
quickstang said:
Mines exactly the same size & same issue. I updated from 7.1.2. The 44.5 MB should be the update I believe from 017 Android O to 019.
The image you state was what has been on my phone for a few days. Nothing new yet unless that image that caused issues was fixed.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
I just rechecked updates & still the same 1053.3 MB that isn't fixed yet.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just to be clear I had OTA updates for each install, including the previous 7.1.2 updates.
5/19/2017 Android O preview 2 1053.3 MB (OPP2.170420.019)
5/19/2017 Android O preview 2 44.5 MB (OPP2.170420.019) -- failed 2x (will not install but Android Pay is now working) -- see Android Police page
5/18/2017 Android O preview 2 1053.1 MB (OPP2.170420.017)
- Doesn't work:
- - Android Pay
- - Showtime Anywhere
5/2/2017 N2G47O May 5, 2017 Security update 1,345,871,245
I never had 017. Just 019 after I signed up for the beta program.
There should be a fix soon.
I'm just glad my phone rebooted after getting the red triangle. I was worried.
Sent from my Nexus 6P using Tapatalk
quickstang said:
I never had 017. Just 019 after I signed up for the beta program.
There should be a fix soon.
I'm just glad my phone rebooted after getting the red triangle. I was worried.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Imagine how I felt when I turned away for one minute during the first install of the bad .019 and saw the dead Android and the word "Error"
stevemw said:
Imagine how I felt when I turned away for one minute during the first install of the bad .019 and saw the dead Android and the word "Error"
Click to expand...
Click to collapse
I encountered that at night & was worried. Mines stock, & i was like... Oh great, a dead phone.
I do think that after reading some of the O issues in the G+ thread, I may hold off anyway.
Sent from my Nexus 6P using Tapatalk
So I think I'm ****ed... got the "No command" error too. Phone keeps rebooting into the error. Anyway to fix this?
Darkne0 said:
So I think I'm ****ed... got the "No command" error too. Phone keeps rebooting into the error. Anyway to fix this?
Click to expand...
Click to collapse
Were you on a previous O build? I was on 7.1.2 & it either automatically rebooted or I held down the power button & it rebooted.
Not sure if it was luck or what.
Sent from my Nexus 6P using Tapatalk
quickstang said:
Were you on a previous O build? I was on 7.1.2 & it either automatically rebooted or I held down the power button & it rebooted.
Not sure if it was luck or what.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I was on 7.1.2, all stock. It rebooted, but to the same error each time.
Darkne0 said:
So I think I'm ****ed... got the "No command" error too. Phone keeps rebooting into the error. Anyway to fix this?
Click to expand...
Click to collapse
I don't know if you fixed it, just download the official 7.1.2 Rom, put phone in adb holding power and volume down, fish it and you're good