Database Users

[GUIDE][osprey][merlin]How to root ANY Moto G 2015 model on Marshmallow

This guide covers ALL Moto G 2015 models (including the G Turbo) that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1540, XT1541, XT1543, etc., the method is identical. In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question.
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP for the Moto G 2015 or TWRP for Moto G Turbo.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
EDIT: I no longer own or use this device, but will keep this thread open and will check it periodically for assisting the few people left out there who haven't rooted their Moto G 2015 yet.

Alternate Method
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 95% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
After this is complete and boot is verified, update the SuperSU app via the Play Store to the current version, then open the SuperSU app and it should prompt you to update the su binary, go ahead and do that via the "Normal" process and reboot when complete.

can confirm, a simple flash won't work, phone stays on the splash screen, had to type op's command for root to work
Sent from my Nexus 6 using Tapatalk

After successful flashing super su it is not showing in app drawer , should I flash it again

25vikasp said:
After successful flashing super su it is not showing in app drawer , should I flash it again
Click to expand...
Click to collapse
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file

acejavelin said:
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
Click to expand...
Click to collapse
[/QUOTE]
See this.i don't know

25vikasp said:
See this.i don't know
Click to expand...
Click to collapse
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76

acejavelin said:
See this.i don't know
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
Click to expand...
Click to collapse
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse

25vikasp said:
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
Thank you... I will update the OP to show that 2.77beta is not compatible.

stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me

krisbeowolf said:
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
Click to expand...
Click to collapse
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...

krisbeowolf said:
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
Click to expand...
Click to collapse
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
can you give me the link

krisbeowolf said:
can you give me the link
Click to expand...
Click to collapse
Read the first post of this thread, completely, paying attention to prerequisite #3!!! If you are using SuperSU v2.62-3 Beta you are NOT following my instructions for rooting, are you sure you are posting in the correct thread?
acejavelin said:
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. As of this posting UPDATE-SuperSU-v2.76-20160630161323.zip is the current stable version.
NOTE: Version 2.77 BETA is intended specifically for the Note 7 and should not be used for rooting Moto devices, in testing it doesn't brick or stop boot, it just doesn't show up or work.
Click to expand...
Click to collapse

How to make backup before unlocking bootloader?
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.

sanchith.hegde said:
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
Click to expand...
Click to collapse
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Click to expand...
Click to collapse
Thanks man for your help.
By the way, will ADB work without root?

sanchith.hegde said:
Thanks man for your help.
By the way, will ADB work without root?
Click to expand...
Click to collapse
Yes, just enable it in Developer options.

I absolutely can not get Super User Root, I followed this OP to the letter, I have tried to root, in TWRP Recovery, using the linked SuperSu from both storages ie.. internal storage, and one I placed on my adaptive/portable/ExtSdcard. Went to advanced, terminal typed the "echo.....etc", then flashed, and it says while flashing the Super Su file it's installing "systemless" and looks fine, goes through the whole process tells me to reboot, and then just loads right up no wait, BUT NO Super Su file, tried downloading SuperSu apk from playstore manually, after boot up and it doesn't recognize any root[emoji30]
I have tried this on both allowing the changes at the beginning of recovery, and also not allowing the changes, at the beginning of the recovery, lucky I backed up at first boot of TWRP, which I went into immediately after flashing it via adb/fastboot
I am at a loss, and completely frustrated at this point, any assistance would be so so thankful, thanks
Sent from my MotoG3 using XDA-Developers mobile app

Magisk on US996 (Unlocked) v20 -- Should we us it instead of SuperSU? If so, how?

I have a v20 US996 (unlocked) that I'm getting ready to unlock the bootloader and then I'll want to root. I've always rooted with SuperSU in the past, but now there is also Magisk.
For our v20s (US996):
1) Should we use Magisk instead of SuperSU?
2) Is it as stable as SuperSU (without random reboots, etc)?
3) If 1+2 are "yes" then where can I find out how to root with Magisk safely without any problems?
Thanks!

I say yes to your first two questions. I accidentally upgraded to 10H on the 996 and I thought I was stuck with an unrootable phone. I had already had an unlocked bootloader and I used ADB to flash TWRP, flashed Magisk and boom. Rooted again. Been happy ever since. I don't have the exact thread for Magisk but if you Google I wanna say Magisk 14.0 you should be able to find it. Been working great for me. Hope that helps.

Anyone else's thoughts?

Also, will I still be able to use the 2nd screen?
And where can I find instructions specific to the v20?

Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.

Sizzlechest said:
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Click to expand...
Click to collapse
Especially with chainfire retiring, now is all the more reason to use magisk only. I've been using supersu for the entire duration of my smart phones but I need to make the switch.

Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594

baldybill said:
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.

GreenDinoXD said:
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
Click to expand...
Click to collapse
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?

baldybill said:
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
Click to expand...
Click to collapse
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.

GreenDinoXD said:
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
Click to expand...
Click to collapse
Please do, I don't want to mess up my phone.
It's never been unlocked or rooted. [Currently, I'm having trouble getting the unlock image from LG. ]

