Database Develop

Flashing 4.3 with a Mac keeping all your data

You will find other versions but this is how I did it and how I solved a few common problems. If you do it exactly following the instructions, you should not loose data. I flashed from Android 4.2.2 rooted.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Then if you want to root:
1. On your Mac, download TWRP recovery from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
2. Connect your Nexus 4 (debug mode) and put it in fastboot mode (point 5 above)
3. In terminal mode enter: ./fastboot flash recovery FILENAME.img (replace FILENAME by the file name of TWRP file you just downloaded)
4. Reboot your phone
5. Download directly from your phone this file (SuperSU): http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
6. Shut down your phone and boot it in recovery mode (Once off, push vol+, vol-, and power all together). Choose recovery mode with vol-
7. Once you are in TWRP recovery mode push "Install", look for SuperSU file you just downloaded and follow instructions to flash the zip file.
That's it! You are now root. All your data are intact.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/ and http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/

jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2

veteran_troller said:
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea but it takes only a few minutes to download the original factory file.

jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
this procedure wipe everything...I updated in this way yesterday

Works
Nice post. Works exactly as described.
Thanks!!
Matt
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse

alakyr said:
this procedure wipe everything...I updated in this way yesterday
Click to expand...
Click to collapse
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!

jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
If you delete userdata.img from zipfile it will not wipe your data.

My data wiped too
I followed everything precisely on a completely stock Nexus 4 and it wiped my data too.. Not to critical for me since I dont do much with my phone so its not a bother but just for reference for others...

Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe

Remoteconcern said:
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Click to expand...
Click to collapse
My Nexus 4 doesnt have an sd card..

I am sorry for those who have lost data but I did exactly what I have said and preserved all my data without any other manipulation. All my apps are still there, gmail accounts, WiFi passwords, etc... I am not an expert, maybe somebody will be able to explain when data are deleted and when not.

For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium

Is the root okay?
Thanks

Root is fine. Using SuperSU 1.43
Sent from my Nexus 4 using xda premium

this didnt wipe /data for me either.

jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta

alakyr said:
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, that was the problem, you didn't follow exactly the process. If you use -w flag it will wipe your data. I am sorry for you.

Noiseboy1176 said:
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.

jipi said:
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
Click to expand...
Click to collapse
Agreed. That's what I usually do, but was feeling lazy and the version of adb I had works for everything I've tried so far... Unlocking boot loader on 4.2.2, flashing numerous recoveries, radios etc. So I thought it would be fine. Of course, it is possible that my problem was the archive utility I used to extract the ROM and not adb related at all. Either way, I figured ppl should know in case it happens to them.

Must the bootloader be unlocked to do this flash? Have flash many roms with Windows PC but now Im a mac user and never flashed roms with mac and yesterday i tried and didnt get it is the an video tutorial on this?

Use fastboot to flash 4.4.3 without waiting for OTA

This is the well-established way to flash factory images without waiting for the OTA, using a Windows computer.
You can have a custom recovery, but you must otherwise be stock.
Your bootloader must be unlocked.
You should not lose apps (except for non-stock system apps) or data, but don't hold me responsible if you do.
You will have to reload non-stock system apps like Xposed framework (in fact, I uninstalled the Xposed framework using the Xposed framework installer before starting this process).
This is a modification of the process explained here, which I have mostly cut-and-pasted:
http://forum.xda-developers.com/nexus-4/general/flash-android-4-3-build-clean-flash-t2376681
(Credit to mc704.)
1. You must have ADB, fastboot, and USB drivers for the N4 on your PC. Not hard to find; the thread referenced above tells you one way to get them. Put adb.exe, fastboot.exe, AdbWinApi.dll, and AdbWinUsbApi.dll in a folder on your PC - let's call it C:\N4Update
2. Enable USB Debugging via Developer settings on your phone.
3. The Nexus 4 (mako) 4.4.3 image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images#occamktu84l
Step 1: Use 7zip or an equivalent compression program to extract the stock 4.4.3 image file that has extension .TGZ
Step 2: You should see a stock image file that has extension .TAR...extract this once again with 7zip (or equivalent) into C:\N4Update
Step 3: Plug your device into the PC (USB debugging should be enabled)
Step 4: Launch command prompt from C:\N4Update, or alternatively start a command prompt (start --> run --> "cmd") and cd to it (cd C:\N4Update)
Step 5: Verify that the PC is detecting your device by typing in command prompt "adb devices" (you should see a code representing your device, and then "device" following it); if not, recheck usb debugging, and unplug and replug the phone back into your PC
Step 6: Turn your N4 off and go into fastboot (bootloader) mode (hold power button + Volume Up & Down all together)
Step 7: Type in the command prompt each step one at a time and wait for it to complete (obviously, don't enter the quotation marks):
"fastboot flash bootloader bootloader-mako-makoz30d.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-ktu84l.zip"
Step 8: At this point, your N4 will reboot. This will take some time as your apps are re-initialized, but it should be clear what's going on.
Step 9: You will now have 4.4.3. You will be unrooted and have stock recovery. If you want, you can stop here.
If you want to install the TWRP custom recovery and regain root:
Step 10: Download the new version of SuperSU onto the N4 from here: http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Step 11: Download TWRP onto your PC in C:\N4Update from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.7.0.0-mako.img
Step 12: Boot N4 back into fastboot (bootloader) mode while connected to the PC.
Step 13: With the command prompt from Step 4 above, type "fastboot flash recovery openrecovery-twrp-2.7.0.0-mako.img"
Step 14: Boot from the bootloader into Recovery by pressing volume up to display "Recovery" and then the power button to select.
Step 15: Use TWRP to install the zip (SuperSU) file from Step 10 to regain root.
Step 16: Reboot system.
You should now have a rooted system, with all of your old apps and data (except for system apps, which need to be reinstalled), and the latest TWRP custom recovery.

Don't wanna sound rude, but is there point in creating another how-to thread, along the other threads which some(link) are even mentioned in sticky roll-up threads? Plus it's 99% copy/paste, which you even mention so that's nice from you.
It's nice that someone have will to write(or even copy/paste/edit) tutorials, but by having more threads help is harder to find(search).
Just my humble opinion and experience

Also you can jsut remove the recovery img from the update package to keep your custom recovery

well I for one appreciate you posting this as now I don't have to search all over gods creation to find the old thread

Nevermind

i did all steps... but im spammed google now launcher has stopped
will factory reset help?

Night5talker said:
i did all steps... but im spammed google now launcher has stopped
will factory reset help?
Click to expand...
Click to collapse
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)

