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.
Related
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!
Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:
random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong
I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img
opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!
"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.
what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way
Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4
how is this method different from if i just removed the -w wipe parameter?
maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'
hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.
Hi Nexus 6 experts -
My Nexus 6 arrived today, so of course the first thing I did was follow this thread to unlock the boot loader, gain root, and TWRP:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Now I'm reading about how this breaks OTA updates, and after 30 minutes of looking for the right answer across the forums, I'm in need of some more accurate advice.
1. Is this the right location for downloading factory images?
https://developers.google.com/android/nexus/images
Part of my confusion stems from the fact that my build number for 5.0 is currently LNX07M, and the one listed for 5.0 is LRX21O. Does this matter at all? Could I flash the files from 5.0.1 (LRX22C) without any issue?
2. In order to flash 5.0.1, is this the right procedure to follow?
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
I'm looking for how to flash the right images in the right sequence with fastboot, as I'd rather not use any toolkits. The aforementioned post flashes the radio image, then the system image. Is anything else missing there?
3. I'm assuming I need to re-flash root again after this point - is the version listed in the beginners guide still applicable?
Since I've had the phone for all of 2 hours I'm trying my best not to brick it. Any insight would be appreciated, thanks!
EDIT: Download the factory images from the google link above and extract everything. The first extraction renders the radio and bootloader images, along with a zip file. Extract the zip file and you'll find the boot, cache, recovery, and system images. Using fastboot is easy:
fastboot flash <type> <filename>
example:
fastboot flash system system.img
As far as I can tell, <type> is specific to every file. Very easy, only takes a few minutes, and you only need to flash what you need.
Yes Lollipop requires 100% stock for OTA updates now. But OTA is overrated
1. Yes indeed. thats the right place. Wasn't LNX07M the pre-release developer preview?
2. The image contains a flash-all script for windows and linux, but this will wipe data (unless you remove the -w i believe) but I prefer to flash individually.
flashing Radio isnt essential but you will probably want to try it at least. You also want to flash the system and boot images (boot image is the kernel). Then flash SuperSU from recovery. I know OTA's have a script that replace your recovery on first boot if you dont immediately root. I havent flashed a factory image for a whiole so not sure if these have them too, so just a word of caution there.
3. I tend to go for the latest from the beta thread personally, but there is no hard going for older versions except that some things might not gain root properly due to the changes with SElinux etc
Hey thanks rootSU - this is exactly what I was looking for! Once I run through that process I'll add the details to my original post.
So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?
scotbotmosh said:
So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?
Click to expand...
Click to collapse
I only flashed a few of the files, like boot, system and radio. Recovery will remove twrp so you don't want that. Order doesn't seem to matter.
im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...
cobyman7035 said:
im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...
Click to expand...
Click to collapse
Yeah you shouldn't need to revert/unroot and use the OTA. Just flash what you need from the factory image. System is the only major one to flash, boot would be the kernel, so use whatever you need for the decrypted version.
I'm assuming userdata overwrites /data which would wipe your files and apps.
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
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.