Database Users

The Unofficial Thread of Official OTA Updates

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since we got update threads scattered everywhere, I figured I'd organized things into one thread, as well as give away some new updates.
Retail EU:
81.5.31006-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.32002-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.4002-91.2.26001.Retail.en.EU 4.0.4-4.1.2
Retail GB:
81.5.31002-81.5.39001.Retail.en.GB 4.0.4-4.0.4
81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2
Orange GB:
81.5.31002-91.2.26001.Orange.en.GB 4.0.4-4.1.2
O2 DE:
81.5.32002-81.5.39002.O2.en.DE 4.0.4-4.0.4
81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2
Vodafone FR:
81.5.31002-81.5.39001.Vodafone.en.FR 4.0.4-4.0.4
81.5.39001-91.2.26001.Vodafone.en.FR 4.0.4-4.1.2
Brasil BR:
871.110.12008-871.110.12012.Brasil.en.BR 4.0.4-4.0.4
871.110.12012-871.111.20003.Brasil.en.BR 4.0.4-4.0.4
871.111.20003-982.50.20.Brasil.en.BR 4.0.4-4.1.2
AmericaMovil MX:
871.110.13009-982.50.25004.AmericaMovil.en.MX 4.0.4-4.1.2
If you have an OTA update.zip please PM it to me or contact me on google talk ([email protected]) and I will quick add it to this thread, with safe hosting, credits to The Firmware Team's Pzyduck for providing safe-haven for these types of files.
Instructions for pulling an OTA update.zip:
Do NOT install the update! Do these first!
Be rooted. We got plenty of methods. Motofail2go for ICS, and my RAZRiRoot.zip for turl1's Clockworkmod.
Download the Root Explorer app, or the ES File Manager app. (Instructions are for Root Explorer.)
Open Root Explorer and go to the ~/cache/ directory, which resides on the root directory of the phone '~/'
Hit the 'Mount R/W' in the corner, if successful will then say 'Mount R/O'
Copy the update file .zip from the ~/cache/ to your sdcard, external to be safe. External is in ~/mnt/external1/ and Internal is ~/sdcard/.
Copy over the update file .zip from the sdcard(s) you chose to your computer and upload it.
You will want to use Voodoo's OTA Rootkeeper before updating if you have a locked bootloader, you can find my thread on a RAZR i compatible version here.
Send me or post a link here to the update and exactly what System Version you were on, and where the update takes you to.
The community will thank you for your help!
Enjoy. Remember to do your part to the community and contribute all updates!

Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?

Vistaus said:
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Click to expand...
Click to collapse
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.

Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890

HSD-Pilot said:
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
Click to expand...
Click to collapse
Thanks! Uploaded to server, renamed, and added to the OP.

mattlgroff said:
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Click to expand...
Click to collapse
mattlgroff, im in 81.5.31006.Retail.en.EU - 4.0.4. and in software update i get notification of an ota. i down loaded that file when ask if i want to install it i select yes. but when in recovery it always fails. why, isnt that the official? because after that i tried flashing it in recovery but it fails too.
before alll this i was already on 81.5.40002.Retail.en.EU - 4.0.4. coming from 81.5.31006.Retail.en.EU. but i wanted to downgrade back to 81.5.31006.Retail.en.EU. and my phone died. thanks to hsd pilot my phone came back to life he sended me a file http://forum.xda-developers.com/attachment.php?attachmentid=1528201&d=1354399653. but now im stuck in what i told you at the begining. why?? what can i do to go back to 81.5.40002.Retail.en.EU. i know this is not the thread sorry but i was watching your new otas. and i cant install the one for my version.

Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890

HSD-Pilot said:
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
Click to expand...
Click to collapse
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.