NYZack said:
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)
Click to expand...
Click to collapse
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher

Night5talker said:
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher
Click to expand...
Click to collapse
Well, sorry, don't quite understand: you could always just uninstall the Google Now launcher, make sure everything else is working, and then reinstall it once you confirm there's no other problem.

Anyone could just mention the procedure for doing same thing but through Wug toolkit.
In general I prefer to avoid fastboot commands and flash everything though pc.
Unleashed by my Nexus 4

No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".

DarsVaeda said:
No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".
Click to expand...
Click to collapse
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !

mashedbymachines said:
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !
Click to expand...
Click to collapse
Yeah, this is the key point - if that -w flag is not removed, you will lose all apps/data. One of the reasons I put this up is that I think the step-by-step method is interesting, instructive (you can see what's actually happening), not much more time-consuming than running the automated script, and lets you have more granular control.
(And I apologize if it's littering the forum and semi-plagiarism, but I thought a very detailed, confirmed step-by-step guide with up-to-date precise download links might be useful to people who haven't gone through the process before.)

What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-occam-ktu84l.zip
echo Press any key to exit...
pause >nul
Click to expand...
Click to collapse
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.

Erroneus said:
What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.
Click to expand...
Click to collapse
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?

fdg59 said:
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?
Click to expand...
Click to collapse
Actually, you have to run the unzip program twice:
For example, when updating to Android version 4.4.4 (Yes, a new version has already been released since this post):
Here is the downloaded file
occam-ktu84p-factory-b6ac3ad6.tar
Unzipping it will give you this:
occam-ktu84p-factory-b6ac3ad6
And unzipping that one more time will give you the directory "occam-ktu84p" containing the following files:
bootloader-mako-makoz30d.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-ktu84p.zip
radio-mako-m9615a-cefwmazm-2.0.1701.03.img
WARNING: As was mentioned many times, remove the -w from the following line in the flash-all.bat file unless you intend to wipe your phone clean. I don't understand the issue with Notepad++ noted in a previous post, as you have to hit "save" like any other program (It is the program that I use as well).
fastboot -w update image-occam-ktu84p.zip
If what you were really asking is whether you need to unzip the file image-occam-ktu84p.zip.......The answer is no.

ah ah yes 4.4.4, that's why i am asking, because i always used to unzip everything and the flash items individually using fastboot which i always liked. The problem however was that my nexus 4 has 16gb and after flashing and wiping everything clean the memory showed up at 8gb so i had to factory reset through stock recovery which i didn't enjoy as much. thanks for all the help!

Update Nexus 7 to 5.0 from 4.4.4 (root + unlocked bootloader) KEEP DATA

This is a "re-tread" of a post I previously made, taking an account of the steps I took to successfully update my Nexus 7 from 4.4.4 to 5.0. Note: This is for an unlocked bootloader, if you don't have an unlocked bootloader you will lose your data; consider TiBackup.
My Nexus 7 [WiFi] was rooted on 4.4.4, unlocked bootloader, but stock rom, stock system (as far as I remember). I couldn't find a walkthrough so I'll make one with my experience. This worked for me on my Mac, I hope this helps you.
In the end I didn't lose any data, still have unlocked bootloader and rooted with CWM Recovery & SuperSU (you can replace with TWRP recovery or CWM Touch if desired)
Directions ("./" = file path to platform-tools folder, if you 'cd' to that location the "./" will pull that location in the terminal)
1. You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html.
2. UNZIP and you will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
3. Download the factory images 4.4 (KRT16S) (4.4 required, see HERE, Google broke its own bootloader) and 5.0 (LRX21P) for your Nexus 7: https://developers.google.com/android/nexus/images#nakasi (WARNING: Download the correct images for YOUR device, Nexus 7 Wi-Fi vs Mobile)
4. Unzip the 4.4 image file you downloaded and copy "bootloader-grouper-4.23.img" (img name depends on your build) to your "platform-tools" folder (where adb and fastboot are). (WARNING: the bootloader image in 5.0 is broken see HERE)
5. Unzip the 5.0 image file you downloaded and copy all content, except for "bootloader-grouper-4.23.img," to your "platform-tools" folder (where adb and fastboot are).
6. Plug your Nexus 7 into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate "Developer Options" menu where you will be able to activate "USB debugging")
7. Open terminal and "cd" to the platform-tools folder
8. Verify ADB is working type "./adb devices"
9. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
10. Type:
"./fastboot flash bootloader ./bootloader-grouper-4.23.img" (img name depends on your build)
11. If you have "WiFi Only" skip to step 12; for Mobile flash radio type:
"./fastboot reboot-bootloader"
"./fastboot flash radio ./radio-XXXXXXXX.img" (img name depends on your build)
12. Type:
"./fastboot reboot-bootloader"
"./fastboot update ./image-nakasi-lrx21p.zip" (zip name depends on your build)
It will then reboot (takes a while, 5-10 minutes on boot animation, then it must update App info, another 5-10 miuntes) and then you will be in Android 5.0 with all your data preserved.
Then if you want a custom recovery:
1. On your computer, download CWM, CWM Touch, or TWRP recovery from here: CWM Dwnld or TWRP Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Place the image file you downloaded in your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. In the terminal type:
"./fastboot flash recovery ./FILENAME.img" (replace FILENAME.img by the file name of the CWM/TWRP file you just downloaded)
5. Verify Recovery - Shut down your device and boot it into recovery mode (Once off, push vol- and power together). Choose recovery mode with vol-, then power to select (Note: if you get an Android on his back you still have stock recovery, retry Steps 1-4. I flashed CWM, CWM Touch. and TWRP with no success, plugged my cable into a different USB port and got it first try; try different cables and ports)
Then if you want a root:
Note: If you don't have an unlocked bootloader you will lose data. Already unlocked should be fine, when you boot there should be an open lock at the bottom of the screen below the Google logo. On PC WugFresh Nexus Root Toolkit might be your best option, for me on Mac it is not available so this is what I did.
1. On your computer, download CF-Auto-Root from here: Auto Root Dwnld (WARNING: Download the correct image for YOUR device, Nexus 7 WiFi vs Mobile)
2. Unzip the CF-Auto-Root file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are)
3. Connect your Nexus 7 (debug mode) and put it in fastboot mode (step 9 above): type in terminal "./adb reboot-bootloader"
4. Type: (Note: Step 4 commands need to be run as Admin)
"chmod +x root-mac.sh"
"ls -al"
"./root-mac.sh"
5. Follow on-screen prompt and type your Mac User Account password and ENTER
6. Let the phone go through its thing (Red Android screen), it will reboot when complete.
That is it!
Thanks to Phil Tech: http://youtu.be/IPg_FGbeyq0
Thanks to jipi: http://forum.xda-developers.com/showthread.php?t=2377691
Good luck and happy flashing.

Thanks for the effort.

Thanks ! I did that, more or less adapted. The result was just awefully slow, so I had to do a wipe to start with a clean slate.
Android, the new Windows: reinstall every 6 months....

I've followed the procedure on w8.1 64bit.
All went well but I lost adb after 5.0 finally booted. So I could not install root through NRT (1.9.8).
Adb mode was recognised in windows device manager but adb commands failed with no device found.
Suprisingly fastboot was working.
The solution was to uninstall NRT and adb drivers and reinstall them.

Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.

dg170775 said:
Great guide!!
Followed the steps to the 'T' and I've got Lollipop on my Nexus 7 Wi-Fi.
If the Bootloader is already on 4.23 then Step 10 can be skipped, as I did.
Click to expand...
Click to collapse
True, I was already on 4.23, but still flashed it anyways. Thanks for the input.

[TUTORIAL] Applying an OTA update with stock + root/custom recovery

Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.

Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM

It worked for me

I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?

azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.

I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo

Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..

azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer

Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot

Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d

BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.

+1 for flashing boot.img worked perfect after I did that.

I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.

This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!

Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img

Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.

gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.

Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.

guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.

RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.