Need help rooting - Google Pixel 3 XL Questions & Answers

Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles

EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.

EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
Possible corrupted magisk file? Re-download the latest beta 17.3. I didn't have that problem but the general consensus has been to extract and flash the original boot.img and start over. Yes you will lose twrp, but from the PC you can flash the boot.img and then twrp.img right behind. Personally what I do on the phone is to queue up twrp.zip, kernel.zip, and magisk.zip and flash all 3 at the same time. Kernel is optional. Works well for me. Best of luck.

I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.

Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..

Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
swieder711 said:
I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.
Click to expand...
Click to collapse
I tried to to download latest one from https://github.com/kantjer/MagiskFiles
Getting same error after installing Magisk.

EvergreenExpert said:
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..
Click to expand...
Click to collapse
@EvergreenExpert
Never saw that error before.
So your bootloader is unlocked on your Pixel 3/Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
- flash-all.bat
- flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?

Homeboy76 said:
@EvergreenExpert
Never saw that error before.
So your boot loader is unlocked on your Pixel3/ Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
Flash-all.bat
- Flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?
Click to expand...
Click to collapse
Yes.. I did exactly that. Also tried to install newer version of Magisk.
Here is screenshot of folder with SDK Platform-tools: r28.0.1 and all files in it used.
https://photos.google.com/share/AF1...?key=U29nMDFYWFJnNnA4LTJNLTJTOWl3c3V1NFV0b3JB
Here are all files that I am working with including ones that go on the phone. All done from Windows 10 machine.
https://photos.google.com/share/AF1...?key=VnF4czY2OTZXS2JEdUJXcE50N3VJLXliVWlkYVVR
Bootloader unlocked on Pixel 3 XL. Pin set. Files on the phone copied over USB to Internal Shared Storage.
Phone boots fine even after Magisk uninstaller is installed. As soon as Magisk is installed it will not boot right. It will start booting, will show G for 2 minutes and reboots again just to show the error mentioned above. If I install TWRP on the phone it will reboot to TWRP instead of showing the error.
Got my phone on black Friday.. Maybe that why the phone was discounted.. LOL

Quick update... and one question.
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles

EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
@EvergreenExpert
So you Added swipe to allow modifications after fastboot boot twrp.img? When you Reboot system did you skip (uncheck the two boxes - One is, "Install twrp as system")?
No. I always suggest twrp users swipe to allow modification (See guide below)
OTA System updates will unroot your phone. You can download the OTA image and sideload it.
After I root my phone, I go to Settings > System > Advanced > Deveoper options > turn off 'Automatic updates.
Then I do the following, monthly: Open this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Do #4 'keep data' to update the factory image , then #8 to reroot.

Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.

EvergreenExpert said:
Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.
Click to expand...
Click to collapse
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.

Homeboy76 said:
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.
Click to expand...
Click to collapse
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
So instead of swiping to allow modifications you chose 'Keep read only' and it worked.
Great, thanks for sharing.

EvergreenExpert said:
Maybe I am doing something wrong after all....
Click to expand...
Click to collapse
No. I believe your intuition is correct. Ever since systemless root was the norm, I have *always* hit "keep read only" per Chainfire. I also install TWRP via the zip file (perm) because it is a Swiss Army knife I insist on having, and the stock recovery blows.. and IF for whatever reason I need blowing... I just flash the original boot.img. End of story. I also turn off the "twrp app install" and in settings turn off the screen timeout. Best of luck! :good:

EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
Where is the swipe to Allow modifications...never seen it

EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
What was the exact build of TWRP that you used?

Everytime i install twrp i am asked to modify system. Or keep read only. Every version ive ever flashed

Hey guys, I am running into the same issue, with Magisk 18.1. Freezes on the load screen and then resets recovery (TWRP) after. The last time I tried to load the Magisk zip however, I got an error that read that vendor was not found or was busy.

Related

[Simple method] Root N10 5G using Magisk for factory stock

First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first

