Database Develop

[GUIDE][VIDEO] Droid MAXX/Ultra/Mini - Return to stock (RSD Lite OR manual flash)

NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear

Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app

Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app

Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!

allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app

allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app

YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.

will it work if i want to downgrade from 4.4 to 4.2 ?

No

YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!

Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app

First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?

kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.

OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...

kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot

I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.

Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader

akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.

One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?

TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?

[Q] VZW DEV 4.4 to 4.4.2 update failure opinion Question

Hi all!
Just a quick synopsis. I've held off for a while. I've read just about everything related as it's come across here over the past few weeks.
I've been perfectly happy with where I sat:
VZW Dev Ed, Rooted, TWRP, xPosed, Tehter & Gravity Box modules.
I'm not fond of ADB commands, etc. but can work my way through them.
Today, I decided to to take a quick stab at things (a little differently).
So, here's what I did:
1) Unfroze some bloat
2) Unistalled xposed Framework
3) USED Flashify to backup my TWRP
4) USED Flashify to install stock recovery
5) Downloaded OTA
6) Installed 4.4.2 update
7) It FAILED
So, I restored my TWRP recovery through Flashify; re-installed xPosed Framework; refroze the bloat and I'm back to where I was before.
The only thing that I really think might have caused the update to fail was the fact that I had AOSP Browser installed. (with its related installer)
So, that's my question here....opinions...would that cause the update to fail?
I've since tried to uninstall that browser with the related installer but it keeps getting hung and force closes when trying.
Opinions? (other than..."please, use ADB commands")
I'm assuming flashing my system ui might take care of that?
Thanks for ideas. I know I'll take the time to get it done "proper". Just haven't been pressed to do it yet.

Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.

hlaalu said:
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
Click to expand...
Click to collapse
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?

Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.

Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X

Dburgessme2 said:
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Click to expand...
Click to collapse
Hmm double check that it checks for subscription when tethering to make sure it changed the files back?
I'm a little rusty with fastboot, but it doesn't wipe your data unless you ask it to:
Code:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
[B]$ fastboot erase userdata[/B]
$ fastboot erase cache
$ fastboot oem lock
So I think if you just don't do the fastboot erase userdata command your data is safe. I'll wait for someone with more experience to confirm that.
But even if that's not the case, I'll still wait because we have to fastboot for root and recovery anyways, might as well just do everything in one go.

Schaweet said:
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7

Roland Stone said:
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Click to expand...
Click to collapse
Nope, I didn't extract it myself. I'll have to do that to make sure I've got the "real deal".
Thanks!
DB's Nexus 7

Dburgessme2 said:
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Click to expand...
Click to collapse
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X

Schaweet said:
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Just flash it through recovery I assume?
DB's Nexus 7

Yes
Flashing the system and recovery images is still the most fail safe method. It doesn't erase your settings or data.
Sent from my Dev Edition Moto X

Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app

awerner68 said:
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?

Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app

bigv5150 said:
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
So, fxz the 4.4.2 image for vzw 1060 through rsd lite? But remove "erase data" line from the xml file first. Then, TWRP recovery back (root). That about right?
I think the last thing I used rsd lite for was on old Droid X.
Any quick refresher would be appreciated.
Thanks!
DB's Moto X

Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app

bigv5150 said:
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
OK. And now I have to ask... What is HoM? (googled with no good results)
DB's Nexus 7

Dburgessme2 said:
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Click to expand...
Click to collapse
I downloaded the .ZIP file and flashed it with TWRP. Using TWRP to replace itself.

HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app

bigv5150 said:
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
And, this HoM should work with the Vzw 1060 Dev Ed?
DB's Moto X

5.0.1 on Rooted Nexus 6?

Searched and didn't find any good links. I'm decent at figuring out how to normally do things, but I can't find a way to install 5.0.1 on my rooted Nexus 6? Anyone know how? I have TWRP installed and the stock ROM. Just wanted to deactivate encryption.

Use fastboot. There's a thread here full of info for it. Pretty easy to do, just needs to be done in the right order
Sent from my Nexus 6 using Tapatalk
Edit: see this thread: http://forum.xda-developers.com/showthread.php?t=2969137

Is it even worth the hassle to update from 5.0? What's the benefit?

I haven't really noticed anything. Newer radios and some bug fixes I believe.
Sent from my Nexus 6 using Tapatalk

this worked for me from the thread posted above:
HixVAC said:
1. Extract image-shamu-lrx22c.zip
2. Move the system.img from the extracted file into the same directory as fastboot
3. Move radio-shamu-d4.0-9625-02.55.04.img to the same directory as fastboot
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
Then proceed to take care of root if you had/want root
Click to expand...
Click to collapse
in my case I did this after the last reboot:
fastboot reboot-recovery
then I flashed the latest SU from chainfire and all was well. kept all my settings. had to let it optimize all the apps. If you are unencrypted you stay that way.

I did a nandroid backup in TWRP to an OTG drive and then used wug's toolkit to restore to stock with the google factory 5.0.1 image and then re-flashed TWRP and restored data from my nandroid. Worked perfectly. Hope this helps. Good luck

Nexus 6----5.1 to 5.1.1

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.

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