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

Search This thread
By:
Advanced…
Gygun

Gygun

Senior Member
Mar 13, 2016
59
32
Hello guys. New Pixel user here. I just bought a Japanese Pixel 7 and want it to root it. In the first post it says I need to download a factory image (global) to use it. Will it remplace my Japanese versión of Android? I think there are differences (like payment methods support) and stuff, and I want to keep my Japanese Rom (but rooted). Is it posible? Will that factory Image remplace my current one? Thank you and sorry for the noob question!

Edit: the phone has this hardware chip (https://en.m.wikipedia.org/wiki/FeliCa) that I want to continue using it.
 
Last edited:
H

Homeboy76

Recognized Contributor
Aug 24, 2012
3,872
2,310
Google Pixel XL
Google Pixel 7 Pro
Gygun said:
Hello guys. New Pixel user here. I just bought a Japanese Pixel 7 and want it to root it. In the first post it says I need to download a factory image (global) to use it. Will it remplace my Japanese versión of Android? I think there are differences (like payment methods support) and stuff, and I want to keep my Japanese Rom (but rooted). Is it posible? Will that factory Image remplace my current one? Thank you and sorry for the noob question!

Edit: the phone has this hardware chip (https://en.m.wikipedia.org/wiki/FeliCa) that I want to continue using it.
Click to expand...
Click to collapse
¯\_( ͡❛ ͜ʖ ͡❛)_/¯

Here is the limited information I found about Pixel 7 Pro / Pixel 7 Japanese Models:
  1. Question Pixel 7 Pro US vs Japan variant by: vanthatou
  2. Google Models:
    • Google Pixel 7 Pro (GFE4J 128GB)MODEL 4
      Countries or regions available: Japan
    • Google Pixel 7 Pro (GFE4J 256GB)MODEL 5
      Countries or regions available: Japan
    • Google Pixel 7 (GO3Z5 128GB)MODEL 1
      Countries or regions available: Japan
    • Google Pixel 7 (GO3Z5 256GB)MODEL 2
      Countries or regions available: Japan
Google is your friend!
 
Last edited:
  • Like
Reactions: Slim2none4u
A

askylitangel

Senior Member
Jun 6, 2015
76
3
So my P7P passes SafetyNet but I cant seem to be able to use my Barclays Banking anymore. Can anyone help? (Am UK based if asking)
 
Slim2none4u

Slim2none4u

Senior Member
Oct 28, 2011
913
580
49
Livermore Falls
www.youtube.com
Verizon Droid Incredible 2
Sprint HTC EVO 4G LTE
simplepinoi177

simplepinoi177

Forum Moderator
Staff member
Apr 29, 2012
1,401
2
1,860
Bay Area, California
Google Pixel 5
Google Pixel 7 Pro
nordilf said:
Nice Guid, thx.

One thing at 2) Prerequisites .... A Computer with SDK Platformtools r33.0.0 , the link gets you to r34.0. Maybe you could change the link to r33.0.3 or to the thread Platform-Tools v34.0.0 HAS ISSUES, that provide the r33.0.3 links
Click to expand...
Click to collapse
to add on to this suggestion, if OP does not wish to direct to another Guide/Thread, you can get the URL links from THIS POST ; just be sure to credit @Namelesswonder for providing/pointing out the URL links (he, himself, may not actually be personally sharing/hosting the files, but still...)...
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
3,872
2,310
Google Pixel XL
Google Pixel 7 Pro
nordilf said:
Nice Guid, thx.

One thing at 2) Prerequisites .... A Computer with SDK Platformtools r33.0.0 , the link gets you to r34.0. Maybe you could change the link to r33.0.3 or to the thread Platform-Tools v34.0.0 HAS ISSUES, that provide the r33.0.3 links
Click to expand...
Click to collapse
@nordilf
Thank you.
I believe the latest SDK Platform-tools is rev. 34.0.0 (RC2).

It was released yesterday (March 08,2023).

The OP has been updated.

<Edit> The SDK Platform-tools download links are still downloading SDK Platform-tools R 34.0.0 and not SDK Platform-tools R 34.0.0 (RC2).
 

