Related
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.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210405.005, Apr 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776322
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776321
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693776320
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ2A.210305.006, Mar 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210305.006-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145746585
coral-rq2a.210305.006-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145746583
April 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210405.005-0d148a1d.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq2a.210305.006-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210305.006-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq2a.210405.005-0d148a1d.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
niko26 said:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Maybe you should update your platform tools to the latest version: it's v31.0.0 as of February 2021. Your log says you're running 30.0.4.
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
You'll have to re-root after each update. The method used to keep root when updating via OTA was removed from Magisk b/c it was causing problems on Pixels.
niko26 said:
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
i5lee8bit said:
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
Click to expand...
Click to collapse
Ohhh yes thanks to remember me i forgot to write FLASH i was only boot without flash. Thanks for all
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Ghisy said:
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Click to expand...
Click to collapse
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
@Lughnasadh Yeah, I'm already rooted on v22. Just did the app update then direct install and it worked fine! I've been in the rooting game since the HTC Desire but the latest changes with Magisk confused me for a minute there!
Thanks
bluizzo said:
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
Click to expand...
Click to collapse
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Lughnasadh said:
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
Click to expand...
Click to collapse
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
i5lee8bit said:
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
Click to expand...
Click to collapse
Nah, you're good fam. I ended up accidentally flashing the factory img and I'm back with root. Thank you for your help and the guides
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Thank you.
TWRP got stuck booting: I see the logo, "teamwin" and the version used 3.5.2_10-0
Everything was up to date, I'll try it again with an older version of TWRP.
Well, I dont know how to boot into LOS. It just froze on the mentioned screen.
Has anyone a idea what to do?
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
Ok, I tried it my way - it wont work (of course). Maybe TWRP is still not supported for Android 11.
Now I'll try it your way (thx again).
In order to flash the kernel, I'll have to unzip the elementalx file, I assume. And boot the avaible image, which is called "dtbo.img".
I'll give this a go...
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
fastboot flash boot boot.img did not work. I renamed the file to boot.img (did not mention this before).
Tried it twice, but nothing worked afterwards, not even recovery and I was not able to turn the device off.
Had to flash LOS again.
I also tried flashing the kernel using sideload while flashing the rom again.
Sideload did work, BUT the wifi was not working at all.
I dont want to bother you, but might there be another way?
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
uppon2 said:
That is all. Keep in mind things like wifi might not work if you forget to flash the kernel modules! - Just be sure it is always a 2 step process.
Click to expand...
Click to collapse
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
caraman said:
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
Click to expand...
Click to collapse
Wifi is usually a kernel module that gets loaded through an init script on boot. It's possible to build the wifi module built-in to the kernel, which makes it so it doesn't have to load separately through an init script.
So if youre not using the stock kernel you'd have to ask whoever makes the kernel you are using.
caraman said:
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
Click to expand...
Click to collapse
Magisk should not be that complicated. All the hard work has been done and can be found in Magisk documentation. There are install instructions for just about any type device and if there is LOS for your device I'm sure it is covered. The latest Magisk is not TWRP flashable the same way as it used to be and newer devices often don't have ramdisk in boot image and root is achieved thru recovery instead. You referenced several threads and guides but no indication of Magisk instructions. Read the Magisk installation instructions for your device type, they're not just suggestions, they work.
Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?
even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!
OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?
Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.
Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.
Hi,
I've tried to flash a new magisk-boot img, following this guide, after downloading the signed flashable zip LE2113_11_F.75.
I've patched the boot.img with my magisk app, and after flashing it,my OnePlus 9 doesn't boot anymore.
I've got this error : QUALCOMM CrashDump Mode. dm-verity device corrupted. verity-ctr
I can't boot to TWRP, I tried a fastboot boot and a fastboot flash recovery, but I always get a Qualcomm dump error.
Can someone help me to fix this issue ?
Thanks !
this refrence might help-
Help needed! Qualcomm Crash dump after trying to reinstall magisk upon upgrade to Android 11
Hi, Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error. After...
forum.xda-developers.com
"The update to [Insert Version Here] does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to [Insert Version Here] is finished though, so you can still have root.
In your case manually upgrading to [Insert Version Here], letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc"
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Flashing A/B zip to inactive slot : B
Step 1/2
Error applying update: 23 (ErrorCode:: kDownloadManifestParseError)
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
AutruiP said:
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Click to expand...
Click to collapse
It's not a problem if one slot is broken, it will probably fix itself on the next update.
Hi, thanks for your answer.
The fact that you talked about the next update made me try to locally install the update with the signed flashable zip, using the system updater. It worked and fixed everything !
Thanks