Develop Bugs

How to root?

Hi everyone
My phone model is xt2075-3,I want to root
Can I directly flash the latest magisk(20.4) to get root permission after unlocking BL?

I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!

If you use the Magisk Manager to patch the boot image manually, and then flash that through fastboot - will that work also?
(My phone has yet to arrive so can't test this just yet...)

Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again

sniper9911 said:
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
Click to expand...
Click to collapse
where did you find the boot.img and the patched one?
Thanks

Mr.Krulez said:
where did you find the boot.img and the patched one?
Thanks
Click to expand...
Click to collapse
Get the full stock image by downloading rescue and smart assistant app from lenovo which supports moto phones ... Do login and get the fastboot rescue option while plugging your phone in the pc in fastboot mode .. then it will download it full firmware for your varient
Becareful that continue to flash the firmware will wipe your phone completely
After that get a copy of the boot.img file ... Copy it to the internal memory and install magisk manager apk from its official github site ... Now patch the boot.img you copied in your phone inside the magisk app then copy it back to your pc
Lear how to flash it from fastboot
Flash it
Done .. you are now rooted by patched boot.img with stock recovery !
Sent from my moto g 5G plus using Tapatalk
View attachment 5143479View attachment 5143477View attachment 5143481

Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery

Hi Guys,
my device is a/b device, bootloader unlocked, could you please kindly advise to flash twrp
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
thanks and kind regards

emanuel said:
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
Click to expand...
Click to collapse
I think the flash method fails because there is no partition called "recovery" - as an A/B device it looks like there are two:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_b -> /dev/block/sdf20
if you have the Magisk zip file on the internal storage you can use the "fastboot boot twrp.img" method to flash it from there (for some reason TWRP can't see the SD card on my device)

Now for my question... my rooted (UK Retail) device has indicated that there is an OTA update:
I've tried using the method described here to restore the boot partition to stock so that it doesn't interfere with the process, but it fails (see attached images).
Does anyone know of a working method? I have downloaded the full (2+GB) update so am prepared to flash that (and restore everything else from backups) if necessary - but would rather not if it can be avoided...
{
"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"
}

xth88312 said:
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
Click to expand...
Click to collapse
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?

I unlocked my phone through the official Motorola site:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I downloaded the latest Magisk and MagiskManager in the same directory from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I downloaded the original firmware from https://mirrors.lolinet.com/ and extracted the boot.img in the same directory, then issued, through the ADB connection:
Code:
adb install ./MagiskManager-*.apk
adb push ./boot.img /sdcard/Download/
(Replace the star as needed)
I opened MagiskManager app (you need to be connected to the Internet) and in the Magisk card I tapped Install > "Select and Patch a File". I browsed for and selected /sdcard/Download/boot.img and tapped "Let's go". A patched image /sdcard/Download/magisk_patched_*.img is created. Then, through the ADB connection, I issued:
Code:
adb pull /sdcard/Download/magisk_patched_*.img
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched_*.img
fastboot reboot
At reboot, the phone was rooted.

boringtech said:
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL] TWRP 3.5.0.0
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
thats the link for twrp for moto g 5g plus..
use at own risk as i havent tried it myself so im not responsible for bricked devices etc...FLASH AT OWN RISK....

Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll have to patch bo
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
you need to
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll need the patched boot.img to gain root, thats how ive had to root all my moto phones ive had, never been able to just flash supersu etc, someone will jump in if im wrong but as far as i know you need to patch the boot.img....
Remember everything you do is at your own risk i take no responsibility for.what you do with your device

Development [ROM][Android 11][OP9Pro] crDroid v7

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4

Awesome.

I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?

burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS

gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader

Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?

CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!

I'll flash and report tomorrow .
post logs through here or telegram?

ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff

I know it may not be recommended, but has anyone been able to flash this without using a computer?

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible

TWRP is death.

This is awesome news brother

So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?

crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy

gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?

djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after

gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.

truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job

[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

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"