Attachments

  • platform-tools_r33.0.3-windows.zip
    5.4 MB · Views: 7
Last edited:
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide Platform-Tools v34.0.3 has a different bug - May 1, 2023 TQ2A.230505.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Replies
3K
Views
203K
JakeDHS07
JakeDHS07
Freak07
Development [Kernel][04.05.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.4 for Pixel 7/Pro aka "Pantah"
Replies
1K
Views
144K
schmeggy929
schmeggy929
badabing2003
Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
Replies
807
Views
55K
HipKat
HipKat
N
Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7
Replies
329
Views
47K
J
jake.99x3
roirraW "edor" ehT
General May 16, 2023 QPR3 Beta 3.2 T3B3.230413.009 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]
Replies
476
Views
64K
WillyRy
WillyRy

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 8
    H
    Homeboy76
    Update
    I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
    View
    5
    H
    Homeboy76
    ChillDuder said:
    i had to do --disable-verity --disable-verification along with wipe data -w at least once with stock rom flashing to get disabled verification, for e.g. custom kernels. ok.
    and if i wish to stay disabled verification i had to continue to do so.

    but do had this to do also with every custom rom flashes?
    thanks in advance
    Click to expand...
    Click to collapse
    Yes, you have to --disable-verity --disable-verification every time you update the factory image. If you want to use a Custom kernel. If you skip doing it once the next time you do it you will have to wipe your phone.
    View
    4
    H
    Homeboy76
    OP Changes
    I added additional notes to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~,
    5. Root/Reroot with Magisk and Pass SafetyNet.,
    • Patching the boot/init_boot.img - to root/reroot.,
    1 & 2.
    View
    3
    H
    Homeboy76
    SDK Platform-tools Update
    SDK Platform-tools r. 34.0.3, was released May 22, 2023.

    @badabing2003 reported a problem when using it.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575

    @Lughnasadh, suggested a fix.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601

    @badabing2003, confirmed the suggested fix works.
    https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617

    Note: If you use Windows SDK Platform- tools r. 34.0.3. You must set the environment variable.

    I think the same is true if you use Linux SDK Platform-tools r. 34.0.3. You must set the enviroment variable.
    View
    3
    H
    Homeboy76
    Update
    SDK Platform Tools r. 34.0.1 fixed
    View
  • 33
    H
    Homeboy76
    [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
    Android Security Bulletin—May 2023
    Pixel Update Bulletin—May 2023    ​

    Introduction
    This Guide is for Pixel 7 Pro 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. NEW

      • Android Security Bulletin—April 2023
      • "...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.

        1. 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
        2. 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
      • 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
    4. Update(s)

    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • @topjohnwu - Magisk.
      • @Lughnasadh - for his many helpful contributions to this thread.
      • @badabing2003 - for Pixel Flasher and for his many helpful contributions to this thread.
      • 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. Manually Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. If you haven't updated your phones Factory image in a while. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
        2. 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.
        3. If you are uncomfortable manually flashing the Factory image, see Use Pixelflasher...below.
        4. Always verify you have the latest working version of SDK Platform-Tools installed on your computer.
        5. 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.
        6. 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
        7. Backup your data
        8. Download the latest Factory Image: Pixel 7 Pro - cheetah to your Computer.
        9. Go to Part II - INSTRUCTIONS => 4. Extract the flash-all.bat and the init_boot.img files from the Factory Image.
      • Flash Factory Image Keep Data

        • Upgrading 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-cheetah-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-cheetah-a9999a-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot update image-cheetah-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 a 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-cheetah-....img
          2. flash-all.bat
          3. image-cheetah-....zip
          4. radio-cheetah-....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 init_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-cheetah-aaaaaa-9.9-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot flash radio radio-cheetah-a99999-999999-999999-a-9999999.img
          fastboot reboot-bootloader
          ping -n 5 127.0.0.1 >nul
          fastboot - w update --disable-verity --disable-verification image-cheetah-AA1A.999999.999.A9.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-cheetah-....img
          2. flash-all.bat
          3. image-cheetah-....zip
          4. radio-cheetah-....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 until 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.
      • Use PixelFlasher by @badabing2003
    3. Take the OTA Update and Maintain Root

      • XDA member @S8rooted&tooted does this to Take the OTA Update and Maintain Root

        ...I don't untick auto updates and restart it on the update screen.
        Steps I do
        I see the update notification
        I uninstall Magisk, just restore images
        Go to update screen and let it fully update
        Once the restart button is there on update screen,
        I head over to magisk install to inactive slot,
        After that is done go back to update screen and restart it there via bottom restart button...
    4. Extract the flash-all.bat and the boot/init_boot.img files from the Factory Image

      1. Download the latest Factory image to your phone.
      2. Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
      3. Open the folder you extracted the Factory image to and extract the Image file (image-cheetah-aa9a.999999.999.zip) into the folder. The, stock, init_boot.img file should be in this folder.
    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/init_boot.img - to root/reroot.

        1. 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.
        2. Extract the boot/init_boot.img file from the Factory Image.
          • Download the latest Factory image to your phone.
          • Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
          • Open the folder you extracted the Factory image to and extract the Image file (image-cheetah-aa9a.999999.999.zip). The, stock, boot/init_boot.img file should be in this folder.
        3. Install Magisk Canary - Download app-release.apk
          or
          Magisk Beta/Stable App
        4. Open Magisk Beta/Canary/Stable App
        5. The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
        6. Tap Install (next to Magisk)
        7. Tap, Select and Patch a File
        8. Select the init_boot.img file you extracted from the latest factory image.
        9. Tap the ✓ (Check Mark)
        10. Tap Let's Go
        11. When you see done, the init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
        12. Reboot
        13. Copy/Move the magisk_patched....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
        14. Boot fastboot mode
        15. Connect the phone to the Computer with USB cord.
        16. Open a Command Prompt in the folder you copied the patched boot.img to.
        17. Type fastboot flash init_boot magic_patched....img at the Prompt and press enter.
        18. Type fastboot reboot at the Prompt and press enter.
        19. Important, if your phone boot loops try one of the following options:
          • Flash the 'stock' init_boot.img to both slots: fastboot flash init_boot --slot all init_boot.img
          • 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.
        20. 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 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.
        3. Settings for Magisk
          • 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.
        4. 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
        5. 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.
        6. 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.
    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
    2. Themes, Apps, and Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 13 T.W.R.P.
    View
    8
    H
    Homeboy76
    Update
    I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
    View
    7
    simplepinoi177
    simplepinoi177
    @Homeboy76
    I'm sure everybody would join in on my congratulations on becoming a Recognized Contributor! You certainly work diligently enough on this thread and on all your others to deserve the title!
    View
    6
    badabing2003
    badabing2003
    foamerman said:
    OK The sdk files that I downloaded are from AUG 2022 version 33.0.3
    adb and fastboot are in Windows C: \Platform-Tools
    Here are the directory contents
    Ok for some reason I can't post the contents of the dir. so adb fastboot files and magisk_patched-25200_OKTza.img are in the Platform-Tools directory. Is that what your asking?
    Click to expand...
    Click to collapse
    I know what your problem is, I'm trying to be helpful here, but I find it that you are either unwilling or unable to provide the information you're being asked.
    If it is the former, then I don't want to waste my time, if it is the latter, perhaps modding is not for you.
    I'm not asking those for my benefit, I'm asking them so that I provide you precise commands and instructions to get this to work.
    Just because you downloaded a specific version of the SDK does not make it that it is being used.
    How many times I have to ask you the provide the output of the where commands
    You say everything is in C:\Platform-Tools directory, yet your screenshot shows that you are not operating in C:\Platform-Tools directory.
    1670157147221.png


    If your need my further assistance, please find a way to supply the information asked of you in this post.
    Apologies if this sounds a bit harsh, put yourself in my shoes.
    View
    6
    D
    dd805bb
    Reported as bug.

    It's been confirmed and fix is being done on GitHub. FYI everyone. Open source rules.
    View

New posts