LMY48I OTA Failed - Nexus 4 Q&A, Help & Troubleshooting

I got the LMY48I OTA update today but it's failed, after a reboot I've cleared the cache and checked for updates and it's no longer available. Will the update be re-pushed to my device eventually or am I stuck having to sideload it now?

It got offered again, however it's also failed again. Tried to follow the advice here https://productforums.google.com/forum/#!topic/nexus/CYhvUSjWfw8;context-place=forum/nexus but bumped the power button and it rebooted. Will have to try again. Do I need to be clearing the cache each time to get the offer?

Managed to get the output from the recovery console on the third attempt:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/bin/install-recovery.sh" has unex
pected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to
keep it in this state and file a bug repo
rt!

Are you on 100% Stock firmware? You must not have root, custom recovery or any system modifications for OTA's to work.

Can you sideload the OTA? I had to root my mother Nexus 4 to install a new kernal so it wouldn't go in to the deep sleep of death.

I had the same problem, with "unexpected content" found in another file. Android 5.1.1 stock, no root. This is how I solved it:
1) Boot into recovery mode and clear cache
2) Reboot into android. Go to "Settings -> Apps", tap on the three points in the upper right corner and select "Reset app preferences"
3) Update all apps from the play store
4) Go to "Settings -> Storage" and tap on "Cached data". Clear cached data.
5)After that, I ran the OTA update and it succeeded.
Good luck with that!

n0b0dy666 said:
Are you on 100% Stock firmware? You must not have root, custom recovery or any system modifications for OTA's to work.
Click to expand...
Click to collapse
The only modified file I have is /system/etc/hosts but that has persisted through the last 1/2 dozen OTA updates without causing issues.

apopberz said:
The only modified file I have is /system/etc/hosts but that has persisted through the last 1/2 dozen OTA updates without causing issues.
Click to expand...
Click to collapse
With 5.+ they changed the way that the file check occurs, which is why you have not had issues previously. *Any* modification to the system partition (1 byte out of place), and the OTA will fail. You can flash the stock system.img for your current build, and should then be able to grab and execute the OTA the "normal" way and it will work. It is a bit of a pain in the butt.

ariesgodofwar said:
With 5.+ they changed the way that the file check occurs, which is why you have not had issues previously. *Any* modification to the system partition (1 byte out of place), and the OTA will fail. You can flash the stock system.img for your current build, and should then be able to grab and execute the OTA the "normal" way and it will work. It is a bit of a pain in the butt.
Click to expand...
Click to collapse
Will I loose data if I do this? Not bothered about keeping root at the end of it all - I installed Root for some extra features in Tasker and never actually used them really.
Otherwise what's the easiest way of hiding the system update icon? Replacing it with a Nexus 5 in *name Nexus 5 release date*

generationgav said:
Will I loose data if I do this? Not bothered about keeping root at the end of it all - I installed Root for some extra features in Tasker and never actually used them really.
Otherwise what's the easiest way of hiding the system update icon? Replacing it with a Nexus 5 in *name Nexus 5 release date*
Click to expand...
Click to collapse
No, you will not lose your data by flashing ONLY the system.img file, but will lose root (which you can easily just re-root AFTER you install the OTA.)

Related

Can I do OTA if I rooter my Nexus?

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

[Q] /system/etc/gps.conf issue when trying to update to KitKat

I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.
jaredmorgs said:
I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.
Click to expand...
Click to collapse
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.
racerklm said:
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.
Click to expand...
Click to collapse
I decided to install scrosler's Stock 4.4 ROM, which now has the update applied. It's working great.
Thanks for the advice either way. Would love to know why gps.conf was blocking the update.

Need help with update for nexus 4

Hello
I am using a nexus 4 and today the kitkat update showed up on was downloaded and their was a notification... I clicked that and it took me to the screen which says that you will update to four point four etc etc.. I clicked reboot and install then it rebooted and said updating system then suddenly it showed me an error there was an Android lying down with a red triangle above it I shut down the phone and rebooted then the phone started up and everything was normal there was no update but my phone works on four point three..
. I use a rooted phone could this be Beal cause of root help
I yes that notification doesn't appear now
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
eksasol said:
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
Click to expand...
Click to collapse
But I did not tamper with system files so I don't think there is a possibility of that.....
The update notification is not sowing up I went to about phone and clicked system updates but now it shows your phone is up to date

Moto G 4G/LTE 4.4.4 OTA - 21.1.46.en.EU (XT1039)

Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
Updates from Android 4.4.3 (21.1.31.peregrine_reteu.reteuall.en.EU) to Android 4.4.4 (21.1.46.peregrine_reteu.reteuall.en.EU)
Update brings:
Android 4.4.4 Kitkat
SD Card Fixes
Requirements:
21.1.31.en.EU peregrine (Moto G 4G) --> WILL NOT WORK IF en.US, en.BR, OR en.UK
Locked bootloader ONLY:
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install.
2. If it says latest (and you are on 4.4.3), Download the OTA here and place in root internal SD directory.
3. Repeat Step 1
4. Done
Unlocked bootloader + Root/Recovery ONLY
1. Follow this thread and flash the latest 4.4.4
OR MANUALLY
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install. If you have recovery error (stock recovery) or nothing happens in recovery and it keeps restarting (custom recovery) then go to Step 2.
2. You may have altered your system partition (e.g. modified hosts file, uninstalled system apps). If it's reversible (try disabling Xposed, restoring hosts file) you can try and undo it and attempt to install again. If this does not work, you will need restore /system partition to stock by flashing just the system.img chunks through fastboot (from stock firmware).
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
NOTE: If you feel uncomfortable to do this and are happy to stay with 4.4.3, then fastboot erase cache to stop phone restarting and trying to update.
3. Once flash is complete, reboot and go back to Step 1 to reinstall OTA.
4. Still no luck?? Download the OTA here and place in root internal SD directory. If you have stock recovery go to Settings --> About Phone --> System Updates to Download & Install. Otherwise go to CWM/TWRP and Install the OTA.
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
jkoetsier said:
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
Click to expand...
Click to collapse
Can't say I've had any problem with Android 4.4.3 or 4.4.4 with SD card. So it hasn't affected me that way. Did you try reinserting and rebooting?
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Got it installed thanks to your guide.
Had to root again after the update, and reinstall busybox.
Thanks again !
Seems that there are even different versions of soft for Europe, I have vs 21.1.31.pregrine_retgb.retgball.en.GB.retgb (XT1039) and my phone does not provide any update yet. Anyone here with this system version?
gartzen said:
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Click to expand...
Click to collapse
Appears to be a mismatch. I would not advise to install this OTA if you do not have en.EU even though you have the same model number....
I believe there are many variations sold around the world including US (XT1045), BRAZIL (XT1040), EUROPE (XT1039), and now UK (XT1039). Here in Australia we use en.EU because of the same LTE bands.
I guess I'll have to wait my OTA to tell me there's an update, or a CM version for our phone!
Thanks anyway
Work in XT1045?
Luckily I fixed the sd card issue by formatting it...
Incredible, all 3g 444 versions are out, the 444 eu lte is out, the only missing yet is the 444 eu 3g
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
reef2009 said:
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
Click to expand...
Click to collapse
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
vpnair said:
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
Click to expand...
Click to collapse
I did clear cache and dalvic, So I don't know what's the problem.
Besides that 4.4.4 fixes all fc's.
Since last year I don't have the time to figure out what's wrong but it works and that's the thing
AlbertoJOG said:
Work in XT1045?
Click to expand...
Click to collapse
I don't think it does. I have one too but we have the US version and they have the EU. Guess we just gotta wait.

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

Categories

Resources