mattlgroff said:
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.[/QUOTE
thank you guys!!! that was the problem and another one was that i erase alot of apk.s that i dont use so at time of flashing i saw it said something about an apk. missing so i fastbooted again and flash boot.img and here i am with the 40002.rt.eu. and now waiting for jellybean
Click to expand...
Click to collapse

If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.

joel_sinbad said:
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
Click to expand...
Click to collapse
Yes you can.

I have version 871.110.12008.XT890.Brasil.en.BR installed from sbf.droid-developers
My Razr i bootloader is unlooked and rooted. When i try to install the update with the android button (in about system) i recive error message after reboot. How can i install this update manually with fastboot console?
Thanks!

First, use an Root Explorer and copy your downloaded Update Zip out of the Cache Folder and leak it
Edit : Ok, it's in the OP already. Sorry, it's 1am in Germany :sly:
Your RazR i is rooted, how did you root it? If you used the Unlocked Root (insecure Kernel), than grap the boot signed out of the sbf you flashed and use fastboot to install it
fastboot flash boot boot_signed.
After that it should work. If not, you maybe deleted some System Apps. If that's the case, flash the system_signed.
Sent from my XT890

Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating

josmel91 said:
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
Click to expand...
Click to collapse
I have no clue. I'd ask in the Q&A section if you want an answer quickly

Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.

Semseddin said:
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Click to expand...
Click to collapse
After getting a DMCA Takedown Request from posting those before from the MB886 I'm afraid I can't help you there.

The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.

jenova941 said:
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
Click to expand...
Click to collapse
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works

mattlgroff said:
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
Click to expand...
Click to collapse
Thanks, downloading. Do I just flash it using CWM, RSD Lite or something else?

Unable to install 4.2.2 upodate

I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

Here is the error I am getting.
sent from my nexus 4 using google mind control

The OTA installer checks every single file it intends to patch before anything happens.
If a single file that is checked has been changed by even one byte, not one patch operation will occur.
The message you are getting means you did something to change or remove that file compared to how it was in the stock ROM.
Note that the installer halts on the first error of this type; there could be zero or many more of these errors awaiting you.
In short, OTAs are not meant for patching random non-Stock ROMs.

I installed beats from play store. Gutted. Just backing up all my data and gonna factory reset and try again
sent from my nexus 4 using google mind control

R: Unable to install 4.2.2 upodate
I had error 7 with TWRP recovery. Then I installed clockworkmod and it worked.
Nexus 7 3G - Tapatalk

Androll79 said:
I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phoneView attachment 1728828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem.but i flash stock recovery with WugFresh toolkit and wait until OTA update notification.and you will get your android running 4.2.2 version.

Odp: Unable to install 4.2.2 upodate
Guys, guys, guys. You need STOCK recovery for official updates.
Sent from my BMW E34 using XDA App

I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

There is modified OTA floating somewhere that skips check, worked for me since it reported that GoogleCalendar.apk was different than it should be....

Folks,
You need to stare at the actual error message.
If the failed assert() is complaining about a file (e.g. see the OP's 2nd image attachment) then THAT FILE IS THE PROBLEM. It means that it was altered or removed by a root-privileged operator from the way it was in the stock ROM.
If the failed assert is complaining about a build number, then it is possible that using a different recovery will allow the OTA to succeed.
So you have a couple of choices:
A) Go and find the stock version of the file and put it back into your ROM (with the correct file ownership and permission modes) and repeat the OTA install. Seems like a dumb idea though, as the installer stops on the first error encountered - you will need to keep repeating this process until you have restored all changed files. Could be only one file, could be a few, could be many. Note also that this applies to the boot image, too. Got a custom kernel? You'll need to put the stock boot image back in place, too.
B) Back up your apps using TiB or Carbon. While you are at it, take a nandroid backup too. Install the Factory 4.2.2 ROM, reinstall your fave custom recovery, and root the factory ROM. Boot it up, enter your Google creds, restore your apps & data (Carbon or TiB). Yep, you are gonna have to redo your homescreens. Big deal; that's something you would do anyway when hopping between ROMs (unless you have this covered already by using a non-stock Home/Launcher app which has its' own backup/restore capability)
C) Just wait a little bit - your ROM Dev will probably release a version based on 4.2.2. At that time you can do some stupid thing like overflashing the replacement ROM without wiping.
Unless you know exactly what you are doing, running a modified OTA with *all checks* suppressed is a seriously brain-dead idea. (Removing only the build version check should allow alternate recovery use - but for goodness sake, the OTA nukes the recovery anyway, so what's the big deal about putting the 4.2.1 stock recovery back in place ahead of the OTA?)
Look, running the Stock OTA is going to remove your recovery and very likely disable your root. You are going to need to put your recovery back and re-root anyway. Doing things the right way is barely more effort than what you are going to need to do the crufty way.
good luck

GPE 5.1 Android L-MR1 notification

Just got a notification saying that the 5.1 GPE update is available for download. I don't even have a gpe phone just the loserskater gpe rom....I'm downloading the update right now if someone wants me to upload it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One_M8 using XDA Free mobile app

Can you pull the OTA file and upload it?

digitalhigh said:
Can you pull the OTA file and upload it?
Click to expand...
Click to collapse
I have it uploaded to my site already.
I need someone who isn't rooted and hasn't touched the system on 5.1 to PM me please so you can help me pull the system partition so I can create a 5.1 RUU. You must have time to be able to pull the system, root the device and then pull the system again and upload both images.
Thanks

Update error
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela

ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
As far as I understand you will need a rooted 5.1 version... Or you can flash the unrooted ruu and then update...

Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.

Destroyer706 said:
Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.
Click to expand...
Click to collapse
Mmm.. not so cool.. but thanks for the reply anyways.
Maybe to much of an effort to unroot (any link on how to do that for this device?).
Might wait for the RUU rooted/unrooted from graffixnyc as that's much more simple to apply.
Ratatella

ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.

benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
PS: Found rooted and non-rooted 5.1 RUU for M8 here:
http://www.graffixnyc.com/m8.php
Ratatella

ratatella said:
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
Click to expand...
Click to collapse
Funnily enough, it's in the GPe OTA thread

boot issue
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.

So if I'm on a custom ROM this update is just the stock GPE ROM? So in order to maintain the ROM I'm using I need to wait for a rom release and ignore this?

I just got this OTA update as well.
I converted my phone to UNrooted 5.1 RUU last week.
I run the update, it reboots goes through the install with no errors, restarts, goes through the "Android is upgrading... and optimizing apps".
But once it's finished, the update notification still popsup as if it didn't upgrade... ran it a second time, and for whatever reason this time it "took". Checked my phone and it said it's up to date.
Very odd.

Is it needed?
Hi everyone,
A bit of a newbie, so not quite sure if this is obvious to everyone else, but here goes...
I recently installed the rooted version of [RUU] M8 Google Edition Conversion. 5.1 LMY470.H4 provided by @graffixnyc as per this thread.
Everything worked fine, and I now have a rooted HTC One M8 running stock GPE 5.1. All fine & dandy, thankyou @graffixnyc...
Today (July 8, 2015) I am told that my phone has downloaded the OTA Android L-MR1 modification. Being in New Zealand it seems to have finally arrived here two months after everyone else received it.
My question is this - do I need to install the upgrade, or have I already got it thanks to the ROM I have already installed?
Another question is - if I do need to install it, are there any special steps and/or procedures I need to take in order to install it without doing something bad (& irrevocable!) to my phone?
Hope this doesn't sound newbie-ish... I am quite prepared to RTFM if someone can point me in the direction of appropriate answers to my questions,
Cheers,
Attobrute

adamparsons said:
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.
Click to expand...
Click to collapse
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.

adamparsons said:
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.
Click to expand...
Click to collapse
I was able to recover from my issue .
For anybody else that runs into the same issue, this is what I did:
1) re-flashed twrp custom recovery
2) made data backup
3) created by own custom (system-only) ruu using graffix's gpe rooted ruu as a base. I basically deleted all img files from the zip file except for the system image.
4) I flashed the custom (system-only) ruu via fastboot
5) let the system boot
6) skipped all the account signup and settings stuff
7) rebooted the system one more time just to make sure things are still good ( I don't think this is necessary but I did it and things seemed to work for me )
8) rebooted into recovery
9) restored data backup that I made in step 2
10) let android do it's thing ( optimize and stuff )
And that's it. Things seem to be back to the way they were before applying the update. Even the android update notification, which caused me all this pain to begin with, is back.
The only thing I have left to do I guess is figure out how to get rid of the notification.
BTW, If I'm not mistaken, this update is not needed. I think it's already included in the 5.1 GPE room graffix supplies.

