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!
Related
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
Prerequisites
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
**User Impo5sible says its possible with custom recovery and kernels I'm not 100% sure so YMMV*** *ANOTHER EDIT - USERS REPORT GETTING STUCK ON NEXUS LOGO if you have a custom rom/kernel and not using the -w command to wipe DATA)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
SDK /w adb & fastboot Link: http://developer.android.com/sdk/index.html
PDAnet Link:http://pdanet.co/
3. ENABLE USB Debugging via Developer settings
(press the build button 7 times to activate it the "settings --> about phone --> Build Number --> go back --> Developer Settings --> Check USB Debugging)
4. Android 4.3 Image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to PTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot"
for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera ptp... unplug and replug the phone back into your comp
**take a breather we are almost done**
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock the Device
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"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 -w update image-occam-jwr66v.zip"
***NOTES FOR THIS STEP***
*REMOVE the -w from the last step if you want to keep your data (assuming your bootloader was already unlocked)*
***User chrisjcks noted you can use the flash-all.bat file that was in the zip to make life easier***
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc. I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is unlocked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & PTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
MISC info.
1. People who are using custom recoveries & root & would like to KEEP ROOT... Check this post out it should help you fellars
http://forum.xda-developers.com/showpost.php?p=43917716&postcount=56
2. STUCK ON BOOT LOGO? Check this post out for the fix
http://forum.xda-developers.com/showpost.php?p=43920888&postcount=85
3. NEW ROOT BY CHAINFIRE
http://forum.xda-developers.com/showthread.php?t=2025274
mc704 said:
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
FIRST
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
3. ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
4. 4.3 Image from Google (https://developers.google.com/android/nexus/images)
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to MTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera mtp... unplug and replug the phone back into your comp
* take a breather we are almost done
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock yadda yadda
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"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 -w update image-occam-jwr66v.zip"
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is locked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & MTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
Click to expand...
Click to collapse
or you could just unzip it, and double click the Flash All bat file. :laugh:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
I'm old school I'm not too familiar with it . If you want to write a mini guide to consolidate all of this for everyone, I'll update the OP.
mbwelch said:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
Click to expand...
Click to collapse
It wipes the system. or atleast it did for me
If you remove the "-w" from the last step it won't wipe data
Sent from my Nexus 7
mc704 said:
.... no custom recovery, kernels, radios, etc)
Click to expand...
Click to collapse
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
Impo5sible said:
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Click to expand...
Click to collapse
There are always exceptions but I'll note that in the OP for people to see. I'd wrote the guide with the intention of a no failure rate or possible errors.
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
LOVE ME PLEASE said:
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
They are pushing the OTA I believe for a short time
chrisjcks said:
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
Click to expand...
Click to collapse
Sure thing I'll update it in the OP:good: thanks for the contribution
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
dan in la said:
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
Click to expand...
Click to collapse
yup. and system.img if you want to remove root
delete - misread the previous question.
(sure i used to be able to delete my own posts.....)
how can we check which radio version is currently on device
mangomonkey00 said:
how can we check which radio version is currently on device
Click to expand...
Click to collapse
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Look in Settings => About
easy way
For me, All i did was extract the package and edit the .bat file and remove the -w in the code. Then ran it under fastboot. It updated my apps and updated to 4.3, no data wipe.
thanks OP got mine updated to 4.3 without -w
vickpick said:
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
yup. and system.img if you want to remove root
Click to expand...
Click to collapse
Who would like to remove root?
And to summarize:
If someone has stock rom, rooted, with custom kernel, all he has to to do in order not to lose his data and rooting is to flash everything except: system.img and userdata.img?
After that, he will have the update with all data still available?
otariq said:
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
mine says 84 i suppose the latest was 83 have i done something wrong and also in quick system info pro in properties its opengl es cm 1.1 which i think should be 3.0
what should i do
checked it has to be 84 but what about opengl es
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
_______________________________________________________________________________
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Thank you for posting this. I tried three other methods to get root back before this, and none of them worked. This one did the trick without any problems at all. Thanks again!
Wug's Nexus Root Toolkit 1.9.4
kyoshiro22 said:
Wug's Nexus Root Toolkit 1.9.4
Click to expand...
Click to collapse
I know there's Toolkit's out there, but this is for those who choose to take the "Fastboot" approach.
gestevez1213 said:
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP[ - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Click to expand...
Click to collapse
This is NOT working.... I tried it 3 times on 2 devices
papayayoghurt said:
This is NOT working.... I tried it 3 times on 2 devices
Click to expand...
Click to collapse
What part are you stuck at?
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
I used chainfires auto root for the N5 (stock lollipop Boot loader). Worked great. Just download to a PC put phone into boot loader and run the bat file. I can't link but a quick google will find it for you.
Sent from my Nexus 5 using Tapatalk
andrelessa said:
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
Click to expand...
Click to collapse
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Personally, I'm using the autoroot from chainfire. Works like a charm, no custom recovery is needed (I have the stock recovery).
gestevez1213 said:
What part are you stuck at?
Click to expand...
Click to collapse
Everything is working, but then SuperSU can´t find a Binary.
gestevez1213 said:
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Click to expand...
Click to collapse
Yes, I read somewhere that TWRP need this...
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Are you running the official lollipop release? It should work with that. Delete the app, and try again.
Just put your phone in bootloader and run cf-autoroot from windows if you dont want twrp.
I have twrp but its not working like that
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Had the same issue and needed to flash the updated kernel from chainfire : https://www.androidfilehost.com/?fid=95747613655047375
Why are you trying to do this the hard way? Just use chainfire's autoroot.
It works perfect and it's literally one command
fastboot boot CHautoroot.img (or whatever the file name is)
cf-auto-root is the way
I agree, just use cf-auto-root. You should be good to go in no time.
Just for FYI, if you already have unlocked bootloader, it won't wipe your data, if you are concerned.
CF-auto-root roots N5 without modifying your kernel. I believe, if you flash the SuperSU in TWRP, it would modify the kernel. It's nothing bad, but if you want to remain "stock" and don't want to reflash stock ROM later to get the OTA, just use "Full unroot" from SuperSU app and you are stock and ready for next OTA.
I have encrypted the storage on my Nexus 5. Will CF-Auto-Root wipe my storage?
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
I have the same error.
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
Hey,
I enrolled to the Android Nougat program and rooted my phone (chainfire) a few days ago. Decided to un-root (using superSU), and it said I was unrooted. After doing the un-rooting, the OEM unlock-option was greyed out (and on OFF setting), but the phone recovery says it's unlocked api 3.... I pretty much just wanted to unenroll and go back to MM. Every time I choose unroll from Google, download the MM OTA and it reboots I get an error. Just an image of android with message "ERROR". The only way to get the phone working is to do a hard reset and go back to Nougat.
Not quite sure what is wrong here. Any suggestions?
It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.
dahawthorne said:
It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.
Click to expand...
Click to collapse
I received the OTA but while installing MM it gives me an error, so I have to go back to Nougat every time. I've tried the unenroll option several times and it gives me the same "error" every time. So, I should try manually flashing MM, then?
UPDATE:
I tried the following:
Downloaded and tried to sideload 6.0.1 (MOB30W) to my Nexus 6-device. It got up to 46% and after it gave me and error saying:
WARNING: No file_contexts. This package is for shamu devices; this is a "".
E: Error in /sideload/package.zip
Status 7
Installation aborted.
UPDATE2:
Tried another package. Didn't work. All the OTA updates stop at 46% giving me the same error. Device remains unlocked, but appears not to be rooted. Still stuck on Nougat.
What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.
dahawthorne said:
What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.
Click to expand...
Click to collapse
No, the checksum is fine. The package is fine. I mean I tried several OTA packages for N6 and it always stops at 46%. There's something else going on here. Maybe if I re-root with chainfire and the use another method to unroot it? Which is the correct method, I have no idea?
Factory reset, and try sideloading MOB30W again.
dahawthorne said:
Factory reset, and try sideloading MOB30W again.
Click to expand...
Click to collapse
Done it like 5 times already. Also wiped cache. No help.
Hannes084 said:
Done it like 5 times already. Also wiped cache. No help.
Click to expand...
Click to collapse
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app
Dude, just flash the system image you want. Forget about the OTA
The OTA is a system image.
fast69mopar said:
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Root with SuperSU? I think you mean with chainfire?
dahawthorne said:
The OTA is a system image.
Click to expand...
Click to collapse
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.
blanco2701 said:
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.
Click to expand...
Click to collapse
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.
Hannes084 said:
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.
Click to expand...
Click to collapse
Well my friend I have no idea since I'm on Windows. Google how to use adb and fastboot on ubuntu, there should be a solution for you.
This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image 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 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:
This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image 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 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
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.
Hannes084 said:
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.
Click to expand...
Click to collapse
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.
blanco2701 said:
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.
Click to expand...
Click to collapse
Thanks, doing that now!
Hannes084 said:
Thanks, doing that now!
Click to expand...
Click to collapse
Just be sure to have selected "oem unlocking" in the developer options, make a backup (everything will be wiped), and start flashing!. There are several guides everywhere.
This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?
ihuntinde said:
This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?
Click to expand...
Click to collapse
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:
v12xke said:
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:
Click to expand...
Click to collapse
Thanks for the reply. I can confirm that I have an unlocked bootloader.
Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...
So.. for those that need it, here are my exact steps for a bootloader unlocked Pixel 4XL bought from the Google Store:
1. Download full factory image from here: https://developers.google.com/android/images#coral (10.0.0 (QQ1B.191205.012.A1, Dec 2019))
2. Extract the zip file, open the zip inside of that extracted folder and copy the boot.img to your phone's Downloads folder.
2a. I used a usb cable to my PC and put the phone in File transfer / Android Auto to do this)
3. In Magisk Manager, click Install. Click Install again in the popup. Choose Select and Patch a File.
4. Find the boot.img that you copied to your phone's Download folder. Select it.
5. Copy the magisk_patched.img file from your phone's Download folder to the unzipped factory image folder.
5a. Refer to 2a above. You may have to disconnect the usb cable and reconnect. For some reason, my PC wasn't refreshing the folder with the patched file until I did this.
6. With your phone connected and in File transfer mode. Open a command prompt in the folder you unzipped the factory image to.
6a. You may be able to shift and right-click then click Open Command Prompt window here. That will open the command prompt at that exact folder instead of having to navigate to it through the command prompt. If you are a newer version of Windows 10, you may only see the Powershell option. I am not sure if Powershell will work. However, to get to a "command prompt" to be able to run the flash-all and fastboot commands. Simply type cmd and hit <enter>. Then you can use the adb, flash-all, and fastboot commands as explained below. ** WARNING: I DID NOT USE POWERSHELL, USE AT YOUR OWN RISK **
6b. Type adb reboot bootloader.
7. Remembering this is a dirty flash (i.e, keeping all of your data) edit the flash-all.bat file in any type of editor (even notepad). Look for the line that says fastboot -w update image-coral-qq1b.191205.012.a1.zip and remove the -w. So, the line just above echo Press any key to exit... should look like this:
7a. fastboot update image-coral-qq1b.191205.012.a1.zip
8. Wait for the flashing to finish and for your phone to reboot and fully boot back up.
9. Once it's connected, put your phone in File Transfer usb mode again.
10. Open a command prompt and type adb reboot bootloader
10a. See 6a
11. Once the phone is in fastboot mode, type fastboot flash boot magisk_patched.img
12. Once that is done, type adb reboot.
You should now be on the December update and rooted.
If you get the error that says "should be flashed in fastbootd", I can confirm that you do not have a new enough version of fastboot.exe. You can do one of two things. First, download the latest platform tools from here: https://developer.android.com/studio/releases/platform-tools
1. Either hunt down every copy of your platform-tools folder (I had multiple for some dumb reason) and consolidate to just one, then update your platform-tolls. Then update your system environment variables and point it to this new folder (making sure it's the only folder pointing to a platform-tools version).
2. Download the new version and copy the fastboot.exe and adb.exe directly into the folder with the flash-all.bat. This will guarantee you are using the correct version.
Hope this helps someone...
ihuntinde said:
Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...
Click to expand...
Click to collapse
This happens more than you know. Glad you got it sorted. Next time (in a couple of weeks) it will be a snap.