Database Develop

Unable to install OTA LRX21O

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

[Q] Error while installing 5.0.1 update

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.

[Q] How to flash OTA updates once rooted/custom recovery?

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.

[Q] 5.1.1. OTA Update Error

My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.

I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?

Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.

Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.

^same here...rooted and T-Mobile.

skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896

Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?

neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.

I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.

robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.

Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.

bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.

I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.

Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time

Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.

Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.

The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.

peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.

November Security Updates are out!

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