Database Develop

Magisk manager v13 not working

I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it

Jô$èph D said:
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Click to expand...
Click to collapse
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.

freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
Ok then ill give it a shot

freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
I need to get stock boot img I don't have it pls help

Jô$èph D said:
I need to get stock boot img I don't have it pls help
Click to expand...
Click to collapse
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.

freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Can you pls link me the post for that file

freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks

Jô$èph D said:
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks and I will stay active on this and other threads
Click to expand...
Click to collapse
Sure thing. See you around!

Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?

yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
I wanted to use systemless xposed framework because the official version is not supported on my device. Also I wanted to use the modules that are specifically for magisk

yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
Systemless xposed does not work either found this out earlier today device would not boot after installation of xposed through magisk

Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.

yaconsult said:
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
Click to expand...
Click to collapse
I will have to see if it works when a new version of magisk is launched.

Help with Treble ROMs

I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks

Try to install the stock recovery and ramdisk.

+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.

After I flashed a treble gsi, I need to flash stock recovery?

Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.

ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry

Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.

ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.

XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP

ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.

XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3

Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!

Lineage OS 17 unable to root with Magisk

Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks

vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP

ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time

vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot

ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root

vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!

jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.

vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...

I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).

I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?

Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.

Made an OB1 Magisk Patched boot.img

7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Don't install TWRP yet. The people who are infinitely smarter than I am will make a TWRP that will work for OB1, and that's way above my pay grade. I hope this helps someone.
[Tutorial] How to flash a new boot.img via Fastboot
Hey Guys, since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode) If you have fastboot already installed on your...
forum.xda-developers.com
Here's how to use it.

getting 'unable to parse kernel log' error

peachypickle said:
getting 'unable to parse kernel log' error
Click to expand...
Click to collapse
it worked fine for me.

How install oxygen os open beta 1 android 11 with keep rooted? Any video tutorial?

it's not too bad...
Install the OTA
Go to magisk manager and pick install.
pick install to inactive slot (after OTA)
make sure you don't have any modules enabled that may be incompatible.
reboot
when the 11 TWRP drops, you can install it as a magisk module to gain custom recovery back

Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.

spheady said:
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
Click to expand...
Click to collapse
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.

spheady said:
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
Click to expand...
Click to collapse
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?

LokifiedMee said:
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
Click to expand...
Click to collapse
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun

Crazyinsanejames said:
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Click to expand...
Click to collapse
Ohh couldn't find Orangefox dual boot's post today so here is the twrp file. It's not really worked on right now and has option to flash magisk on R11 Pass but the copy of magisk is no good on the R11 OS but has magisk. 20.4 option for a Q10 is, when it IDs it. You'll see. The script options. PS orangfox dual booting with three different drives rocks. Also it has a app manager and a magisk mange GUI. Almost forgot beta 10 version 17-19 will not successful y flash this twrp. But any other copy for the phone on xda or OnePlus.com work fine. It's a encryption variety problem. If your password becomes corrupt (only on OS can have password type security on a dual boot setup... I got away with using the same password on both OSs for a minute though. ) in the root partition thiers a directory called Ffiles, with .zip you can flash while TWRped to fix a few things like that. Other than that let me know. Lol I want to mention Evey time you flash an OTA or anything that will alter the work this twrp installs, you need to flash the file afterwards, before rebooting. And reboot after flashing it so everything links up. Of coarse you can select to reboot right back to recovery. Best luck I couldn't find their post on xda so that's why I typed up so much. Lol I'll be funny again I don't know who this stuff on how to downgrade really but thiers a Windows tool that has capibillities err what ever to flash a OTA of 10 in fastboot mode. Anyways no worries. It's called all-in-one flash tool. Works on maney OnePlus phones. Maybe for encrypted data partitions. I run unencrypted stuff I do not like encryption on any electric devices.

aNGERY said:
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Click to expand...
Click to collapse
I just want to say thank you. I tried the new magisk update and it didn't work. I could get to recovery and figured I had PB1 for Andoid11 anffd I would flash to gety baclk to working. Of course I lost root, but was able to get it back with magisk_patched_Ei056.img flashed to boot. It works fine. Can hang with root until TWRP gets updated.
VERY APPRECIATED.

Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!

Crazyinsanejames said:
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Click to expand...
Click to collapse
Well found out thevendor.img didnt work lol. Anyways heres cheap trick i found if your not on an OS with twrp
http://Link removed

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
I'm pretty sure it's insinuated that it's pertaining to OOS11. Don't be willfully obtuse.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
35090 for Android 11 on the OnePlus 7 pro will not work without decrypting it.

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
actually I take that back.
Download TWRP for guacamole
Download TWRP Open Recovery for guacamole
dl.twrp.me
Here you go, 3.5.0_9-0 is the one release on 12/28. Install it and let us know how you like it!

spheady said:
Lol nice it worked. Lol it also
Ty tried for fun. Think thos thread is for ppl trying to boot a .img file of twrp. Can this flash via fastboot. So twrp to twrp I think ill keep my dual boot Twrp its not so basic.ty
Click to expand...
Click to collapse
You can reboot to recovery from the OS with this twrp installed?

Question Bootloop with patched boot.img

Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco

Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.

Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed

Do you unlock bootloader?

zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?

Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...

leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop

you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?

nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.

I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.

MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).

Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.

louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk

Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.