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
Related
Hi everyone, I have a rooted with stock rom nexus7 with TWRP recovery, every time I want to update to 4.3, it fails, at first it comes to install and after saying 'Verifying Package', it goes to recovery first menu, Any suggestions??
by the way, I don't want to loose any of my data.
Gosh, there are so many threads on this. Did you search or read anything? The specific error is important, but you didn't say what it was. Depending on which error you have determines how to fix it. Was it an 'Error executing updater binary in zip...' or did you get a verification failure on a file such as 'debuggerd' or a system app that you may have replaced or frozen? I was able to fix my problems for a stock rom and kernel, rooted with TWRP after reading the threads in this forum. And your data won't be 'loose' nor will you lose data with this update, but you will lose root, which can be regained easily.
So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
bankmaggot said:
So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
Click to expand...
Click to collapse
Update: I was able to get to the recovery mode hitting down+power. I'm kind of lost at this point. Just give me 4.3 anything at this point.:crying:
I am in the same boat!! Any ideas, i have tried to do a sideload but i get an error installing //sideload.zip
checking for md5 file
skipping md5 check : no md5 file found
warning no file_contexts
file_getprop: failed to stat "/system/build.prop": No such file or directory
e:error executing updater binary in zip '//sideloader.zip'
download factory image and flash it via fastboot..for instructions -->Click Me!
anto.danny said:
download factory image and flash it via fastboot..for instructions -->Click Me!
Click to expand...
Click to collapse
Brilliant, that fixed. Thank you :good:
I just got the new OTA for Lolipop 5.0.1. I used ADB to pull the URL for the download and downloaded the attached ZIP using my browser. The URL pulled from ADB was an extremely long randomized string of characters that expired the moment my device was done updating. It seems the link is only active during the update process, so the only way to leave the link active longer is to battery pull or something in the middle of the update. I love you guys... but not that much
Keep in mind that this OTA was offered to me on 22.21.16, so I am assuming that you probably need to be on that update before you can use this OTA.
Let me know if you guys have any questions or run into any issues!
I'm rooted and running TWRP on my XT1064 with 22.21.16. Is there a way to just fastboot flash this update? I don't mind losing root. Thanks!
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Edit: I went ahead and flashed stock recovery and rebooted. After boot looping several times it rebooted into the system and gave me the message "Software update unsuccessful. There was a problem ....blah, blah, blah." But I still show an update available when I check.
I suspect it is because I am unlocked and rooted, even though I have stock recovery installed. Any thoughts on this guys? I am going to hold fast until I know for sure.
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
DoubleIk said:
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
Click to expand...
Click to collapse
Not sure if it makes a difference or not. I just put what the build was listed as when I got the update notification.
I put that there in case that was why some people couldn't update from 22.21.6 to 22.21.16
shishir95 said:
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
Click to expand...
Click to collapse
Nice theory, but I am now totally restored back to stock with stock recovery and unrooted. Still no luck with the update. Same thing happens.
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
thisisjason said:
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
Click to expand...
Click to collapse
From what I've seen, that is correct.
Any news XT1068 android 5.0.1 #India?
Moto G 2014 5.0.1
Hello good day friends will have some manual to perform the installation ?? and try it for apply update from ADB and I mark error in sideload package , installation aborted
How do I can install this update?
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.)
Hi everyone,
Got my 6P a few days ago. First thing I did was unlock the bootloader, flash the MTC20F image and get on with my day. Now I didn't flash the userdata file because well.. I just didn't.
Anyway, with every reboot now, I get the message about your device software can not be checked for corruption and it says to re lock my bootloader. Phone works fine though. I've left the BL unlocked.
Decided to venture into the world of Android N, enrolled my device into the beta program. OTA notification came. I hit restart and install. After 'Processing the update package', it rebooted into recovery and showed the green android guy with 'error' written underneath him.
Recovery log showed:
E: Failed to Map file
installation aborted
So I rebooted and I'm still in MM (obviously), and nothing happened except a huge waste of my time. This didn't happen on my Nexus 6 when I enrolled for Android N DP1 and it received and installed the OTA with an unlocked bootloader.
So what's up with this? Any ideas?
Is there a way I can get my hands on the NPD90G OTA and sideload through stock recovery without losing my data?
All replies will be appreciated.
Sent from my Nexus 6P
I have not tried yet but I would use Nexus Root Toolkit. Choose flash stock / unroot. In the workflow underneath where you choose the factory image there is a check box in Setttings for "No Wipe Mode". I would read up a bit and see if this grenades the install from 6 -> 7 but it is a good place to start.