I have got a very different situation here. I was using 4.4.4 (KITKAT). I skipped 5.0.0 (LOLLIPOP) OTA update cause there were lots of rumours about the device going into a bootloop. Last week I DIRECTLY (HOW IS THIS EVEN POSSIBLE??) got a "5.0.1" OTA. I mistakenly installed it. So basically I skipped "5.0.0" update and directly installed "5.0.1" and now my Nexus 4 "UNROOTED" device is bootlooping. What should I do?
1. Should I downgrade to 4.4.4 with deleting/editing "-w" thing in "flash-all.bat"? I read somewhere that downgrading wipes all the data. What are my options going back to KITKAT?
3. What should I do to backup? I don't want to flash all my data.
4. Will the deleting "-w" thing work on "5.0.1" factory image?
5. Will the deleting "-w" thing work on "4.4.4" factory image?
6. Do I have to download SDK to perform all the tasks?
Any reply would be greatly appreciated. Thanks in advance. Cheers!
First download official nexus 4 5.0.1 factory image from here https://developers.google.com/android/nexus/images and extract all files till you have separate img files like boot.img, system.img etc.
Then download and install Wugfresh toolkit and install all necessary drivers.
Finally use the toolkit to install all img one by one, except the userdata.img.
At the end you will have a full stock working 5.0.1 system, with no data loss.
Just curious because, even though we shouldn't need them if they haven't changed, they didn't include the bootloader and radio, as every other MM monthly, has included. Anything odd or did your security update go smoothly. With all the N mystery around the factory image, just wondering.
I flashed the full MTC20L OTA from https://developers.google.com/android/nexus/ota over MTC20F. Android Security Patch level: September 6, 2016. Full OTA has bootloader, radio, and vendor files. No issues so far. The Kernel has a build date of Aug 9 2016. I will wait for Google to fix the bugs and post full OTA's and Factory Images before upgrading to N. This is my primary device, so it needs to work.
SpookyTunes said:
I flashed the full MTC20L OTA from https://developers.google.com/android/nexus/ota over MTC20F. Android Security Patch level: September 6, 2016. The Kernel has a build date of Aug 9 2016. I will wait for Google to fix the bugs and post full OTA's and Factory Images before upgrading. This is my primary device, so it needs to work.
Click to expand...
Click to collapse
I manually do so via fastboot so it's entirely different, but good to know the OTA was fine.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
I manually do so via fastboot so it's entirely different, but good to know the OTA was fine.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
blitzkriegger said:
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
Click to expand...
Click to collapse
I did that a few days ago to MTC20F. More referring to the monthly update from that to L. I suspect it is fine but this whole N thing has been weird.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
I did that a few days ago to MTC20F. More referring to the monthly update from that to L. I suspect it is fine but this whole N thing has been weird.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The android-info.txt located within the images zip mentioned that the same bootloader and radio version as the August zip were required so I thought it was safe to flash away. I guess the non-inclusion of the bootloader/radio on the latest image was accidental.
Indeed N has been weird for a lot of people. I'm just lucky I haven't experienced the issues others were having with N. I just think of the delay in releasing N images as an opportunity to spend a little more time with M stuff. I'm going with the speculation that the full release of N for the 6p has been delayed due to VR. Or another possibility is that official images will debut with the MR1 release.
blitzkriegger said:
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
Click to expand...
Click to collapse
Can you explain step by step to revert back to MM from N ?
ariefabuzaky said:
Can you explain step by step to revert back to MM from N ?
Click to expand...
Click to collapse
Just flash the factory image. Instructions are here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
EDIT: Or, if you're going to restore a previous Nandroid, make sure that you use TWRP 3.0.2-0 or 3.0.2-2.
ariefabuzaky said:
Can you explain step by step to revert back to MM from N ?
Click to expand...
Click to collapse
Okay Buddy. Here are some assumptions prior to doing the steps:
*You have the required adb/fastboot/adb environment configured on your computer as mentioned on the intro of Heisenberg's How-to Guide
*You either have the August factory images or at least a copy of the August bootloader and radio image
*You have the latest September factory image
*You are on TWP 3.0.2-2
Steps:
1.) Copy/paste all important files you have on your phone to your PC.
2.) Next, make sure that the September image files are extracted within the "SDK Tools">"platform-tools" folder on your computer.
3.) Next extract or copy/paste the August bootloader (bootloader-angler-angler-03.54.img) and radio (radio-angler-angler-03.61.img) images within the "SDK Tools">"platform-tools" folder on your computer.
4.) Once you are all set reboot your phone to TWRP recovery first. Once within recovery go to "Wipe">
Advanced Wipe", place a check mark on all items then proceed with the wipe.
5.) If you want a decrypted system like I did, or make everything as clean as can be go to back to "Wipe">"Format Data" and proceed to format data.
6.) After formatting data, my practice is to reboot back to TWRP first. Once back to TWRP I then reboot to fastboot.
7.) Once on fastboot flash the images as specified on item#9 of Hesienberg's guide. Make sure that you execute the reboot-bootloader command after flashing the August bootloader. Also execute the same reboot-bootloader command after flashing August radio. Then flash away the remaining images (except recovery.img if you wish to keep TWRP).
8.) When done flashing all files my practice is to reboot-bootloader again. Then afterwards reboot to system. Then patiently wait for the phone to boot.
Disclaimer:Some of the steps are not fully required. It's just my practice as I flash totally clean.
blitzkriegger said:
Okay Buddy. Here are some assumptions prior to doing the steps:
*You have the required adb/fastboot/adb environment configured on your computer as mentioned on the intro of Heisenberg's How-to Guide
*You either have the August factory images or at least a copy of the August bootloader and radio image
*You have the latest September factory image
*You are on TWP 3.0.2-2
Steps:
1.) Copy/paste all important files you have on your phone to your PC.
2.) Next, make sure that the September image files are extracted within the "SDK Tools">"platform-tools" folder on your computer.
3.) Next extract or copy/paste the August bootloader (bootloader-angler-angler-03.54.img) and radio (radio-angler-angler-03.61.img) images within the "SDK Tools">"platform-tools" folder on your computer.
4.) Once you are all set reboot your phone to TWRP recovery first. Once within recovery go to "Wipe">
Advanced Wipe", place a check mark on all items then proceed with the wipe.
5.) If you want a decrypted system like I did, or make everything as clean as can be go to back to "Wipe">"Format Data" and proceed to format data.
6.) After formatting data, my practice is to reboot back to TWRP first. Once back to TWRP I then reboot to fastboot.
7.) Once on fastboot flash the images as specified on item#9 of Hesienberg's guide. Make sure that you execute the reboot-bootloader command after flashing the August bootloader. Also execute the same reboot-bootloader command after flashing August radio. Then flash away the remaining images (except recovery.img if you wish to keep TWRP).
8.) When done flashing all files my practice is to reboot-bootloader again. Then afterwards reboot to system. Then patiently wait for the phone to boot.
Disclaimer:Some of the steps are not fully required. It's just my practice as I flash totally clean.
Click to expand...
Click to collapse
Thanks you very much mate.
blitzkriegger said:
The android-info.txt located within the images zip mentioned that the same bootloader and radio version as the August zip were required so I thought it was safe to flash away. I guess the non-inclusion of the bootloader/radio on the latest image was accidental.
Indeed N has been weird for a lot of people. I'm just lucky I haven't experienced the issues others were having with N. I just think of the delay in releasing N images as an opportunity to spend a little more time with M stuff. I'm going with the speculation that the full release of N for the 6p has been delayed due to VR. Or another possibility is that official images will debut with the MR1 release.
Click to expand...
Click to collapse
Well, at least updating to the September release via normal flashing process worked fine, too. Really hoping we're not flashing any more MM monthlies ...
Sent from my Nexus 6P using Tapatalk
I DLed the factory image and applied the update via fast boot like I always have. Just been sitting on the animated screen for about 5-10 minutes now. Normally it loads faster after an update.
EDIT: I figured out the problem. The 7.1.2 factory image from Google's site is missing the cache.img file. I just used one of the previous factory images cache.img file and that worked to apply the 7.1.2 update. Not sure if there will be any problems.
You only need to download the full factory image (not the OTA image), extract and flash the system, boot, and vendor *.img files via fastboot. If the bootloader and baseband also need to be updated, those can also be flashed using fastboot.
Google's web site has factory image, full OTA, and vendor images. But the vendor images had two tgz (one fron Huawei, other other from QualComm). Since I am not sure how to flash "tgz", I have downloaded the full OTA, which contained vendor.img. My questions are...
1) It also had radio-xxx.img. When I did not flash it, LineageOS did not complain about it as it did for vendor.img. But is it generally recommended when updating vendor.img, to flash the radio img in the same ZIP as well?
2)Downloading the full OTA may not be efficient. Can I download only the two tgz files, and flash them? How, just like the vendor.img? When I decompressed the tgz file, it only contained one sh file.
No you don't need to update your radio. You do need to update your bootloader though from time to time. Generally it will be specified by the developer.This site has all the up-to -date images so you don't have to waste your time with downloading stock firmware.
I always update my bootloader and radio on every monthly release, and I've switched between stock rom, lineage (currently) and the various roms like Pure Nexus and what not.
BL and Radio aren't tied to a rom, so if you run stock, lineage, or something else, you can safely update to the latest regardless. It won't give you issues.
As per downloading, occasionally some users post them here, however I personally don't like relying on others, so I download every month and check for updates to Radio and BL, flash if required, and then check the ROM if it requires an updated vendor. Example, the most recent nightly of Lineage for the 6P requires the May 2018 vendor, whereas previously it was the one from December (IIRC)
Flash a custom rom directly to your pixel 3a or 3a xl using google factory image zip.
I didnt expect this to work but it did. i flash my pixel 3a alot doing development experiments and found it a hassle to first flash the whole device using the google factory images then using adb sideload to flash the custom rom.
so i had an idea. what if i could flash all the partitions with fresh images and flash the custom rom at the same time. i could then control which slot gets flashed and avoid the process of flashing stock first then rebooting into the bootloader flashing the custom boot then rebooting to the recovery and adb sideloading the custom rom.
AFAIK this will only work for google devices with factory images downloaded from the google factory image site.
so lets get started. Btw i am in no way responsible for any damage this may cause to your device by following this how to. your warranty is now void.
so as you know you should have an unlocked bootloader. I will not go into that process here so you will need to look that up on your own and come back.
so go here and download the latest factory image according to the android version you would like to flash.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
while thats downloading go ahead and grab the payload.bin dumper and set it up. you can find that here.....
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
next find the custom rom you would like to flash according to the android version of the factory image you just downloaded
extract the custom rom zip and cd into the folder created from extracting it. now copy the payload.bin from there and paste it into the payload dumper folder you downloaded and set up in the previous steps and extract the payload.bin
now extract the factory image zip you downloaded according the android version of the custom rom zip and cd into those folders and create a new folder calling it what ever you like but for the intent of this guide call it stockimage.
now extract the contents of the stock image zip into the folder you just created.
now open another window and go to the output of the payload dumper and move the contents of that folder into the stockimage folder you created in the previous step and replace the stock partition images with the custom partition images from the payload dumpers output
when that completes zip up everything in the stockimage folder and name it the same name as the zip in the factory images folder we unzipped earlier. then replace the stock image zip in that folder with the new one we just created.
now rebbot your pixel 3a or 3a xl into the bootloader and run sh flash-all.sh and when it completes you will now boot into the custom rom instead of the factory stock rom.
so now you know how to flash a custom rom all in one shot using fastboot and avoiding the adb sideloading of the custom rom zip.
tested and working on Google Pixel 3A
enjoy