Related
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.
Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause
Hitman478™ said:
Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause
Click to expand...
Click to collapse
No, I didn't disable any module before the update. How should I now proceed?
I have tried this:
- flashed patched boot image
- disabled all the modules
- flashed stock boot image
- flashed patched boot image, now this time the modules were disabled
and other one, because this wasn't worked:
- flashed patched boot image
- uninstalled (with restore images) Magisk
- flashed stock boot image
- flashed patched boot image
but my issue still occurs in both cases. If I disable all the modules the SIM is working with the patched boot image, if I enable any of them, the SIM stops working.
So the problem is that I haven't disabled the modules, but now what should I do?
Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.
Sir Mohd said:
Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.
Click to expand...
Click to collapse
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.
Th3Scr34m said:
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.
Click to expand...
Click to collapse
Mine as well working now,
I flashed OB1 EU and i reinstall Magisk again and patch it
So SIM, WIFI, Magisk working fine now,
I think there is a problem with latest update with magisk IDK if some1 can confirm by any chance
Thanks.
Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.
Click to expand...
Click to collapse
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick
Felheipe said:
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick
Click to expand...
Click to collapse
Yes I had (and have now with the new setup) but I had it before 10.0.9 and didn't cause this kind of issues - actually I did this process 3 times without any problem.
You have to remove call recording module and.than reinstall
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html
Sir Mohd said:
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html
Click to expand...
Click to collapse
Thanks for the link, but I already found that information (and realized my mistake).
But on that page there is no clear answer on my original question. Does the flashing of patched_boot.img make me lose my apps and data?
I tried and found out, the apps and data are still there.
And, more important, magisk is working again!
Copied my oxygenOS-update.zip to my pc and patched my boot.img using these steps starting from step 2.
GoodSoul said:
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin dumper (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Click to expand...
Click to collapse
karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Simply flashing stock or patched boot img would not impact your apps and data, evenprevious magisk modules.
Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater,
whats the link u downloaded 10.0.11 HD65BA (EU) ota package from?
Click to expand...
Click to collapse
Hi,
OnePlus7T HD1903
I had working root, survived many OTA's, after each OTA I launched Magisk, flash inactive boot bank, it works perfect.
Last time i did the same, but have bootloop.
I downloaded ZIP with OTA, extracted payload, extracted stock boot.img, flash into phone so it boot
Tha same image I'm trying to patch with Magisk Manager 7.5.1 - but everytme i have bootloop.
Force encryption / dm-verify enabled.
Can I have working, patched IMG for my phone?
Or how to resolve my issue?
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)
Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/
Hello
I have big problem.
After patching img over Magisk and flash this new patched img, can not start system / boot loop to POCO logo, or boot loop to MIUI logo - here system starting, but every restart and boot loop
Help please
Thanks
Hi!
Which boot-img did you patch and where did it come from?
How did you flash it?
So:
I received an update 12.5.8.0.RKHEUXM
After the update, I always have to root the phone again.
So I took boot.img from the original 12.5.8.0.RKHEUXM and patched it via Magisk.
I flashed the patched boot.img via ADB.
Well, after the restart, my phone will boot only after the MIUI logo and a bit of a melody, and the phone will restart again. This restart is performed about 4 times and remains/stops in fastboot mode,or it will return to TWRP after clearing dalvik and cache and restarting.
He does what he wants
I've had a problem with that before, but it was enough to delete Dalvik and the cache via temporary TWRP.
Then the system booted up normally, but now it doesn't work even after deleting Dalvik and the cache.
Here is a link to the thread where I solved it. Nobody actually advised me there, I just tried to clear dalvik and cache via TWRP and it was after the problem. Unfortunately, now the problem persists.
Poco F3 - Boot Loop to POCO logo / Please help
Hello. I have a big problem after updating the firmware. Poco F3 root over magisk. After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM. After the restart, both the phone and the system booted up. I patched the original boot.img...
forum.xda-developers.com
Thats what I did also with 12.5.8.0.RKHEUXM and everything is working fine.
Updated to 12.5.8.0 via the MIUI updater, but downloading the full rom, as the updater told me that the incremental update (~58MB) wouldn't work.
Then downloaded the the recovery file here: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.8.0.RKHEUXM/
Unzipped it and extracted the boot.img with payload-dumper-go on my Mac: https://github.com/ssut/payload-dumper-go
Patched the boot.img with Magisk on the phone.
Copied the patched_boot.img file back to the Mac.
Flashed the patched_boot.img from the mac with fastboot to both partitions:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Friend, I did exactly what you were writing, and unfortunately my system won't start
The only thing I did differently was to download the big rom 6gb update so I didn't have to extract boot.img. I didn't have to use a payload dumper.
Any other solution?
But I don't want to lose data and applications!
Did you try wiping data partition?
takichiman said:
Did you try wiping data partition?
Click to expand...
Click to collapse
Where should I do it?
But I don't want to lose data and applications!!!!!
I have bootloop to MIUI logo 4times - 5times and then stop in fastboot mode , It stops in fastboot mode and after pressing and holding the power button, the mobile starts only in fastboot mode, it no longer starts booting to the MIUI log
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
takichiman said:
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
Click to expand...
Click to collapse
You didn't give me much advice, my friend
I don't want to lose any data, or applications, pictures, just anything.
If it went after deleting the dalvik / cache last time, then why shouldn't it go now?
The system boots only to the miui logo, then the boot loop.
I don't understand why this is so.
And can't you somehow refresh the whole rom without losing data, applications and files?
Boot temp recovery, backup boot, patch backed boot and flash patched boot ... Just rename the boot backed image of twrp in boot.img, patch and flash ...
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Dark-Yox said:
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Click to expand...
Click to collapse
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
snx413 said:
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
When you boot, you have access normally
snx413 said:
When you boot, you have access normally
Click to expand...
Click to collapse
And how do I remove them? instructions please
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
You can remove them in TWRP
jkmaxfli said:
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Click to expand...
Click to collapse
Dirty flash the whole ROM then
Adb shell
then
magisk --remove-modules
Dark-Yox said:
You can remove them in TWRP
Dirty flash the whole ROM then
Click to expand...
Click to collapse
How it dirty flash ?
I used it over TWRP recovery ROM zip file, and not work flashing
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com
HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.
jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse
Only data partition is shared. All else have both A and B parts