Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect.
1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA
2-ENABLE USB DEBUGGING IN DEVELOPER OPTIONS
3-INSTALL 15 seconds ADB Installer v1.4.3 AND OnePlus_USB_Drivers_Setup.exe
4-CONNECT YOUR ONEPLUS 7T TO PC AND ALLOW USB DEBUGGING REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UNLOCK BOOTLOADER (THIS PROCESS WILL ERASE ALL YOUR DATA)GO TO C:\adb AND OPEN A Windows PowerShell (SHIFT+Right-Click)
Code:
adb devices
adb reboot bootloader
Code:
fastboot oem unlock
INSTALL MAGISK AND PATH boot.img1-INSTALL Magisk-66e30a77(22006).apk
2-DOWNLOAD AND UNZIP boot.img
boot.img (GLOBAL) FROM OnePlus7TOxygen_14.O.25_OTA_0250_all_2103170010_42034d7f PAYLOAD.BIN
boot.img (EUROPE) FROM OnePlus7TOxygen_14.E.25_OTA_0250_all_2103162336_da326df80dc PAYLOAD.BIN
boot.img (INDIA) FROM OnePlus7TOxygen_14.I.25_OTA_0250_all_2103170010_f57745e564 PAYLOAD.BIN
3-PASTE boot.img IN THE ONEPLUS 7T ROOT DIRECTORY
4-Open Magisk
5-In "Magisk" select "Install"
"SELECT AND PATCH A FILE"
NOW SELECT boot.img FILE FROM OP7T ROOT DIRECTORY and "LET´S GO"
PATCHED boot.img = magisk_patched.zip (GLOBAL VARIANT, I DON'T KNOW IF IT WORKS WITH THE OTHER VARIANTS)
FLASH PATH BOOT.IMG1-COPY PATCHED BOOT.IMG ("magisk_patched.img") FROM DOWNLOAD DIRECTORY and paste it on C:\adb
2-ENABLE USB DEBUGGING IN DEVELOPER OPTIONS AGAIN
3-CONNECT YOUR ONEPLUS 7T TO PC AND ALLOW USB DEBUGGING REQUEST
GO TO C:\adb AND OPEN A Windows PowerShell (SHIFT+Right-Click)
Code:
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
NOW JUST GO INTO MAGISK AND INSTALL THE APP
That's all!
You don't need to flash, you just need to boot, then install it from magical again, then reboot
HydraMaZ said:
You don't need to flash, you just need to boot, then install it from magical again, then reboot
Click to expand...
Click to collapse
In my case, when I tried just boot, my phone froze in "Fastboot Mode" screen.
Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!
Success in installing Magisk and patched img for EU also successful. But always fail on Safetynet. Any suggestions?
Nevermind. Figured it out. Someone already helped. Forgot about the Magisk hide feature inside settings.
miguelang611 said:
Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!
Click to expand...
Click to collapse
miguelang611 said:
Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!
Click to expand...
Click to collapse
Actually, I have been flashing Global on my 7T HD1903 since I purchased it. But recently, I have been having problems with the Global rom Android 11. Camera freezing on other modes aside from Photo. So I downgraded to 10.0.16. The took the plunge of flashing the EU rom Android 11. And hey, nicely flashed with no known errors or issues.
Then try this rooting process. And it all worked fine. MaYBE e you should try EU rom too.
zer0se7en said:
Actually, I have been flashing Global on my 7T HD1903 since I purchased it. But recently, I have been having problems with the Global rom Android 11. Camera freezing on other modes aside from Photo. So I downgraded to 10.0.16. The took the plunge of flashing the EU rom Android 11. And hey, nicely flashed with no known errors or issues.
Then tried this rooting process. And it all worked fine.Maybe you should try WU rom too.
Click to expand...
Click to collapse
My issue was caused by a Magisk module, which strangely enough made android phone to fail, the process I was doing was right, except I didn't uninstall all modules before A11 update
I'm relatively new to payload dumpers and patching boot.img's so decided to sideload the Magisk.apk (22000) via fastbooted twrp instead, it worked a charm and all rooted.
Only issue was I forgot to install the magisk app before hand so had to install it to get it on the app drawer, other than that, no issues.
miguelang611 said:
My issue was caused by a Magisk module, which strangely enough made android phone to fail, the process I was doing was right, except I didn't uninstall all modules before A11 update
Click to expand...
Click to collapse
I do recall having this problem, it was already a bother ten months ago. I never found the actual problem, I just used several files until I got the right one working fine. Up until now I was using a rooted Oxygen OS 10.0.5 with magisk and it seemed to do the trick for me, but I got an automatic update a week ago and I got to root back my phone, might aswell update it.
But I fear that if I update to the 11 OS and try to root it, the exact problem will appear, I will wait for any fix in the future.
Update :
I did it following a few tutorial from everywhere.
There's a lot of ways to do it but ultimately, you should have magisk on canary then patch your own boot.img (either see how to extract the payload file or get the correct boot.img version )
Then follow this :
[SOLVED] Magisk patched boot.img for Android 11?
Hi there, I managed to patch the boot.img with Magisk 20.4 (20400). Then I replaced the patched boot.img and updated to Android 11 with "flash_all.bat" method. However, the phone did not boot until I flashed stock original boot.img from Android...
forum.xda-developers.com
So this process seems to have gotten me farther than anything else has so far. Been trying to root my 7T. Unfortunately, it also seems to have bricked my phone. Any advice?
Hi, I'm Android 10 root. I guess I shouldn't update OTA if I want to keep root right? The usual process would fail?
When I boot from the patched boot.img and even when I'm booting from stock boot.img the phone starts woth boot animation and finally the screen just turns black. Sometimes when I press Power + Volume up/down in no specific order, I get a kind of "menu" where I can restart or lock the screen but it's almost unresponsive and it seems to not react to touch inputs. Did anyone had similar problems? Up to Oxygen 10.x I had never any problems with fastboot boot boot.img
Unfortunately with Oxygen 11 it seems more complicated now.
I've tried everything and cant get Android 11 rooted successfully. Patched boot img myself, used other boot imgs from the forums, newest Magisk, older Magisk, Canary builds, everything I can think of... None of the patched boot imgs will boot...just stuck on boot screen (boot loop). I'm using a converted Tmobile model on Global firmware.
Odd that some people seem to have no trouble just rooting like normal but some of us cant get 11 to root.
Any ideas or tips that I could try?
Hey Guys I just rooted my phone and my wifi isn't turning on and my phone is taking 10-15 mins to reboot any fix for this? (Indian Variant One Plus 7t)
Has anyone managed to root a European 7T running stock Android 11?
BritSwedeGuy said:
Has anyone managed to root a European 7T running stock Android 11?
Click to expand...
Click to collapse
Yes. it was few weeks ago now but I think I used the 'Chinese' TWRP. However, I think that there are a few other options. What have you tried?.
mikefnz said:
Yes. it was few weeks ago now but I think I used the 'Chinese' TWRP. However, I think that there are a few other options. What have you tried?.
Click to expand...
Click to collapse
I've cracked it by extracting and patching the boot.img myself.
The files are here...
File folder on MEGA
mega.nz
I just use magisk canary and flash via Chinese twrp and rooted oos10, oos11, any custom ROMs easily
HueyT said:
I just use magisk canary and flash via Chinese twrp and rooted oos10, oos11, any custom ROMs easily
Click to expand...
Click to collapse
I am on rooted Android 10. How do i flash Chinese TWRP?
jesrani said:
I am on rooted Android 10. How do i flash Chinese TWRP?
Click to expand...
Click to collapse
Put such file in your adb folder in PC, rename img file to twrp.img, and type "fastboot flash recovery twrp.img" while phone is in bootloader mode
Related
So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!
CarteNoir said:
So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.
Homeboy76 said:
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.
Click to expand...
Click to collapse
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarteNoir said:
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
Click to expand...
Click to collapse
have you done a 2nd reboot? sometimes that's the charm...
Captain Hindsight said:
have you done a 2nd reboot? sometimes that's the charm...
Click to expand...
Click to collapse
I've done multiple reboots sadly. Still nothing.
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?
tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
CarteNoir said:
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?
Click to expand...
Click to collapse
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
pcriz said:
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse
pcriz said:
TWRP does not flash over magisk, never has and isn't now.
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?
CarteNoir said:
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?
Click to expand...
Click to collapse
So I think you would want to fastboot the stock boot.IMG. flash the kernel, then turn around and flash twrp, reboot, install magisk.
If Elemental is doing something more to make this work I don't know what it is, but essentially every custom kernel or kernel that comes packaged with a custom rom does the same thing.
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/
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 ALL MAGISK MODULES BEFORE EXECUTING OTA UPGRADE
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and 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 and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and 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 and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
flash original (stock) boot.Img above to unroot
HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
Thanks. Would that work for Indian version also? And would that wipe data?
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:
Thanks. Would that work for Indian version also? And would that wipe data?
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
All variants share same boot, data fine
HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and 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 and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
In such situation always remember, flashing original boot.img may not work best is change the partition. so if you are in a go to b and boot. Use temp TWRP custom recovery to change partition if you cannot change via command line. and once you are able to boot, flash magisk properly on both partition.
This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: I have Magisk ver. 25.2
RRRb50 said:
This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
View attachment 5716169
Edit: I have Magisk ver. 25.2
Click to expand...
Click to collapse
did you install magisk25 apk?
thexile said:
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img
المخزون: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g
Magisk v23.0 مصححة: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc
ملاحظة: قم بتعطيل كافة وحدات MAGISK قبل تنفيذ ترقية OTA
Click to expand...
Click to collapse
I am on OOs 11.0.9.1. my device went into bootloop after i updated some magisk modules.
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 installed twrp on partition a and now I am having root. I was not able to install Magisk25.2.apk but was able to install some other version, I think Canary release. So most things seem to work. However when I click Add Systemless Host, nothing seems to be happening. AdAway is not working. How can I get this to work again.
HDFC banking app is also detecting root even though I have installed HideMyApplist and configured DevOptsHide and HideMyApplist in LsPosed. Not sure what is the mistake. Can anyone advice?
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