Okay i am going to copy the exact text that the person who helped me said. It is really well explained and he says the steps very clearly. To do a TWRP backup and restore it it's one of the main buttons on the screen, I highly recommend using an SD card. Use the select storage button to change between internal storage and the SDcard, just check the box for data, and that has all your apps and pretty much everything else. And when you do the kdz part below you can just restore the version f firmware and do the update that way and skip the ota. I copy and pasted most of the rest from the last time I typed this up.
Get a hold of LGUP and downloading the kdz, heres (https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817) a good thread on it, with even all the tools attached except the kdz, for getting on the older more stable twrp just flash flash it in fastboot (use lgup to restore the kdz which gets back to full stock, then use fastboot to get the info needed to fill out the form on LG's site(https://developer.lge.com/resource/mobile/RetrieveBootloader.dev), (basically this guide has it all listed out, plus once you've created an lg account and actually gotten to the form, the page with has directions too(http://www.droidviews.com/unlock-bootloader-on-lg-v20-us996/))
So heres how we're going to get twrp on here from a stock, but unlocked us996. You probably don't need the no-verity-opt-encrypt if also flashing supersu or magisk but I did it anyway to be safe.First get the latest version of no-verity-opt-encrypt.zip from here(https://build.nethunter.com/android-tools/no-verity-opt-encrypt/), and the stable version of Twrp-3.0.2-1-us996.img from a different directory on the same site(https://build.nethunter.com/test-builds/twrp/lge/), if you have an sd card in your phone put the no-verity zip on it ahead of time (and if you want to save a boot, put magisk on there too) (if not twrp should let you transfer it from your pc, but I havn't done it that way). So go ahead and reboot into fastboot (adb reboot bootloader) mode, then fastboot flash the_FULL_PATH_to_twrp-3.0.2-1-us996.img . once it successfully completes, until we flash the no verity zip in twrp if the phone boots into stock it will overwrite twrp and it will need to be reflashed in fastboot mode. So once you've flashed it the first time, pull the battery, wait a second, then put it back in, hold down volume down, hold the power button just until the LG logo appears, then let go of the power button, and immediately press (and release) it once while still holding down volume down, keep holding volume down until, if you've done it successfully, it will ask you to factory reset your phone (for future note, while twrp is installed this will NOT factory reset your phone), say yes both times and twrp will boot shortly.
From here, go to install, and then change to your sd card and install the no-verity-opt-encrypt.zip, then go back and hit wipe (in twrp), on the wipe screen, hit the format data button (the correct button will make you type out yes to confirm), from here twrp will be installed and not tampered with and you can safely install magisk or a custom rom, and/or boot back into stock.
I do not know where i downloaded magisk from but here is the latest version:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance

I'm in a similar situation, with a fresh US996 factory-unlocked. Does this method (stock + magisk + twrp) preserve Android Pay / SafetyNet?

I switched from SuperSU to Magisk and now I can download Netflix from Play Store.
Switch away if you want to.

Thanks, GreenDinaXD, I'll give that a try after a while.

Thanks

GreenDinoXD said:
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
Click to expand...
Click to collapse
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?

baldybill said:
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
Click to expand...
Click to collapse
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.

With my experience from MagiskSU, absolutely, Magisk let's you use any anti-root app, like Snapchat, or Netflix, etc... So you don't need to go through the Xposed McCluster**** ordeal

GreenDinoXD said:
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
Click to expand...
Click to collapse
Are there stability issues with Magisk? Random reboots?
I'm curious since this is my everyday phone and I want it to be running decently. Thanks!

Do I have to flash no verity?

I really just want to root stock. I have the Boost Mobile Perry.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).

I really don't care about encryption.

guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.

Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.

guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.

Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img

i have the moto e4 mkt which no verity version do i have to flash ?

Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.

madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome

Root for P-SMR7-RC003-RZR 210107.3225

Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.

thanks for this.. i was looking everywhere for boot extraction tools

Hi. I am looking for some method to flash a recovery or rooted boot for Razer 2 since the USB port on it is messed up.
Not sure if it is the software or the hardware, but the only way I can charge it at all (slowly) if I use an USB A to C cable and the device is off (well, not really since it flashes the logo, vibrates, and now complains about the unlocked boot-loader)
The stock recovery has the option "apply update from SD card" Are there any signed images in update.zip form I could just throw on the sd card?

By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.​

There isn't one. Once booted you can use ADB over WiFi. But Fastboot only works with USB.

You're far better off updating to the newest firmware and patching via magisk than ever using downloaded pre-patched boot images

That would be true if we could get Magisk to patch a un-rooted phone. All I've done here is extract the latest stock firmware and patch it with Magisk so others can flash it. I believe the first time you boot after, it askes you to updated to the latest version.

hackthis02 said:
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
Click to expand...
Click to collapse
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.

kylster said:
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
Click to expand...
Click to collapse
Take the patched one and flash it like you would any boot.img
Flash w/ Fastboot

pensive said:
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.​
Click to expand...
Click to collapse
not sure if i can paste here, but here we go...
Spoiler
https://www.reddit.com/r/razerphone/comments/iyb47z
im not sure why in razer webpage is incorrect, but is the same server AWS
P-SMR7-RC003-RZR 210107.3225Security Maintenance Release / Over The Air (OTA) UpgradeGlobal (Aura)9.0 Pie2021 February 05
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3225-user-full.zip

Hey I recognize that post

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541