ROOT with PIE Guide

Search This thread

shango22

Senior Member
Jun 16, 2013
52
5
Root

Questions as I'm considering root
1. Is it stable? No major bugs on latest firmware (i.e. blutooth, lte issues etc)
2. Is there a chroma varient for GSI?
3. Is there a high brightness mod?

Thanks having trouble finding the answers.
 

Generic123.

Senior Member
May 3, 2016
147
29
OnePlus Nord N10 5G
Does anyone have a idea if there a MR2 version yet?

Can't you just flash the Arter97 Kernel, and then flash Magisk through the provided TWRP?

Questions as I'm considering root
1. Is it stable? No major bugs on latest firmware (i.e. blutooth, lte issues etc)
2. Is there a chroma varient for GSI?
3. Is there a high brightness mod?

Thanks having trouble finding the answers.

1. Stock is pretty stable; I had no issues when I used it. However, based on your 2nd question, it seems like you want to switch to a GSI. In that case, GSI's are pretty stable, with a few notable issues:

  • Bluetooth audio does not work unless you delete 2 apks from /vendor/overlay(BluetoothResCommon.apk and RazerAuraBluetoothRes.apk). Make sure you do this before you boot into the GSI for the first time.

  • The fingerprint sensor has a tendency to not work, meaning that you'll have to type in your password sometimes.

  • When you try to charge while the phone is off, the screen will constantly flicker blue; the only way to stop it is to turn off the phone, or just turn it on.

  • There will be points where you cannot receive texts; just re-insert your SIM card into your phone. You will have to do this every time you reboot the phone.
2. You could use Logo+, which is an alternative app for the Chroma app.
3. I don't think you're going to find any "mod" that can turn up the brightness of the display above it's max brightness, as that would probably destroy the screen if it existed.
 
  • Like
Reactions: AlDollaz

madroxide13

Member
Apr 6, 2019
7
2
Does anyone know if we are able to use Google pay or even Netflix if our phone is rooted? Has that problem been fixed?
 

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
I am having trouble rooting Razer Phone 2. It is brand new, stock everything.

I successfully unlocked the bootloader following chpimentelpr instructions. This is confirmed when I boot into fastboot mode - it states bootloader is unlocked.