How To Guide Method to upgrade every month, without wiping data and retaining root

Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling verification and verity and did not have to wipe their phones, but request everyone, who have verification and verity disabled and using this guide, make sure you backup all the data and post your results here (I suggest backing up data anyway for everyone).
Following is a guide to update Pixel 6 Pro (perhaps all Pixel devices) every month, without wiping and retaining root. I tested it on my Pixel 6 Pro from 12.0.0 (SD1A.210817.015.A4, Oct 2021) to 12.0.0 (SD1A.210817.036, Nov 2021). There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google site and extract them in one folder.
2) Extract the boot.img from image-raven-xxxxxxx.zip which was extracted from the image in the above step and patch it in Magisk Manager (latest canary build from https://github.com/topjohnwu/Magisk) on your phone and copy it back to the folder where you extracted the factory image and platform-tools. Rename the copied file to magisk_patched.img
3) Open flash-all.bat in notepad, add --skip-reboot and remove -w from the fastboot update line. Also add the following lines after the fastboot update line to flash the Magisk patched boot.img automatically:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
After editing, the edited part of your flash-all.bat should look something like this:
Code:
fastboot --skip-reboot update [****image_name****]
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
echo Press any key to exit...
Note: [****image_name****] is just a placeholder and needs to be the name of zip file which was originally there in flash-all.bat, do not change that. Be careful to rename the Magisk patched boot.img to magisk_patched.img or in the alternative make appropriate modifications in the flash-all.bat
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Update 1: I updated from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SD1A.210817.037, Nov 2021) successfully using my method, without loosing data and root.
Update 2: I updated from 12.0.0 (SD1A.210817.037, Nov 2021) to 12.0.0 (SQ1D.211205.016.A1, Dec 2021) successfully using my method, without loosing data and root.
Update 3: I updated from 12.0.0 (SQ1D.211205.016.A1, Dec 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022) successfully using my method, without loosing data and root.
Update 4: I updated from 12.0.0 (SQ1D.220105.007, Jan 2022) to 12.0.0 (SQ1D.220205.003, Feb 2022) successfully using my method, without loosing data and root.
Update 5: I updated from 12.0.0 (SQ1D.220205.003, Feb 2022) to Android 12L DP 3 successfully using my method, without loosing data and root.
Update 6: I updated from Android 12L DP 3 to Android 13 DP successfully using my method, without loosing data and root.
gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Why did you return it?
Gytole said:
Why did you return it?
Click to expand...
Click to collapse
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?
gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.
cd993 said:
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?
Click to expand...
Click to collapse
I got mine on a contract, but here in Canada, it is not allowed for the carriers to restrict bootloader unlocking. I will simply relock the bootloader before returning. That's what I did with Pixel 5 too.
Gytole said:
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.
Click to expand...
Click to collapse
I am sure you will love it. I swapped my Oneplus 7 Pro for this Pixel 4 XL in 2020 and haven't regretted a single day. The monthly updates and betas are something that I love.
What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?
gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......
cd993 said:
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......
Click to expand...
Click to collapse
Are you sure you rebooted to bootloader after flash-all.bat finished?
gururoop said:
Are you sure you rebooted to bootloader after flash-all.bat finished?
Click to expand...
Click to collapse
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm
cd993 said:
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm
Click to expand...
Click to collapse
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.
spotmark said:
What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?
Click to expand...
Click to collapse
Some people have reported that it doesn't work because you need to disable verity and verification for new devices.
gururoop said:
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.
Click to expand...
Click to collapse
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just tried this on my P6Pro. Managed to update from .015 to .036 and retained root.
Also still passing SafetyNet with USNF 2.2 beta
cd993 said:
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
View attachment 5447353
Click to expand...
Click to collapse
I am not sure, but these kind of errors are usually related to cables. Try switching the cable and see.
In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post
In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?
Annil said:
In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post
Click to expand...
Click to collapse
Well, I have used this method for several months on my Pixel 4 XL (without disabling verity and verification) and now even on Pixel 6 Pro with same results. I have never tinkered with slots, but still managed to keep data and root.
Cares said:
In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?
Click to expand...
Click to collapse
Just to avoid the hassle of another reboot to flash the Magisk patched boot image for root.

Question How to upgrade to the latest patch of Android 12

