[EMUI8+][WINDOWS] Introducing the HUAWEI Debloater! - Huawei Y6 Themes, Apps, and Mods

EVEN THOUGH THIS TOOL IS SAFE TO USE, DO THIS AT YOUR OWN RISK, DISABLING SYSTEM APPS CAN CAUSE INSTABILITY. I AM NOT RESPONSIBLE FOR YOUR ACTIONS!
So if you're continuing along, BACKUP ANY DATA IN CASE THIS GOES TERRIBLY WRONG.
INSTALLATION INSTRUCTIONS:
- Download the zip file and extract the folders to the root of your C: drive
- Open the HUAWEIDebloater folder
- Open the debloater batch file.
Once you see a command window, make sure you plug your device in and allow USB debugging in developer options. To enable developer options (if you haven't already):
Go to [Settings] -> [System] -> [About phone] and tap on the build number 7 times. Then go back to [System] -> [Developer Options] and enable USB debugging.
Once debloat is done, you can restart the phone.
If you want to enable and undo the changes, run the Undo Changes batch file.
Once the debloat is done, the device will reboot for good measure.
UPDATE 1.2:
- Fixed some apps not disabling
- User is now required to press a key to restart.
NOTE: If running Windows 10, you may see a popup that says "Windows protected your PC", this is because the batch scripts aren't verified by Microsoft and the OS thinks it's malware. so tap "Run anyway" as it WILL NOT damage your computer.

Related

How to install ClockworkMod Recovery on Android 1.5 when permission is denied Cliq XT

Phone is Rooted. Trying to install CyanogenMod by following official instructions: http://wiki.cyanogenmod.com/wiki/Motorola_Cliq_XT:_Full_Update_Guide
Cliq XT phone was never updated from Android 1.5 so directly installing ROM Manager from Market is not an option since it requires Android 2. Trying Method 2 and this part is a problem:
adb push recovery-clockwork-4.0.0.5-zeppelin.img /sdcard/recovery-clockwork-4.0.0.5-zeppelin.img
* * * Permission Denied * * *
There is nothing in official instructions talking about enabling permissions.
EDIT, fixed: I turned the USB drive off on the phone. I guess you are supposed to not turn on USB drive on the phone.
1. I moved image file recovery-clockwork-4.0.0.5-zeppelin.img to
C:\android-sdk-windows\platform-tools
2. Rooted phone can be accessed from Windows and USB Debugging is checked under Phone Settings > Applications > Development
3. Windows DOS prompt
cd android-sdk-windows\platform-tools
adb push recovery-clockwork-4.0.0.5-zeppelin.img /sdcard/recovery-clockwork-4.0.0.5-zeppelin.img
* * * Permission Denied * * *
After that I would try to do the following but there is nothing in official instructions talking about enabling permissions.
adb shell
su
cd /sdcard/
flash_image recovery recovery-clockwork-4.0.0.5-zeppelin.img
reboot recovery
The ClockworkMod Recovery should now be installed on the Motorola Cliq XT.
CyanogenMod 7 for Cliq XT
0. The Cliq XT is known as Zeppelin.
CyanogenMod nightlies changelog: http://cm-nightlies.appspot.com/?device=zeppelin
CyanogenMod nightly download: http://download.cyanogenmod.com/?type=nightly&device=zeppelin
1. Install Motorola USB drivers:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
2. Copy latest version of Google Apps like gapps-gb-20110828-signed.zip and the latest nightly build like cm_zeppelin_full-246.zip to the SD card.
http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
http://download.cyanogenmod.com/?type=nightly&device=zeppelin
3. Install Java SE Runtime Environment (JRE): http://www.oracle.com/technetwork/java/javase/downloads/
4. Get Android SDK zip: http://developer.android.com/sdk/
5. Unzip it and start SDK Manager.exe and download Android SDK Tools.
6. Get ClockworkMod Recovery:
http://download.clockworkmod.com/recoveries/recovery-clockwork-4.0.0.5-zeppelin.img
Copy recovery-clockwork-4.0.0.5-zeppelin.img to
Android SDK folder android-sdk-windows\platform-tools
7. Phone Settings > Applications > Unknown sources (select green check mark to activate it)
Settings > Applications > Development > Enable USB Debugging
Make sure the phone is rooted. Check if Superuser icon is in the drawer menu.
In case of problems, flash back to Blur_Version.1.31.44
*** Connect the phone to computer but DO NOT enable USB Drive ***
8. Use DOS to navigate to the android-sdk-windows\platform-tools directory
for example, if the folder location is C:\android-sdk-windows\platform-tools
then in type this in DOS:
c:
cd android-sdk-windows\platform-tools
adb shell
su
***You must press on Allow on the phone when prompted***
cd /sdcard/
flash_image recovery recovery-clockwork-4.0.0.5-zeppelin.img
reboot recovery
As the phone reboots, hold the Camera button (top of the phone on the right) while phone is powering on.
When prompted, press Volume Down button (bottom of the phone on the right).
9. Use Volume buttons to navigate, Camera button (top of the phone on the right) to select:
wipe data/factory reset > Yes -- delete all user data > * wait for Data wipe to complete * >
10. Use Volume buttons to navigate, Camera button (top of the phone on the right) to select:
wipe cache partition > Yes -- Wipe Cache > * wait for Cache wipe to complete * >
11. Use Volume buttons to navigate, Camera button (top of the phone on the right) to select:
Install zip from sdcard > choose zip from sdcard > CyanogenMod update.zip, for example cm_zeppelin_full-246.zip > Yes - Install cm_zeppelin_fu > * wait for Install from sdcard to complete * >
12. Use Volume buttons to navigate, Camera button (top of the phone on the right) to select:
choose zip from sdcard > Latest version of Google Apps, for example gapps-gb-20110828-signed.zip > Yes - Install gapps-gb-20110 > * wait for install from scdard to complete * >
13. Press Power button to go back to main list > reboot system now
Make a backup of this initial state before starting your personal customizations and app installs:
14. Wait for the first boot to settle, go to your Android drawer and Open ROM Manager app > Backup Current ROM > Install ClockworkMod Recovery when prompted > Allow > Backup Current ROM
• Updating from a previous build:
Open Rom Manager > Install ROM from SD Card > Select the latest nightly >
A window will pop up [Leave Wipe Dalvik CHECKED here]
(optionally, CHECK: Backup Current ROM)

Tecmobile You 25 root

Hello,
After a long time looking ways to root the You 25, I've found the right way to do it.
The You 25 is very similar to Micromax A51, as some users suggested. It is based on broadcom cpu.
Quick characteristics: gb 2,3,7, 256Mb ram, 256Mb rom, 2Gb Sdcard, dual sims, 3g ....
On Win7: Disable antivirus
1) Download unlockroot23
2) Execute unlockroot23
3) Two items:
- execute install driver
- You 25ower off; take off batteryand back ; connect You 25 usb cable to the pc; wait driverdetection (popup tells adb installed or something similar); poweron you25; set it in debug mode and unknown source checked (in settings applications menu) ...
4) Execute unlookroot.exe
2 panes popup opens:
- Click on ROOT (in green) item on the left pane,
- Click on the detected You25 item on the right pane;
Normally rooting is executed (the root button greys on);
Once finished, the You25 reboots (I d'ont remember exactly ...)
After reboot, check for SuperSu icon is there.
Check su with terminal, should ask su access to SuperSu.
Thanks to forii, which I haven't bookmarked. Just in case: Browse with search " Micromax a51 root".
.
Tecmobile you25: Fixing vulnerabilities (trying)
Hello,
After the rooting, I try to fixmaster key vulnerabilities.
With the forii help ,many thanks to them, I come up with a solution:
- Install bluebox from Google play;
- Install Xposed framework for Gingerbread 2.3 (Xposedinstaller-2.2-2013005.apk (1.25Mb)) from androidforums.com);
- Install Master key fix (support Gingerbread) me.piebridge.masterkeyfixgb_v2-0d0824.apk from Xposed module repository repo.xposed.info
Once setup Xposed and install the module, running bluebox shows all fixed.

