[Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More

Search This thread
By:
Advanced…
H

Homeboy76

Senior Member
Aug 24, 2012
3,692
2,175
Google Pixel XL
Google Pixel 7 Pro
T

tortelo

Member
Aug 4, 2022
13
2
Just gave rooting my phone another try.

I unlocked bootloader, then followed the steps under "Root/Reroot with Magisk and Pass SafetyNet" with the factory image "13.0.0 (TQ1A.230205.002, Feb 2023)".

When loading, my phone now bootloops 2-3 times, then displays:

Android Recovery
google/redfine/redfin
13/TQ1A.221205.011/9244662
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

There I can choose between "Try again" and "Factory data reset".

Why does this happen and how do I fix it? I don't mind losing the data on the phone.
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,692
2,175
Google Pixel XL
Google Pixel 7 Pro
tortelo said:
Just gave rooting my phone another try.

I unlocked bootloader, then followed the steps under "Root/Reroot with Magisk and Pass SafetyNet" with the factory image "13.0.0 (TQ1A.230205.002, Feb 2023)".

When loading, my phone now bootloops 2-3 times, then displays:

Android Recovery
google/redfine/redfin
13/TQ1A.221205.011/9244662
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

There I can choose between "Try again" and "Factory data reset".

Why does this happen and how do I fix it? I don't mind losing the data on the phone.
Click to expand...
Click to collapse
Did you use SDK Platform-tools r.33.0.3?

Try: PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones by @badabing2003
 
  • Like
Reactions: badabing2003
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,872
2,457
tortelo said:
I think not. The file I download was called "platform tools_r34.0.0 windows.zip". I don't know how I can check the version of my platform tools.
Click to expand...
Click to collapse
Code: 
adb --version
Should tell you, should like that is your issue.
Replace the Android platform tools with version 33.0.3
Get into bootloader mode
Repeat flashing and you should be fine.
 
  • Like
Reactions: Homeboy76
T

tortelo

Member
Aug 4, 2022
13
2
badabing2003 said:
Code: 
adb --version
Should tell you, should like that is your issue.
Replace the Android platform tools with version 33.0.3
Get into bootloader mode
Repeat flashing and you should be fine.
Click to expand...
Click to collapse
I did check and had initially indeed used platform tools version 34. I still have the historical version 33.0.3 installed and re-flashed using it. I then started my phone.

The Google logo appeared for a short time, then I am presented with some minimal bootloader showing the following text alongside a red triangle with an exclamation mark inside:

"Press power button to continue

Your device is corrupt. It can't be trusted and may not work properly.

Visit this link on another device:
g.co/ABH"

If I press the power button, I get through to the usual bootloader with the amber triangle and an exclamation mark, though the text is not rendered properly.


In the usual bootloader I can press the power button, then the Google logo will appear and not change. (I left the phone in this state for 8 hours yesterday night to see if anything would happen after a while.)
 
Last edited:
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,872
2,457
tortelo said:
I did check and had initially indeed used platform tools version 34. I still have the historical version 33.0.3 installed and re-flashed using it. I then started my phone.

The Google logo appeared for a short time, then I am presented with some minimal bootloader showing the following text alongside a red triangle with an exclamation mark inside:

"Press power button to continue

Your device is corrupt. It can't be trusted and may not work properly.

Visit this link on another device:
g.co/ABH"

If I press the power button, I get through to the usual bootloader with the amber triangle and an exclamation mark, though the text is not rendered properly.


In the usual bootloader I can press the power button, then the Google logo will appear and not change. (I left the phone in this state for 8 hours yesterday night to see if anything would happen after a while.)
Click to expand...
Click to collapse
Are you doing anything other than running flash_all script?
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,872
2,457
tortelo said:
Would it be worth it to try to return phone to stock using the Android flash tool? Or could that mess with another repair attempt later on?
Click to expand...
Click to collapse
what you;'re doing is just patching the boot, but you have a messed up system that did not complete flashing all the partitions, those need to be fixed.
You can use any method you like to flash full factory image, Android Flash tool would work.
Once you fix it, then worry about patching to have root.
 
  • Like
Reactions: Homeboy76
T

tortelo

Member
Aug 4, 2022
13
2
badabing2003 said:
what you;'re doing is just patching the boot, but you have a messed up system that did not complete flashing all the partitions, those need to be fixed.
You can use any method you like to flash full factory image, Android Flash tool would work.
Once you fix it, then worry about patching to have root.
Click to expand...
Click to collapse
Thanks, I used the Android Flash tool to flash the full factory image, then your tool to patch and flash. Works perfectly now.
 
  • Like
Reactions: badabing2003
Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
4,952
5,714
Google Nexus 5
Huawei Nexus 6P
  • Like
Reactions: Homeboy76
H

Homeboy76

Senior Member
Aug 24, 2012
3,692
2,175
Google Pixel XL
Google Pixel 7 Pro
  • Haha
Reactions: Lughnasadh
PirateNL

PirateNL

Senior Member
Aug 15, 2010
106
11
LG Optimus G
LG Optimus 2x
Hi guys,

I want to install LineageOS on my Pixel 5 and I'm currently in the process of unlocking the bootloader and rooting. I'm following the official guide over here: https://wiki.lineageos.org/devices/redfin/install

I think I managed to unlock the bootloader as it says "UNLOCKED". However secure boot looks be still enabled? This is the output of the fastboot screen:

Code: 
Fastboot mode
Product revision: redfin MP1.0(ROW)
Bootloader version: r3-0.5-9150479
Baseband version: g7250-00220-221017-B-9183951
Serial Number: <removed>
Secure boot: PRODUCTION
NOS production: yes
DRAM: 8GB Hynix LPDDR4X
UFS: 128GB SKHynix
Device State: unlocked
Boot slot: a

Then when I try to do a factory reset in recovery, I get these weird errors, I believe the wiping process is unable to fully remove the encryption.

Code: 
[  225.264874] -- Wiping data...
[  225.331454] ERROR:   recovery: [libfs_mgr]Unable to enable ext4 verity on /dev/block/by-name/metadata because /system/bin/tune2fs is missing
[  225.950192] ERROR: cutils-trace: Error opening trace file: No such file or directory (2)
[  225.988250] Formatting /data...
[  228.079107] warning: wipe_block_device: Wipe via secure discard failed, used discard instead
[  228.079208] I:format_volume: wipe metadata encrypted /dev/block/bootdevice/by-name/userdata with size 117155278848
[  228.147012] Wiping Titan M...
[  228.177912] ERROR: libnos_datagram: can't send spi message: Try again
[  228.271275] ERROR: libnos_datagram: can't send spi message: Try again
[  228.347925] ERROR: libnos_datagram: can't send spi message: Try again
[  228.400876] ERROR: libnos_datagram: can't send spi message: Try again
[  228.514532] ERROR: libnos_datagram: can't send spi message: Try again
[  228.633100] ERROR: libnos_datagram: can't send spi message: Try again
[  228.750409] ERROR: libnos_datagram: can't send spi message: Try again
[  228.883519] ERROR: libnos_datagram: can't send spi message: Try again
[  229.015105] ERROR: libnos_datagram: can't send spi message: Try again
[  229.166389] ERROR: libnos_datagram: can't send spi message: Try again
[  229.332746] ERROR: libnos_datagram: can't send spi message: Try again
[  229.499162] ERROR: libnos_datagram: can't send spi message: Try again
[  229.682214] ERROR: libnos_datagram: can't send spi message: Try again
[  229.865296] ERROR: libnos_datagram: can't send spi message: Try again
[  230.064942] ERROR: libnos_datagram: can't send spi message: Try again
[  230.264678] ERROR: libnos_datagram: can't send spi message: Try again
[  230.480985] ERROR: libnos_datagram: can't send spi message: Try again
[  230.696342] ERROR: libnos_datagram: can't send spi message: Try again
[  230.930310] ERROR: libnos_datagram: can't send spi message: Try again
[  231.161764] ERROR: libnos_datagram: can't send spi message: Try again
[  231.412928] ERROR: libnos_datagram: can't send spi message: Try again
[  231.679882] ERROR: libnos_datagram: can't send spi message: Try again
[  231.944834] ERROR: libnos_datagram: can't send spi message: Try again
[  232.229021] ERROR: libnos_datagram: can't send spi message: Try again
[  232.510621] ERROR: libnos_datagram: can't send spi message: Try again
[  232.811927] ERROR: libnos_datagram: can't send spi message: Try again
[  233.118753] Data wipe complete.

Although I'm able to flash LineageOS, and the ROM seems to work stable and fine; the OTA update functionality does not work, return yet another "Error applying update: 7(ErrorCode:: kInstallDeviceOpenError)" error.

These errors indicate to me that something must have gone wrong while I was unlocking the bootloader as wiping and updating secure boot-related components are not working.

I'm open to all ideas/suggestions. Thank you!
 
H

Homeboy76

Senior Member
Aug 24, 2012
3,692
2,175
Google Pixel XL
Google Pixel 7 Pro
PirateNL said:
Hi guys,

I want to install LineageOS on my Pixel 5 and I'm currently in the process of unlocking the bootloader and rooting. I'm following the official guide over here: https://wiki.lineageos.org/devices/redfin/install

I think I managed to unlock the bootloader as it says "UNLOCKED". However secure boot looks be still enabled? This is the output of the fastboot screen:

Code: 
Fastboot mode
Product revision: redfin MP1.0(ROW)
Bootloader version: r3-0.5-9150479
Baseband version: g7250-00220-221017-B-9183951
Serial Number: <removed>
Secure boot: PRODUCTION
NOS production: yes
DRAM: 8GB Hynix LPDDR4X
UFS: 128GB SKHynix
Device State: unlocked
Boot slot: a

Then when I try to do a factory reset in recovery, I get these weird errors, I believe the wiping process is unable to fully remove the encryption.

Code: 
[  225.264874] -- Wiping data...
[  225.331454] ERROR:   recovery: [libfs_mgr]Unable to enable ext4 verity on /dev/block/by-name/metadata because /system/bin/tune2fs is missing
[  225.950192] ERROR: cutils-trace: Error opening trace file: No such file or directory (2)
[  225.988250] Formatting /data...
[  228.079107] warning: wipe_block_device: Wipe via secure discard failed, used discard instead
[  228.079208] I:format_volume: wipe metadata encrypted /dev/block/bootdevice/by-name/userdata with size 117155278848
[  228.147012] Wiping Titan M...
[  228.177912] ERROR: libnos_datagram: can't send spi message: Try again
[  228.271275] ERROR: libnos_datagram: can't send spi message: Try again
[  228.347925] ERROR: libnos_datagram: can't send spi message: Try again
[  228.400876] ERROR: libnos_datagram: can't send spi message: Try again
[  228.514532] ERROR: libnos_datagram: can't send spi message: Try again
[  228.633100] ERROR: libnos_datagram: can't send spi message: Try again
[  228.750409] ERROR: libnos_datagram: can't send spi message: Try again
[  228.883519] ERROR: libnos_datagram: can't send spi message: Try again
[  229.015105] ERROR: libnos_datagram: can't send spi message: Try again
[  229.166389] ERROR: libnos_datagram: can't send spi message: Try again
[  229.332746] ERROR: libnos_datagram: can't send spi message: Try again
[  229.499162] ERROR: libnos_datagram: can't send spi message: Try again
[  229.682214] ERROR: libnos_datagram: can't send spi message: Try again
[  229.865296] ERROR: libnos_datagram: can't send spi message: Try again
[  230.064942] ERROR: libnos_datagram: can't send spi message: Try again
[  230.264678] ERROR: libnos_datagram: can't send spi message: Try again
[  230.480985] ERROR: libnos_datagram: can't send spi message: Try again
[  230.696342] ERROR: libnos_datagram: can't send spi message: Try again
[  230.930310] ERROR: libnos_datagram: can't send spi message: Try again
[  231.161764] ERROR: libnos_datagram: can't send spi message: Try again
[  231.412928] ERROR: libnos_datagram: can't send spi message: Try again
[  231.679882] ERROR: libnos_datagram: can't send spi message: Try again
[  231.944834] ERROR: libnos_datagram: can't send spi message: Try again
[  232.229021] ERROR: libnos_datagram: can't send spi message: Try again
[  232.510621] ERROR: libnos_datagram: can't send spi message: Try again
[  232.811927] ERROR: libnos_datagram: can't send spi message: Try again
[  233.118753] Data wipe complete.

Although I'm able to flash LineageOS, and the ROM seems to work stable and fine; the OTA update functionality does not work, return yet another "Error applying update: 7(ErrorCode:: kInstallDeviceOpenError)" error.

These errors indicate to me that something must have gone wrong while I was unlocking the bootloader as wiping and updating secure boot-related components are not working.

I'm open to all ideas/suggestions. Thank you!
Click to expand...
Click to collapse
Post your question on this thread: [ROM][OFFICIAL][redfin] LineageOS 20 by aleasto
 
You must log in or register to reply here.

Similar threads

M
[Guide] Flash Magisk on Android 12
Replies
370
Views
79K
K
kartikeya98
V0latyle
[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
410
Views
38K
A
ankutsa
R
[Tutorial] Unlock Bootloader, get root and valid Safetynet
Replies
305
Views
56K
V0latyle
V0latyle
Az Biker
UPDATING Pixel 5 Factory Image & Re-Rooting
Replies
47
Views
15K
{davros}
{davros}
S
[Video][Tutorial] How to enable 5G for Unlisted Countries on Pixel 4a(5G) and Pixel 5 using QPST.
Replies
74
Views
21K
P
prith

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    H
    Homeboy76
    SDK Platform-tools Update
    SDK Platform-tools r34.0.0 and r34.0.1 are not working.

    Use SDK Platform-tools r33.0.3: https://forum.xda-developers.com/t/...der-pass-safetynet-more.4187609/post-88261743
    View
    1
    omartins
    omartins
    Homeboy76 said:
    SDK Platform-tools
    Several members of the XDA community have
    written posts that SDK Platform-tools r34.0.1 broken. Problem: fastbootd not working

    SDK Platform-tools r33.0.3 is attached : OP post #769
    Click to expand...
    Click to collapse
    Always on the edge 😅 (thank you)

    Nevertheless, why not add this same alert to OP or / and attach r33.0.3 to the same post?
    View
    1
    H
    Homeboy76
    omartins said:
    Always on the edge 😅 (thank you)

    Nevertheless, why not add this same alert to OP or / and attach r33.0.3 to the same post?
    Click to expand...
    Click to collapse
    Excellent suggestion, I added a link to SDK Platform-tools rev. 33.0.3 to the OP and attach SDK Platform-tools rev. 33.0.3 to the same post, kinda.
    View
    1
    badabing2003
    badabing2003
    FritzM said:
    Just wondering if there is a reason not to use rev. 34.0.0?
    Click to expand...
    Click to collapse
    just 3 or 4 posts before yours, @Homeboy76 clearly stated the reason, it applies to 34.0.0 and 34.0.1
    View
    1
    F
    FritzM
    badabing2003 said:
    Are you saying that it worked after you installed a driver from that post?
    I personally would not dare trust that.
    1- Source is not from the official Google.
    2- Unisgned, yet it says Google?
    Click to expand...
    Click to collapse
    Now that I think about it, I don't know why I did not get it from Google! Thanks for raising that mistake. I checked all the SHA256 hashes for the files and they all match with the files from your Google link. Also, the device manager shows the driver as signed by Google and did not prompt during the driver installation saying anything about not signed. Below is a screenshot from the Device Manager on PC.
    driver.jpg
    .

    I updated the driver to the version from your Google link and the content in above screenshot did not change.
    I guess I was lucky this time, but I will remember this! Thanks again.
    View
  • 51
    H
    Homeboy76
    [Guide] Root Pixel 5 with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—March 2023
    Pixel Update Bulletin—March 2023    ​

    Introduction
    This Guide is for Pixel 5 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 ~ ~ ~
    1. 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.
        .
    2. Prerequisites

    3. Update(s)

      1. Factory/OTA Images - 13 Mar
      2. Magisk Alpha - app-release_555a54ec-alpha.apk 2 Sep
      3. Magisk Beta - 25.2 21Jul
      4. Magisk Canary
        Note: Magisk Canary 25207, 25208, 25209 (some devices), and 25210 are broken.
        - Use Magisk Canary 25206
        - Tap the 3 dot menu across from 5b2934603f => Tap Go to file =>
        Tap app-release.apk => Tap the 3 dot menu across from 10.9 MB => Tap Download
      5. Magisk Cygisk - Click Pages 5 for installation Instructions.
      6. Magisk Delta - app-release
      7. Magisk Stable - 25.2 21Jul
      8. TWRP - 370_11-0... 04Oct - Waiting for T.R.W.P. for Android 13
      9. SafetyNet - kdrag0n safetynet-fix-v2.4.0.zip 09Jan
        This version only supports Zygisk (Magisk 24 and newer).
      10. SDK Platform-tools - r33.0.3 Aug 2022
      11. Custom Kernels
    4. NEW

      • "...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."

        Magisk General Support / Discussion

        This is the place for general support and...
        forum.xda-developers.com forum.xda-developers.com
      • Android 14 Beta are up.
        Builds are only available for the following Pixel devices:

        1. Google Pixel 4a5(G)
        2. Google Pixel 5 and 5a
        3. Google Pixel 6 and 6 Pro
        4. Google Pixel 6a
        5. Google Pixel 7 and 7 Pro
      • Android 13 QPR3 beta images are up.
        Release notes - for QPR3 beta
        1. Factory Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • 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
        2. OTA Images
          Builds are only available for the following Pixel devices:

          • Google Pixel 4a and 4a (5G)
          • Google Pixel 5 and 5a
          • Google Pixel 6 and 6 Pro
          • Google Pixel 6a
          • Google Pixel 7 and 7 Pro
    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    (The Instructions listed below are not steps, they are individual sets of instructions.)
    1. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. 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.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. 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

        1. Backup your data/Internal storage
        2. Use the Android flash tool:
          select Wipe => Force Flash Partitions => Lock Bootloader.
      • Lock Bootloader

        1. If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.
    2. Install/Update Factory Image keep data, wipe data, or try badabing2003 PixelFlasher

      • Important Note(s):

        1. If the previous factory image was rooted (you used Magisk to patch the boot.img of the previous factory image). Open Magisk manager and disable all Magisk modules.
        2. If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash Factory Image Keep Data (below).
        3. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 5 - redfin.
        4. 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.
        5. 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

            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. 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
            4. fastboot Reboot
          • If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
            Please post Comments/Discussions/Questions about PixelFlasher on that thread.
        6. Backup your data
        7. Download the latest Factory Image: Pixel 5 - redfin to your Computer.
        8. 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 Android 13
          * E D I T - flash-all.bat file *
          Flash to current/Active Slot.
          * * * S T A R T - E D I T * * *
          @Echo off

          PATH=%PATH%;"%SYSTEMROOT%\System32"
          fastboot flash bootloader bootloader-redfin-a9-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin-a9999-99999-999999-b-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-redfin-aa9a.999999.999.zip
          Note:The -w is removed to Keep Data.
          echo Press any key to exit...
          pause >nul
          exit
          * * * * E N D - E D I T * * * *
          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.
          * * * * * E N D * * * * *
        • Flash Other Slot bat file - Save 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:
          1. bootloader-redfin-....img
          2. flash-all.bat
          3. image-redfin-....zip
          4. radio-redfin-....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-redfin-a9-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-redfin-a9999-99999-999999-b-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot -w update --disable-verity --disable-verification image-redfin-aa9a.999999.999.zip
          echo Press any key to exit...
          pause >nul
          exit
          Notes:
          1. The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
          2. When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
          3. 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.
          4. Some kernels require Disabling verity and verification
          5. 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:
          1. bootloader-redfin-....img
          2. flash-all.bat
          3. image-redfin-....zip
          4. radio-redfin-....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 complete.
        • Setup phone
        • Enable Developer Mode and USB Debugging
          1. Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
          2. 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.
    3. Take the OTA Update and Maintain Root

      • This set of instructions was written by @topjohnwu: Install Magisk to Inactive Slot , use Magisk Canary, Beta or Stable.
      • NOTE: After you Open Magisk and Restore Images. If you had a Custom Kernel installed, Please check the OP of the Custom Kernel thread you install for the instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you installed Mods Please check the OP of the Mod thread you installed for instruction to remove the Mod and return your phone to Stock before you download the OTA.
      • 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
        • fastboot Reboot
    4. Extract Files from Factory Image/Flash boot.img

      • Extract Files from Factory Image

        1. Extract flash-all.bat and boot.img file
        2. Download the latest Factory image to your phone.
        3. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
      • Flash boot.img

        1. Flashing the boot.img removes root.
        2. 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.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot --slot all boot.img
        6. Reboot
    5. 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.

        1. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the boot.img file.
        2. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        3. Open Magisk Beta/Canary/Stable App
        4. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        11. Reboot
        12. 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
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. 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
            1. Press the Power button until the phone turns off.
            2. Press the Power and Volume Down to boot the bootloader.
            3. 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
            4. fastboot Reboot.
        19. Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
      • Pass Safety Net with SafetyNet Fix

        1. Download File(s)
        2. Install kdrag0n or Displax's safetyNet Fix
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the kdrag0n SafetyNet Fix or Displax's SafetyNet Fix file you downloaded.
          • Tap the kdrag0n SafetyNet Fix or 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.
        3. 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.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, Google Wallet, etc. data[/B]
          • 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, Google Wallet, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification, It may take 24 hours for Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    6. 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

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/Download
        7. Tap, Reboot
        8. Done!
    7. Install/Update Magisk Modules

      • Download Modules
      • Install Modules from Storage

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Install Modules from Fox2Code/Fox Magisk Module Manager

        1. Open Fox2Code/Fox Magisk Module Manager
        2. Tap the Modules icon
        3. Locate the Module you want to install
        4. Tap Install
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
      • Update Modules

        1. Open Fox2Code/Fox Magisk Module Manager
        2. You, will see the Modules that have Updates.
        3. Tap the Module you want to update.
        4. Tap install.
        5. After it installs, tap the Disc Icon to save the install log.
        6. Tap Reboot
    8. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. 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.
        2. 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.
        3. 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.
    9. 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.
    10. ADB Sideload

    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. Custom ROMs

      • Need help with a Custom ROM?
        1. 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.
        2. 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.
        3. 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
        1. Google Pixel 5 ROMs, Kernels, Recoveries, & Other
        2. Other Custom ROMs
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 T.W.R.P.
    View
    6
    H
    Homeboy76
    :) I hope you all have a Joyful Holiday season with your family and loves ones. :)

    ~ ~ ~ Stay safe ~ ~ ~​
    View
    5
    Ducter
    Ducter
    prgopala said:
    is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.
    Click to expand...
    Click to collapse
    You should have your stock image you can push over. I do not think replacing the boot image with another patched image would disable anything. You can also use adb to remove any modules. Regardless heres my patched boot image and the command to remove modules. Power off, connect phone enter this command, hold power button to boot phone.

    adb wait-for-device shell magisk --remove-modules

    Patched December build boot image
    here
    View
    4
    badabing2003
    badabing2003
    For people who are having bootloops with patched boot.img
    Please pay attention to this step in the guide
    Section 7
    Under Patching boot.img
    4- Depending on the version of Magisk Manager installed: Set the Update Channel to Beta or Canary.

    Even if you install beta / canary magisk apk, if you don't select the matching channel, you'd get a bootloop, so don't forget that important step.
    View
    3
    V0latyle
    V0latyle
    elong7681 said:
    Thank you for your help I really appreciate it!
    Click to expand...
    Click to collapse
    Absolutely, helping each other is what makes this community work.
    View

New posts