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).
Apologies if this is a really stupid question, I have tried to search for a solution and found a few replies to other posts but I still don't really understand how to solve my problem.
My phone is rooted, running stock rom and had franco kernel on it.
I wanted to install the 4.3 OTA update so flashed the stock kernel and tried to update, but it failed saying "warning no file_contextsVerifying.. etc etc". I didn't write down the whole error message as I thought that I'd be able to recreate it if needed by trying to update again.
However, I now have stock rom and kernel but am still on 4.2.2 and when I check for updates it tells me that my phone is up to date.
How can I get to stock everything and update OTA without losing any of my apps/data and remaining rooted? Thanks for any help!
You need the stock recovery as well, without it the OTA won't run (has been mentioned hundreds of times before, see the OTA thread in General for more info)
EddyOS said:
You need the stock recovery as well, without it the OTA won't run (has been mentioned hundreds of times before, see the OTA thread in General for more info)
Click to expand...
Click to collapse
You don't need stock recovery. Twrp or CWM can install the update. Try this http://forum.xda-developers.com/showthread.php?p=37482646
From my BLACKED OUT N4
spaceman860 said:
You don't need stock recovery. Twrp or CWM can install the update. Try this http://forum.xda-developers.com/showthread.php?p=37482646
From my BLACKED OUT N4
Click to expand...
Click to collapse
You do if you want to do the process normally (ie. download OTA and flash without having to manually choose it in recovery). And that link goes to the Franco kernel thread, which I'm pretty sure has no bearing here
EddyOS said:
You do if you want to do the process normally (ie. download OTA and flash without having to manually choose it in recovery). And that link goes to the Franco kernel thread, which I'm pretty sure has no bearing here
Click to expand...
Click to collapse
You can use a custom recovery to do it normally to when you get the notification just click on it. The reason I posted that link is because he had Franco kernel which changes a system file the link shows you how to change it back
From my BLACKED OUT N4
EddyOS said:
You do if you want to do the process normally (ie. download OTA and flash without having to manually choose it in recovery). And that link goes to the Franco kernel thread, which I'm pretty sure has no bearing here
Click to expand...
Click to collapse
So if I'm happy downloading the update on my computer and flashing it via cwm, I wouldn't need stock recovery? Does that mean that in my phones current state (stock rom, stock kernel and cwm) I could just do that to get to 4.3 and wouldn't lose any apps/data? Sorry if the answer to that is obvious...it just didn't like trying to install the ota update.
IMHO if you want to update via OTA you're better off being 100% stock, it will unroot you and there have been issues re-rooting 4.3 unless you know what you're doing. You also need the stock kernel to flash the OTA so you'll need to flash that back before hand. Easiest thing to do is back up your apps, flash the 4.3 factory image, re-root and restore your apps/data
I don't want to have issues re-routing so I guess my safest bet is to just stick with what I have right now?
Hi everyone, I'm having a hell of a time trying to update my phone from 4.2.2 to 4.3 (stock rom). I have searched the forums (or tried to) and have done general Google searches, but nothing with my problems came up. I rooted my phone a while back, lost root when my phone updated to 4.2.2, then used wugfresh's Nexus Root Toolkit to get it back. Ever since 4.3 came out, I have been unable to update. I was using TWRP, and when updating through the phone it would simply dump me back there and not continue. I was then instructed to manually flash through TWRP, which I tried to do, but halfway through the flash it simply stops. I believe it said "signature verification failed". Someone had me try using the NRT to push the update as well, but that hasnt worked either. It just fails.
After asking around some more, I was instructed to flash the stock recovery, which I have now done. Now when I try to update (through the phone), it takes me to stock recovery, starts installing the update, and (yet again) halfway through the android guy just has an X on it and it says "failed". With Kit Kat supposedly coming out in two days, I really want to be ready to get the update asap. Could anybody help me out?
Also, if possible I would like there to be a way to do so without losing the data on my phone. But its not necessary.
I am sorry if this same problem has come up before. I tried going through other threads and the ones suggested after typing in the thread title.
Why don't you just use the toolkit to bring you back to stock and unroot? Once that is done you will get the update OTA
I am on stock, and I am getting the update OTA. It is just failing to install every time I try to install the update.
Your did something wrong when going back to stock. Did you unroot and relock the boot loader?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Or you can just flash all the .img file of the 4.3 using adb.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
I did same thing without any problems after I unrooted and installed stock kernel.
Just use Wug toolkit and factory 4.3 image.
Now open image and extract radio, bootloader and system img.
Now use Wug and flash only these img.
Then reroot and start flashing custom kernel or roms.
Sent from my NookColor using Tapatalk 4
If everything else fail, do it manually.. Seek this thread.. http://forum.xda-developers.com/showthread.php?t=2010312.
Never do anything using toolkits.. Manual way is always the best.
this tool may help you:
Have you ever get into a situation where you have a custom recovery on a stock rom and then get a OTA update then you find out that you need to flash the stock recovery to flash?, well this Nexus 4 Stock Recovery Flasher will sort it all out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2413550
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.
OFFICIAL FXZ IS AVAILABLE: http://sbf.droid-developers.org/phone.php?device=0
I can verify, I was about to get a refurb from Verizon and this was the only thing could unbrick it.
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
icase81 said:
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
Click to expand...
Click to collapse
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Q9Nap said:
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Click to expand...
Click to collapse
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
icase81 said:
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
Click to expand...
Click to collapse
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Q9Nap said:
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Click to expand...
Click to collapse
Cache definitely didn't fix it. Tried that last night. I spent 40 minutes redownloading and setting up apps, so wiping user data again wouldn't be fun. I'll check it out in a few minutes and report back.
EDIT: Nope, cache and userdata wipe did not fix it. Oh well, I'll just wait until the fxz image is out for 4.4.2 and try that then.
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
I would like to know this as well!
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
your question really belongs in the q & a section...
as the op states, this recovery is for use only if you have bricked while attempting to apply the update.
to apply the update successfully, you need to have an unmodified system. so if you've made any changes to system files, you should start from the beginning to get to unmodified, rooted 4.4; then apply the update.
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Q9Nap said:
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Click to expand...
Click to collapse
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
icase81 said:
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
Click to expand...
Click to collapse
sure, np. glad you got it working. it's unfortunate that locked users lose root with the 4.4.2 build though.
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
wmjchoi said:
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
Click to expand...
Click to collapse
I'm not familiar with that particular toolkit, but I'm assuming it flashed gpt and motoboot to the 4.4.2 version (I'm also hoping you meant to type 4.4.2, otherwise, flashing an old version might be your problem) both of which you shouldn't try to downgrade. I would recommend re-flashing all of 4.4.2 from the sbf (which is hopefully what that toolkit does -- you should probably post in that thread for this)
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
leffer said:
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
Click to expand...
Click to collapse
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
KidJoe said:
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
Click to expand...
Click to collapse
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Would I use the T-Mobile fxz to fastboot flash a Dev Ed. GSM on T-Mobile plan?
leffer said:
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Click to expand...
Click to collapse
I might be in the same boat, any help would be appreciated. I was rooted pre-4.4.2, and took the VZW OTA, root survived... everything has been good. Now when I try a factory reset it, it boots to FastBoot mode and Recovery option just reboots the phone.
It does say: Partition (recovery) Security Version Downgraded
Fastboot Reason: Boot Failure
Phone can reboot into Android and works just fine. Should I flash the entire 4.4.2 image or is there a glaring red flag that I'm missing like trying 4.2.2 or 4.4 first?
Thanks all!