The last one went down well so here's another one for anyone using this phone:
Offering a prepatched boot_a.img and boot_b.img to any that want them to flash via fastboot or TWRP.
Contains:
Latest 8.1 Stock version of Razer's Generic-Branded boot.img patched with Magisk Root, RootHide and Modules 19.3, TWRP, and Xposed.
(Xposed may need to be reinstalled via Magisk
If so, install Riru - Core, then Riru - EdXposed - Sandhook)
(If installed through Magisk, it will sometimes keep the Safetynet Check valid letting you use MagiskHide to access some banking apps etc)
--
Why?: Timesaver and ease of use.
Creating a functional boot image with these options is trial and error and can be a pain.
--
--
Download:
[/url]https://drive.google.com/file/d/1ewUP9rBQdoeIQgiIXhN-nNB1Vy0LtUnk/view?usp=drivesdk[/url]
--
To any that want to test; if this doesn't work then just flash stock img and you'll be fine.
(Can't promise this patched boot image will work for you but it'll be nice if it does.
The last one worked great.) =)
Terms:
(Still, for the sake of disclaimer and to prevent most trolling etc I am NOT responsible for any damage you cause to your phone. You or your legal guardian are/is responsible for your property.
You agree that you will backup your boot.img files or at least download a fresh one from razer's website.
By using these files you are agreeing to these terms.)
-
P.S: For any not aware you can flash an image to a specific slot by using
fastboot flash boot_a
Or
boot_b
Instead of just boot (which flashes both with the same image)
doesnt work
after i flash either or both of them and reboot it says your device has been unlocked blah blah then when that goes away it reboots into download mode.
Edit: I can however, access twrp by holding vol up while booting with a usb in the pc
Edit2: yeah cant get this to work at all, flashing stock img.
Thanks very much for doing this. Would you be able to provide a prepatched boot img for the new pie update or do you know if this one works with pie? Maybe Razer didn't touch the boot img when they provided the update.
Sorry for not seeing replies to this thread earlier.
#1 I'm sorry for your issues with the image and that you're not able to get it working. I wish I knew how to help.
#2 When I update and can make some new boot images and upload em. It may be a while until I update.
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.
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
adb devices
adb reboot bootloader
fastboot flash boot "D:\Downloads\boot_patched.img"
fastboot reboot
Click to expand...
Click to collapse
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
fastboot flash boot_a "D:\Downloads\boot_patched.img"
fastboot flash boot_b "D:\Downloads\boot_patched.img"
Click to expand...
Click to collapse
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
iamMG said:
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
Click to expand...
Click to collapse
I had an issue before, with the Canary APK. Try installing the v23 app and repatch your boot IMG with it. Worth a shot.
I tried, again, with v23. Same bootloop occuring.
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
@soka said:
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
Click to expand...
Click to collapse
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
iamMG said:
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
Click to expand...
Click to collapse
True, sorry just trying to help you narrow it down.
@soka said:
True, sorry just trying to help you narrow it down.
Click to expand...
Click to collapse
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
iamMG said:
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
Click to expand...
Click to collapse
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
BillGoss said:
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
Click to expand...
Click to collapse
Thanks, I will try this method and report back.
Btw, after you booted using this method, for how much time did the boot animation showed up (the two circling white dots around bigger red dot)?
Edit: I tried this method. No luck. The boot animation goes on 5-10 minutes, at which point I reboot into bootloader and flash the stock boot image.
Anyway, I ended up downgrading to OxygenOS 10.3.8.
Starting to give up as well... Never had any issues before (on Android 10) to flash root on O7Pro, but ever since Android 11, I keep having "boot loop" issues. Aka, the boot logo keeps loading and never boots into the OS. Only works again if I re-patch the original boot.img file.
This is starting to get.. VERY, VERY annoying. Why isn't there any proper method of getting this to work?
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
hkdoublecat said:
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Click to expand...
Click to collapse
I am too afraid to upgrade to OOS 11, only to find out root doesn't work for me. The restore function of this unofficial TWRP version is buggy so can't really depend on it to restore OOS 10.3.8. So, I have decided to stay on the latter until Team Recovery releases a proper update for Android 11.
altwu said:
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
Click to expand...
Click to collapse
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Mangtas_666 said:
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Click to expand...
Click to collapse
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
altwu said:
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
Click to expand...
Click to collapse
i tried attaching the images to the post but they're not showing up. i tried editing the post to attach the images, but they're still not showing up. sorry.
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.
i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
and what if i want to root the phone? flashing the stock rom gets rid of magisk, am i stuck without an option to root it? or should i install a custom recovery or cus os like calyxos?
new problem, i cant flash the stock rom using sp flash tool, gives me this weird error:
STATUS_BROM_CMD_STARTCMD_FAIL
any help?
I did this to my old phone if sp flash ain't working
"fasboot flash all slot a". if a/b partition
"fastboot flash all". if not a/b partition
and I feel like this method is faster than sp flash tool
edit:
lucky you could go to fastboot unlike mine can't go anywhere when I tried to flash my device it just reboot after 6 or 5 seconds ;-;
Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524
Tzuyoda said:
Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524
Click to expand...
Click to collapse
Download Infinix Stock ROM for all models (Latest Firmware)
Download the latest Infinix Stock ROM Firmware (Flash File) for all the available Infinix smartphones, feature phones, and tablets.
androidmtk.com
I could only find this one site that has all of the stock roms of XOS. Not exactly the model number. Just a 'c' and 'b' difference
Did you fix it? If not I can help you
I think the stock roms would work.
boomzkik said:
Did you fix it? If not I can help you
Click to expand...
Click to collapse
do you have the latest firmware files? i removed root and updated ota and i cant find any source of firmwares online, only the stock ones. can i use stock boot.img and patch it with magisk then install the patched stock boot.img with fastboot on an updated firmware?
mlgpro12345 said:
i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help
Click to expand...
Click to collapse
Please I need your help on how you were able to root your infinix hot 10. I have the same phone and I was following YouTube tutorials they told me to use minimal adb and fastboot.. all the commands worked great but when I use command fastboot flash boot and paste my patched boot img it shows error... Unknown partition cannot determine image filename for boot img or so.