Related
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.
i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.
forgot to attach the screenshots
GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app
If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.
With the Verizon Kit Kat roll out, and now that there is an ATT Kit Kat soak starting soon, so undoubtedly they and the other carriers will start getting it, I wanted to summarize some of the information found in these two main threads ->
http://forum.xda-developers.com/showthread.php?t=2534060
http://forum.xda-developers.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)
This might make it easier for those Verizon users who haven't received Kit Kat yet, or those of you on other carriers as Kit Kat starts rolling out. These are the most common issues and questions I've seen asked....
You will lose root when you take the KitKat OTA.
There is no way to retain root while upgrading to Kit Kat Updated Root for KitKat released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
If your phone has a LOCKED BootLoader, you will not be able to root KitKit at this time. UPDATED Root for KitKat 4.4 has been released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Note: If you have an unlocked boot loader, or developer edition, root is obtainable. (see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP )
You must be unrooted, reverse the impacts of PwnMyMoto and/or RockMyMoto or you will be stuck in a boot loop when the OTA. (how to fix posted later)
Once on Kit Kat, you can't flash back to past firmware, unless you have an unlocked boot loader. (see the updates section below, and the SlapMyMoto threads)
You must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
there are several options to get back to "stock" without loosing your data. (posted later in this thread), some are more techincal, some are more noob friendly.
If you want to thether "for free", FoxFi doesn't work. Any past hacks that require root wont work, unless your phone has been Rooted update:see the EDITS & UPDATES section at the bottom of this post)
Kit Kat brings some style and status bar changes to be aware of. Like everything being WHITE, no more blue, no data traffic arrows, etc For more info please see -> http://www.androidpolice.com/2013/1...nd-only-shows-connectivity-in-quick-settings/
Note: If you have flashed your phone with another carrier's ROM, or have tried the previously leaked T-Mobile or ATT pre-release roms, these steps may not work!!
Motorola Fastboot, mFastboot, and android SDK fastboot... what's the difference?
When you install the ADB and Platform Tools from the AndroidSDK, you will also get a fastboot.exe. This standard fastboot.exe is compatible with most, if not all, Android devices to flash parts or partitions with. Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot.
Having two fastboot.exe files, one that comes with the AndroidSDK install, and one from Moto, can get confusing, and presents a challenge. You can't put the Moto one into your PlatoformTools folder with the AndroidSDK one due to the same name. If you overwrite the AndroidSDK one with the Moto one (keeping the same file name of fastboot.exe) it could be overwritten with a future update of the Android SDK. Because of this, some have renamed the Moto fasboot.exe to mfastboot.exe. So if when you see reference to mfastboot.exe, they are talking about the Moto tweaked version of fastboot.exe that has been renamed so as to not overwrite the one included with AndroidSDK. Simple, right??
So, where can you get the Moto Fastboot.exe, or mfastboot.exe?
You can grab the Moto Fastboot.EXE from -> https://www.dropbox.com/s/kyqjzpjgamrepf1/fastboot.exe (Thanks to Cell Zealot) Note: you will want to rename this one before putting in your PlatformTools folder so future updates to the Android SDK doesn't overwrite it. Alternate download -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 Another way to get it is to request the GSM Developer Edition recovery image directly from Motorola (HERE) as they recently added the updated fastboot.exe along with minimal ADB support.
I take no responsibility for any issues, errors, problems, etc. you encounter while attempting to unroot, get back to stock, etc or using these instructions. Please backup your data BEFORE you attempt anything below!!
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8 users have had issues.
You will need...
To know what version ROM is on your phone before you touch anything. On Phone... App Drawer -> Settings -> About... Make note of the build number.
Motorola Device Drivers -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Adb Drivers, Android Platform Tools from the Android SDK, some good tutorials -> http://forum.xda-developers.com/showthread.php?t=1830108 or see -> http://www.xda-developers.com/android/lightweight-adb-and-fastboot-installer/
Updated Moto fastboot if you will be doing things manually See above!
MicroUSB Cable.
NOTE: the GSM Moto X Developer Edition recovery image available by request from Motorola (HERE) has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need for the Adb Drivers and Android Platform Tools from the Android SDK.
NOTE2: The T-Mobile XT1053 Retail and Moto Maker versions use the same Rom/Recovery Image as the GSM Developer Edition X. The Verizon XT1060 Retail and MotoMaker versions use the same Rom/Recovery Images as the Verizon Developer Edition phones. The the recovery images are available by request directly from Motorola (HERE). Unlockibility of the bootloader is NOT part of the ROM or Recovery Images that we can flash, so flashing the Developer Edition ROM/Recovery images will NOT have an impact on unlocking your bootloader. This tip is just in case you would feel more comfortable downloading the ROM files directly from Motorola, or if sbf.droid-developers.org has problems again.
Then select from one of the following options...
Option 1 The "Moto X Tool Kit"
See -> http://forum.xda-developers.com/showthread.php?t=2477132
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for yor phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2 Fastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept the KitKat OTA without losing data/apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.) See above.
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and and be ready for the update.
NOTE: to combat a 401 ERROR while doing the update, some users have also had to flash do the following
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier. HOWEVER, before as part of STEP 4, while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone.
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier.
Option 5 Using mFastboot to manually flash your phone's firmware (without wiping data).
This is the same as using option 3, but usese Moto fastboot instead of RSD. This will not erase your data and apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.)
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (note: mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down button and Power button.
After a few seconds release Power, you should be in fastboot menu on phone.
Connect phone to PC.
open command prompt and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready for the update.
Main issues encountered during the Kit Kit upgrade install...
Boot loop while trying to install the update. This is usually caused by having used PwnMyMoto or RockMyMoto to root. Those tools replace the stock recovery which is needed to install the OTA. You must re-install the stock recovery with one of the above options.
Error 252 reported by the "update". Again this is related to having been rooted but not restoring to Stock
Error 401. One of your files still isn't stock. See the NOTE in option 2 above, or see -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315
Some apps haven't been upgraded to be Kit Kat Compatible... Foxfi, HBOGo, and others. You have to wait for the app vendor to update.
Some apps partially work.. WellsFargo app, I can't deposit a check via camera, but rest of app works. Again, we have to wait for the vendor to update it.
Hope this helps!!
EDITs & Updates: Here are a few more things found since the initial posting...
For those running the T-Mobile Pre-Release leak, I just wanted to link to this thread here -> Oficial tmobile KK over tmobile leak It pretty much summarizes the ability of using Option 3 and/or 4 above to flash TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip over the leaked T-Mobile pre-release rom. (Thanks beelzebu)
There are reports of Verizon Moto X (non-developer) users who took the KK 4.4 update yet were able to flash back to the previous 4.2.2 w/camera fix rom. Please see -> [Q] Return to JB from kitkat on Verizon Moto X (locked) for more details.
Be sure to keep up on the [BOUNTY/PLEDGE/NON-DEV VARIANTS] ROOT 4.4 for MOTO X ($325) as there is some rumblings that a root for Non-Developer Edition KitKat 4.4 might be being worked on.
Tethering options for ROOTED KitKat 4.4 (currently limited to unlocked bootloader)... so far there are two....
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
(per -> http://forum.xda-developers.com/showthread.php?t=2449534 )
See -> Native tether for VZW DE 4.4 <- This works for rooted with locked boot loader too!!
Root for KitKit users who have a locked bootloader has been released. See -> SlapMyMoto 0.5c Beta (4.4 root, RW to system) (thanks Jcase!!)
When I re-downloaded the GSM Moto X Developer Edition KitKat recovery image recently, available by request from Motorola (HERE) I noticed it has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need to download the Adb Drivers and Android Platform Tools from the Android SDK.
If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.
well done sir! hopefully people actually read this because it will clear up a lot of the clog going on in the threads about kit kat. It was getting ridiculous trying to answer the same simple question a dozen times. Good write up.
thread Title changed. (forgot I had to be in advanced mode..)
Thanks, I stole your idea for thread title.
KidJoe said:
Looking at the thread title I wish I would have called it... Some lessons learned while preparing for and taking the kit kat update.
Click to expand...
Click to collapse
change it then ha. you can change your thread title sir.
i would call it something different personally. Like FAQ for Kit kat and How to prepare for it or something. there is a lot more than just lessons learned. This is a answer to all your simple questions thread. Or call it Read This before Asking Any questions about kit kat ota lol
Should help many people
Sent from my XT1058 using Tapatalk
fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
http://forum.xda-developers.com/showthread.php?p=47698477#post47698477
jayboyyyy said:
fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
Click to expand...
Click to collapse
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.
KidJoe said:
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.
Click to expand...
Click to collapse
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.
jayboyyyy said:
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.
Click to expand...
Click to collapse
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!
Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk
rod.gui said:
Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
If you are not rooted, and therefore haven't used any root needing apps to remove or otherwise mess with system files, there is no need to do anything.
KidJoe said:
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!
Click to expand...
Click to collapse
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha
this post saved me from wiping my phone :3
jayboyyyy said:
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha
Click to expand...
Click to collapse
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.
jimmydafish said:
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.
Click to expand...
Click to collapse
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.
Added a few more things to the Initial post.. See.. Edits & Updates...
What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.
KidJoe said:
Added a few more things to the Initial post.. See.. Edits & Updates...
Click to expand...
Click to collapse
Non developer edition on 4.4 now has root
And it is possible to downgrade to 4.2.2. I've done it multiple times already when testing.
Added a couple updates to the OP
jayboyyyy said:
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.
Click to expand...
Click to collapse
AFAIK, u can downgrade the ATT phone back to 4.2.2, but the post-camera ota one.
robsw said:
What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.
Click to expand...
Click to collapse
The GSM DE uses the Retail (TMO) ROM.
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
I finally was able to fix my wifi issue. I have been unable to flash anything from my windows 10 laptop to my phone. Adb and fastboot worked fine except for the flash command? I reloaded all the drivers on numerous occasions just to make sure and also manually loaded them even thought the drivers are digitally signed and windows is happy. Still have not figured that one out yet. I tried the one step firmware batch file from http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833. I put the NON-HLOS.bin, nowarning.bin and the stock kernal, v4tk-kernel-uber-alias-V6.img in the same folder as the extracted, Auto Flash Firmware script and ran the autoflashfirmware. bat file. To my surprise it worked. I still have the unlocked bootloader warning, I can live with that, however I now have my wifi back....Yea.... Thanks to all the people who devote hours setting up tools that help noobs like myself..... History,,, tried to root 6.0 MM on new XT1575 after bootloader unlock and twrp recovery. Soft brick because I did not read enough. Restore back to 5.1.1.. Lost Wifi until now.......