[Help!] Update System with Terminal Emulator with Error "no space left on device"

[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.

[SOLVED] Soft boot-loop/brick on Eken GC10X Tablet

Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.

How To Guide [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More

[Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—June 2023
Pixel Update Bulletin—June 2023​
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, the order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting them
.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 13 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 13.0.0 (TQ3A.230605.010, Jun 2023)​b. 13.0.0 (TQ3A.230605.010.A1, Jun 2023, T-Mobile, T-Mobile MVNOs)​c. Which one should I use?​
OTA Image
a. 13.0.0 (TQ3A.230605.010, Jun 2023)​b. 13.0.0 (TQ3A.230605.010.A1, Jun 2023, T-Mobile, T-Mobile MVNOs)​c. Which one should I use? ​
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.​
b. Update Platform Tools, regularly, for optimal performance.​
c. Need Google's USB Drivers for your Pixel Phone?​
NEW
Both Slots Bootable
@badabing2003 has found a way to Have both slots bootable.
He has automated the procedure and added it to PixelFlasher.
@Lughnasadh tested the Both Slots Bootable procedure on his Google Pixel 7 Pro and Google Pixel 6 Pro phones: It works!
Android 14 Beta are up.
Builds are only available for the following Pixel devices:
Google Pixel 4a5(G)
Google Pixel 5 and 5a
Google Pixel 6 and 6 Pro
Google Pixel 6a
Google Pixel 7 and 7 Pro
* * * 64-bit-only system images * * *
Google Pixel 4a (5G)
Google Pixel 5
Google Pixel 6
Google Pixel 6 Pro
Android 14 GSI binaries and release
Pixel 4a5(G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a Pro
Pixel 7 and 7 Pro
Update(s)
Factory/OTA Images - 13 June
Android 14 DP
Factory images and OTA images
Android 14 GSI binaries and release
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
a. Google Pixel 6 Pro ROMs, Kernels, Recoveries, & Other​b. ElementalX Kernel Manager​
My Other Guides
Pixel 7 Pro
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
@topjohnwu - Magisk.
vvb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Manually Install/Update Factory Image keep data or wipe data.
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
"Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time
Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.
After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot (seamless updates for more information on slots) of the device. The inactive slot contains an older bootloader whose anti-rollback version has not been incremented. If the active slot is then flashed with a build that fails to boot, the fallback mechanism of seamless updates kicks in and the device tries to boot from the inactive slot. Since the inactive slot contains the older bootloader, the device enters an unbootable state.
To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot"...
If you want to update to the Android 13 Factory image without wiping your phone: Do Flash Factory Image Keep Data (below).
Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
then type
fastboot Reboot
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Upgrading to Android 13
* E D I T - flash-all.bat file *
Flash to current/Active Slot.
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot [update image-oriole-aa9a.999999.999.zip
Note:The -w is removed to Keep Data.
echo Press any key to exit...
pause >nul
exit
Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to new Android Version.
See Flash Other Slot bat file... below, to flash to the other/inactive slot.
* * * * E N D - Edit * * * *
Updating Android 13
Flash to Other/Inactive Slot.
Note: See Flash Other Slot bat file... below.
* * * * Create - Flash Other Slot bat file * * * *
Save Flash Other Slot bat file - as flash-other.bat
Note: To run this file type flash-other at the Command Prompt.
ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
echo This is the slot you are currently on.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
fastboot --set-active=other
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo This is the slot you switched to.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
flash-all
exit
* * E N D - Creating File * *
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Data/Internal Storage.
Do not edit the flash-all.bat file.
If you need to disable Verity and Verification: See Disabling Verity and Verification below.
Disabling Verity and Verification
* E D I T - flash-all.bat file *
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot --set-active=other
fastboot reboot-bootloader
fastboot flash bootloader bootloader-oriole-slider-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-oriole-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot - w update --disable-verity --disable-verification image-oriole-aa9a.999999.999.zip
echo Press any key to exit...
pause >nul
exit
Notes:
The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
Some kernels require Disabling verity and verification
To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
* * * * E N D - Edit * * * *
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
android-info.txt
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
On your phone: Boot the bootloader (fastboot mode) (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot.image from the Factory image:
Extract the Factory Image file that you downloaded (oriole-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-oriole-aa9a.999999.999.zip) into a folder. The stock boot.img file should be in this folder.
Patch the boot.img:
Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Sideload the OTA zip file
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
(Optional) Verify Computer sees your device:
Type: adb devices and press return.
Your device number should shows up with "sideload" next to it.
Sideload the OTA zip file
Select the Apply update from ADB option from the recovery text menu
Type:
adb sideload oriole-ota-aa9a.999999.999-a99999aa.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Note: This slot is bootable and NOT ROOTED
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Sideload the OTA zip file
Type: adb sideload oriole-ota-aa9a.999999.999-a99999aa.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash Magisk_patched....img to root
On the phone: Boot bootloader/fastboot mode
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Note: This slot is bootable and ROOTED.
Done!
Extract Files from Factory Image: flash-all.bat boot/init_boot.img Flash boot/init_boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-oriole-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot/init_boot.img
Flashing the boot/init_boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Android 13
Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot/init_boot image:
Open the Magisk Manager app and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
Extract the boot/init_boot.img file from the Factory Image.
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-oriole-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
Install Magisk Canary - Download app-release.apk
or
Magisk Beta/Stable App
Open Magisk Beta/Canary/Stable App
The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Copy it to a USB drive and transfer it to your computer.
Move it to your computer using adb push
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important, if your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Remove Modules
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
fastboot Reboot.
Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
Read @badabing2003 post
Pass Safety Net with SafetyNet Fix
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 6 ROMs, Kernels, Recoveries, & Other
Other Custom Rom
[ROM][13][raven][oriole] riceDroid 8.0[AOSP][PIXEL]
Themes, Apps, and Mods
Google Pixel 6 Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.
huzzah!
Homeboy76 said:
[Guide] Root Pixel 6 Android 12 with Magisk + Unlock/Lock Bootloader + More
Android Security Bulletin—January 2022
Pixel Update Bulletin—January 2022​
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 5'.
NEW
Understand 5G network...
With the Magisk Canary update to 23016, there is no longer a need to wipe or --disable verity -- disable verification
Magisk Alpha (vvb2060)
Download Link.
The differences between the different variants of Magisk
Magisk Modules for Magisk Alpha/Canary
a. GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it​
b. Fox Magisk Module Manager Releases​
Update(s)
Factory/OTA Images - Jan
Magisk Canary - Magisk-23016 15Dec
TWRP - Waiting for T.R.W.P. for Android 12
SafetyNet - SafetyNetFix v2.2.1 (Zygisk) 22Dec
SDK Platform-tools - r31.0.3 18Aug
Custom ROMs[/INDENT]
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0​
Custom Kernels[/INDENT]
a. ElementalX - Check ElementalX Kernel Manager​
b. [KERNEL] CleanSlate P6 - S1.2.0 |S2S|AdBlock|VIB|BatterySvr [Nov 22] by tbalden​
c. [KERNEL] [blu_spark r45] [A12]​
Custom ROMs
a. ProtonAOSP[12] 01Nov​
b. lineage v18-1 redfin[12] Nightly​
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 12 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)​
b. Which one should I use?​
OTA Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)​
b. Which one should I use?​
A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
Important Notes:
a. Update Platform Tools, regularly, for optimal performance.​
b. Need Google's USB Drivers for your Pixel Phone?​
My Other Guides
My other guides:
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Google - Android 12 factory/OTA images.
@topjohnwu - Magisk.
vb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ INSTRUCTIONS ~ ~ ~ ​
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
Install Magisk Canary 23016
Note: Tap 3 dot menu across from canary => Download, app-debug.apk
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error:while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
to this: fastboot update image-oriole-sq1d.999999.999.zip
Note: If you do not remove the -w your internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Root/Reroot with Magisk and Pass SafetyNet.
Android 12
Upgrade to Android 12: OP, INSTRUCTIONS, Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
Do #6 - Extract boot.img
Install Magisk Canary
Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
Open Magisk Canary App
Set the Update Channel Canary.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes:If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass Safety Net with SafetyNet Fix 2.2.1
Download File(s)
Universal SafetyNet Fix · v2.2.1 (Zygisk)
Why Zygisk?
Install SafetyNet Fix 2.2.1
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the SafetyNetFix file you downloaded
Tap the SafetyNetFix file
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk and Enforce DenyList.
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
Optional Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll down to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification.
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-sp1d.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-oriole-sp1d.999999.999.zip) into the folder.
Copy the boot.img file to the computer's Platform-tools folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Custom ROMs
Need help with a Custom ROM?
First, read and follow the Installation Instructions. The installation instructions are in the OP.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
None
Unofficial
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Apps/Mods/Scripts/Tethering/Themes
Tulsadiver's Mods
Stand alone Clock, Navbargone, etc. Mods
Quick Pull down Tile-Accent Colors
ADB Font Installer including the lockscreen clock
ADB Magisk Module Mod Maker
Other Mods
[MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
aodNotify - Notification Light / LED for Pixel 6!
How-To Enable Two-Button Navigation on Android 12 (Root Required)!
Audio switcher
T.W.R.P. Backup/Restore
Waiting for Android 12 T.W.R.P.
Click to expand...
Click to collapse
Great resource, thanks. Think you can put it in the How To Guide so it's easy to find?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
bobby janow said:
Great resource, thanks. Think you can put it in the How To Guide so it's easy to find?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
XDA Staff moved it. Are you suggesting I should make a Guide for the Pixel 6 Pro?
Thank you @Homeboy76 as always your guides are excellent.
Nice.!
I put this thread on the watch list incase I have a brain fart. And need to find a good reference for what I am working on at that moment.
Homeboy76 said:
XDA Staff moved it. Are you suggesting I should make a Guide for the Pixel 6 Pro?
Click to expand...
Click to collapse
For sure! Depending on your time committments that would be great.
When I go to patch the boot.img I get an error in Magisk
Code:
- Device platform: arm64-v8a
- Installing 92546e8a (23016)
! Process error
! Installation failed
In the logs, I see the following error in the stack trace
Code:
java.io.FileNotFoundException: /storage/emulated/0/boot.img: open failed: EACCES (Permission denied)
It seems like Magisk doesn't have permission to access the boot image?
EDIT:
Nevermind, it was caused by the app I was using to select the file. I used Google's default Files app and that fixed it
As always, great work! Boomarked in case i have a brain fart
Homeboy76 said:
[Guide] Root Pixel 6 Android 12 with Magisk + Unlock/Lock Bootloader + More
Android Security Bulletin—January 2022
Pixel Update Bulletin—January 2022​
Introduction
This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 6'.
NEW
Understand 5G network...
With the Magisk Canary update to 23016, there is no longer a need to wipe or --disable verity -- disable verification
Magisk Alpha (vvb2060)
Download Link.
The differences between the different variants of Magisk
Magisk Modules for Magisk Alpha/Canary
a. GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it​
b. Fox Magisk Module Manager Releases​
Update(s)
Factory/OTA Images - Jan
Magisk Canary - Magisk-23016 15Dec
TWRP - Waiting for T.R.W.P. for Android 12
SafetyNet - SafetyNetFix v2.2.1 (Zygisk) 22Dec
SDK Platform-tools - r31.0.3 18Aug
Custom ROMs[/INDENT]
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0​
Custom Kernels[/INDENT]
a. ElementalX - Check ElementalX Kernel Manager​
b. [KERNEL] CleanSlate P6 - S1.3.1 |S2S|AdBlock|VIB|BatterySvr [Jan 15] tbalden​
c. [KERNEL] [blu_spark r45] [A12]​
Custom ROMs
a. ProtonAOSP[12] 01Nov​
b. lineage v18-1 redfin[12] Nightly​
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 6 phone with an unlocked bootloader.
The latest Android 12 Factory or OTA Image: "oriole" for Pixel 6
Factory Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)​
b. Which one should I use?​
OTA Image
a. 12.0.0 (SQ1D.220105.007, Jan 2022)​
b. Which one should I use?​
A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
Important Notes:
a. Update Platform Tools, regularly, for optimal performance.​
b. Need Google's USB Drivers for your Pixel Phone?​
My Other Guides
My other guides:
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Google - Android 12 factory/OTA images.
@topjohnwu - Magisk.
vvb2060 - Magisk alpha.
Those I may have, inadvertently, forgotten.
~ ~ ~ INSTRUCTIONS ~ ~ ~ ​
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
Install Magisk Canary 23016
Note: Tap 3 dot menu across from canary => Download, app-debug.apk
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
If you get an error:while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 6 - oriole to your Computer.
Extract the factory Image to a folder.
Flash Factory Image Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
to this: fastboot update image-oriole-sq1d.999999.999.zip
Note: If you do not remove the -w your internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is completed.
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-oriole-....img
flash-all.bat
image-oriole-....zip
radio-oriole-....img
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Root/Reroot with Magisk and Pass SafetyNet.
Android 12
Upgrade to Android 12: OP, INSTRUCTIONS, Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
Do #6 - Extract boot.img
Install Magisk Canary
Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
Open Magisk Canary App
Set the Update Channel Canary.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes:If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass Safety Net with SafetyNet Fix 2.2.1
Download File(s)
Universal SafetyNet Fix · v2.2.1 (Zygisk)
Why Zygisk?
Install SafetyNet Fix 2.2.1
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the SafetyNetFix file you downloaded
Tap the SafetyNetFix file
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk and Enforce DenyList.
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
Optional Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll down to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification.
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 12 (R) T.W.R.P
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Extract the Factory Image file (oriole-sp1d.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-oriole-sp1d.999999.999.zip) into the folder.
Copy the boot.img file to the computer's Platform-tools folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Custom ROMs
Need help with a Custom ROM?
First, read and follow the Installation Instructions. The installation instructions are in the OP.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
ROMs
Alpha/Beta
None
Official
None
Unofficial
[ROM][SNOWCONE][oriole][12] StatiXOS v5.0
Apps/Mods/Scripts/Tethering/Themes
Tulsadiver's Mods
Stand alone Clock, Navbargone, etc. Mods
Quick Pull down Tile-Accent Colors
ADB Font Installer including the lockscreen clock
ADB Magisk Module Mod Maker
Other Mods
[MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
aodNotify - Notification Light / LED for Pixel 6!
How-To Enable Two-Button Navigation on Android 12 (Root Required)!
Audio switcher
T.W.R.P. Backup/Restore
Waiting for Android 12 T.W.R.P.
Click to expand...
Click to collapse
C:\Users\Derek>fastboot flash boot C:\Users\Derek\Desktop\magisk_patched-23016_zt99Y.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.853s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.869s
This is the error i get. Even when trying the stock boot.img
What can i do to fix this?
deadliving said:
C:\Users\Derek>fastboot flash boot C:\Users\Derek\Desktop\magisk_patched-23016_zt99Y.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.853s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.869s
This is the error i get. Even when trying the stock boot.img
What can i do to fix this?
Click to expand...
Click to collapse
I'm assuming you have the latest version of SDK Platform-tools r. 31.0.3 installed on your computer, there are no typing errors on the command fastboot..., USB debugging is enabled, and fastboot.exe is in this folder:
C:\Users\Derek\Desktop
Try opening Command Prompt in this folder:
C:\Users\Derek\Desktop
Then type:
fastboot flash boot magisk_patched-23016_zt99Y.img to flash it.
After jan. Update my device when rebooting shows ypur device is corrupted before the unlocked bootloader screen warning is this normal? Wasnt there in dec. Update
Nightf0x_007 said:
After jan. Update my device when rebooting shows ypur device is corrupted before the unlocked bootloader screen warning is this normal? Wasnt there in dec. Update
Click to expand...
Click to collapse
No!
Curious, how did you update your phone?
Homeboy76 said:
No!
Curious, how did you update your phone?
Click to expand...
Click to collapse
This is how i updated to dec.
-Executed flash-all flashed bootloader & radio but didnt want to update the device
- fastboot update the image
- fastboot boot magisk patched image
- opened magisk and directly installed magisk
Nightf0x_007 said:
This is how i updated to dec.
-Executed flash-all flashed bootloader & radio but didnt want to update the device
- fastboot update the image
- fastboot boot magisk patched image
- opened magisk and directly installed magisk
Click to expand...
Click to collapse
"Executed flash-all flashed bootloader & radio but didnt want to update the device"
What?
Homeboy76 said:
"Executed flash-all flashed bootloader & radio but didnt want to update the device"
What?
Click to expand...
Click to collapse
Flash-all without -w
Nightf0x_007 said:
Flash-all without -w
Click to expand...
Click to collapse
Did you patch the boot.img with magisk-canary_23016?
Homeboy76 said:
Did you patch the boot.img with magisk-canary_23016?
Click to expand...
Click to collapse
Yes ofcourse, i might end up backing up my data and resetting and flash protonaosp
Update!
Magisk Canary 23017
@Homeboy76
Is this link correct?
Google Pixel 5 - LineageOS 18.1
LineageOS 18.1 Changelog for Google Pixel 5 (redfin). This page is listing the official LineageOS 18.1 (Android 11 11.0) changes and downloads for Google Pixel 5 (redfin).
www.lineageoslog.com
It points to Pixel 5

Categories

Resources