getting errors when trying to take the january OTA security update
im using systemless root 2.66
twrp wont install the ota. anyone know how?
With TWRP, you can't take an OTA. You need to have stock Android recovery, unmodified /system, and unmodified boot.img (so no custom kernel). Otherwise the OTA will fail.
ugh i thought one of th ebenefit of systemless root was to be able to easily to ota updates. anyone have a flashable zip?
If you need twrp just boot from it in fastboot and retain stock recovery
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Chainfire wrote that if you use the SuperSU unroot function you should be able to apply the "real" OTA (i.e. not a sideload of a downloaded OTA, though maybe that might work too) and then reroot.
Alternatively, download the full image, unzip everything including the zip within the zip, copy the system.img, boot.img, and the TWRP for your device to your ADB folder. Copy SuperSU v2.67 to a folder on your phone. Then boot into bootloader, flash system, boot & TWRP, boot into TWRP recovery, and install SuperSU. Job done. No settings, data or apps lost. I know because I did it last night on my Nexus 6 & Nexus 10.
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
JimSmith94 said:
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Not_A_Dev said:
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
Click to expand...
Click to collapse
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
RMarkwald said:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
Click to expand...
Click to collapse
Thanks! I have already installed MMB29Q with fastboot, but next time I might try OTA with Chainfire's FlashFire: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Sent from my Nexus 6 using Tapatalk
Anyone have the ota from mmb29k?
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot flash system system.img
8. fastboot flash boot boot.img
9. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Not_A_Dev said:
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
13. fastboot reboot-bootloader
14. reflash superSu
15. reflash Xposed
Would this work?
Click to expand...
Click to collapse
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
This method (outlined above) works great. This is exactly the same setup I have (n6 + root + xposed) and is also precisely how I've been applying the monthly updates. Never experienced any issues.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
I'll give it a shot. I agree, and thanks for the suggestion.
Edit: Happy to report that the method in post #13 leads to a successful update of the most recent Shamu image. My device is now updated to MMB29Q, still runs TWRP, is rooted, and runs Xposed. 20 minutes tops for the whole project.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
Excellent may i knidly ask pls
last two steps:
what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Thanks tonnes...I believe my user data is preserved
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Most of the time they don't update bootloader and radio...
90% of the time, you can just fastboot flash only system. Basically the equivalent of dirty flashing your rom.
The above where you clear everything before flashing is basically the equivalent of wiping cache 3x... It wipes the partition when you flash. Think about it, if you flash userdata... you end up with all your data being deleted and a blank userdata partition. It doesn't copy the img on top of what is currently there, it replaces it. You can do extra steps if you want... But you really don't need to.
sunandoghosh said:
Excellent may i knidly ask pls
last two steps: what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Click to expand...
Click to collapse
^ This. One step that's also missing above is that once system.img and supersu have been flashed, there is hardly any space on /system to flash xposed (that's just how Google does things these days). So one would have to remove a few non-essential system apps (files, such as Google Books, Google Newsstand or the like) to make some room for xposed.
This thread is turning into a fastboot flash factory image thread rather than an ota thread. That's ok, it's a good thing ...I've been waiting for a thread like this and your posts inspired me to do my first flash to update security for my rooted phone (with xposed) since I initially set it up in December.
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Quote:
Originally Posted by Not_A_Dev
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
Click to expand...
Click to collapse
I roughly followed above steps, but had some comments/questions along the way:
I skipped the first and second erases as suggested above, but I kept the third erase (cache) because it is included in the xda n6 stock flashing tutorial here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I rebooted to android system between steps 10 and 11 because I wanted to make sure everything was ok. But that was a bad idea because:
A- it overwrote my twrp with stock recovery (even though I never flashed recovery)! So I had to fastboot boot twrp later.
B- it took extra time formatting stuff that was probably undone later.
And yet I still have to boot into android at some point in time to clear space before I flash the xposed zip in twrp. Maybe next time I should reboot to clear space between steps 11 and 12?
I was pleasantly surprised to see when completed flashing the xposed zip that I didn't have to reinstall the xposed apk and that the xposed modules were already enabled and configured exactly the way I left them. Good stuff.
Related
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse
Hey guys just want to play it safe and run it by you guys,
I have a N6 from Moto, Its on 5.1 and build LMY47M with rooted stock. Of course I want to hop on that steamy 5.1.1 so I wanna be sure I'm doing it right. I can't just flash the OTA download I believe. Could I flash the factory image? What can I do to prevent my stuff from being wiped?
dynamo147 said:
Hey guys just want to play it safe and run it by you guys,
I have a N6 from Moto, Its on 5.1 and build LMY47M with rooted stock. Of course I want to hop on that steamy 5.1.1 so I wanna be sure I'm doing it right. I can't just flash the OTA download I believe. Could I flash the factory image? What can I do to prevent my stuff from being wiped?
Click to expand...
Click to collapse
You could try flashing the system.img, the bootloader.img, recovery.img, boot.img, radio.img, and the cache.img without flashing the userdata.img (which wipes your device) but I would just suggest wiping data. I have read though that numerous people have been successful updating to the new build without wiping anything though.
patmw123 said:
You could try flashing the system.img, the bootloader.img, recovery.img, boot.img, radio.img, and the cache.img without flashing the userdata.img (which wipes your device) but I would just suggest wiping data. I have read though that numerous people have been successful updating to the new build without wiping anything though.
Click to expand...
Click to collapse
Wiping is NEVER required, and anybody who jumps crazy into wipes is wasting a LOT of time.
---------- Post added at 02:19 PM ---------- Previous post was at 02:00 PM ----------
dynamo147 said:
Hey guys just want to play it safe and run it by you guys,
I have a N6 from Moto, Its on 5.1 and build LMY47M with rooted stock. Of course I want to hop on that steamy 5.1.1 so I wanna be sure I'm doing it right. I can't just flash the OTA download I believe. Could I flash the factory image? What can I do to prevent my stuff from being wiped?
Click to expand...
Click to collapse
Download the factory full image.
Extract it to your disk somewhere.
One of the files that is extracted will be "image-shamu-lyz28e.zip". Extract FROM it... boot.img, recovery.img, system.img. The other files in there are potentially harmful.
Modify the file "flash-all.sh" to read as;
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-shamu-d4.01-9625-05.14+fsg-9625-02.93.img
fastboot reboot-bootloader
sleep 5
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
*** If you have a custom recovery installed that you want to maintain, you can omit the line that flashes boot.img
Then run the script flash-all.sh
Option 1: no force encrypt.
-When flash-all.sh has completed, it will still be in the fastboot/bootloader screen. If you HAVE a custom recovery installed, run "fastboot reboot-recovery" otherwise run "fastboot boot somecustomrecovery.img".
-Find in the custom recovery's menus, the option to SIDELOAD. Then run "adb sideload NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip" (yes, you will have to find that NO_FORCE_ENCRYPT file, which is somewhere on this forum that you can find as easily as I can find a link for you, so you can find it yourself). This will disable the force-encrypt flag.
IF you are satisfied here and want to start using your phone as a phone, you may perform a *normal reboot* at this point, otherwise....
Option 2: root
a) restart sideload mode, and run "adb sideload root.zip" followed by a normal reboot,
OR
b) "adb reboot bootloader" followed by "fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img" which will automatically trigger a normal reboot.
Appreciate the advice everyone!
Sent from my Nexus 6 using XDA Free mobile app
Oh man so to keep a TWRP recovery I need to omit the boot IMG and not the recovery image?
"If you have a custom recovery installed that you want to maintain, you can omit the line that flashes boot.img"
Also this is just me bit l not understanding, but what is the purpose of extracting the boot recovery and system images? I first was thinking those would be the only things I'm flashing but it looks likes the script flashes other stuff too that I did not extract, just curious
Sent from my Nexus 6 using XDA Free mobile app
doitright said:
Wiping is NEVER required, and anybody who jumps crazy into wipes is wasting a LOT of time.
Click to expand...
Click to collapse
I never said wiping was required. I was just making a suggestion as that is what I prefer to do. I clearly mentioned in my post that there were a good amount of people who updated without wiping. In no way did I ever say it was "required".
Thanks @doitright.
One quick question though. I could not find CF Autoroot for 5.1 for my Nexus 6 on chainfires site. It's just there till 5.0. So if i use the CF-Auto-Root-shamu-shamu-nexus6.img for 5.0, will it work? Or it might mess up my device?
u4atharva said:
Thanks @doitright.
One quick question though. I could not find CF Autoroot for 5.1 for my Nexus 6 on chainfires site. It's just there till 5.0. So if i use the CF-Auto-Root-shamu-shamu-nexus6.img for 5.0, will it work? Or it might mess up my device?
Click to expand...
Click to collapse
CF Auto Root should root a 5.1.1 rom, or in fastboot boot into TWRP and flash the latest superSU.zip.
Thanks gee2012.
So I'm just gonna go grab the factory image for 5.1, run the following commands:
"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-shamu-d4.01-9625-05.14+fsg-9625-02.93.img
fastboot reboot-bootloader
sleep 5
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
"
and then from TWRP, I'll flash the latest superSU.
Does that sound about right to you?
Thanks!
Did anyone update to 5.1.1 a 64GB N6?
Did your phone show 32GB after update?
Did you have to do hardware reset to see 64GB?
Thank you.
3f62011 said:
Did anyone update to 5.1.1 a 64GB N6?
Did your phone show 32GB after update?
Did you have to do hardware reset to see 64GB?
Thank you.
Click to expand...
Click to collapse
Common problem. Fastboot format userdata will fix without wiping data.
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
I'm not sure you can be rooted on lollipop to take updates. That could be the problem. Try unrooting.
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
doitright said:
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
tcrews said:
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
Click to expand...
Click to collapse
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
Hey doitright
So I can download the 5.1.1 (For Sprint, USC ONLY) (LMY47Z) even tho its saying US Only, and this was the one I received on the system update!!!
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. To "update" your system to the next version with factory images you would flash bootloader, restart the bootloader, flash the radio, restart the bootloader then flash boot.img and system.img and then reboot the phone. Re-root after.
All Done
Thanks to everyone, all done now, and special thanks to "tcrews" all sorted out now mate, I used fastboot to flash 5.1 (recovery, bootloader, boot and system) then did the same thing for the 5.1.1. I didn't lose any data or apps all working perfectly fine. I had to "Root" the device after, then flashed the "Xposed Firmware". :good: :good:
Yes, thanks as well! I had this issue when the OTA showed up on my Nexus 6 yesterday. Did what vampire_8_7 indicated above, and everything is working with no loss of data or apps. Thanks everyone!
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
You cannot flash the OTA. You can only flash stock. I also have no idea if you're doing something wrong. Probably though, that is usually the case.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
- Fastboot erase system
- Fastboot flash system system.img
- Fastboot flash boot boot.img if you have a custom kernel
- Fastboot flash recovery recovery.img if you have a custom recovery
- Fastboot erase cache and then fastboot flash cache cache.img.
Reboot and sideload the OTA and that should do it because you still have have modified system files on your phone.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
Hey mate
The idea is to go complete stock before you flash any OTA, and this can be achieved by just flashing the "System.img" and the "bootloader.img" file to you device.
DON'T FORGET TO TAKE A FULL BACKUP Note: This warning above is more precaution thing, and this method never wiped any data but its good to have the backup always.
You need to download the official stock image for your device, if you have that's fine keep reading through.
Factory Images
You have to extract the image and get the "system.img" and "bootloader.img"
Copy and Paste the "System.img" and "bootloader.img" files in the fastboot folder.
Open the cmd as admin navigate to the directory where the fastboot resides, then start typing these commands.
fastboot flash bootloader bootloader-XXXX.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Now you have to copy (Boot.img , bootloader.img, system.img and the radio.img) from the OTA image you have and paste it in the fastboot folder, then you will run the previous 2 commands in addition to these 2 commands below.
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
After performing this you should have 5.1.1 on your device without wiping any of your personal data or apps.
vampire_8_7 said:
...
Click to expand...
Click to collapse
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
mar1nasr said:
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
Click to expand...
Click to collapse
No Problems bro. Happy to hear that it worked. XDA is always the place where you can get help
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
mar1nasr said:
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
Click to expand...
Click to collapse
All official updates encrypt.
tcrews said:
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. .
Click to expand...
Click to collapse
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
ikirilenko said:
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
Click to expand...
Click to collapse
I always place these img`s in the /android/sdk/platform-tools/ folder, or extract them and right-click/shift copy to path. Then with cmd in fastboot erase system then flash system system.img and fastboot flash recovery recovery.img. Dowloadlink below in my signature Phantasmagoria and extract the downloaded file until you see the img`s.
gee2012 said:
Then with cmd in fastboot erase system then flash system system.img
Click to expand...
Click to collapse
Out of curiosity, why do you erase system first?
6.0.0 (MRA58N) for the Nexus 5 @ https://developers.google.com/android/nexus/images?hl=en
Reddit: https://www.reddit.com/r/Android/comments/3r95t2/android_60_november_security_update_images_are_out/
EDIT: Details at https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
So OTA usually comes out days after??
Sent from my Nexus 5 using XDA Free mobile app
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
sutobe said:
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
Click to expand...
Click to collapse
I've personally had no issues with the first 6.0 build on Windows 10 Pro x64, although only ever tried small files (<300MB)
Ok I made a Nandroid and installed 6.0 afterwards. File transfer worked for me now (don't know why it was so faulty before).....but there is still the thing with TWRP and TItanium Backup folders not showing up in Windows Explorer.
If I have a TWRP and / or Titanium Backup folder saved on my desktop's harddrive and want to move it to the phone's SD card the process fails while telling me that the folder already excists....but I can only see them via the phone's file explorer.
That means it is not impossible to move your backed up files to the SD card, it is just terribly awful. Always switch to MTP everytime you reconnect the phone with USB, then rename and move the backup-folders to the SD card and move their content to the proper backup folders (which you can't see in Windows) via a phone explorer.........who at Google had that great idea?
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
FreemanAMG said:
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
Click to expand...
Click to collapse
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
GROGG88 said:
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
Click to expand...
Click to collapse
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
FreemanAMG said:
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
Click to expand...
Click to collapse
I attached it in one of the last couple pages.
OTA failed for me. Using TWRP
fakitol said:
OTA failed for me. Using TWRP
Click to expand...
Click to collapse
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Because people are lazy and stupid at the same time often.
Sent from my Nexus 5 using Tapatalk
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
KC57 said:
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
Click to expand...
Click to collapse
Just flash the factory image but leave out the userdata.img file
EddyOS said:
Just flash the factory image but leave out the userdata.img file
Click to expand...
Click to collapse
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
KC57 said:
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
Click to expand...
Click to collapse
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Apologies for what is probably a dumb question but is there an easy repo of the contents of the OTA updates in flashable zip format?
EddyOS said:
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Click to expand...
Click to collapse
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
anyone a mirror for the 2,5 MB OTA file?
landwomble said:
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
Click to expand...
Click to collapse
Yes, but with official system files so you should be OK. Worst case scenario, backup data before doing anything in case you have to do a factory reset (e.g. if it shows 16GB on a 32GB device)
---------- Post added at 08:49 PM ---------- Previous post was at 08:49 PM ----------
hanschke said:
anyone a mirror for the 2,5 MB OTA file?
Click to expand...
Click to collapse
Don't need a mirror with the official Google server links - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
agel1 said:
can somebody tell me how to do it without losing data or root ?
Click to expand...
Click to collapse
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
NLBeev said:
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
Click to expand...
Click to collapse
sorry dont understand
Im already rooted and with twrp installed
agel1 said:
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
Click to expand...
Click to collapse
Download the factory image of the version you desire to end up on.
Unzip it, then unzip the folder contained in it, then in a terminal/cmd run:
Code:
fastboot flash bootloader bootloader-shamu-*.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-*.img
fastboot reboot-bootloader
cd shamu-*
fastboot flash boot boot.img
fastboot flash system system.img
Now, you said you wanted to retain root too, if that isn't the case, just run:
Code:
fastboot reboot
If you do still want root, download TWRP, cd to the Downloads directory, then either run:
Code:
fastboot boot twrp-3.1.0-0-shamu.img
if you want to keep the stock recovery
OR
Code:
fastboot flash recovery twrp-3.1.0-0-shamu.img
if you want to keep TWRP.
Now that you're on TWRP, just use file explorer to drag and drop the newest SuperSU zip (at the time of writing this, 2.79 is the latest stable, and SR3-2.79 is the latest beta) if you're on Windows or Linux, or use
Code:
adb push [I]nameofsupersu[/I].zip /sdcard/
.
Now reboot.
Have fun! It may take up to 15 minutes to boot (for dex-opting, and encrypting if you were decrypted and decided to re-encrypt), so don't interrupt that first boot process, just let it go. It will also need to "Optimize" all installed apps, so that could take a long while as well.
agel1 said:
sorry dont understand
Im already rooted and with twrp installed
Click to expand...
Click to collapse
Bad reading by me. Sorry.
Nevertheless you can upgrade to 7.1.1 by flashing the lite ROM of Danvdh.
There is a possibility that dirty flashing will cause reboot issue. Backup first and update your bootloader and radio before flashing the ROM.
There's a thread with flashable zips with latest bootloader/radio.
https://forum.xda-developers.com/showthread.php?p=59728002/
Latest TWRP: https://eu.dl.twrp.me/shamu
Why is everyone recommending the difficult ways???
Just download the OTA image from google and sideload it from your PC.
You don't even need TWRP, unloaded bootloader or root access to do it and you won't loose any data or settings.
More info and OTA images at https://developers.google.com/android/ota