Hey guys recived an update through the OnePlus oxygen updater today, currently in the "Stable" Android 12 release but after downloading the latest patch i noticed that there is no local upgrade option like it used to be prior, am i missing something here ? Thanks.
How to update from OnePlus 9 Pro Oxygen OS 12.0.0.0.LE15 to today's fixed OOS 12? Local update no longer available in settings/update
This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Zip file not showing on update.. and yes is in main storage
Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Progaros said:
This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Click to expand...
Click to collapse
Thanks a ton! This helped me to upgrade my incremental update!
PKkeys said:
Thanks a ton! This helped me to upgrade my incremental update!
Click to expand...
Click to collapse
Didn't work for me guide above so used APK to bring back local upgrade
More importantly, now that you patched to the latest, is it still a cleveland steamer?
toolhas4degrees said:
Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Click to expand...
Click to collapse
any other option to install incremental update? because i am getting failed message during installation despite this procedures
AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
The problem is Google installer... And the fact you need to patch 2 images and remove verification and verity
toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
Makes sense. Thank you for this post.
If possible, I think it would be helpful to others if you (or somebody else) can upload and share those new stock vendor-boot/boot/vbmeta images that were dumped using the msmtool. Would save a lot of trouble to others.
Thanks again!
toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.
terlynn4 said:
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.
Click to expand...
Click to collapse
Where did you get a boot image from? This method will work on an6 magisk. You can't on a incremental update.. if you had a full zip yes I tried with alpha first the old method of removing and patching no longer works. So msm tool is your option... Other than that show me how you updated without pulling it. Since the ita won't work with payload dumper
toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.
toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
jeffsga88 said:
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.
Click to expand...
Click to collapse
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?
terlynn4 said:
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?
Click to expand...
Click to collapse
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Would been nice if you read what I posted earlier
toolhas4degrees said:
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Click to expand...
Click to collapse
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.
terlynn4 said:
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.
Click to expand...
Click to collapse
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything
toolhas4degrees said:
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything
Click to expand...
Click to collapse
It's still an install to inactive slot and reboot, regardless if there are any/many differences. The same process also worked from 36 to 38. And there are two threads besides this one with other people who rooted using only boot.img and direct install with alpha. Maybe you had issues because of skipping a version? In any case, the simple steps are the easiest path for most people. Great info in your post for anyone who has problems though.

Question How to root OnePlus 9RT 5G?

I just got my new Oneplus 9RT 5G. I searched a lot but unable to find a method to root it via TWRP.
Can anyone please share a link to TWRP recovery so that I can flash it and root it via Magisk?
I tried to unlock the bootloader by going to the fastboot mode but keep getting 'failed' message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have enabled 'USB debugging' and 'allow OEM unlock' in the developer options.
Use fastboot flashing unlock instead of oem unlock.
penguinus said:
Use fastboot flashing unlock instead of oem unlock.
Click to expand...
Click to collapse
Okay and what about a compatible TWRP recovery file that I can flash?
No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system
penguinus said:
No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system
Click to expand...
Click to collapse
Okay. How to get the stock firmware? I checked the official website. It's not available.
archz2 said:
Okay. How to get the stock firmware? I checked the official website. It's not available.
Click to expand...
Click to collapse
Yes, it is not available on site. If you have chinese firmware (ColorOS), you can get full rom from OTA servers. Even more, for the most recent versions I can provide ready to use boot.img. But for indian Oxygen full roms not availabe yet. You can try to dump boot.img from your phone using dd.
penguinus said:
You can try to dump boot.img from your phone using dd.
Click to expand...
Click to collapse
How do I do it? Please provide step by step process. I bought this phone in India and it's running Android 11 , Oxygen OS.
Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.
penguinus said:
Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.
Click to expand...
Click to collapse
Okay. Thanks a lot.
I checked the boot image, all the three step went absolutely fine.
To obtain Magisk, everything went well till step no. 5.
When I try to reboot with the patched image in the bootloader, the phone keeps booting in the bootloader itself. I also changed the name of the image from 'magisk_patched_bco6o' to 'bestimage', just to make sure that there aren't any special characters in the filename. Same. The phone kept booting in the fastboot mode using the image.
Now what should I do?
Edit.
I just updated the Magisk app directly from its UI. Now the phone booted fine using step 6. My device is rooted! Thanks a ton!
Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?
archz2 said:
Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?
Click to expand...
Click to collapse
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.
archz2 said:
My device is rooted! Thanks a ton!
Click to expand...
Click to collapse
What ROM version is it? Especially a build number. Want to know what version of Oxygen is elighble for rooting with provided boot.img.
Here's the build information
Okay.
penguinus said:
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.
Click to expand...
Click to collapse
Okay can I install a normal magisk app now since my device is already rooted?
Having a direct internet repository in magisk is quite convenient.
Another question. I want to install Lsposed on this phone to install GravityBox module. Now in my previous phone, (oneplus 5t running stock oxygen OS, Android 10) , I always used to keep a edxposed uninstaller zip file which helped in cases when there would be a bootloop after installing a module. I used to flash that zip in the TWRP, get back things to normal, and then uninstall a particular xposed module.
Now I don't have any TWRP on this phone. I don't have any custom recovery installed on this phone!
What do you recommend for doing xposed/lsposed/edxposed based flashing and module installation?
I can't say for sure it will not work. I just know stable version of Magisk DOESN'T work with 9RT chinese version (ColorOS). The chance to get it worked on OxigenOS is minimal as it looks for me. And what is happening with chinese phone with current magisk is bootloop. So I think it is better to not even try. At least while you don't have full ROM to recover.
Regarding absense of net repository in canary, there is a post from Magisk creator about it. Unfortunately, these functions will not back. I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Sorry, I don't have much experience with Magisk modules, the only recommendation for now is to not experiment too much while we don't have msm tool or at least full ROM.
Okay. And any comment on installing xposed? I don't have any TWRP or any custom recovery.
I didn't tried it, but please check threads of lsposed and EdXposed
Looks like both can be installed as Magisk modules, but needs Riru. Probably will give them a try later.
Thanks. I successfully installed latest Riru, Lsposed and GravityBox. All good so far.
Having issues with Viper installations. Will post about it in a separate thread.
penguinus said:
I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Click to expand...
Click to collapse
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?
archz2 said:
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?
Click to expand...
Click to collapse
After installing and activating safetynet fix you should clear data for Google Play Store and Google Play Services. Then open Play Store -> Settings -> About -> Play Protect certification. Should be "Device is certified"

