Does anyone successful root razer phone? kindly looking for video tutorial from 0 . Or anyone be able root my phone remotely? I'm living in n Everett , WA. I will pay the service if success thank you
Recently pulled mine out of storage to see if I was going to be able to use it for anything.
Unfortunately, most guides are out of date or give instructions that simply do not work anymore.
My best advice to you is that if you're going to root, avoid TWRP completely. Every attempt to modify a boot image or flash updated boot images from within TWRP caused my device to bootloop.
If you want to do it yourself (and I recommend that you do)
On your Razer Phone, Unlock bootloader,
Unlock flashing and flashing critical,
Flash the entire last Pie boot image from Razer ( https://developer.razer.com/razer-phone-dev-tools/factory-images/ ) 9.0 - MR2
Reboot into the OS and make sure you get the Welcome screen before shutting it down.
On a different phone, Copy the Razer Pie boot.img from the Razer system image download above (9.0 - MR2) to the other phone (any other phone that has Magisk)
Go into Magisk, click to update Magisk Manager, but instead select update an image file from SD Card. (The Razer Pie boot.img file)
When the boot.img file is updated from within Magisk Manager, copy it back off the phone to your PC.
Reboot your Razer Phone into Download/Fastboot mode,
And flash that modified boot.img to your phone. (fastboot flash boot_a magisk_patched.img, fastboot flash boot_b magisk_patched.img)
I was unable to get any boot images to stick if I didn't reboot into the OS after flashing stock first.
If you are on Pie already, you can try my boot image. But as always, if you **** up, I'm not going to be able to help you fix it. These instructions assume that you know how to get into fastboot and use fastboot flashing commands. So if you know how to flash a stock image from Razer, you should know how to flash a modified boot image.
https://www.androidfilehost.com/?fid=8889791610682915381
MD5: 9cfe9fe7ed040511c1dfb3454207c1c4
File: Magisk Patched boot.img for Razer Phone (2017) latest Pie devices (cheryl-p-release-7083) ONLY. No TWRP.
I was also able to get Substratum to work on Razer Phone 1 Pie. That was a bit of an ordeal in of itself.
Can make a thread if people need to know how.
Related
I am trying to root my IN2017 and am struggling with understanding the next steps. I have the bootloader unlocked (T-mobile and OnePlus), installed Magisk Manager, installed TWRP, but cannot figure out the next step. Basically all directions mention a boot.img but I cannot find one for the IM2017. Am I missing something here?
Any help would be greatly appreciated!
Since you are using a T-Mobile variant, you are still running Android 10. Simply download the latest Magisk zip from github and flash it in TWRP. Done.
Another possibility - in TWRP take a full backup of the device and transfer this to your computer. The boot should be named "boot.emmc.win" rename this to boot.img, upload it to your oneplus. In magisk manager, patch this file for magisk. Take the new magisk-patched-boot.img and transfer it back to you computer. From your computer use fastboot and in the directory with the patched boot image type:
fastboot flash boot_a magisk-patched-boot.img
fastboot flash boot_b magisk-patched-boot.img
(or replace magisk-patched-boot.img with whatever it is named)
Hope this helps.
Once the device is rooted, make sure you take the persistent.img and transfer this off the device, in case in the future you lose your fingerprint sensor! If this image on the device gets corrupted, then you will lose your ability to unlock by fingerprint.
Hope this helps.
Cheers,
B.D.
So my awesome OP7Pro got drowned and I had to get a new one. I foolishly let it update to 11.0.1.1 right away, because I thought I could still use my tried and true method of booting (not flashing) to TWRP and using that to flash Magisk, as I want root but I don't really need TWRP. This has always worked for me before, but when I tell the phone to fastboot boot the twrp image it just sits there with the Fastboot Mode image on the screen.
Plan B was to try to figure out how to patch my boot.img. I downloaded the 2.4GB zip vix Oxygen Updater and extracted it to get to the payload.bin, but I can't seem to get Python and Visual C++ set up right to help me extract the boot.img. Even if I get that done I'm not sure I really understand the specific next steps, though I think it is us adb to use Magisk to patch it, then use adb to boot via the patched boot.img, and then install magisk and let it patch the "real" boot image.
Any help in regaining root would be appreciated.
Found a kind sound who had posted a patched and original boot.img from 11.0.1.1, and I was able to use that and the steps I noted under Plan B to get things settled.
There's a method on Magisk to let you to revert boot and apply OTA, and install root again.
This method applied to most Moto phones.
1. Check for update. Settings >>> System >>> update.
2. If you found a new version available, go to Magisk and "uninstall" and revert to original boot.
3. Install OTA system update. DO NOT REBOOT!
4. Go back to Magisk and install on "unused partition". Reboot when finished
If there's an error "unable to revert", you need to get ROM matched the build number, and get the boot.img, copy the boot to the phone and let Magisk "install and patch". This method will give an original boot to revert, and run step 2 again.
If the method above didn't work, you need to do the following.
1. Assume you have original boot and updated boot. Reboot in fastbootd (only for models shipped with Android Q, R, S) or bootloader (shipped with Android P or earlier)
Code:
fastboot reboot fastboot
or
Code:
adb reboot fastboot
2. From there, you can flash original boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot into command window, and press enter.
Reboot when finished
3. Install OTA, and hopefully you have updated boot with matched build number. When OTA installation finished, copy updated boot to the phone and patch it with Magisk, and copy back to host computer, and reboot.
4. Once the phone finished post update, reboot to fastbootd
Code:
adb reboot fastboot
, and flash patched boot.
Done
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
noobtoob said:
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
Click to expand...
Click to collapse
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing.
gullzway said:
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing
Click to expand...
Click to collapse
Well, fastest method for me was:
1. Boot to twrp>backup data. Copy backup off phone.
2. Update phone from LMSA.
3. Follow previous root guide to patch the boot.img (extract from LMSA folder on computer).
4. Fastboot flash the patched boot image.
5. Boot to twrp>copy backup to twrp folder on device>restore data.
You don't have to setup your phone for any of this.
Edit: Obviously you have to setup your phone to install magisk and patch the boot.img. I mean minimal, like skipping all the account .
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP