Mi Max 2 Stock Rom Fastboot

[Siri]

Thispage contains binary image files that allow you to restore your Nexusor Pixel device's original factory firmware. You will find these files usefulif you have flashed custom builds on your device, and wish to return yourdevice to its factory state.

These files are for use only on your personal Nexus or Pixel devices and maynot be disassembled, decompiled, reverse engineered, modified or redistributedby you or used in any way except as specifically set forth in the licenseterms that came with your device.

After taking an Android 13 update and successfully booting the device postupdate, an Android 12 build resides in the inactive slot (seamless updatesfor more information on slots) of the device. The inactive slot contains anolder bootloader whose anti-rollback version has not been incremented.If the active slot is then flashed with a build that fails to boot, thefallback mechanism of seamless updates kicks in and the device tries toboot from the inactive slot. Since the inactive slot contains the olderbootloader, the device enters an unbootable state.

To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, orPixel 6 Pro device with an Android 13 build for the first time, pleaseflash the bootloader partition to the inactive slot after successfullyupdating and booting into Android 13 at least once. This can be done byfollowing these steps:

Option 1 (recommended):After a successful boot into Android 13 for the first time, sideload thefull OTA image corresponding tothat build and reboot the device to ensure that both slots have a bootableimage.

Extract the contents of the factory ROM .zip file, identify thebootloader image in the extracted files, and follow the sequence of eventsas listed below to flash the bootloader to both the slots. Substitute thename of the bootloader image with that of your device for the Pixel 6 andPixel 6a.

Flash the Android 13 bootloader to the inactive slot. The following commandis specific to a particular build of a Pixel 6 Pro device. Substitute thename of the bootloader image determined in the first step above, ifdifferent, for the image file name argument.

After flashing the inactive slot bootloader to an Android 13 bootloader,reboot to that slot to ensure that the bootloader will be marked asbootable. Important: Please run the exact sequence of commands as listedbelow. Don't forget to enter the full line fastboot reboot bootloader whenrebooting. Failure to do so may leave your device in an unbootable state.

While it may be possible to restore certain data backed up to your GoogleAccount, apps and their associated data will be uninstalled. Before proceeding,please ensure that data you would like to retain isbacked up to your Google Account.

Downloading of the system image and use of the device software is subject to theGoogle Terms of Service. Bycontinuing, you agree to theGoogle Terms of Service andPrivacy Policy. Yourdownloading of the system image and use of the device software may also besubject to certain third-party terms of service, which can be found inSettings > About phone > Legal information, or as otherwise provided.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Hi, fellow fairphoners!

I used my fairphone4 happily for almost 2 years now with calyxOS and felt like i wasnt missing a thing, but ive now upgraded to a fairphone5, and handed my 4 down to my GF.

Im somewhat stuck reverting to stock now tho. Ive downloaded the most recent fastboot package from here and ran the .sh file from cli. Im on EndeavourOS (Arch) and my platform-tools are correctly installed und working. I work with adb and fastboot a lot so i can warrant for that, as you can also see below.

cool /sarcasm.

I saw that post with one eye but apparently didnt want it to be true, so kept looking

Weirdly i got the same error from my windows-vm but didnt check the version there.Will come back with attempt from another version!

so yeah, this is aparently an issue with the specifically packaged fastboot version for arch. Using the officially supplied binary from google got me to actually run the flashing script successfully. Thanks for the assistance!

I'm selling my Pixel 7 Pro, which has been running GrapheneOS for almost a year. I recently followed the "Side of Burritos" tutorial to revert to the stock OS. Everything went smoothly until the last step, where I realized that you need to remove the non-stock key before locking the bootloader, which wasn't mentioned earlier in the tutorial.

Unfortunately, at that point, the GrapheneOS web installer failed to recognize my Pixel when connected via the Android Flash Tool. Despite this, my Pixel successfully booted with stock Android, and I confirmed its functionality by adding my card to Google Wallet.

My question is whether there has been an update to the Android Flash Tool that automatically removes the non-stock key, or if there is something I need to address before selling my device. Any insights would be appreciated.

[deleted] Ok, so I've read through that site you linked to and it's all a bunch of Greek to me. Maybe this is a stupid question but is that the same thing as terminal on Mac? Do I connect my pixel to my Mac and paste the command in the terminal?

Installation of the stock OS via the stock factory images is the same process described above. However, before flashing and locking, there's an additional step to fully revert the device to a clean factory state.

The GrapheneOS factory images flash a non-stock Android Verified Boot key which needs to be erased to fully revert back to a stock device state. Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it:

Fawkes If you think it'll make things easier for you sure. Once you'll be reverting back to stock again, you remove it right after you get into fastboot mode and before flashing the stock factory image (using Android Flash Tool).

lk2nd/lk1st provides automatic device and hardware detection, additional bootloader features like file system boot, Dual Booting (booting from SD card) and additional firmware features, which include initializing secondary CPU cores and various debugging commands that allow better understanding of the hardware for research and development purposes.

Note: If your stock bootloader uses the same key combinations, you need to wait a bit before pressing the volume keys. Usually, waiting until the screen turns on and/or the device vibrates should be enough to make the stock bootloader ignore the keys.

Note: fastboot flash boot boot.img will flash the actual boot image with 512 KiB offset into the boot partition. This is done to avoid replacing lk2nd (since it is also booted from the boot partition).

If the device shows up via fastboot you can get a log file from lk2nd using fastboot oem lk_log && fastboot get_staged , where is either some text file to write to (e.g. output.txt) or /dev/stdout to write the log to standard output.

Currently known solutions are to flash Android Lollipop 5.1 or above firmware to get a better bootloader, or flash TZ/HYP firmware from DragonBoard 410c, which is DANGEROUS. Otherwise you will have to comment out unused device trees to avoid that the bootloader gets confused.

If you have trouble with the installation process, ask for help on the official GrapheneOS chat channel. There are almost always people around willing to help with it. Before asking for help, make an attempt to follow the guide on your own and then ask for help with anything you get stuck on.

You need a USB cable for attaching the device to a laptop or desktop. Whenever possible, use the high quality standards compliant USB-C cable packaged with the device. If your computer doesn't have any USB-C ports, you'll need a high quality USB-C to USB-A cable. You should avoid using a USB hub such as the front panel on a desktop computer case. Connect directly to a rear port on a desktop or the ports on a laptop. Many widely distributed USB cables and hubs are broken and are the most common source of issues for installing GrapheneOS.

Installing from an OS in a virtual machine is not recommended. USB passthrough is often not reliable. To rule out these problems, install from an OS running on bare metal. Virtual machines are also often configured to have overly limited memory and storage space.

You need one of the officially supported devices. To make sure that the device can be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier variants of Pixels use the same stock OS and firmware with a non-zero carrier id flashed onto the persist partition in the factory. The carrier id activates carrier-specific configuration in the stock OS including disabling carrier and bootloader unlocking. The carrier may be able to remotely disable this, but their support staff may not be aware and they probably won't do it. Get a carrier agnostic device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id and the hardware is the same.

It's best practice to update the device before installing GrapheneOS to have the latest firmware for connecting the device to the computer and performing the early flashing process. Either way, GrapheneOS flashes the latest firmware early in the installation process.

Next, go to Settings > System > Developer options and toggle on the OEM unlocking setting. On device model variants (SKUs) which support being sold as locked devices by carriers, enabling OEM unlocking requires internet access so that the stock OS can check if the device was sold as locked by a carrier.

3a8082e126