[GUIDE] Bootloader Unlock and Root Note 10+ 5G SM-N976N (Exynos Version) - Samsung Galaxy Note 10+ Guides, News, & Discussion

Ended up with one of these in my tech shop some how, figured I'd try it and was successful at unlocking the bootloader!
Needed Files
- Odin Patched 3.14.1
- SM-N976N KOO Firmwarre
- 7Zip
- vbmeta-disabler: https://forum.xda-developers.com/at...371913/?hash=4ffe83be111a345e3fb35895ba1a5995
- LZ4: https://github.com/lz4/lz4/releases
- ADB/Fastboot (makes things easier)
- Magisk Manager
Instructions
-- bootloader unlock
1.) Use ODIN to flash the KOO Firmware you download
2.) DO NOT connect to wifi during Setup, go through without connecting
3.) Open Settings, enable Developer Options and disable Auto Updates
4.) Connect to Wifi, and wait for "Preparing setup" Notification to start. IMMEDIATELY disconnect from Wifi (this is what worked for me)
5.) Go to Time and Date settings, manually set the date 11 days previous to current date ... for example, April 29th, set it to April 18th
6.) Go to developer options and OEM Unlock should suddenly be there!
7.) Power off device completely, plug into a charger, and hold Vol Up+Vol Down+Power until the blue download mode screen comes up
8.) Hold Vol Up until it asks if you want to unlock bootloader
9.) Factory reset will occur, but its unlocked! Congrats!
TWRP Rooting (if on Android 11, DO NOT do this method with 12)
1.) Rename Magisk.apk to magisk.zip
2.) Reboot to Download, flash VBMeta_disabler
3.) Reboot again to download, flash twrp as AP
4.) Immediately boot to it upon reset via holding Vol Up as it restarts
5.) Go to ADB Sideload under Advanced
6.) using CMD,
Code:
adb sideload magisk.zip
7.) do a factory reset
Congrats! Rooted!
Non-TWRP Method (recommended)
1.) Open the AP file in 7zip
2.) Extract boot.img.lz4
3.) use lz4 to extract the boot.img
Code:
lz4 <path to lz4> boot.img
4.) install magisk manager on device
5.) Patch boot.img
6.) Pull the patched boot.img off phone storage
7.) Name it boot.img, use 7zip to create boot.tar
8.) Flash it as AP with Odin Patched
Rooted!
IF DEVICE DOESN'T BOOT, DO A FACTORY RESET. It needs to just reformat the data partitoins and such. Worked for me perfectly
Also might get a force close upon first boot of TADownloader... just close it and ignore it!

Related

Help rooting Pixel C!!

Hi guys,
I've been using WugFresh's root toolkit to root the pixel which has worked fine thus far. Recently I upgraded OTA to Nougat 7.1.2 (N2G47O). Now I've lost root and can't seem to get it back. Attempting to root the device through the toolkit no longer works as the file dependancy hasn't updated properly - "No-Force Encrypt" needs to be downloaded/updated. The link doesn't work however. I'm suspecting that WugFresh hasn't updated to the latest file to match N2G47O.
I don't understand this properly and information online seems limited. Can anyone advise on how to get this thing rooted again? With or without the toolkit will be fine.
Thanks in advance.
Just fastboot flash TWRP then install Magisk in TWRP. Poof... root.
To elaborate on this: download the latest latest "Recovery Flashable.zip" from http://www.supersu.com/download and copy it to the Download folder of your tablet.
In NRT under "Options > Custom recovery" select "Utilize Open Recovery by Team Win Recovery", then use Advanced Utilities to either
- "Fastboot Flash > Recovery" to flash TWRP, then "Quick Tools > Reboot recovery" to start TWRP
or
- "Fastboot Boot > Custom recovery" to start TWRP only once / non-permanent.
In TWRP allow write access to /system, then "Install" SuperSU.ZIP from your Download folder and reboot.
Thanks for your help guys. There seems to be another problem now though. I've followed the steps above and attempted to install TWRP recovery using the tools on the NRT. During the process TWRP asked me for the key to decrypt system data. I don't have one as far as I'm aware. Only my regular system pin. I tried that but it isn't accepting it. I had to accept TWRP leaving the system unmodified. Now I cannot boot into the system at all, only into the TWRP recovery! Why is it encrypted? I never set up encryption...
You seem to have somehow messed up your /system image. To restore it without losing your data, follow these steps:
- find the folder where your ADB.EXE is installed. Typically that would be C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data
- we will call that the ADB folder
- download a Pixel C N2G47W factory image from here: https://developers.google.com/android/images
- there will be a "bootloader-dragon-google_smaug.7900.50.0.img" and a "image-ryu-n2g47w.zip" inside the downloaded ZIP file. Copy these to your ADB folder.
- start TWRP. Press Cancel when asked for encryption key. If asked for write access to /system: allow it
- select Wipe, then Advanced Wipe. Select "Dalvik / ART Cache" and "Cache", then Swipe to Wipe
- In TWRP select Reboot, then Bootloader. If asked to install TWRP: Do Not Install. Should end up with "Waiting for fastboot command".
- alternatively: start your tablet manually into fastboot mode: Power off, then hold the volume down button, after 2 seconds shortly press the power button and hold it until a menu appears
- select "Switch to fastboot mode" with the volume buttons, start it with the power button. "Waiting for fastboot command".
- when in fastboot mode: start an administrative command prompt, CD to your ADB folder
Code:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.50.0.img
fastboot reboot-bootloader
- wait until it says "Waiting for fastboot command" again
Code:
fastboot update image-ryu-n2g47w.zip
- after several flash actions (be patient!) the Pixel C will boot into Android. It may take a while and a second boot can occur.
To install SuperSU you can't use the Download folder of the tablet because /data is encrypted (sorry, my bad).
If you can use a USB stick with OTG, then:
- copy the "Recovery Flashable.zip" from http://www.supersu.com/download to the USB stick
- use NRT to start TWRP without flashing it (Advanced Utilities, Fastboot Boot, Custom Recovery)
- press Cancel when asked for encryption key. If asked for write access to /system: allow it.
- attach the USB stick
- Install, Select Storage, USB OTG, OK
- select SuperSU.ZIP from USB stick and reboot.
If you cannot attach a USB stick:
- copy SuperSU.ZIP to your ADB folder
- start TWRP as described above
- Advanced, ADB Sideload
Code:
adb sideload SuperSU-v2.78-201609011115.zip
- Reboot
This worked a treat. Now rooted and running 7.1.2! Thank you for taking the time to help out. +1

