It seems that I cant even boot to system after flashing magisk by this method.
• Bootloader already unlocked
If anyone know the solution please assist me on how to install magisk to Xperia Z3
You have to use this tool to remove Sony RIC AND apply the DRM Fix to your boot.img (or a custom kernel boot.img).
Both RIC disabled and DRM Fix is needed, otherways it wont boot.
https://forum.xda-developers.com/xpe...el-dm-t3301605
Then flash the new fixed boot.img through fastboot:
fastboot flash boot boot.img
After that just flash newest Magisk (or patch it from within the Magisk Manager app).
ELF doesnt work for newer devices.
Greets
Related
I'm trying to get Magisk working by using BootBridge-SonyELF.zip and Magiskv14 or v14.3 and whenever I flash using TWRP magisk isn't installed.
I'm currently running stock 23.5.A.1.291, flasing 14.3 without boot bridge gives me bootloop.
I've also tried Advanced_Stock_Kernel_Z3_MM_6.0.1_23.5.A.0.575_twrp_3.0.2-0 and .291, same result.
Any Ideas?
Today I tried patching the boot.img in magisk manager for the boot.img from Advanced_Stock_Kernel_Z3_MM_6.0.1_23.5.A.0.575 and .295 and after flasing and rebooting magisk reports it's not installed
You have to use this tool to remove Sony RIC AND apply the DRM Fix to your boot.img (or a custom kernel boot.img).
Both RIC disabled and DRM Fix is needed, otherways it wont boot.
https://forum.xda-developers.com/xpe...el-dm-t3301605
Then flash the new fixed boot.img through fastboot:
fastboot flash boot boot.img
After that just flash newest Magisk (or patch it from within the Magisk Manager app).
ELF doesnt work for newer devices.
Greets
So I rooted my Pixel 3 and installed Magisk but installed a bad module and got a bootloop so I flashed the original boot.img to both boot slots but the phone is still in a bootloop. Any suggestions? Can't use TWRP because Android 10.
Edit: Did a full reinstall of the factory image for the update I'm on and it worked didn't lose data.
fastboot flash bootloader boot.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image.zip
Edit 2:
New question though, when I try to install magisk now it won't work - I'm assuming this is because the files for the old Magisk modules are still there and it runs them automatically. Is there any way to get rid of those? Might be a different problem too not sure.
TheHolyCity said:
So I rooted my Pixel 3 and installed Magisk but installed a bad module and got a bootloop so I flashed the original boot.img to both boot slots but the phone is still in a bootloop. Any suggestions? Can't use TWRP because Android 10.
Edit: Did a full reinstall of the factory image for the update I'm on and it worked didn't lose data.
fastboot flash bootloader boot.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image.zip
Edit 2:
New question though, when I try to install magisk now it won't work - I'm assuming this is because the files for the old Magisk modules are still there and it runs them automatically. Is there any way to get rid of those? Might be a different problem too not sure.
Click to expand...
Click to collapse
Here is what you need and need to do.
https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433
Hello.yesterday i tried to root my OnePlus 7 pro.i unlocked the bootloader first and then I have installed the twrp on slot a and slot b.then I have installed magisk,from this moment the WiFi on my phone stopped working.(when I am turning them on the automatically turned off)I tried again to flash stock ROM and twrp but when I install magisk I had the same problem.Then somehow I accidentally bricked the phone and today I have the stock ROM with unlocked bootloader and I need your help to root.
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
The phone now is stock and unrooted
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
20.3 is the latest version and works perfectly fine on mine
o.o
How is it not stable?
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
Can you Share a screen capture of your twrp file and your fastboot command
I will try again later and post screenshots
Dont understand.
HermitDash said:
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Click to expand...
Click to collapse
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Can you explain this easier method you said here to try it as i am a noob?
panagiwtis90 said:
Can you explain this easier method you said here to try it as i am a noob?
Click to expand...
Click to collapse
Okay, new to this thread. Where are you at right now? Booting? Which OS, TWRP, Magisk versions?
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
I am on the same version what I did was find the patched boot image with magisk for Android 10 flashed it using adb then installed magisk manager and I had root.
https://forum.xda-developers.com/on...atched-boot-image-oneplus-7-pro-t3964345/amp/
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Follow this guide and you won't need to use the patched boot,img file. I've never liked using the patched boot img.
Thank you GeekMcLeod your method worked
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Click to expand...
Click to collapse
It's just easier than having to manually extract the boot.img
fastboot boot twrp is just to get twrp up and running then flashing the script actually installs it.
Yes it does say that it'll unroot you but for those that are unrooted already this step doesn't do anything.
After flashing you reboot TWRP so it works fresh post-script.
Then install magisk as usual and reboot to system done.
This is if you want both TWRP and Magisk all done at the same time vs booting the boot.img installing Magisk then installing TWRP where I can have it all done within TWRP which is the usual route people take to get to root.
My comment below in red font:
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same.
Fastboot boot twrp just remotely boots a "temporary" (one time) instance of TWRP, but does not install TWRP to the device. Flashing the TWRP installer zip is for installing TWRP on the device. This is optional and a matter of personal preference, and not needed to achieve root. What the installer zip does, is extract the boot.img and injects TWRP, then installs that modified boot.img back to the phone.
And when you do flash the twrp.zip it says your now unrooted flash magisk.
Correct. When the installer zip patches the boot.img to install TWRP (as described above), root is removed.
And when you flash magisk it actually then unroots magisk.
Not correct. Magisk roots the phone. If you flashed Magisk and did not have root, what may be happened, is that you may have flashed Magisk to one slot, then somehow booted to the other (unrooted) slot.
The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Manually patching the boot.img is certainly a valid way to achieve root, and maybe more reliable. I'd hesitate to say it is "easier".
Also, if you flash TWRP as a Magisk module, you will still need to flash Magisk again to have root. Flashing TWRP by that method will still unroot the phone, same as the other method (as I described above).
Click to expand...
Click to collapse
---------- Post added at 08:56 AM ---------- Previous post was at 08:44 AM ----------
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
You did it wrong. Those two command do completely different things. So the difference in commands is a big one.
As I mentioned above, fastboot boot TWRP.img just remotely boots a temporary (one time) instance of a boot.img that has been patched to include TWRP. Then the correct way to install TWRP to the phone is (from the temporary booted TWRP) flash the TWRP installer zip, which properly extracts your phone's boot.img partition, patches it to install TWRP, then installs the modified boot.img back to the phone.
Fastboot flash boot TWRP.img does something completely different. It flashes the img to the boot partition. "Flash" is the action in this case, and "boot" is the location (not the action). The TWRP img is not meant to be installed to the phone. Don't know for sure, but I highly suspect that boot.img has some differences depending on your 7 Pro model. So when folks incorrectly flash TWRP.img, they are replacing the phone's kernel and breaking WiFi, and sometimes cell network and/or Bluetooth. Again, the correct way to install TWRP is to use the installer zip (as described in the previous paragraph) which properly takes your phones specific boot.img and patches it.
What folks should understand, is that A/B partition devices (like the 7 Pro) do not have a discrete recovery partition. Recovery is part of the boot partition, which also contains the kernel. So by doing "flash boot" you are messing with the kernel in ways you should not, and therefore results like broken WiFi is not surprising.
---------- Post added at 09:06 AM ---------- Previous post was at 08:56 AM ----------
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
Magisk if fine. Your issues are due to pilot error, as I've described above.
Any guides available for this latest OTA security update to preserve or restore root after applying?
Haven't yet done this on a 4a. Last did something similar on a Pixel 3a, but don't want to risk assuming the steps are the same, or even similar.
Anyone succesfully applied the security update yet and been able to restore Magisk?
This is what i did:
1. download both the full OTA file and the factory image file.
2. extract the boot.img from the factory image
3. in magisk patch the extracted boot image, copy back to PC
4. apply update in recovery - adb sideload ota_file.zip
5. reboot to bootloader
6. flash your rooted boot image from step 3
7. reboot phone.
8. i failed safety net and had to install this module through magisk - https://github.com/kdrag0n/safetynet-fix
I downloaded and installed the Jan OTA before realizing the Magisk inactive slot trick was broken :-(
Instead of restarting (and losing root) I patched the latest booot.img, restarted to fastboot, flashed the patched boot... Now when I try to restart it's the black google screen for a while, then back to fastboot with "no valid slot to boot" massage. Any advice on how to fix this? Or if it can't be fixed, best way to start fresh with rooted factory rom? Thanks!
Just try to flash both slots:
fastboot flash boot_a boot.root.sunfish-rq1a.210105.002.img
fastboot flash boot_b boot.root.sunfish-rq1a.210105.002.img
mrpeters said:
Any guides available for this latest OTA security update to preserve or restore root after applying?
Haven't yet done this on a 4a. Last did something similar on a Pixel 3a, but don't want to risk assuming the steps are the same, or even similar.
Anyone succesfully applied the security update yet and been able to restore Magisk?
Click to expand...
Click to collapse
Yea its all basically the same procedure on all A/B devices today and Magisk!
Meth0d said:
Just try to flash both slots:
fastboot flash boot_a boot.root.sunfish-rq1a.210105.002.img
fastboot flash boot_b boot.root.sunfish-rq1a.210105.002.img
Click to expand...
Click to collapse
Thanks so much for the suggestion. Unfortunately that didn't work, still was getting to the black google screen for a couple min and then back to fastboot.
So I used google's flash link to install the newest version of stock ROM via chrome browser, and it worked, my data was preserved as well! Root was lost.
In case anyone else had this problem, when I went to re-root using fastboot flash boot (patched img) I was getting:
FAILED (remote: Failed to write to partition Not Found)
So I flashed as you described above to boot_a and boot_b and IT WORKED! THANK YOU!!
Everyone hello!
After updating by ota (86->151), magisk app can't detect new patched boot. Of course, have flashed new patched boot in slot B (if flashing in slot A, phone goes to bootloop).
Any suggestions?
Did you make sure to patch the boot from 151 and have you tried not forcing a slot selection?
Something similar happened to me so I just restored my phone using the fastboot return to stock method I downgraded I am on 86 now don't plan on updating. When I did update my phone was acting weird it wasn't as smooth so I downgraded everything's good well except for safety net but I think that's a Google issue for now
If updated using OTA from Asus helpdesk site file - After flashing the file, You gotta make sure to open magisk and flash to inactive slot before the first reboot. If not, it's too late to fastboot patch it. Not sure why though. It's a learning from my Trials and errors.
If updated using RAW - You need to uninstall Magisk before anything. Open the app, Uninstall Magisk, and reboot. Then Flash Raw in fastboot, and then flash the Patched boot image made from the same firmware.
If you flash Raw while on magisk, and then patch with a Magisk patched Boot IMG - it results in bootloop. I dont whats the cause, or how it happens. Recovery for this is to flash Magisk Uninstall zip in TWRP, and then flash Raw, and then fastboot flash with Magisk patched boot image.
Since there is not TWRP for ROG 5 - I can suggest revert back to the working firmware (Previous version) with magisk, boot in, Uninstall Magisk, and then Flash the new Raw file. This method so far worked for me in the latest file.
Cheers!
JazonX said:
If updated using RAW - You need to uninstall Magisk before anything. Open the app, Uninstall Magisk, and reboot. Then Flash Raw in fastboot, and then flash the Patched boot image made from the same firmware.
If you flash Raw while on magisk, and then patch with a Magisk patched Boot IMG - it results in bootloop. I dont whats the cause, or how it happens. Recovery for this is to flash Magisk Uninstall zip in TWRP, and then flash Raw, and then fastboot flash with Magisk patched boot image.
Click to expand...
Click to collapse
It should overwrite the boot, which is the entire Magisk. Never had an issue not uninstalling.