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
Helloguys and gals,
I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8
I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.
To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.
So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?
Edit: My phone is still on the update from November 2018.
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
bafforosso said:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
Click to expand...
Click to collapse
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
levibuko said:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
Click to expand...
Click to collapse
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :
Code:
fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
tenthousandfeet said:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
Click to expand...
Click to collapse
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
wangdaning said:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
Click to expand...
Click to collapse
Tried that. No success.
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
wangdaning said:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
Click to expand...
Click to collapse
I had a similar thought, but no dice. Tried installing Magisk 19.2, which boot looped just like the latest 19.3.
I even went back to 16.7, and though that one didn't boot loop it also didn't show up in the system. Magisk Manager didn't recognize it, anyway.
Though I'm loathe to do a full wipe/reset and then reconfigure all my junk, I may be headed in that direction as I'm running out of other ideas. Perhaps I'll save a backup just before that I can return to if the reset is fruitless.
---------- Post added at 07:53 AM ---------- Previous post was at 07:36 AM ----------
Magisk 18.0 does the same as 16.7 - no bootloop, but no root.
Interestingly, I noticed that the 18.0 and 16.7 zip installers say something about the partition being boot_a, whereas the bootlooping 19.2 and 19.3 zip installers say it's boot_b.
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
sliding_billy said:
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
Click to expand...
Click to collapse
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
sliding_billy said:
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
Click to expand...
Click to collapse
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
tenthousandfeet said:
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
Click to expand...
Click to collapse
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
Please update when/if you find a solution. We are both in the same boat.
I'll let you know if I get anything working.
sliding_billy said:
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
Click to expand...
Click to collapse
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
tenthousandfeet said:
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
Click to expand...
Click to collapse
It still looks like your boot slot ended up the one you had tried already (b), since you changes to a and ran flash-all, changed back to b and ran flash-all and rebooted. As for the old platform tools, that could definnitly have an impact on running the fastboot of the patched boot. Other than that, I think a flash-all with the -w is the only approach left.
I'm also in the same boat. I've tried all the various install methods, and done the double "flash-all" on both slots, and no matter what, it ends in a bootloop.
Haven't tried the -w yet so I'll be interested if anyone gives that a go. Until then I'm dying with no root
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.
Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery
Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link
lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!
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!!