Related
EDIT: November 14, 2012: As of today this is applicable to all three versions of the Galaxy Nexus: maguro (GSM/HSPA) and toro (Verizon CDMA/LTE) and toroplus (Sprint CDMA/LTE). I have also updated the adb and fastboot files to the latest versions as of today.
I have created this thread to give a step-by-step on how to flash the latest yakju/takju (or mysid for toro users) build available on Google's developer site. (These are full ROMs. See this thread for updating to latest OTA build using incremental updates.)
This method works for earlier builds as well, and is essentially a "return-to-stock" method.
You can easily convert ANY GSM/HSPA (i.e., maguro) device to stock yakju (or takju) from any non-yakju build (yakjuxw, yakjuxs, yakjuux, yakjusc, yakjuzs, yakjudv, yakjukr, yakjujp, yakjuxe, etc.).
For toro and toroplus devices (i.e., Verizon and Sprint devices), this will return your device to stock.
I will no longer be be providing support in the previous thread here, as it has over 1,000 replies and a lot of confusing information/misinformation.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. I will continually add to this post to make it clearer as we go along.
So, without further ado:
How to flash yakju/takju on your GSM/HSPA Galaxy Nexus (or how to flash mysid on your Verison CDMA/LTE Galaxy Nexus and mysidpr on your Sprint CDMA/LTE Galaxy Nexus)
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) This method is EXACTLY the same as a "return to stock" method. If you follow this (including the optional steps in part D), you will be fully stock.
3) yakju is a generic build, meaning no specific localizations. There are reports that yakju does NOT contain certain dictionaries (such as Norwegian, Swedish, Danish, and possible others). So, if you currently have these dictionaries, and want to keep them, do not flash yakju or takju.
4) MacOS-specific instructions: a) replace fastboot in the steps below with ./fastboot-mac and b) no drivers required.
A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) Once you have backed up your data, you may want to back up your current build (not required). If so, follow the instructions in this thread.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the platform-tools-v16.zip attachment from this post and extract the contents to the directory created in step 1.
3) Download the version of Android you want from here. So, let's say you want the yakju JRO03C image, go to the JRO03C link that is under the heading Factory Images "yakju" for Galaxy Nexus "maguro" (GSM/HSPA+). Older versions are no longer available on that site; however, oldblue910 has provided a mirror on his site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files (or seven for toro and toroplus devices) ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume up and volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located) and do the following:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
E. Optional -- Root
1) After finishing this process, if you want to root, see here.
Notes on optional items and other issues:
1) This note is NOT for n00bs. To be on a "yakju" (or takju) build, all you need is the system and data images. If you want to flash the newer bootloader, radio, kernel (boot image) or recovery, go ahead. If you want to flash a different ones go right ahead, that is fine also.
2) Yes, you will receive the OTA update notification (when it is available) for the next update, regardless of which bootloader, radio, kernel or recovery you are running.
3) BUT, being on yakju or takju does NOT mean you will get the OTA notification immediately when it is announced/available. It could still take minutes or months (yes, months) following the first person who got it, before you get it. The advantage of yakju and takju , is that the updates are available before the other builds, so you can manually install them yourself. See here.
4) WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the corresponding boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically, but it will install using a custom recovery like CWM. See this thread for details.
5) This note is NOT for n00bs. There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
6) Jelly Bean requires a newer bootloader. I would not flash anything earlier than LA03, or you may have issues.
Notes on the bootloader:
1) Do NOT re-lock your bootloader after you are finished. The is no need.
2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all.
3) If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects.
4) If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader.
5) ONLY re-lock your bootloader if you need to return your device to the store. The command is: fastboot oem lock
6) As of June 2, 2012, a method has been found to unlock the bootloader without wiping (but root is required), and segv11 put it together in an app for us. See here. So, if you have root, there is no issue with re-locking the bootloader if you want -- just make sure you don't lose root, or you will have to wipe to unlock it again.
[HOW-TO] Install official JRN84D (Jelly Bean 4.1) on your GSM Galaxy Nexus
EDIT: As of Jul 27th, 2012, this information is no longer required -- the yakju/takju JRO03C factory images are now posted on Google's site here.
Here is my take on how to flash JRN84D (official) on ANY maguro (i.e., GSM/HSPA) Galaxy Nexus, regarless of what build you are currently running.
Notes:
1) Doing it this way will leave you with an official JRN84D ROM, and you will receive future updates, assuming that there are any for JRN84D (which is almost certainly the case).
2) Method 2 assumes that you have: a) the drivers properly installed, b) an unlocked bootloader, and c) you have downloaded the attachment in the first post of this thread.
3) Both these methods will require you to wipe your data, but NOT the files you have in /sdcard. (I tried to get it to work without wiping data, but I couldn't get it to work. This is not to say that it won't work for all of you, but I can guarantee that it will work if you wipe.) The Play Store will automatically re-install all your apps, and your can restore the app data with Titanium Backup (root required of course).
4) I have had NO issues whatsoever so far with the OS. There are some apps, however, that are not yet compatible with Jelly Bean (like CallRecorder).
5) Jelly Bean requires a newer bootloader. Do not try to flash this without having LA03 or newer, or you may have issues.
Method 1: CWM 5.5.0.2 recovery already installed
1) Download takju JRN84D from here (this is Koush's repack) to your computer and rename (or delete) this file: /system/etc/install-recovery.sh. Use 7zip to do this, not WinZip or WinRar or whatever. This will prevent the ROM from overwriting CWM with the stock recovery. If you want to have the stock recovery so that future updates will install automatically, leave the ROM as is. (We all know that if you have CWM, you will have to install the update manually through CWM -- it will not install automatically, but it will install just the same, right? ) Note: Some users have reported that they could not flash the zip after deleting the install-recovery.sh file. If it doesn't flash for you after you deleted the file, just re-flash the unmodified zip.
2) Move the file to /sdcard on your phone.
3) Download the CWM-flashable version of the XXLF1 radio from here and the CWM-flashable version of the LC03 bootloader from here to /sdcard.
4) Backup your app data using Titanium Backup. Root is required for this step. Alternatively, if you do not have root, you could try using this, but no guarantees it will work.
5) Reboot your phone into CWM.
6) Select "wipe data/factory reset" and select "Yes -- delete all user data"
7) Select "wipe cache partition" and select "Yes - Wipe Cache"
8) Select "advanced" and select "Wipe Dalvik Cache" and select "Yes - Wipe Dalvik Cache"
9) Select "*****Go Back*****" to return to the main menu
10) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the bootloader file you downloaded, and flash it.
11) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the radio file you downloaded, and flash it.
12) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the JRN84D file you downloaded, and flash it.
13) Optional -- If you want root, flash one of the attachments the same way. (Either ChainsDD's Superuser or Chainfire's SuperSU. Note that you may have issues with Superuser, as it has yet to be updated.)
14) Go back to the main menu and select "reboot system now".
15) Done! Enjoy stock Jelly Bean 4.1
Method 2: Stock recovery (or any other recovery aside from CWM 5.5.0.2) installed
1) Download CWM from here to the same directory on your computer as your fastboot file, and rename it to cwm.img.
2) Download takju JRN84D from here to /sdcard on your phone. (This is Koush's repack.)
3) Download the CWM-flashable version of the XXLF1 radio from here and the CWM-flashable version of the LC03 bootloader from here to /sdcard.
4) Backup your app data using Titanium Backup. Root is required for this step. Alternatively, if you do not have root, you could try using this, but no guarantees it will work.
5) Reboot your phone into fastboot mode (turn off and press vol up + vol down + power) and plug into your computer.
6) Open a command prompt in the same directory as your fastboot file and type: fastboot boot cwm.img
7) On your device, CWM should be booted up. You can unplug your device from your computer if you wish. From now on, everything is done on your device.
8) Select "wipe data/factory reset" and select "Yes -- delete all user data"
9) Select "wipe cache partition" and select "Yes - Wipe Cache"
10) Select "advanced" and select "Wipe Dalvik Cache" and select "Yes - Wipe Dalvik Cache"
11) Select "*****Go Back*****" to return to the main menu
12) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the bootloader file you downloaded, and flash it.
13) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the radio file you downloaded, and flash it.
14) Select "install zip from sdcard" and select "choose zip from sdcard" and navigate and select the JRN84D file you downloaded, and flash it.
15) Optional -- If you want root, flash one of the attachments the same way. (Either ChainsDD's Superuser or Chainfire's SuperSU. Note that you may have issues with Superuser, as it has yet to be updated.)
16) Go back to the main menu and select "reboot system now".
17) Done! Enjoy stock Jelly Bean 4.1.
As always you are king =]
- Google Galaxy Nexus
Thank you very much. As someone who is completely green at the android thing, I made it through this instructional with barely a hick-up. I think if I had done as you said and read through the entire post before starting then I might have saved myself some time.
THANKS!
efrant said:
A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
Click to expand...
Click to collapse
If I have pdanet drivers installed and I can do successful fastboot and adb devices commands does that necessarily mean I am good to go? Or would you still recommend replacing them before I start flashing?
what's the benefits of this over the Gnex toolkit? Just curious as I'm new to the nexus
Sent from my Galaxy Nexus using Tapatalk 2
NCguy said:
If I have pdanet drivers installed and I can do successful fastboot and adb devices commands does that necessarily mean I am good to go? Or would you still recommend replacing them before I start flashing?
Click to expand...
Click to collapse
If you have them installed and fastboot is working fine for you, then you are ok.
Thegodfather156 said:
what's the benefits of this over the Gnex toolkit? Just curious as I'm new to the nexus
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
efrant said:
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Click to expand...
Click to collapse
Great thats why I'm here. I wanna learn more about how android works. Thanks for this thread. Also I've read that before. I'm not that noobish
Sent from my Galaxy Nexus using Tapatalk 2
Does usb debugging have to be turned on for this? Also I have the samsung drivers installed, if fastboot recognizes my phone does that mean that they work correctly?
SirRomie said:
Does usb debugging have to be turned on for this? Also I have the samsung drivers installed, if fastboot recognizes my phone does that mean that they work correctly?
Click to expand...
Click to collapse
No for your first question, and most likely yes for your second.
Amazingly simple guide. I finally got around to doing this, much thanks!
efrant said:
You actually see what is happening step-by-step in this method, in the hopes that you will learn something.
A toolkit does not run you through the steps, so it breeds a new wave of users who don't know how to use fastboot and don't know how to troubleshoot.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Click to expand...
Click to collapse
This is the main and only reason why I don't use toolkits. Excellent work!
Sent from my Galaxy Nexus using Tapatalk 2
I just want to start this post by saying I am very new to this and I do not want to screw anything up. I have the correct files and drivers ready, but when I type the command "fastboot oem unlock" my phone says it is already unlocked. Just to be clear bootloader and being factory unlocked to use with any carrier are two different things?
Also if my phone's bootloader is unlocked, that could mean that the previous owner tinkered with this phone (I think), so am I able to just type in all of the commands that follow the unlock step without issue? Should I wipe my phone anyway? I am going from 4.0.1 yakjuux to 4.0.4 yakju and if so before or after fastboot is done?
SirRomie said:
I just want to start this post by saying I am very new to this and I do not want to screw anything up.
Click to expand...
Click to collapse
No problem. We are here to help!
SirRomie said:
I have the correct files and drivers ready, but when I type the command "fastboot oem unlock" my phone says it is already unlocked. Just to be clear bootloader and being factory unlocked to use with any carrier are two different things?
Click to expand...
Click to collapse
Yes, they are different.
SirRomie said:
Also if my phone's bootloader is unlocked, that could mean that the previous owner tinkered with this phone (I think), so am I able to just type in all of the commands that follow the unlock step without issue?
Click to expand...
Click to collapse
Yes and yes.
SirRomie said:
Should I wipe my phone anyway? I am going from 4.0.1 yakjuux to 4.0.4 yakju and if so before or after fastboot is done?
Click to expand...
Click to collapse
The procedure will wipe (assuming you do step 10 in part D).
Thanks efrant for all of your help! I have managed to get 4.0.4 working, however, my playstore doesn't work... It says server error retry also my phone is from the UK so it says playshop now. Anyway to change this and also get it working?
EDIT: clearing data worked. It still says playshop though. Would downloading another locale help? I don't think there was a locale change on the other build yet it said store and not shop.
flashing alternative radios
Hi efrant,
I have previously done this method and loving 4.0.4. Now I am wondering about trying different radios, as I am in Australia
To flash a new radio in fastboot, do i just type:
fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
Or do i have to reboot the bootloader, and flash all the other stuff first?
After I flash the radio, do I just reboot the bootloader and that is that... or do I need to flash the system partition, boot partition and erase the cache too?
If I change the radio, I have to return it back to XXLA2 for future OTA updates to install successfully, right
Running:
Stock Android 4.0.4
19250XXLA2
3.0.8-gda6252b
IMM76I
sagiballs said:
Hi efrant,
I have previously done this method and loving 4.0.4. Now I am wondering about trying different radios, as I am in Australia
To flash a new radio in fastboot, do i just type:
fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
Or do i have to reboot the bootloader, and flash all the other stuff first?
After I flash the radio, do I just reboot the bootloader and that is that... or do I need to flash the system partition, boot partition and erase the cache too?
If I change the radio, I have to return it back to XXLA2 for future OTA updates to install successfully, right
Running:
Stock Android 4.0.4
19250XXLA2
3.0.8-gda6252b
IMM76I
Click to expand...
Click to collapse
All you have to do is to boot into fastboot mode, and type: fastboot flash radio (radio-maguro-i9250xxla02.img) <- whatever the name of the radio image is
I would also type the following: fastboot erase cache
And then reboot: fastboot reboot
Nothing else.
As for your second, yes, you will need to flash back to XXLA2 for future OTA updates to install successfully.
Well I managed to get everything working. The guide made it as simple as can be. The set-up was the main hurdle, but once everything was downloaded and unzipped, it was a piece of cake.
Thanks again efrant for making this! I finally am happy with my Nexus.
chubiprince said:
Hi... I am not really an expert with this things, so I would just like to ask you if I am doing the right way. I am not an Android expert, and I am really new to this kind of thing.
Click to expand...
Click to collapse
Please don't quote massive amounts of the first post. There is no need.
chubiprince said:
- I have none of these in my laptop, so I will just skip these right?
Click to expand...
Click to collapse
Not sure what you are asking. The post says do NOT install those drivers. If you haven't, then why are you asking if you should skip them?
chubiprince said:
- Uhmmm, yeah. I don't know how to install it. Install it where? My GNex? Or in my laptop?
Click to expand...
Click to collapse
If you are asking this question (i.e., do I install the drivers on my GNex or on my laptop), then, no offence, but you have bigger problems that what can be solved by me telling you what to do. You should try and do a bit more reading, before attempting this.
chubiprince said:
- Will this toolkit (http://www.tested.com/news/feature/...-data-from-your-galaxy-nexusno-root-required/) affect in updating my GNex?
Click to expand...
Click to collapse
No it should not.
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Same problem but didn't understand your procedure
Thank you for your solution but I didn't understand
I had the same problem : I rooted my phone by flashing pre-rooted system.img. It worked but now I want to be able to update OTA. So I need to replace pre-rooted system.img with stock one.
Can you please explain how you "erased system, boot.img and droid_boot.img then reflashed WW versions"?
I tried the following : fastboot erase system, fastboot erase cache, and then adb sideload UL-Z00A-WW-2.13.40.13-user.zip with official firmware downloaded from asus.com. But now my phone is blocked on black boot screen "ASUS in search of incredible, powered by android". I can only boot to recovery. Can you repair my phone without wiping data? Thank you.
Not even any clue
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
remidem said:
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
Click to expand...
Click to collapse
Apparently you can unroot through supersu. This should then allow OTA updates...
Already tried
ultramag69 said:
Apparently you can unroot through supersu. This should then allow OTA updates...
Click to expand...
Click to collapse
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
remidem said:
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
Click to expand...
Click to collapse
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Impossible to update with sdcard
ultramag69 said:
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Click to expand...
Click to collapse
Thank you for your reply. I tried OTA update with sdcard:
1) In Settings/About/Software information, my current version is 2.13.40
2) I dowloaded, from http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999 update from 2.13 to 2.14
3) Copied to external sd, in root folder, and renamed zip to MOFD_SDCARD.zip
4) Rebooted in recovery
5) Update failed. Here is my log:
Finding update package...
I:Update location: /sdcard/MOFD_SDUPDATE.zip
Opening update package...
E:file path:/sdcard/MOFD_SDUPDATE.zip
Installing update...
script aborted: Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_20150529_9543_user:user/release-keys.
Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_2015
E:Error in /sdcard/MOFD_SDUPDATE.zip
(Status 7)
SD Installation aborted.
This is because the version of system.img is 2.18 and the fimware version is 2.13.
Indeed I have 2 choices:
- override system with a system.img in version 2.13, but I cannot find any.
- try to apply OTA update 2.17 to 2.18 or 2.18 to 2.19 but it seems risky.
Finally I found!!! I think that a version of the firmware is tagged in system partition and another version (classically the same) is tagged in data partition (this is the one you see in Parameters -> About -> Firmware version). When I wanted to flash a firmware the same version as the one written in parameters (2.13), my phone refused to downgrade because the version of system was higher (2.18). So I had to format the system partition, apply update with official 2.18 firmware. And it worked! My phone was unrooted and I could apply method 3 root.
My issue occurred because I made the following:
1) bought a phone with a 2.13 firware
2) used it for months, applied OTA updates until 2.18
3) flashed a 2.18 pre-rooted system.img
4) used it for weeks until a made an update of supersu
5) my phone couldn't boot any more, so I wiped data (I could avoid that, if I knew!). It made a factory reset, ie get back firmware to 2.13, but system was still in 2.18
Here is the procedure to revert a phone flashed with a pre-rooted system.img (to sell it, send back to warranty, or root with another method):
1) Download official firmware from asus website in the same or higher version of your pre-rooted system.img. Do not rely on version in Parameters -> About -> Firmware version. Or simply download the latest version.
2) In your phone bootloader, enter the following commands with your PC:
fastboot erase system (I'm not sure it is necessary)
fastboot format system
3) With your phone, go into recovery menu, then to "Update with adb"
4) With your PC, go to the directory where you downloaded the firmware as zip, and enter the following command: adb sideload nom_du_fichier_teléchargé.zip
5) It takes about an hour
6) You can reboot
After that I used method 3 to root again, so that I can now OTA update exactly the same way I used to do before rooting. Moreover, I think I can update supersu as well.
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
wrecklesswun said:
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
Click to expand...
Click to collapse
Someone said you need to use fastboot to flash droidboot.img, boot.img, system.img and recovery.img to go back to an older version. Not sure if this works as I unlocked bootloader when I had the chance.
If you can't then you might have to wait for the "Official" unlock tool but ASUS will know and you will be out of warranty.
ultramag69 said:
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Click to expand...
Click to collapse
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
kamranyusuf said:
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
Click to expand...
Click to collapse
VERY IMPORTANT - Make sure you have checked the MD5 checksum on the boot, droid_boot and recovery image files as these are definitely needed to boot phone. If these are corrupt then you can brick your phone... You have been warned...
Download firmware from here-http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
It is pre-rooted but the other files needed are included in the folder.
2. Put phone in fastboot mode and erased droid_boot.img, boot.img, recovery.img and system.img using command "fastboot erase (put choice here)"
3. Flash the files I just erased back on using fast boot - "
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
This got me the pre-rooted 2.13.40.13. As the supersu has been inserted it is fine to use OTA to update, just make sure you don't update supersu before the OTA flash.
Good luck....
And may you retain a strand or 3 of hair like Homer Simpson....
My phone is the ASUS Zenfone 3 deluxe (zs550kl) model and its bricked only can enter fastboot or adb still but my os will not boot I tried going to asus website for stock firmware (UL-Z018-WW-11.40.71.37-user.zip) and stock kernel (ZS550KL_Kermel_11_40_71_37.zip). how do I install these to fix my phone unless there is a better way to make it boot. by the way im new to android I always had iphone jailbroken until last year I am android now but give me noob instructions for the how to. maybe I should add this I already have adb/fastboot installed and the commands for adb devices or fastboot devices when in fastboot mode both recognize my device so maybe my commands are wrong or something but I tried every way I could toinstill firmware and not sure what to flash kernel as the zip or the file unzipped please help thanks in advance. Not sure why this happened exactly but my bootloader is unlocked already but was never rooted so if there is another way to install another custom firmware besides stock I would like those instructions also thanks again
first off your phone is soft brick meaning all you have to do is flash the stock android software back onto your phone.
install to sd card -> boot into recovery (stock or twrp whatever you have works)
flash from sd
let it load (this will work if you have the correct files)
it will reboot and will work good as new again.
you shouldnt have to flash the kernal, just the UL-Z0 file.
That would have worked yesterday but im having another issue now basically instead of waiting for a response on here I went ahead and did other stuff now my recovery menu is not showing up so I cant install from sd now the only option I'm getting is fastboot so is there a way to fix the stock recovery option or even install a custom recovery which might be eaiser because my bootloader is already unlocked. I was going to try to flash stock recovery my self but not sure how exactly I know I use fastboot flash recovery (recovery file name in the folder) and I think it's .img but not sure so I think it will be either .zip or .img file type but not sure what it will be called if it's stock or custom and not sure where to find either. Last issue I'm not sure of is the actual files I downloaded from asus.com the firmware for my specific phone model not working when I try to flash it as the .zip file so my question is do you need to do something with it such as edit the script of something inside the zip of it and I also downloaded the kernel for my specific phone model from the Asus site and not sure if I needed it when flashing stock rom back to device or how to even flash it on the device please help if you can and I know some questions might be dumb to you but remember I'm a noob when it comes to Android recently left iPhone and I was a pro there every phone had a jailbreak and all types of stuff so I know I can get this just takes time I'm sure
I have this exact issue with a new Padfone Infinity A86... No access to stock recovery, only fast boot... But in my case I'm even unable to flash the recovery.img from a firmware package...
I'm wondering if you guys can help this person, maybe there is something in that solution for my Padfone
1: download the full firmware package
2: use sdat2img to convert the sparse system image to a regular one
3: use fastboot to flash the stock boot.img & the newly converted system.img
4: hoping you didn't flash the recovery partition, if you did, reflash the stock dump from the file in my Bootloader unlock thread via fastboot
5: reboot to recovery & do a factory reset
Read the documentation at each step, do your research, learn the process.
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
If I am on a custom ROM and want to update I usually download the latest firmware zip from google and extract the vendor.img and Flash it thru twrp after updating the custom ROM.
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
annoyingduck said:
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
Click to expand...
Click to collapse
Wow this is such a phenomenal post, thank you very much for taking your time to write this! I never smacked that thank button so hard in my life.