We can root in an easy way without unlocking the bootloader
I think this method works with all versions realme
Don't forget to activate OEM unlocking From Developer options
1-You must install drivers:
Realme USB Driver - Realme Firmware
From here you can download USB driver for realme mobile phones. The given USB driver is supported only for the Windows operating system
realmefirmware.com
Realme USB Driver - Google Drive
drive.google.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download SPD Flash Tool R26.21.2801 - Official SPD/Unisoc Flash Tool
Download SPD Flash Tool R26.21.2801 to Flash Stock Firmware on Spreadtrum Smartphone and Tablets.
spdflashtool.com
2-You have to unpack the ROM using SPD_Upgrade_Tool
https://www.gsmmafia.com/ Here are the ROMs
After completing the extraction, make a patch for the boot With Magisk-v24.3
You will get a rooted boot file Replace it with the old boot
In the end, flash the device and you will notice that you have the root
I am attaching an explanatory video
not the group you looking for but thanks for sharing this
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
thanks.
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
How can we create realme c25y group in xda
Excuse me I want to ask, will this delete all internal data?
Doly12 said:
Excuse me I want to ask, will this delete all internal data?
Click to expand...
Click to collapse
yes.
Yo, how did you flash it?
Biglet0w said:
Yo, how did you flash it?
Click to expand...
Click to collapse
spd flash tool
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
Hi
When I try to call the emergency numbers, I can't, it says that the credit is not enough to make the call
I rebooted and flashed according to the video you posted, but it didn't work
I changed the chip but the same problem remains
Can you give me a solution to this problem
my phone recognize sim but when call people it said cellular is not available, when i use my sim in other phone it work normal, i try flash the rom again but spd tool said error !!!GSM Cali in phone is not calibrated.Reserved[7]:0x00000000,[ID=0x2] pls help
i have rmx3269_11_A.18 and its not on gsmmafia this build number what i do please help
Can i install twrp from c25 or c25s
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Reyproject said:
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Click to expand...
Click to collapse
1) I don't think so.
2)Yes.
JA sunny said:
1) I don't think so.
2)Yes.
Click to expand...
Click to collapse
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
I think you need to have the bootloader unlocked to boot into custom img
elokuba said:
Can i install twrp from c25 or c25s
Click to expand...
Click to collapse
Don't
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
Can you please check if this works
File
XDA forum
JA sunny said:
Can you please check if this works
File
XDA forum
Click to expand...
Click to collapse
What does it do?
Reyproject said:
What does it do?
Click to expand...
Click to collapse
removes the black bar on the notch/punchhole side that you see on some apps and games when the phone is in landscape. I'll root my phone if this works.
Related
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Jharrisonkerr said:
So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Click to expand...
Click to collapse
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
MartinX3 said:
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
Click to expand...
Click to collapse
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Jharrisonkerr said:
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Click to expand...
Click to collapse
Hi Jharrison,
You did say it hangs
At twrp boot logo?
MartinX3 said:
Hi Jharrison,
You did say it hangs
At twrp boot logo?
Click to expand...
Click to collapse
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Jharrisonkerr said:
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Click to expand...
Click to collapse
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
MartinX3 said:
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
Click to expand...
Click to collapse
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Jharrisonkerr said:
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Click to expand...
Click to collapse
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
MartinX3 said:
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
Click to expand...
Click to collapse
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Jharrisonkerr said:
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Click to expand...
Click to collapse
The correct way is in the first post of the first page in the main twrp thread.
Managed to get it working, however once all installed it asks to update the magisk app to 19.3 which I have done however it is now stuck in a bootloop where it loads Sony and powered by android and then reboots every time.
What's the fix for this?
So far I've fixed it by reinstalling the previous version through twrp. Is there issues with magisk 19.3?
Alos now in the magisk manager I have the manager showing up to date(7.3.2) but magisk is showing not installed only able to install magisk 19.3?
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
MartinX3 said:
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
Click to expand...
Click to collapse
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Jharrisonkerr said:
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Click to expand...
Click to collapse
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Tried the magisk uninstaller but every time I do it comes up with error 1 and then never installs.
The flash boot.sin sounds a easy fix, I will try that and see. If not looks like a full firmware reinstall is on the cards. I'll stick with 18.1 when I do as that seemed to work until I updated. I'll wait till a stable release of 19.4 is released.
Many thanks for your help so far Martin.
MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Jharrisonkerr said:
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Click to expand...
Click to collapse
The app is fine
MartinX3 said:
The app is fine
Click to expand...
Click to collapse
Awesome I'll update the app to latest then and leave magisk at 18.1 as root is working fine so far.
Many thanks for your help with all this Martin. :good:
MartinX3 said:
The correct way is in the first post of the first page in the main twrp thread.
Click to expand...
Click to collapse
Can you share the link please? I visited your profile but did not found the that thread how to flash my sony xz3 using TWRP.
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Lemmy554 said:
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Click to expand...
Click to collapse
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Almasd said:
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Click to expand...
Click to collapse
In Magisk Manager you have to "Tap to start SafetyNet check".
Oh I see. Thanks. It's ctsProfile: true. (Now I'm on stock rom with root)
Almasd said:
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Click to expand...
Click to collapse
How to unlock ur bootloader plz suggest me.
Risul49 said:
How to unlock ur bootloader plz suggest me.
Click to expand...
Click to collapse
I don't have RMX1993(EX) anymore. But below might help you.
If you are on ColorOS (Android 9) or RUI1 (Android 10) then you can directly follow the bootloader unlock tutorials on the internet. But if you are on RUI2 (Android 11) then you need to downgrade to RUI1 first.
I also did the same procedure.
But below is for RMX1901CN Realme X device procedure. I believe it would give you a hint.
1. I found Rollback_RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip (for Chinese version) firmware from Realme X Official Telegram group.
2. Then I opened it from the file manager and the device rebooted automatically and the downgrade firmware was installed. After that, I unlocked it with the DeepTesting app for RUI1 with instructions that I found on the internet.
Also, you might try this method: https://c.realme.com/in/post-details/1476520599785316352
Also, comments on this post might help (I have no idea Realme X2 Pro instruction is works for your device but JFYI): https://c.realme.com/in/post-details/1478098096796815360
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?
So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.
ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O
where is the "Download zip only" option ?
VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...
Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com
I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?