Question Help Rooting T-Mobile variant A13

Good afternoon XDA
Well like the title says, I need help rooting my LE2127 with T-Mobile's release of A13. Made several attempts which all failed.
With A13 installed and the Bootloader unlocked, I then shut off the phone, booted into EDL mode, used the MSMTool to readback the boot.img, transferred that image to the device and patched it with Magisk. From there the device was put into Bootloader mode, and via pc flashed with the command "Fastboot flash boot_ a (img) followed by "Fastboot flash boot_b (img) then reboot into system. This procedure has worked without issue for A11 and A12, but doesn't seem to work on 13. It flashes, then just hangs. With this procedure failing, I then temporarily booted TWRP (since T-Mobile variant is known to have issues with installing it) and attempted to install the Magisk.zip, which also fails. It doesn't seem like TWRP has file system access. I have tried both procedures several times now. I made sure Windows 11 is in test mode, since 11 doesn't play nice with fastboot and Qualcom EDL drivers. I have a known good USB cable, plugged into a USB 2.0 port, and once again the first method mentioned above has worked without issue for T-Mobile's A11 & A12 releases.
Can somebody please help a dumb redneck figure this out? Thanks
DaveImagery said:
Good afternoon XDA
Well like the title says, I need help rooting my LE2127 with T-Mobile's release of A13. Made several attempts which all failed.
With A13 installed and the Bootloader unlocked, I then shut off the phone, booted into EDL mode, used the MSMTool to readback the boot.img, transferred that image to the device and patched it with Magisk. From there the device was put into Bootloader mode, and via pc flashed with the command "Fastboot flash boot_ a (img) followed by "Fastboot flash boot_b (img) then reboot into system. This procedure has worked without issue for A11 and A12, but doesn't seem to work on 13. It flashes, then just hangs. With this procedure failing, I then temporarily booted TWRP (since T-Mobile variant is known to have issues with installing it) and attempted to install the Magisk.zip, which also fails. It doesn't seem like TWRP has file system access. I have tried both procedures several times now. I made sure Windows 11 is in test mode, since 11 doesn't play nice with fastboot and Qualcom EDL drivers. I have a known good USB cable, plugged into a USB 2.0 port, and once again the first method mentioned above has worked without issue for T-Mobile's A11 & A12 releases.
Can somebody please help a dumb redneck figure this out? Thanks
Click to expand...
Click to collapse
Have you tried temp booting the magisk patched image instead of flashing it? fastboot boot boot magiskpatched.img rather than fastboot flash boot_[n] magiskpatched.img
Appreciative said:
Have you tried temp booting the magisk patched image instead of flashing it? fastboot boot boot magiskpatched.img rather than fastboot flash boot_[n] magiskpatched.img
Click to expand...
Click to collapse
Actually I have (forgot to mention that) and same result, just hangs on fastboot logo. Thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't tell you what exactly is wrong on your end but I can tell you that now that I finally found the time, I've rooted mine on the TMO OOS13 with (almost) no trouble. Here's what I did.
Entries in brackets [ ] are commands
Enable developer options
Enable OEM Unlocking
Enable USB debugging
Reboot bootloader
Flash unlock token
Unlock Bootloader
Boot into Android
Skip setup and turn on USB debugging
Reboot bootloader again
Temp boot TWRP
Tap reboot button to see which slot is active (slot A)
Go back to main screen without rebooting
Open ADB shell while booted in TWRP
[dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img]
Reboot system
Install magisk app
Patch /storage/emulated/0/boot_a.img
Copy magisk_patched_boot_a.img to computer hard drive
Reboot bootloader
[fastboot flash boot_a magisk_patched_boot_a.img]
reboot and open magisk
Finish installation via direct install method and reboot
Profit
Verify root is present
Reboot to fastboot
Flash stock boot image to unroot
Verify root is gone
Reboot bootloader again
Temp boot TWRP
Flash magisk-v26.1.apk
Reboot system
Open magisk
Finish installation via direct install method and reboot
Profit
Both methods worked for me. The one hiccup I had was that one of the times I temp booted TWRP it couldn't read my USB stick so I had to reboot back into fastboot mode then temp boot TWRP again, and then it worked fine.
First I rooted by backing up the stock unmodified boot image, patching it with magisk, then flashing the patched boot image via fastboot. Once I verified that this method worked and that magisk was installed properly I unrooted by flashing the stock unmodified boot image, then I checked and verified that magisk was no longer installed and that root access was in fact gone. Next I rooted again by temp booting TWRP and flashing the newest magisk apk, then I verified that this method worked as well and that magisk once again was properly installed.
TWRP never had any problems reading my internal storage but if it did here's what I'd do. Temp boot TWRP again and retry. If TWRP still won't read internal storage after multiple attempts format data, reboot to fastboot, temp boot TWRP again, and retry. If that doesn't work I'd format data again, reboot into Android, reboot to fastboot, temp boot TWRP again and retry. Like I said in my other thread, TWRP is a bit wonky on this phone. I don't know why, but eventually it works. It reminds me of an old worn out doorknob that won't unlock unless you jiggle it while you turn the key.
TheGhost1951 said:
View attachment 5909849
Click to expand...
Click to collapse
Masterchief87 said:
I can't tell you what exactly is wrong on your end but I can tell you that now that I finally found the time, I've rooted mine on the TMO OOS13 with (almost) no trouble. Here's what I did.
Entries in brackets [ ] are commands
Enable developer options
Enable OEM Unlocking
Enable USB debugging
Reboot bootloader
Flash unlock token
Unlock Bootloader
Boot into Android
Skip setup and turn on USB debugging
Reboot bootloader again
Temp boot TWRP
Tap reboot button to see which slot is active (slot A)
Go back to main screen without rebooting
Open ADB shell while booted in TWRP
[dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img]
Reboot system
Install magisk app
Patch /storage/emulated/0/boot_a.img
Copy magisk_patched_boot_a.img to computer hard drive
Reboot bootloader
[fastboot flash boot_a magisk_patched_boot_a.img]
reboot and open magisk
Finish installation via direct install method and reboot
Profit
Verify root is present
Reboot to fastboot
Flash stock boot image to unroot
Verify root is gone
Reboot bootloader again
Temp boot TWRP
Flash magisk-v26.1.apk
Reboot system
Open magisk
Finish installation via direct install method and reboot
Profit
Both methods worked for me. The one hiccup I had was that one of the times I temp booted TWRP it couldn't read my USB stick so I had to reboot back into fastboot mode then temp boot TWRP again, and then it worked fine.
First I rooted by backing up the stock unmodified boot image, patching it with magisk, then flashing the patched boot image via fastboot. Once I verified that this method worked and that magisk was installed properly I unrooted by flashing the stock unmodified boot image, then I checked and verified that magisk was no longer installed and that root access was in fact gone. Next I rooted again by temp booting TWRP and flashing the newest magisk apk, then I verified that this method worked as well and that magisk once again was properly installed.
TWRP never had any problems reading my internal storage but if it did here's what I'd do. Temp boot TWRP again and retry. If TWRP still won't read internal storage after multiple attempts format data, reboot to fastboot, temp boot TWRP again, and retry. If that doesn't work I'd format data again, reboot into Android, reboot to fastboot, temp boot TWRP again and retry. Like I said in my other thread, TWRP is a bit wonky on this phone. I don't know why, but eventually it works. It reminds me of an old worn out doorknob that won't unlock unless you jiggle it while you turn the key.
Click to expand...
Click to collapse
Hello, and many thanks for your comprehensive reply. Aside from how you extracted the boot.img (I did it via MSMTool) that's pretty much the procedure I used as well. Curiously, I had no issues getting TWRP to read from my USB thumb drive, the flashing just failed. In your list you have "Flash magisk 26.1.apk" You mean the zip file right? Also, after you flashed, did it just sit on the Fastboot screen a while, then boot into system, or did it boot into system pretty much immediately? Just curious if perhaps I didn't give it long enough. It just appeared to be hanging.
DaveImagery said:
Hello, and many thanks for your comprehensive reply. Aside from how you extracted the boot.img (I did it via MSMTool) that's pretty much the procedure I used as well. Curiously, I had no issues getting TWRP to read from my USB thumb drive, the flashing just failed. In your list you have "Flash magisk 26.1.apk" You mean the zip file right? Also, after you flashed, did it just sit on the Fastboot screen a while, then boot into system, or did it boot into system pretty much immediately? Just curious if perhaps I didn't give it long enough. It just appeared to be hanging.
Click to expand...
Click to collapse
Normally I'd just flash magisk through TWRP then be done with it but since you were having issues I decided to try patching the boot image as well. As for flashing the Magisk apk, this is a bit of an oversimplification but an apk is basically a zip archive with a different extension. If you want to see for yourself, just rename any apk file to .zip and you'll see that you can view and extract the contents with any file manager that supports zip archives.
With this in mind, it's pretty easy for a developer to make a dual purpose apk file that can be installed like any other app but can also be flashed through recovery like a flashable zip. TWRP just has to be made in a way that allows it to treat an apk the same as a zip, and apparently this is something that TWRP now supports. There's no need to look for a magisk zip file or even rename it from magisk.apk to magisk.zip because TWRP doesn't care about the .apk file extension. Also, official Magisk releases are only uploaded to GitHub and don't come in the form of zip files anymore, so if you go looking somewhere else for a zip file it could be tampered with.
If I remember correctly, the only time it sat at the fastboot screen was when I temp booted TWRP and that only lasted 5 or 10 seconds before TWRP booted up normally. After flashing the patched boot image and giving the reboot command it just showed the orange state warning about the bootloader being unlocked, then booted up normally. The same goes for when I just flashed the magisk apk through TWRP. It just showed the annoying warning about unverified software then booted normally.
After two more failed attempts. Thought I would try another USB cable. EUREKA!!!
flashed the patched magisk boot img and it crashed my phone. Stuck on orange state boot screen...... back to drawing board....starting from scratch with msm tool....ugg I guess I should have tried different cables to do the fastboot boot patched img to see if it would have worked. Lessons learned.. although I had been using the same cable in the past. I guess for A13 it may need to be different.
tried a different cable but still freezes at OnePlus logo with Fastboot Mode printed below the logo......
finally got it done by sideloading the unified twrp recovery and then installing magisk 26.1 done I used twrp for A12 and the the sideload of the unified twrp.
Damn, lol rooting this phone sounds nerve racking.
Not really!
TheGhost1951 said:
Not really!
Click to expand...
Click to collapse
I'm just worried that my banking apps and google wallet will be non-stop issues. I've gotten so used to using those everyday.
SkOrPn said:
I'm just worried that my banking apps and google wallet will be non-stop issues. I've gotten so used to using those everyday.
Click to expand...
Click to collapse
Add to magisk deny list..

Categories

Resources