For some reason, I cannot patch Magisk boot.img using this command: fastboot flash boot_a boot.img
Here is the output of the failure (I'm rooted in terminal):
Code:
[email protected]:/home/XXX/platform-tools# fastboot flash boot_a boot.img
Sending 'boot_a' (20768 KB)                        FAILED (Write to device failed (No such device))
fastboot: error: Command failed

I run Linux (Ubuntu, Mint, and Debian). I downloaded the latest platform tools adb and fastboot. The file "boot.img" is in the same folder as adb and fastboot.

ADB and fastboot recognizes the device. This is confirmed by running fastboot devices. Here is the output:
Code:
[email protected]:/home/XXX/platform-tools# fastboot devices
181939V01500871	fastboot

Why can I not flash to boot_a? I tried boot_b with the same results.
 
Does anyone know if we are able to use Google pay or even Netflix if our phone is rooted? Has that problem been fixed?
Works fine for me on MR2
I am having trouble rooting Razer Phone 2. It is brand new, stock everything.

I successfully unlocked the bootloader following chpimentelpr instructions. This is confirmed when I boot into fastboot mode - it states bootloader is unlocked.

For some reason, I cannot patch Magisk boot.img using this command: fastboot flash boot_a boot.img
Here is the output of the failure (I'm rooted in terminal):
Code:
[email protected]:/home/XXX/platform-tools# fastboot flash boot_a boot.img
Sending 'boot_a' (20768 KB)                        FAILED (Write to device failed (No such device))
fastboot: error: Command failed

I run Linux (Ubuntu, Mint, and Debian). I downloaded the latest platform tools adb and fastboot. The file "boot.img" is in the same folder as adb and fastboot.

ADB and fastboot recognizes the device. This is confirmed by running fastboot devices. Here is the output:
Code:
[email protected]:/home/XXX/platform-tools# fastboot devices
181939V01500871	fastboot

Why can I not flash to boot_a? I tried boot_b with the same results.
Reboot your computer or try a different port and/or cable. It's just a simple com issue
 

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
Hi team,

I got a new cable and that was the initial problem. Now I can flash via fastboot.

I flashed the boot.img from this link from Warrior1988:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454

I downloaded the MR1 because that was the only one available. My phone is MR2 from stock. So when I flashed Warrior's boot.img I got stuck in a boot loop with the razer animation. I believe this is because the boot image is for MR1 and all the other files on the device are related to MR2.

I'm also a little fuzzy on how to install Magisk and at what stage. Should I already have Magisk installed before I flash a boot.img? Or when?

omega, if you have it on MR2, did you actually flash/install Magisk when you were MR1 and then updated? If so, then I likely have to downgrade to MR1, flash/install, and then upgrade to MR2.

The best option would be if Warrior1988 can create an MR2 boot.img. Thanks for all the help team!
Works fine for me on MR2

Reboot your computer or try a different port and/or cable. It's just a simple com issue
 

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
SOLVED

Update
SOLVED

I am now rooted with Magisk on MR2. The work around was to downgrade to MR1 before beginning this entire root process. Razer gives excellent instructions on how to achieve this on their site here:
https://developer.razer.com/razer-phone-dev-tools/general-instructions/

It is important to note that in order to downgrade you must
Code:
fastboot flashing unlock_critical
. You'll brick your device otherwise. After I downgraded to MR1, I was able to follow the instructions to get root with Magisk. It takes time and reading.

I hope this post helps others in a similar situation.


Hi team,

I got a new cable and that was the initial problem. Now I can flash via fastboot.

I flashed the boot.img from this link from Warrior1988:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454

I downloaded the MR1 because that was the only one available. My phone is MR2 from stock. So when I flashed Warrior's boot.img I got stuck in a boot loop with the razer animation. I believe this is because the boot image is for MR1 and all the other files on the device are related to MR2.

I'm also a little fuzzy on how to install Magisk and at what stage. Should I already have Magisk installed before I flash a boot.img? Or when?

omega, if you have it on MR2, did you actually flash/install Magisk when you were MR1 and then updated? If so, then I likely have to downgrade to MR1, flash/install, and then upgrade to MR2.

The best option would be if Warrior1988 can create an MR2 boot.img. Thanks for all the help team!
 
  • Like
Reactions: kenfly

kenfly

Senior Member
Dec 22, 2009
752
56
Update
SOLVED

I am now rooted with Magisk on MR2. The work around was to downgrade to MR1 before beginning this entire root process. Razer gives excellent instructions on how to achieve this on their site here:
https://developer.razer.com/razer-phone-dev-tools/general-instructions/

It is important to note that in order to downgrade you must . You'll brick your device otherwise. After I downgraded to MR1, I was able to follow the instructions to get root with Magisk. It takes time and reading.

I hope this post helps others in a similar situation.
After rooting you can flash mr2 without loosing root? Or is there a process to make sure root isn't lost?
 

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
After rooting you can flash mr2 without loosing root? Or is there a process to make sure root isn't lost?

There is a way to attain MR2 after root, but not through flashing MR2.

Follow Magisk instructions for OTA (over the air) updates. Essentially, you have to flash MR1, install Magisk Manager, then use that to root MR1. After that, you upgrade to MR2 by OTV. Magisk provides specific instructions on how to do this without loosing root.

I have root and am on MR2. I used that method.

Find Magisk's instructions and read them thoroughly. There is a difference between Magisk Manager and Magisk. Two related but separate things.

Hope this helps!
 

kenfly

Senior Member
Dec 22, 2009
752
56
Update
SOLVED

I am now rooted with Magisk on MR2. The work around was to downgrade to MR1 before beginning this entire root process. Razer gives excellent instructions on how to achieve this on their site here:
https://developer.razer.com/razer-phone-dev-tools/general-instructions/

It is important to note that in order to downgrade you must
Code:
fastboot flashing unlock_critical
. You'll brick your device otherwise. After I downgraded to MR1, I was able to follow the instructions to get root with Magisk. It takes time and reading.

I hope this post helps others in a similar situation.

after unlocking the bootloader on MR2 I'm trying to run the fastboo flashing unlock_critical but the terminal just says
Code:
< waiting for device >

and the phone does nothing. just sits on the bootloader screen.

EDIT fastboot devices showed nothing

downloaded the drivers and the platform tools from the razer doc and got it working. apparently my installed ones were to old.
 
Last edited:

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,381
Deep Space Station K7
after unlocking the bootloader on MR2 I'm trying to run the fastboo flashing unlock_critical but the terminal just says
Code:
< waiting for device >

and the phone does nothing. just sits on the bootloader screen.
That sounds like the USB drivers are not installed. The safest check before doing anything is "fastboot devices". That should return the connected device's serial number. If it doesn't, then Fastboot can't find the device and often that's a cable, USB port or driver problem.
 
Last edited:

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
after unlocking the bootloader on MR2 I'm trying to run the fastboo flashing unlock_critical but the terminal just says
Code:
< waiting for device >

and the phone does nothing. just sits on the bootloader screen.

There are a few options to try. First, if you haven't already, try using "sudo" or "su" in terminal because you need super user privileges. If you're using Windows, you need to run your command prompt shell with admin privileges.
Second, make sure fastboot recognizes your devices by typing "fastboot devices" (again, might need sudo). Just because adb recognizes it, does not mean fastboot will. It should, but if not there is your problem.
Third, try a new USB port or buy a new cord. I had to buy a better USB A to USB C cord before this would work. You'd be surprised how often it's a cord or communication issue between the device and PC.
 

kenfly

Senior Member
Dec 22, 2009
752
56
now I'm bootlooping.

sucessful downgrade to MR1
installed magisk boot.img to a and b
installed manager
downloaded MR2 update
went into manager and did the inactive slot install
now bootlooping.
 

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
now I'm bootlooping.

sucessful downgrade to MR1
installed magisk boot.img to a and b
installed manager
downloaded MR2 update
went into manager and did the inactive slot install
now bootlooping.

Sorry to hear you are bootlooping. I am not certain why but we can try to figure it out.

Are you sure when you installed Magisk manager you followed the boot image patch instructions? Additionally, after you install the OTV update of MR2 to the inactive slot, you have to reboot the phone from within Magisk Manager.
 

kenfly

Senior Member
Dec 22, 2009
752
56
Sorry to hear you are bootlooping. I am not certain why but we can try to figure it out.

Are you sure when you installed Magisk manager you followed the boot image patch instructions? Additionally, after you install the OTV update of MR2 to the inactive slot, you have to reboot the phone from within Magisk Manager.

Yes, I followed the dual slot instructions. Although, there was a step that said to reinstall the original boot image (but there was no backup because I was already running the magisk boot.img.)That might've had something to do with it. There just isn't clear instructions here that I've seen to downgrade/ root and upgrade successfully retaining root step by step..

right now im on MR2 with the kernel/TWRP installed but would still like to haz root
 
Last edited:

superkid333

Member
Aug 4, 2016
17
2
Brooklyn
Yes, I followed the dual slot instructions. Although, there was a step that said to reinstall the original boot image (but there was no backup because I was already running the magisk boot.img.)That might've had something to do with it.

right now im on MR2 with the kernel/TWRP installed but would still like to haz root

If you already have a custom recovery TWRP, then you need to follow instructions to install Magisk via Custom Recovery, not Boot Image Patch section. That may also be why. You can install root/Magisk via TWRP. But I'm not familiar with that method entirely. Magisk has instructions as follows:

Code:
Custom Recovery

If your device has custom recovery support, the easiest way is to install it through custom recoveries, such as TWRP.

    Download the Magisk installer zip
    Reboot to custom recovery
    Flash the zip and reboot
    Check whether Magisk Manager is installed. If for some reason it isn’t installed automatically, manually install the APK
That is from this link: https://topjohnwu.github.io/Magisk/install.html

Hope that helps
 

MafiaKitten

Member
Mar 7, 2020
6
0
when i try to do the last steps (flashing the boot img) it gets stuck at waiting for any device, can someone let me know what im doing wrong?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Hi All,

    In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.

    *As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.

    Pre-Requirements:
    -Be sure to have at least 70% of charges... or plug your phone to power
    -Backup anything you consider important
    -Already installed Pie Upgrade via OTA or Side Loaded​

    -Enable Developer Options
    • Open Phone "Settings" and scroll down.
    • You will see an option "Build Number".
    • Simply tap on it 7 times to enable it on your Android Oreo based device.
    • Your device immediately display a message on screen that will say "You are now a developer".
    • The Developer Option is now available in the Settings>System>Developer Options. Enjoy!​

    - Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790

    -Unlock Bootloader
    • To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
    • Using ADB commands reboot on bootloader​

    adb reboot bootloader

    • After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.​


    Root and Installing Magisk
    Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.

    Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post


    • Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:

    fastboot flash boot_a boot.img

    fastboot flash boot_b boot.img

    fastboot reboot


    Install Magisk Download the apk and install it as usual on your RP2, that should be all.

    DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
    3
    Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
    Or are drivers and ADB two separate downloads?



    I assume this is where we plug our phone into our computer?



    For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.

    So your cmd will say:
    C:\Users\YourName>

    And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
    Assuming it was directly in C:, you should see something like:
    C:\adb>

    Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.

    Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.



    I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.

    fastboot flash boot_a boot.img

    fastboot flash boot_b boot.img

    fastboot reboot
    2
    yeah i found out what was wrong, finished flashing the .img files only to get a bootloop cause i flashed MR1 .img files to my phone (MR2) i need to get the .img of build P-MR2-RC001-RZR-190914.3123 but the file is 2 GB and i have a 5KB/S download speed :/ all i need is the .img from it, could you possibly provide me with it? i cant find it elsewhere

    Here you go: P-MR2-RC001-RZR-190914.3123-boot.img
    2
    How about the new update 9 Pie MR2 :
    Build number : P-MR2-SGT-RC002-RZR-190918.3666
    Can somebody help me root this !!!
    2
    This has to be......one of the most usefull and noob friendly guides i have ever seen.....

    You sir....are a God

    Thank You.