Hello,
I installed Android 5.1 GPE with the "Rooted Flashable Stock Rom Build"(zip file install wit twrp) from graffixnyc a month ago. Is there an Update package(ruu?/ota?) that I can use to apply the L-MR1 upgrade without losing my data?
Thanks

Got this update this week too. In fact are two updates, one is 24mb and other is 20mb. Still stays on Android 5.1 instead 5.1.1, but build number changed two times, ending .h5 and .h6. Don't know what changed, maybe just bugfixes.

Can someone upload the ota packages?

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??

5.1.1 root tips / tutorial?

Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!

m123456789 said:
Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
Click to expand...
Click to collapse
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).

levone1 said:
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
Click to expand...
Click to collapse
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035

m123456789 said:
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
Click to expand...
Click to collapse
I haven't yet tried .216. Its new as of a couple of days ago. I also haven't yet tried PRFs. I've read a few threads that seem to indicate occasional problems with them. Since I have unlocked bl, I've been able to root the easy way, so I'm not sure what options or limitations there are with that rooting method. From my experience, I would recommend RockZ1 ROM, (.368). It has anything you would want included, and may well update to the new fw anytime soon...

Don't unlock the bootloader many functions will be lost if you are trying to keep the stock rom.
Sent from my C6902 using XDA Premium 4 mobile app

