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
Related
Hello. I searched the forums and came up empty.
I have a stock 4.2 ROM I rooted. When the system says its updating and rebooting. It kicks me into recovery screen and does not up date.
Do I have to unroot and re lock the boot loader?
I know I'm probably just missing something stupid.
Thanks for any help.
If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.
jonnyg1097 said:
If you were on a custom rom before then your recovery is probably messed up and not the stock recovery. Otherwise I do not know what it is that can be doing it because every time I would flash back to stock 4.2 I would get prompted to update to 4.2.1 and as well to note I have an unlocked bootloader and from what I have read before being rooted shouldnt make a difference.
Perhaps you could grab the toolkit and flash the stock recovery that is in it to your N7 and see if that helps you out.
Click to expand...
Click to collapse
Crap. I was hoping I didn't have to reflash. I dont have a custom ROM never have. I just unlocked this and rooted.
I'm going to try the toolkit when I get home revert from stock to stock, see if the update takes then.
Thanks for you help.
Edit. Looks like I have twrp recovery. This is my issue I assume. Is there a zip I can just flash to update
I have removed twrp back to stock recovery. Now when system reboots to install update, it stats the update then gives me a error. No error code just error. I really dont want to wipe my device as I have it setup for my liking.
I'm using wug's toolkit
I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.
RMarkwald said:
I think (...and may be wrong...), but if you modified anything in /system (deleted any of the stock apps and/or updated them) it won't update either.
Click to expand...
Click to collapse
I owe u a beer. I did add browser.apk to my system dir. I removed it and now I'm fully updated.
Thank you so much.
root keeper and I'm back in business.
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.
First let me apologise if this is in the wrong section. I could not decide if this was the best place for it or q a&a. As the title sais. If i flash twrp will it prevent me from receiving ota updates from Google. I have an HTC sensation XE and if i flash a custom recovery i know from past experience that it prevents ota updates. This nexus 7 however is my first "Google" device you could call it and as such i do not know that.
Can any one inform me on this issue. Also if it will an ota cause loss of root on this nexus like it did on my smartphone or will it stay? If it is gone i suppose it will simply be a matter of using chainfires root tool again when it gets updated for it.
Thanks in advance.
Sent from my Nexus 7 using Tapatalk 4
Q&A would be the best place for the post, but I can offer some insight. Any time you flash a custom rom you will forfeit the option of an ota update from your carrier or Google. This doesn't affect your play store apps as they will update when needed. The information that gets sent to your carrier identifies it as being non-official software so only a few custom ROMs that are well maintained will point the ota updates to its own servers. If you wish to receive official ota updates you should perform a nandroid backup of your stock rom to have a restore point for when a new release comes out. Aside from that, you would have to flash everything back to stock (probably stock recovery too) in order to be seen by the carrier as an eligible device.
Sent from my SGH-I727 using Tapatalk 2
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Ch3vr0n said:
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you install a custom recovery like twrp, you wouldn't be able to install an OTA from Google. You need stock recovery for OTAs.
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Ch3vr0n said:
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Click to expand...
Click to collapse
This has already been brought up many times e.g.
http://forum.xda-developers.com/showthread.php?t=2404833
I thought as much. I'll stick with stock recovery then until i need a custom recovery for some specific reason. For now root access is enough. And if an ota comes out and i lose recovery well I'll just wait for chainfire to update his root tool
i received the jss15j -> jsl36c update on my razorg with twrp recovery installed.
after the update stock recovery was back.
you can boot every recovery or kernel image without flashing it using fastboot:
fastboot boot nameofrecovery.img
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
HowardZ said:
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
Click to expand...
Click to collapse
Good to know.
Sent from my Nexus 7 using Tapatalk 4
I've taken OTAs using custom recoveries before on any number of devices. If you're not careful you can lose your recovery and have to reflash again, but sometimes you don't even lose that.
Well, there might be complications installing an OTA with custom recovery if it comes with a newer bootloader version/radio. Sometimes it works, but there were also reported problems.
Well i just had an ota update to jss15r and lost root as kinda expected. Now ill just have to find out if rerunning the root tool will be enough. Since it is already OEM unlocked i suppose i can simply modify that bat file and remove that line and run it again?
This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!
NishkarshChugh said:
This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!
Click to expand...
Click to collapse
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
pm_dsp_ra said:
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
Click to expand...
Click to collapse
Thank you! This is a working solution, got the sweet OTA on my phone!
Requesting the mods to close this thread. Thank you!
Same problem for me (but to go to 5.0.1 from 5.0)
I re-flashed stock kernel and radio, but still the same message.
Why this 4.3 message??
Edit : wait, I forgot to flash stock recovery
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?