Here you will get the correct steps, files and info to get rooted on Android 11 / DP3 build.
Boot file:
DP3_patched
Canary Manager:
Magisk Manager Canary
1. Download the files above
2. Put the Boot file into downloads directory
3. Install the Canary Manager
4. In the Manager do the following: select "Install" / "Select and patch a file" / Pick the Boot file in Downloads
5. When done take the newly created magisk_patched.img file from Downloads and copy to the ADB/Fastboot directory on your PC
6. Go to fastboot on your device
7. Use the command fastboot boot magisk_patched.img from your PC from ADB
8. Once the device reboots go back to fastboot mode
9. This time use the command fastboot flash boot_a magisk_patched.img
10. Then use this straight after fastboot flash boot_b magisk_patched.img
11. Reboot device and enjoy being rooted
This method should work first time in getting you rooted. Many other ways were tested and worked randomly for some and not others but with this I got it first time on two test attempts.
Hope it works for you all.
Thanks to @mwilky, @osm0sis and @Mike02z for figuring it out properly :good:
All credit to @osm0sis for the initial heads up!
Gpay is working with the root and magisk? Without doesnt works. Thanks
Great news!
Sent from my IN2025 using Tapatalk
vuoshino said:
Gpay is working with the root and magisk? Without doesnt works. Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/android-11-beta-t4113817/post83290875
after step 7, my phone restarts and I get Qualcom CrashDump Mode Attemped to kill init
what now?
i restarted phone with keys..
can i proceed with step 8?
I got root working, but my alert slider doesn't work and fails safety net.
Sent from my IN2025 using Tapatalk
enerGy said:
Here you will get the correct steps, files and info to get rooted on Android 11 / DP3 build.
Boot file:
Boot img
Canary Manager:
Canary Magisk Manager
1. Download the files above
2. Put the Boot file into downloads directory
3. Install the Canary Manager
4. In the Manager do the following: select "Install" / "Select and patch a file" / Pick the Boot file in Downloads
5. When done take the magisk_patched.img file created from Downloads and copy to the ADB/Fastboot directory on your PC
6. Go to fastboot on your device
7. Use the command fastboot boot magisk_patched.img from your PC from ADB
8. Once the device reboots go back to fastboot mode
9. This time use the command fastboot flash boot_a magisk_patched.img
10. Then use this straight after fastboot flash boot_b magisk_patched.img
11. Reboot device and enjoy being rooted
This method should work first time in getting you rooted. Many other ways were tested and worked randomly for some and not others but with this I got it first time on two test attempts.
Hope it works for you all.
Thanks to @mwilky, @osm0sis and @Mike02z for figuring it out properly :good:
Click to expand...
Click to collapse
im onrooted, for do this guide i have to open the bootloader or do something else at the beginning? because when i try to launch the command fastboot boot magisk..... the cmd give me this error: download is not allowed on locked devices... thanks
---------- Post added at 03:43 PM ---------- Previous post was at 03:10 PM ----------
vuoshino said:
im onrooted, for do this guide i have to open the bootloader or do something else at the beginning? because when i try to launch the command fastboot boot magisk..... the cmd give me this error: download is not allowed on locked devices... thanks
Click to expand...
Click to collapse
ok yes was for the locked bootloader. now works properly. thanks
Hi, could anyone send me a dmesg log with the patched boot? You can grab it through either adb root or terminal emulator. I need it as a reference to debug for another device. Thanks!
I cant make safety net to works properly...
Someone can help me?
---------- Post added at 05:03 PM ---------- Previous post was at 04:50 PM ----------
Basicintegrity not pass
Cts profile not pass
Evaltype basic...
This is the error
Now is working. Thanks
I had problems with hiding Magisk (repacking and change name of the Magisk Manager)
In my case it was Google Play Protect that refused me this, so temporarily disabling this worked for me! In case anyone else should stumble upon this issue!
Great guide!
is this method works with magisk manager not canary?
Does not work with the Oneplus pro in2025 keep getting carshdump Mode. Fastboot flashed the new.img so rom can boot. Now when I check magisk it shows I am rooted. So I guess it does work
Not work with magisk. But works fine with canary.
Now I am not eable to use 5g configuration can not be setted.
I am not eable to use the methods and apks
Like OnePlus logkit and engineermode.
These are not working with oos 11.
Is there any ways to enable the 5G connectivity.
Thanks
Spirit81 said:
after step 7, my phone restarts and I get Qualcom CrashDump Mode Attemped to kill init
what now?
i restarted phone with keys..
can i proceed with step 8?
Click to expand...
Click to collapse
I had the same issue of boot to crashdump mode every time I tried to boot the magisk_patched.img that I created using Magisk Manager as well. So, I ended up trying to boot the new.img (the one downloaded from OP) and it booted and was already rooted in Magisk Manager. So from there, booted back to fastboot and flashed the new.img to both boot_a and boot_b and now have root on DP3. Hope that helps.
jeffsga88 said:
I had the same issue of boot to crashdump mode every time I tried to boot the magisk_patched.img that I created using Magisk Manager as well. So, I ended up trying to boot the new.img (the one downloaded from OP) and it booted and was already rooted in Magisk Manager. So from there, booted back to fastboot and flashed the new.img to both boot_a and boot_b and now have root on DP3. Hope that helps.
Click to expand...
Click to collapse
Same for me,with the new img it works
Gesendet von meinem IN2023 mit Tapatalk
vuoshino said:
This is the error
Click to expand...
Click to collapse
How have you solved it?
Upgrade magisk, in the settings turn on the hide option and install magisk with another name. Go into the magisk hide and check google services. Anyway next to turn on magiskhide option google pay will works.
---------- Post added at 06:05 PM ---------- Previous post was at 05:47 PM ----------
Someone use skygo? Is strange, my magisk app is hide and google pay works but sky go is able to see the root. Is alreafy checked in the magiskhide options but i think there is an error with the hide options because magisk doesnt create a new icon. I have the same icon of the original magisk and the option in the settings is the same one: hide magisk manager app...
Related
Update: I used Linux machine instead of Windows and the latest kernel works now.
Kernel modifications:
default.prop modified
ro.secure=0
ro.debuggable=1
Requirement:
1. Your L1
2. Installed drivers (Sony so0112 for both ADB and fastboot)
3. Your phone has to be bootloader unlocked
Warning: your phone will be wiped including DRM and there's no backup solution for Android 7
4. Magisk downloaded and installed
https://forum.xda-developers.com/apps/magisk
5. This modified kernel (sorry, I don't know how to make TWRP so no recovery at this time)
https://androidfilehost.com/?fid=673791459329056251 (patched with Magisk)
https://androidfilehost.com/?fid=889964283620760970 (modified but not patched with Magisk)
Kernel is for G3313, but it should work with other variations.
6. Working ADB
Instructions:
1. enable your phone debug options. Go to About Devices >>> Build Number and hit 7 times until you see Developers Options. Go there to enable USB Debugging and Allow OEM Unlock.
2. plug in your phone and make sure ADB is working
Code:
adb devices
If you don't see it, go to Device Manager and see whether Sony so0112 ADB driver installed. If it's working, go to 3
3. copy the modified kernel to your phone (make sure your phone USB is in file transfer mode) internal memory Downloads folder
4. install and open Magisk and install and patch boot file and locate the downloaded file.
5. locate patched kernel from internal memory /Magiskmanager/ and copy patched_boot.img and copy to your host computer.
6. go to command prompt and copy your ADB folder address and open your file explorer and copy the patched kernel there (e.g. Downloads)
7. use this command to go to fastboot mode
Code:
adb reboot fastboot
If you never unlock the bootloader, you have to write down your phone IMEI and go to https://developer.sonymobile.com/unlockbootloader/ and follow the instruction.
8. if your bootloader unlocked, enter the following command
Code:
fastboot flash boot
and drag the patched kernel and press enter.
9. enter
Code:
fastboot reboot
10. once you're back to the system, enter Magisk Manager again to check boot status. You may be prompted to install a module for Safety Net.
11. your phone is rooted. Done
Credits:
@osm0sis for Android Image Kitchen
@topjohnwu for Magisk
@rrvuhpg, @bigrammy, and @janjan gave me inspiration. It cannot be done without them
Bro i g3311 single sim do a funcionality this tutorial?
Recovery twrp is no
Boot.img is yes
Bro good hardwork
so root is using magisk?
---------- Post added at 07:05 PM ---------- Previous post was at 06:57 PM ----------
Magisk is a zip how install anyidea?
You have to run Magisk Manager to patch the modified kernel, and flash the patched kernel using fasrboot command
I cant signal gsm for g3311
No signal mobile
This boot is bad for my g3311 ???
I will make three different variations for 3311 and 3312 and try again.
No reception at all?
HELPPPPPPPPPPPP
I do not understand the patch for magisk
i am install magsik in 5.0.4
i dont instaled magisk v. 14
please help me how to all install install Thank you
HEKER510 said:
HELPPPPPPPPPPPP
I do not understand the patch for magisk
i am install magsik in 5.0.4
i dont instaled magisk v. 14
please help me how to all install install Thank you
Click to expand...
Click to collapse
It's pretty straightforward.
After the installation, copy the downloaded boot image to your phone and let Magisk get the zip and patch your image file.
Once the image patched, copy the patched image back to host computer and flash in fastboot.
mingkee said:
It's pretty straightforward.
After the installation, copy the downloaded boot image to your phone and let Magisk get the zip and patch your image file.
Once the image patched, copy the patched image back to host computer and flash in fastboot.
Click to expand...
Click to collapse
I am Flash uk verzion
Flashing img for magisk
Flash img for fastboot
My phone no signal gsm
Who IS problem bro
Recovery twrp IS no? Bro
Thankx you reply
---------- Post added at 03:58 PM ---------- Previous post was at 03:20 PM ----------
{
"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"
}
HEKER510 said:
I am Flash uk verzion
Flashing img for magisk
Flash img for fastboot
My phone no signal gsm
Who IS problem bro
Recovery twrp IS no? Bro
Thankx you reply
Click to expand...
Click to collapse
I have checked and I found it cannot read SIM.
You can flash back to 100% stock using flashtool. There's a problem with kernel and probably something is missing.
mingkee said:
I have checked and I found it cannot read SIM.
You can flash back to 100% stock using flashtool. There's a problem with kernel and probably something is missing.
Click to expand...
Click to collapse
ok bro i flashing back for origo fw 79 uk yes ?
i waiting for your new boot.img bro
i am a read this this is so found problem are problem is solved clik this tutorial and read this
Is tutorial for xa xa ultra root no problem please read brother
https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3638727
read
6. Power off the phone and flash ONLY "BOOT_DELIVERY" from a Marshmallow firmware with Flashtool ( exclude all other patitions), you must only see
"boot_delivery.xml" in the "Content" column.
AND
18. Power off the phone again and repeat step 6 with your actual Nougat firmware or the phone will not detect Sim Card(s)
HEKER510 said:
ok bro i flashing back for origo fw 79 uk yes ?
i waiting for your new boot.img bro
i am a read this this is so found problem are problem is solved clik this tutorial and read this
Is tutorial for xa xa ultra root no problem please read brother
https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3638727
read
6. Power off the phone and flash ONLY "BOOT_DELIVERY" from a Marshmallow firmware with Flashtool ( exclude all other patitions), you must only see
"boot_delivery.xml" in the "Content" column.
AND
18. Power off the phone again and repeat step 6 with your actual Nougat firmware or the phone will not detect Sim Card(s)
Click to expand...
Click to collapse
I will upload new boot image. This time I did it in Linux (Ubuntu) platform instead of Windows. It tested on mine and SIM is working now.
Try this one https://androidfilehost.com/?fid=673791459329056251
It's already patched with Magisk, but you may need to install the zip anyway
mingkee said:
I will upload new boot image. This time I did it in Linux (Ubuntu) platform instead of Windows. It tested on mine and SIM is working now.
Try this one https://androidfilehost.com/?fid=673791459329056251
It's already patched with Magisk, but you may need to install the zip anyway
Click to expand...
Click to collapse
Ok bro very thankx i is download and flash thanx
i come back
---------- Post added at 07:37 AM ---------- Previous post was at 07:01 AM ----------
@mingkee
Bro very very thankx its all ok root magisk and signal gsm its ok brother very very thankx for you hardwork
as a thanks you
I sent the theme for L1 with the navbar logo
very very thankx )))))))))))))))))))))))))))))))
Theme Xperia™L1 Black
Download: https://mega.nz/#!bkgy0STK!6a3n9tfWxF1N4kJi1E-_Wx9fhY32svFKs5gAH2eqRqo
Don't try with G3311!!
I tried this with my G3311 and it put it into a boot loop (couldn't even turn device off or enter flash/fastboot mode) I had to take out the battery and replug it just to get into flash mode so I could restore to official Software
This will most likely work for everyone else that had a bootloop after trying this :good:
MasterMasher said:
I tried this with my G3311 and it put it into a boot loop (couldn't even turn device off or enter flash/fastboot mode) I had to take out the battery and replug it just to get into flash mode so I could restore to official Software
This will most likely work for everyone else that had a bootloop after trying this :good:
Click to expand...
Click to collapse
Which kernel did you use?
You should try with the one before patched with Magisk, and let Magisk patch it for you, and flash that one patched by yours.
There may be something going wrong during the process while I read he has no problem (with reception) and you got bootloop.
mingkee said:
Which kernel did you use?
You should try with the one before patched with Magisk, and let Magisk patch it for you, and flash that one patched by yours.
There may be something going wrong during the process while I read he has no problem (with reception) and you got bootloop.
Click to expand...
Click to collapse
I realised where I went wrong it's was all my mistake so my last post was incorrect I used Sony Mobile Flasher to unlock bootloader instead of enabling it in developer settings and then flashed my device with your latest update you commented earlier and it's finally worked :victory:
Great work on the boot.img trying to get it working on my L1 now. I'm missing something tho.
Unlocked bootloader
ADB
Fastboot
Downloaded files
I have to hold volume up while inserting USB to enter fastboot (confirmed by Blue led)
When I executed fastboot code and drag images file over I get an error about unknown directory or it'll just rerun the fastboot help screen
---------- Post added at 11:32 PM ---------- Previous post was at 11:09 PM ----------
.... Wait for it..... Yeah I see I screwed up. Give it another go later after work
flyyyguy said:
Great work on the boot.img trying to get it working on my L1 now. I'm missing something tho.
Unlocked bootloader
ADB
Fastboot
Downloaded files
I have to hold volume up while inserting USB to enter fastboot (confirmed by Blue led)
When I executed fastboot code and drag images file over I get an error about unknown directory or it'll just rerun the fastboot help screen
---------- Post added at 11:32 PM ---------- Previous post was at 11:09 PM ----------
.... Wait for it..... Yeah I see I screwed up. Give it another go later after work
Click to expand...
Click to collapse
Try what I did and download Sony Mobile Flasher and press the 'BLU' (Bootloader unlock) button just to make sure your boot loader really is unlocked or maybe you just enabled OEM unlock in Dev settings but didn't use the tool mentioned above to correctly unlock the bootloader. If that's not the case then did you flash the latest boot image that has been posted in the comments by OP
I did bootloader unlock using fastboot method
It isn't just "fastboot oem unlock". Instead, you have to enter fastboot command as directed with given unlocked code.
flyyyguy said:
Great work on the boot.img trying to get it working on my L1 now. I'm missing something tho.
Unlocked bootloader
ADB
Fastboot
Downloaded files
I have to hold volume up while inserting USB to enter fastboot (confirmed by Blue led)
When I executed fastboot code and drag images file over I get an error about unknown directory or it'll just rerun the fastboot help screen
---------- Post added at 11:32 PM ---------- Previous post was at 11:09 PM ----------
.... Wait for it..... Yeah I see I screwed up. Give it another go later after work
Click to expand...
Click to collapse
mingkee said:
I did bootloader unlock using fastboot method
It isn't just "fastboot oem unlock". Instead, you have to enter fastboot command as directed with given unlocked code.
Click to expand...
Click to collapse
Mingkee is right but I just used Sony Mobile Flasher to unlock bootloader instead works just as well with the click of a button
Actually, I won't end from here.
Since I have set up a dedicated Linux machine, I will try to go further to make recovery.
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
deleted
Closed Due To Deletion By OP
I'm on MIUI, can I Install just clicking that .bat file?
Gemmik said:
I'm on MIUI, can I Install just clicking that .bat file?
Click to expand...
Click to collapse
Yes you can install it but you should go to recovery and do wipe data after installing it.
@TechGenius can I flash this on a European device?
if i flash it can receive official OTA in the future؟؟
sadeg111 said:
if i flash it can receive official OTA in the future؟؟
Click to expand...
Click to collapse
Yes
Tyrany said:
@TechGenius can I flash this on a European device?
Click to expand...
Click to collapse
Yes, without any problems
I cannot flash it... The .bat file doesn't do nothing.
I tried opening it from commands, and it says "current device anti rollback version is greater than this package"
EDIT. Ok, copied the scripts and images folder in "Minimal ADB and Fastboot" folder, and executed flash_all.bat from commands, and now its flashing. Thanks dude.
thanks dude ???
It has to be much time in Mi logo?
It has passed 5min now....
EDIT AGAIN. Rebooted to stock recovery (used THIS guide, and performed a factory reset. Then reboot and voilá!
Thanks again, dude.
For me happens system flashing paused... I have to install Android 9 again.... Any clue that probably happens?
Enviado do meu Mi A3 através do Tapatalk
Can I install it via TWRP?
I'm on miui.
Thanks
please can you provide fastboot rom till they released it officially
Getting stuck at " Sending sparse 'system_a' 1/4 (772551 KB) " What can I do?
EDIT: just waited a lot longer and its ok now, thanks!
is this a official final build? looks more like some "beta" build... a lot qualcomm references... (build number, hw survey... - which is not present on mi a2 devices)
I have rooted this version, magisk says that everything is fine, the problem is when I give permission to an application and restart the phone, when it starts it does not pass the MI logo. I have re-flashed the boot.img that comes with the rom and it has been fixed, but if I re-flash the magisk_patched.img it is again in the MI logo. What could be the solution? Thanks for the help.
adal_elfather said:
I have rooted this version, magisk says that everything is fine, the problem is when I give permission to an application and restart the phone, when it starts it does not pass the MI logo. I have re-flashed the boot.img that comes with the rom and it has been fixed, but if I re-flash the magisk_patched.img it is again in the MI logo. What could be the solution? Thanks for the help.
Click to expand...
Click to collapse
Which application? Which permission? Which Magisk modules do you have installed?
As a start I would try to remove all modules (you must have Magisk patched boot image installed), connect phone to the PC, run this command and restart the phone.
Code:
adb wait-for-device shell magisk --remove-modules
_mysiak_ said:
Which application? Which permission? Which Magisk modules do you have installed?
As a start I would try to remove all modules (you must have Magisk patched boot image installed), connect phone to the PC, run this command and restart the phone.
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
thanks for answering. I am using Lucky Patcher to move some apps to system apps. I have tried the command you shared with me but it restarts and does not go beyond the MI logo.
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
_mysiak_ said:
Which application? Which permission? Which Magisk modules do you have installed?
As a start I would try to remove all modules (you must have Magisk patched boot image installed), connect phone to the PC, run this command and restart the phone.
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
I'm using:
magisk_patched.img patched whit Magisk Manager 20.3 and flashed from fastboot comand:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
initially the phone starts normal and in Magisk Manager says it is installed. But by giving super user permissions to Lucky Patcher and restarting the phone it no longer goes past the MI logo. When I flash the boot.img that brings the rom it starts again but obviously without root.
adal_elfather said:
thanks for answering. I am using Lucky Patcher to move some apps to system apps. I have tried the command you shared with me but it restarts and does not go beyond the MI logo.
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
I'm using:
magisk_patched.img patched whit Magisk Manager 20.3 and flashed from fastboot comand:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
initially the phone starts normal and in Magisk Manager says it is installed. But by giving super user permissions to Lucky Patcher and restarting the phone it no longer goes past the MI logo. When I flash the boot.img that brings the rom it starts again but obviously without root.
Click to expand...
Click to collapse
Boot the phone without root and uninstall lucky patcher (this will also reset root access in Magisk). Then you can flash patched boot back.
Use Magisk module to install apps as system.
_mysiak_ said:
Boot the phone without root and uninstall lucky patcher (this will also reset root access in Magisk). Then you can flash patched boot back.
Use Magisk module to install apps as system.
Click to expand...
Click to collapse
I have already tried but it does not go beyond the MI logo. Only when doing a Factory Reset. Another thing, when I want to enter the recovery mode with the flashed TWRP img it never enters the Recovery, it goes directly to the Fastboot. I cannot install TWRP or root it.
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version
Tapatalk via OnePlus 7T
Thank You
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
If u r already on 10.0.12 EU u dont need the rom
If u r on previous OOS then use the oxygen updater app from Play store to update
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
One guy already upload this file here :
https://drive.google.com/file/d/1-_3fL5HkWS9cplro7iNiIzqlL_AGTz2B/view?usp=drivesdk
Tapatalk via OnePlus 7T
Hm, I have HD65AA India and after boot (not flash) via fastboot attached here patched boot.img I don't have internet (gsm and wifi).
Do you have India's version of that patch ?
KyoshiDev said:
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
Click to expand...
Click to collapse
4. and 5. Step isn't needed.
When you boot your image and check if you have root you just klick: Install --> Install --> direct install. It will automatically patch your actual boot.img and you will permanently have a rooted phone.
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Did not work for me on reboot after root check says not rooted?
---------- Post added at 06:54 PM ---------- Previous post was at 06:44 PM ----------
Nope did not work for me say I do not have root on root check?
=dgim= said:
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Click to expand...
Click to collapse
I have updated to 10.3.4.HD65AA yesterday. Have been rooted since much earlier version with Magisk Canary. Now I want to change to stable but not sure of the process.
How do I uninstall Canary version? There does not seem to be any uninstall option in Magisk Manager Canary version. Can I just uninstall as I would any other app?
Is the file you uploaded correct for my version? Would it install Magisk Stable version?
After going into fastboot do I have to connect to PC and give commands there or in the phone itself. Have done it earlier but I forgot. If from PC, which software to use for ADB?
Edit : Will this wipe data?
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
=dgim= said:
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
jesrani said:
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
Click to expand...
Click to collapse
Booting and flashing TWRP on recovery partition, I suppose, is working.
I didn't flash Magisk install or unistall via TWRP on OP7T.
Are you sure that, after flashing new rom, your device is rooted ?
Even you have installed Magisk Canary, but - SatetyNet etc, is passed in your device after flashed stock 10.3.4 ?
If not, you can just unistall apk (Magisk Manager), clear cache, flash patched boot.img and install stable Magisk (I didn't test stable on 10.3.4).
I'm lost somehow.
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory.
I reboot the bootloader. Fine. I fastboot the patched image. Fine. Check for root. Fine
I reboot the bootloader. Fine. Comes up with a menu. The top of the menu says Start.
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
KyoshiDev said:
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
Click to expand...
Click to collapse
davekaye said:
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory. .
Click to expand...
Click to collapse
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
davekaye said:
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
Click to expand...
Click to collapse
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
davekaye said:
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
Click to expand...
Click to collapse
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
KyoshiDev said:
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
Click to expand...
Click to collapse
Thanks. My fault. Since I don't have a working TWRP I haven't been playing around with any ROMs and I guess I'm rusty. So I tried to put your upgrades on the wrong version of Oxygen (11 not 12) and ran into a bootloop. I could not boot into EDL mode (another issue I have to follow up) and it took me some time to finally boot back to 11 and then do the OTA upgrade to 12. All is working now, so thanks again.
Hello, is SafetyNet supposed to fail or I've messed something up?
1nikolas said:
Hello, is SafetyNet supposed to fail or I've messed something up?
Click to expand...
Click to collapse
Safetynet should pass
So i put this on my US version. HD1905. I should have been more careful. Anyway, everything works well except netflix., which is now a system app and will not run or uninstall.
PS: Do you have US version patched boot file ?
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.