Want to use Sultan kernel, having flashing issues

Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Bverns88 said:
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Click to expand...
Click to collapse
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Ericarthurc said:
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Click to expand...
Click to collapse
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Bverns88 said:
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Click to expand...
Click to collapse
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Ericarthurc said:
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Click to expand...
Click to collapse
Thanks so much. I went and used AZ bikers method and it worked fine. Easy and hassle free. https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330

[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More

[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—June 2023
Pixel Update Bulletin—June 2023​
Introduction
This Guide is for Pixel 4a 5(G) 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 4a 5(G) phone with an unlocked bootloader.
The latest Android Factory or OTA Image: "bramble" for Pixel 4a 5(G)
Factory Image
13.0.0 (TQ3A.230605.011, Jun 2023)
Which one should I use?
OTA Image
13.0.0 (TQ3A.230605.011, Jun 2023)
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 4a5(G) ROMs, Kernels, Recoveries, & Other​b. ElementalX Kernel Manager​
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
@creezalird- Flash Android 12 factory image.
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
Notes:
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 in the SDK Platform- tools folder, 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 you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
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 want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash the 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 4a 5(G) - bramble.
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 4a 5(G) - bramble 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 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-bramble-a9-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-bramble-tp1a.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 [U[Platform-tools[/U] folder:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....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.
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-bramble-aaaaaa-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-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-bramble-AA1A.999999.999.A9.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:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....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
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
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 (bramble-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-bramble-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 bramble-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 bramble-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 (bramble-r2d1a.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-bramble-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 (branble-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
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/init_boot.img file should be in this folder.
Install Magisk Canary - Download app-release.apk
or
Magisk Beta 25.0/Stable 24.3 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 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 11 (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 4a5(G) ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
lineageOS 20.0 for the Google Pixel 4a5(G) (bramble) Nightly
[ROM] [UNOFFICIAL] LineageOS 19.0 - microG Edition By: dic1911
Themes, Apps, and Mods
Google Pixel 4a5(G) Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.
As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.
rmckay1763 said:
As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.
Click to expand...
Click to collapse
Do #3 Return to stock
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Homeboy76 said:
Do #3 Return to stock
Click to expand...
Click to collapse
okay, I just wanted to make sure I did not do anything irrevocable. thanks for putting together a comprehensive guide.
kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.
@LastQuestion
If your phone had root and you did #4 'Keep data' to install the latest factory image. Your bootloop is probably caused by a rouge Magisk module.
That is why I, always, recommend uninstalling Magisk before installing/updating the factory image.
Do you have the latest SDK Platform-tools r 30.0.3? If not, there is s link in the OP - Prerequisites to get the latest SDK Platform-tools.
Have you tried flashing the stock boot.img to both slots to stop the bootloop?
fastboot flash boot --slot all boot.img
If flashing the stock boot.img stops the bootloop and your phone boots.
- boot Safe Mode
- Reboot - To remove all residual files, Magisk modules, etc.
- If your phone has the latest factory image do #7 to root/reroot. Otherwise, Do #4 'keep data', then do #7 to root/reroot.
Homeboy76 said:
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.
Click to expand...
Click to collapse
I do have the latest.
kha1rul said:
I do have the latest.
Click to expand...
Click to collapse
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.
Homeboy76 said:
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.
Click to expand...
Click to collapse
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?
kha1rul said:
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?
Click to expand...
Click to collapse
¯\_(ツ)_/¯
Great work, AGAIN!!
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
You need Universal Safetynet fix v 1.1.1 Magisk module.
lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot
Homeboy76 said:
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot
Click to expand...
Click to collapse
yeah, im an idiot, got it sorted before i seen your post but thank you tho. stupid freakin basic crap.......i never did magisk hide and have it repackaged. I did have to use the universal zip, but once i did all that, worked perfect. but again, thank you very much
kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Not sure if you still need it, but might be usefule for others.
Unlocking bootloader wipes everything including ADB prompt for your computer. You need to boot system, open developer options , enable ADB debugging and grant access to your computer again when the little popup window appears.
Hi ! Please help me my Pixel 4a 5g unlock bootloader Root Magisk and I have update of MAgisk I make it but bootloop !? And my usb debogging not check... And Test to flash-all but permission denied ?
I don't know how do to restart it ? Please
I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?
fremont85 said:
I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?
Click to expand...
Click to collapse
In case anyone else is curious... Yes, the G025E variant is able to be bootloader unlocked.

Id like to beg for help with rooting my RN 8 Pro

Basically I have rooted my old Redmi Note 4 but that was past guarantee so I did not care that much.
My current RN 8 Pro is still 1 year in guarantee so I literally do not have the balls to do it on my own.
Is there any good soul who would help me out with rooting it, pretty please? Thanks very much in advance
btw. I do know stuff about Unlocking Boot Loader, installing TWRP trough Command Window and Flashing Magisk...that should be potentially enough but as I said above no balls and do not want to F things up and brick it.
Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]
Redmi Note 8 Pro [Begonia] [Global Version Only] WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT...
forum.xda-developers.com
A great guide is here :3
Not sure you need my help for that but yeah if ya run into any problems, ill be here to help ya
Ty for responding. I read that but Im still not sure about what TWRP use on my phone (im not sure if i have to use special one or just latest version) and because I want to only root my phone Im also not sure, if I need to get a different ROM or I can do that on this STOCK ONE I have.
I bought my RN 8 Pro in EU. Im gonna try to give you more information about my phone, if you would be able to link me TWRP what I need and other files to root it...that would be awesome (its not like i cant read or im lazy f**k, its more like i dont want to F things up).
Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
Thank you very much
1. UNLOCKING BOOTLOADER :
- Download the Mi Unlock app to PC, and sign in with your Mi Account;
- Enable Developer Option in your phone by tapping the "Build Number" 7 times
- Go to Developer Options "Settings > Additional Settings > Developer Options
- Enable USB Debugging and OEM Unlocking
- Aslo add account in Mi Unlock Status (Can be found in Developer Options
- Install all the required drivers (adb drivers, vcom drivers etc.) In your PC [I'll link these below]
- Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode
- Connect your phone to PC using USB cable and click "Unlock". In Mi Unlock Tool
- You will be given a specific time (168 hours mostly)
- Wait until that and redo Unlock process
- Your device’s bootloader is unlocked
2. FLASHING TWRP :
- Install Minimal ADB and fastboot on your PC [Link will be provided below]
- Download LR Team TWRP [This work for now, I'll provide link below and will update it after we have another proper TWRP]
- Put that TWRP in the file location of ADB and Fastboot (Right click on Minimal ADB and Fastboot icon on desktop and click on Open file location)
- rename that recovery to "twrp" for convenience (optional)
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode
- Type
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type
Code:
fastboot flash recovery twrp.img
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
- Done
3. ROOTING :
- In TWRP mount System
- Go to Advanced > file manager
- then go to system_root > system and delete "recovery-from-boot.p"
- Go home and again go to advanced and Select "Close AVB2.0" swipe to confirm.
- Go back and select "Install Root"
- Here you go magisk 19.4 will be installed (U can chose any other versions afterwards.)
- Reboot the device to system.
- Done!
LINKS
1. Mi Unlock tool
2. Minimal ADB and Fastboot
3. ADB Drivers for MTK
4. MTK USB Drivers
5. LR Team TWRP
Hello once again...I might need some help
I was following these steps but after flashing this TWRP I cant enter into the TWRP...so far Ive tried holding power button then pressing Volume +; holding power button and then holding Volume+; even holding them both but still without any result...any chance you might help me here, please?
*EDIT: Im flashing stock ROM
Go to the system then do
adb reboot recovery
I flashed TWRP recovery once again, then I went for "adb reboot recovery". This is what happened after I used "adb reboot recovery" (attached picture). There is no sign about TWRP. What am I doing wrong? I literally followed the guide the flash of the recovery TWRP is successful. Is there any chance that Im flashing wrong TWRP recovery? Or that Im doing it on stock ROM? Usually its problem between chair and keyboard but I dont know :-/.
So Ive tried to boot TWRP through after flashing it with "fastboot boot twrp.img". It went through but it booted like normal so I ended up in system like when you turn on your phone normally.
Anybody, anything please?
N00B92 said:
Anybody, anything please?
Click to expand...
Click to collapse
First: what version of miui?
If you're on miui 12.5 this method will cause reboot.
If your phone is < 12.0.X its okay.
It looks like flashing recovery worked.
Instead of trying to adb reboot recovery after flashing recovery try this:
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
I was already trying that, if I do it how you typed the screen is gonna keep blinking with MIUI logo.
I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.
N00B92 said:
I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.
Click to expand...
Click to collapse
First you need to enter recovery, i think you didn't flash boot.
Follow the method below exactly.
Original post and files can be found here.
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
I dont have any boot.img in my folder so I cant flash the boot.img. Having stock ROM and I have no clue where to get it.
My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm
Id appreciate any help
Everything I did try is above.
N00B92 said:
My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm
Click to expand...
Click to collapse
madsponge26 said:
Redmi Note 8 Pro
[Begonia]
[Global Version Only]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community
Click to expand...
Click to collapse
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.
Kenora_I said:
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.
Click to expand...
Click to collapse
Thanks. I used the boot.img and I was following the guide which "donkyshot" sent. But I got stucked right after I did those commands in command Window. I disconnected the phone went for the power button hold and then when it was blank I stopped holding power button and I started holding the Volume+ button. The phone was bootlooped on Xiaomi logo...I was waiting several times but nothing. At the end I had to flash the phone with stock ROM I downloaded through MiFlash...I really dont know what I was doing wrong.

How to root the Google Pixel 4a 5g Android 12

Step 1 – Unlock the bootloader​It is important to note the steps described below are intended for the unlocked carrier variant of the Pixel 4a 5g. Most U.S. carriers like to disallow bootloader unlocking, making it impossible to root your phone.
Go to System settings -> About phone -> tap on ‘Build number’ several times until Developer options are enabled
Back out into settings and go to System -> Advanced -> Developer Options -> Enabled ‘OEM Unlocking’
Unplug your phone if it’s plugged into anything and power it off
Boot into the Fastboot interface by holding Power + Vol Down or open Terminal/Shell/Command Prompt/PowerShell (depends on the OS) and type adb reboot fastboot
Plug the phone into your PC and open Terminal/Shell/Command Prompt/PowerShell (depends on the OS)
Type fastboot flashing unlock on the terminal and follow the prompt on your device to unlock the bootloader (Note that this step will factory reset the device)
The bootloader is now unlocked!
Step 2 – Patch the stock boot image using Magisk Manager​While you can find a pre-patched boot image for the Pixel 4a 5g here on xda, make sure to verify its origin. Any pre-patched boot image you download should match the installed software build version, otherwise, you may face severe anomalies. So in case they don't match(for instance the boot image here is for only Android 12 in case you have a higher or lower version as when you found this thread) recommend you patch the boot image yourself.
Download the factory firmware corresponding to the installed version of the stock ROM and extract the boot image from the archive
Copy the boot. img to your device
Install Magisk Manager (grab it from the release section of the project’s GitHub repo)
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
Step 3 – Flash the patched boot image​
Copy the magisk_patched.img to your PC you patched or for Android 12 download this on your PC
Reboot your device back into fastboot (see Unlock section above) or Boot into the Fastboot interface by holding Power + Vol Down or open Terminal/Shell/Command Prompt/PowerShell (depends on the OS) and type adb reboot fastboot
Open a terminal in the directory your patched boot img file is and type fastboot flash boot magisk_patched.image in Android 12 case will be fastboot flash boot magisk_patched-24200_x1HXn.img
You’re now rooted!
Have a look here for in-depth knowledge

Categories

Resources