The device is now in Boot Loop after trying to go from the 5.1.1 to 4.4.4 using Sony Mobily Flasher and then trying to install 14.4.A.0.157 ...
What did I do wrong, what can i do now?
Thanks for any help

I just turned phone off, loaded 14.4.A.0.157 with Sony Mobile Flasher, plugged in with volume down key. Then it was flashing and finished. Then unplugged and started.
And now it keeps restarting at startup (when the "waves" appear). That's a bootloop right? I turned it off with the small red button now.
I tried flashing again with same method. And it is still bootlooping after it......
Any expert could help? Or is the phone broken forever now

Did you wipe data / cache?

Steffe89 said:
Did you wipe data / cache?
Click to expand...
Click to collapse
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.imgur.com/RCJNhRO.jpg

Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app

DetmL said:
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PC Companion does not recognize the phone. When i plug it in, it says searching, but then... "no phone connected"
But in windows i see it connected as a drive which i can not use

m123456789 said:
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
http://i.imgur.com/RCJNhRO.jpg
Click to expand...
Click to collapse
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216

levone1 said:
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
Click to expand...
Click to collapse
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1

I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?

m123456789 said:
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
Click to expand...
Click to collapse
The msg about unknown sources, etc. comes after the flash bc now your phone is stock, so by default they're not checked. It wouldn't have flashed if they weren't checked in the first place. You'll probably hit some bumps, but don't give up. There's almost always a fix...

On rooted 4.4.4 with Superuser installed. Then trying to load the prerooted 5.1.1 zip.
So rebooted with volume down and installed the prerooted zip file from SD. With CWRM
Everything seems to work, but at the end of flashing i saw some message like:
"set_perm some changes failed"
Then after restart all apps get optimized and i am on 5.1.1.
However, i think i lost root, also no SuperUser installed? And the Superuser was included in the zip prerooted file.

Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance

m123456789 said:
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
Click to expand...
Click to collapse
It's not worth it to update, believe me

m123456789 said:
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
Click to expand...
Click to collapse
Open recovery > select 'install' > choose file. You'll get a long reboot and the whole 'optimizing' thing again.

Yes, after installing xposedv75, it rebooted and loaded addiotional ~+100 apps But it seems to work.
What program would you guys recommend in terms of saving data, restricting internet access of apps (and maybe even ads). And some other for spoofing/restricting requested usage access of certain apps?
(I tried Xprivacy, but it is pretty advanced. It did not seem to block inapp ads or internet access, even when you denied it. Also it only lists apps which are newly installed, not preinstalled ones.
Maybe it is easy but I just didn't understand it yet )