Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7).
Full Error:
Code:
-- install from sdcard...
finding update package...
opening update package...
installing update...
assert failed: file_getprop (" /system/build.prop", "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2/vzw/23.15:user/ota-rel-keys,release-keys" || file_getprop(" /system/build.prop" , "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2.1/vzw/23.340:user/ota-rel-keys,release-keys"
E:Error in /sdcard/update.zip
(Status7)
Installation aborted.
doronster195 said:
I was rooted with z4, had apps frozen with titanium backup, have bootstrap, used dx overclocker (to undervoltage and to do a quick-boot with "android" logo rather than Droid Eye). I unrooted, unfroze, stock voltage/speed and turned off apply at boot, FORGOT to undo the quick-boot (but I thought it wouldnt matter since i'm unrooted).
Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7), pressed reboot phone and got the M, followed by the "android" logo that WILL NOT GO AWAY.
Phone won't load, what should I do? Need phone to work soon!
Click to expand...
Click to collapse
Ok it sounds like you are stuck in a bootloop.....you can restart your phone by doing a batt pull then when you go to turn it on hold the power button and home at the same time until you see the exclamation mark and droid guy ..this means you are in recovery mode ...then press the search button and a menu will appear ....use volume rockers to scroll and the camera or menu button to select ....go to data wipe/factory reset and select it ...then reboot and if it works your x will be back to how it came out of box if it doesn't then you will have to sbf ...find the sbf file for whatever system version you are on and flash it and that should work
Well, I did a restore, which worked. However, I'd still like to receive the OTA update. I downloaded the update.zip and want to install it myself. Why was i given this installation aborted error? Was it truly because of what I said above--quick boot option?
Edit: Tried booting into normal recovery (not bootstrap), while not rooted, and no rooting tasks have been done since the restore. Trying to "apply sdcard:update.zip" gives me an Error in /sdcard/update.zip (status 7) Installation Aborted
Edit2: Original Post updated with issue
I'm in the same boat...
I unfroze the bloat and unrooted my phone, it was stock with all bloat froze so nothing out of the ordinary to be concerned about.
Ran update.zip and got the same error as you. I'm not savvy enough to understand or figure out what's going wrong with any certainty. My best guess is that something in the build prop doesn't jive with the build prop the update.zip file checks against. I doubt rooting would have caused any change in my build prop and I never did anything to my phone other than root and freeze bloat so my build prop should be fine.
Problem Solved
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Can you share the sbf I am having the same issue and it is ticking me off. Thanks in advance
i posted the link for the sbf in the above post, i cannot post actual links, so you'll have to add to figure out the url for yourself. Just go to androidchat*org and go to their file database, its in there.
doronster195 said:
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Click to expand...
Click to collapse
Which sbf did you use? Do you have a link to that? PM if necessary...
Related
The update in conventional zip format, with root options is here!
P
Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Can I flash this manually WITHOUT being rooted?
I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.
Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....
tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago
PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...
Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)
JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.
might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post
Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.
I received 2 updates from google today installed the first one and all was well and the second one the update hung on the triangle and exclamation mark. I am not sure what to do. Any and all help is very much appreciated. I am rooted but on the stock last updated rom. I had flashed clockworkmode recovery. Since the first update of the two went well I just figured the second was a slam dunk. Boy was I wrong. How do I go about flashing back to clockworkmode recovery.?
Edit: Pulled battery and hit power button and the device booted back up to frf91 and not frd83d I am still rooted and cannot understand what just happened. I installed the first of two updates that were required and the second hung up and Now it shows me with system up to date. Do I have to flash to stock? I thought I was on stock as it was a manual install of an OTA The only thing i have done is root it with the one click root and flash clockworkmode recovery. No custom roms or anything of that nature. Am I not able to update to Gingerbread now when it comes out? Any help?/Please!!
I had the same thing happen to me about an hour ago. Any one have any info on this?
madmikethespoon said:
I had the same thing happen to me about an hour ago. Any one have any info on this?
Click to expand...
Click to collapse
Are you rooted and have flashed clockworkmode recovery? did the first update seem to install in an odd way but it finished and rebooted back up okay?
i had the same problem happen but it simply hung there with the exlamatiom mark, so i pressed Power + Volume up and this is what was displayed in the recovery:
(this was actually copied from my second retry with a manual install but i'm sure the error was mostly the same)
Finding Update Package...
Opening Update Package....
Verifying Update Package...
Installing Update Package...
Veryifying Current System...
assert failed: apply_patch_check("/system/framework/am.jar","e28...","8cf...")
Error in /sdcard/update.zip
(status 7)
Installation aborted
So i thin i'm running a stock Rom with stock Recovery but i'm not sure... i used this rom --> http://loadbalancing.modaco.com/dow.../update-nexusone-FRG83-stock-radio-signed.zip
(but the link seems to be dead) and installed it with Rom manager using the clockwork recovery later i used the Flash_image method to reinstall stock recovery but i have a feeling something isn't right... any help??
thx in advance
Hey all - Thank you in advance for your help.
So, I'm trying to install the OTA update manually. I had my device rooted and apks renamed, so i was getting a status 7 verification error. I was led to install an odexed stock rom to try and fix this, which i did via clockwork.
Now, i'm installing, and i get this verification error -
assert failed: apply_patch_check("/system/bin/debuggerd", "cd2295b78eff070929c4d7300a379cff6f429f2a", "bef703a3638dcd9c461304d99c0cb0ceb36f0573")
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
Does anyone know how to help with this please?
original link was from droid-life.
SBF and try again.
To be more specific, go here for SBF instructions:
http://www.mydroidworld.com/forums/...announces-froyo-system-sbf-rsdlite-4-8-a.html
Follow those steps to SBF to 2.3.15
After this do a factory reset (Settings -> Privacy), when you re-activate etc, go to Settings -> About Phone -> System Updates
Install the update and your done! This is definitely a painful way to do it, but after trying lots of different methods, this was surely the guaranteed way to get it done.
You guys are the very best. Thanks!
I now know how to potentially fix my phone no matter what i do. haha.
So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!
MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.
I just got OTA notification, should I install it? I'm rooted and have custom recovery.
If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.
4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.
By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.
Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it
That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app
@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.
I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?
@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.
Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app
mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?
inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped