i have a rooted nexus 10 , not unlocked no custom recovery , rooted it via tool kit , 4.22 update was available via ota so tablet notified me and when i intalled the update it stoped in the mid and saying error , and now when i restart my tablet after google logo android appears and under it "no command" , how should i fix it.
I got the similar issue.. i can't find out another solutions.. i have to reflash the factory image to 4.2 and OTA 4.2.1 and 4.2.2
then use toolkit again to root it.
since Factory image 4.2.2 has released. just flash to it , will be much easier.
Try to search it.. i saw the other one have the same issue..
A friend of me got the same problem and all he did was go into recovery mode and wipe cache. He got this problem because he updated via ota and he had the aosp browser without the original files on /system/app.
What you have to do is power off your nexus 10 and then press power-vol+ and vol- buttons together. When you get to the dead droid recovery menu, press all 3 buttons. You will get into the recovery options.
thank you guys n another thing... to recieve and install the ota updates succesfully do i have to unroot my tablet?
harrisfayyaz said:
thank you guys n another thing... to recieve and install the ota updates succesfully do i have to unroot my tablet?
Click to expand...
Click to collapse
No; keep in mind that if you mod anything system related (apps, framework, build.prop), you'll need to restore it the way it was before actually running the install process.
Sent from my Nexus
Related
Hi
I have a rooted nexus S. When i first rooted it i had this issue
http://forum.xda-developers.com/showthread.php?t=1135929 and solved it using post #3.
Now when i get OTA updates the phone reboots and then the android icon with a package appears. the install begins but fails to and android with an exclamation mark icon.
I dont have logs because when i reboot the update isnt offered anymore for a really long time. does any one have any idea what could be wrong?
thanks in advance
The verify check has to complete and u need to flash it manually in custom recovery
I got this when I rebooted my NxS several times while the OTA was ready to be installed. It somehow got lost and couldn't be retrieved anymore.
As I couldn't find a solution I just reflashed the official 2.3.4 full rom and then got a) a working stock recovery and b) a working OTA again.
Official stock roms are signed and can be flashed via the stock recovery and don't need unlocked bootloader.
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
boozelclark said:
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
Click to expand...
Click to collapse
Depends on how you define "everything". You'll need at least an open bootloader to flash the superuser zip via a custom recovery(, can relock the bootloader afterwards).
I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?
I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
gbarayah said:
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
Click to expand...
Click to collapse
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
gosku26 said:
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
Click to expand...
Click to collapse
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
I would like to keep my settings if it's possible.
gbarayah said:
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
Click to expand...
Click to collapse
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
gosku26 said:
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
Click to expand...
Click to collapse
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
gbarayah said:
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
Click to expand...
Click to collapse
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
gosku26 said:
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
Click to expand...
Click to collapse
Glad I could help. In the future, as long as you don't modify the system by flashing any modifications, you should be able to get the OTA update to install. Root doesn't affect this, and if you're worried about it, you can always uninstall it.
I opted to update using the stock zip files that were posted above and it worked just fine for me.
I got the 4.4.3 update notification and downloaded it. When it rebooted for the install, it went into TWRP recovery. Not sure what to do with that, I rebooted. Now I am still on 4.4.2 and getting the "up to date" when I check for updates.
I am rooted running stock ROM. Does being unlocked and rooted with custom recovery prevent an OTA install of updates?
I vevs
Sent from my Nexus 7 using XDA Premium 4 mobile app
I'm also looking for help updating to 4.4.3. I uninstalled Xposed and tried to flash the update zip with TWRP but the install failed. Does the update need to be installed via adb sideload?
Sent from my Nexus 7 using Tapatalk
When my n7 was on 4.3.1 stock rooted with unlock bootloader i updated via ota and twrp can handle it. I dont know about 4.4.3. There is a thread discussing this matter but i dont remmember where, i think is in the general. I never used side load but im using nrt nexus root toolkit for udpating to 4.4.3 and it work fine.
vs980
Same problem!!
Exactly same has happened to me. I got the notification for update than i downloaded it, it was about 70 mb , then rebooted my device, goes to TWRP recovery than what ?? I just restarted my device and in settings its still on 4.4.2 what to do Now ????
Hey all
What does TWRP stand for please?
I also got the notification to update to 4.3.3 but after downloading, when the installation began I got an error screen with the android dude lying on his back. I switched my nexus off and on again and I'm still on 4.2.2.
Now I get the same message when I check for updates.
How can I get my tablet to update again please?
My nexus is a regular unrooted tablet with the stock ROM that was installed via the previous ota update.
Many thanks
Sent from my Nexus 7 using XDA Free mobile app
hmmmm, sounds odd. same thing happened to me.
maybe TWRP(Team Win Recovery Project) cant handle it, or we should have updated it first. Or maybe we should have used CWM or Stock Recovery.
but the strange thing is that the tablet cannot find the update again!!
i'll try to update NRT (Nexus Root Toolkit) and see if i can update using that.
Don't install it, until there's an answer in http://forum.xda-developers.com/showthread.php?t=2786758 - a couple of us did install it, and we've lost root, but more importantly, recovery has been wiped, and I've been unable to reflash CWM with fastboot.
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
GrillMouster said:
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
Click to expand...
Click to collapse
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
hamid_valad said:
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
Click to expand...
Click to collapse
Flashing stock recovery.img and stock system.img does not wipe all my data. Everything was still there: all my media, files, apps, and app data.
I think you're right about the Stickmount app. I did have it on my son's tablet, and I had to flash system. Last night I updated my wife's tablet. She did not have Stickmount, so the OTA installed without me having to flash system. Just to be safe I did flash stock recovery first. I put TWRP back on and re-rooted after the OTA.
I used Google's batch file on windows to flash the stock 5.0, having unlocked the bootloader and also installed the chainfire root. Just wondering whether I'll get any fixes, or whether i'll have to always repeat this process, wiping out everything on the device in the process.
You may get prompted to download and install new updates when they arrive, but they will fail upon installation unless you're 100% stock.
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Does the Google image download page (https://developers.google.com/android/nexus/images) get updated as Lollipop gets updated? Or am I going to have to do OTA updates?
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
igeigeige said:
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
Click to expand...
Click to collapse
Well, I'm a bit confused. I'm on stock, but i need root, so i installed cfar, which I think included super su. when a new version of super su came out (i was alerted via google play), i needed to install the twrp recovery (which I didn't have installed at that point) to update it. So I guess I'm not stock any more, even though I've not actually put a non-stock image on. So even if the OTA update message popped up, I doubt it's safe to install it that way, even if it let me. I'm just not sure whether I need to a factory reset/wipe etc before updating, or if I can do a dirty update (the OTA is effectively a dirty update, isn't it?). And, like i said, i'm not sure whether that page gets updated with new images, or whether you're supposed to just put the initial one down and then do OTA updates (and only then root, change the recovery etc).
You have a stock rom but with a CUSTOM recovery. Yes, ota will prompt you to update, but DON'T. You should convert to stock recovery first. Because if you do, the update will push through, but once it asks you to boot to make the update in effect, you will have a NO COMMAND error - bootloop, and only fastboot and recovery (sort of dysfunctional). Just like most of the people here, including me. So make backup of your files first before doing the update. Cheers :good:
Sent from my Nexus 10 using XDA Premium 4 mobile app
If having a custom recovery is an issue, why could I flash ota zips from custom recoveries ever since buying the tablet?
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Rizz67 said:
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Click to expand...
Click to collapse
Hi, what i did was flashing the official factory image from google via fastboot/bootloader... Make a nandroid backup first though.. Because you'll need to clean flash (system partition/cache and data) to avoid future problems.
please educate me
A few weeks ago I rooted my N4 with CFAR (& of course had to wipe out everything). My understanding was that now that my bootloader is unlocked, I can sideload new images, thus sparing me a rewipe -- & in my ignorance, was anticipating that ChainFire would make 5.0.1 images in due course.
So, If I want to root subsequent 5.x.x releases, how would this work in real life??
Can i just restore stock recovery and then install the 5.0.1 ota update without losing everything?