Related
Rom miui 11 stable for realme Q
Sorry English my bad
Fingerprints work
Faceunlock
Bt audio
Wifi,call and more
Bug : No miui camera but may be flash ANX camera support 48mp
Note : Gcam need add configs
Kernel and vendor mod for Q but i thing 5pro will work
How to install:
- wipe all
- flash rom zip
- flash sdcard fix
- flash gapps 9.0 or magisk (if you want)
- if then reboot devices auto boot twrp . you need format data
We are the ones who were used the earliest. So be grateful to the team mokee especially development china CHEN
Link rom and patch : <Mod edit>
Is like the stock Color Os from RealmeQ right?, Only with Asian Languages and English, With MiUi apps and NO Play store or Google apps (Unless flash OGAPPS Of course).
I really need the Spanish Language so is a no go for me, but still, it works pretty good for anyone who wnat to try.
I think would be a good idea to clarify what languages it has.
To clarify, you do all this from TWRP? So this requires that phone is rooted and TWRP installed?
@motherface
The ROM zip packages should be flashed trought TWRP, but its not neccesary to have rooted the phone.
So to clarify, you need to unlock your bootloader, flash TWRP zip trought Fastboot-Bootloader and then reboot to recovery (TWRP).
Tmv_Josue said:
@motherface
The ROM zip packages should be flashed trought TWRP, but its not neccesary to have rooted the phone.
So to clarify, you need to unlock your bootloader, flash TWRP zip trought Fastboot-Bootloader and then reboot to recovery (TWRP).
Click to expand...
Click to collapse
I very much would like to do this - just came from a xiaomi redmi phone, but don't know exactly how to do this. Can you link a tutorial. Gracias
Setup of miui 11 succeeded.If I try to change the default launcher to another one(ex nova launcher), An error message (As launcher apps from third parties may result in problems like data leak, abnormal battery drain and lagging, etc., only those verified by MIUI can be set as your default launcher) appears to change the default launcher. Do you happen to know the solution?
@motherface.
Unlock Bootloader
Go to:
https://forum.xda-developers.com/realme-5-pro/help/realme-5-pro-bootloader-unlock-tutorial-t3985011
1. Install: DeepTesting_SDM710_9.0_Realme.apk
2. Start the in-depth test
3. Download ADB for Windows:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4. Go to: Settings > Additional settings > Developer options > USB Debugging (Activate it)
5. In PC open CMD and put these commands:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
TWRP Install:
Go to:
https://forum.xda-developers.com/re...ild-twrp-realme-q-support-flash-ozip-t3986131
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
Tmv_Josue said:
@motherface.
Unlock Bootloader
Go to:
https://forum.xda-developers.com/realme-5-pro/help/realme-5-pro-bootloader-unlock-tutorial-t3985011
1. Install: DeepTesting_SDM710_9.0_Realme.apk
2. Start the in-depth test
3. Download ADB for Windows:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4. Go to: Settings > Additional settings > Developer options > USB Debugging (Activate it)
5. In PC open CMD and put these commands:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot (System)
TWRP Install:
Go to:
https://forum.xda-developers.com/re...ild-twrp-realme-q-support-flash-ozip-t3986131
adb reboot bootloader
fastboot flash recovery TWRP.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery (Reboot to RECOVERY -TWRP)
Click to expand...
Click to collapse
Got it to work! Thank you very, very much. I am really loving this/needing this. ColorOS is trash.
I initially had issues with the deeptesting app. I think it was because I didn't launch into bootloader through that app itself, and used a different adb command prompt location. Got this work work this time though.
Thanks heaps
I flashed the gapp but it didn't work
hoangnam1103 said:
I flashed the gapp but it didn't work
Click to expand...
Click to collapse
Then download google app installer apk nd try
prashant.palange said:
Then download google app installer apk nd try
Click to expand...
Click to collapse
I installed gapp and downloaded apps from gapp. however I have problems with syncing contacts. It seems the problem is from google sync contact
Hello there
Any possibility to use this ROM with the Realme 5 pro global variant?
@sbsmbm.
Have you tried installing it through the TWRP that works with the R5pro?:
Maybe it works:
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-realme-5-pro-t3985203
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.
The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)
sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
[deleted]
johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working
Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.
I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.
I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?
Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.
I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.
I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com
citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.
Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.
the 099 came from OTA so why whould bootloader be 094?
Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi
I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?
Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA
I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?
Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.
Hi, guys. The patched imaged failed, and the detail is as follows. I am really confused and any comments are welcomed.
device: Redmi K40
Magisk version: v22.0, v22.1, v23.0 report the same behavior
MIUI: xiaomi.eu_multi_HMK40_POCOF3_21.12.8_v12-12-fastboot
Here's what I have done (following the docs)
1. unlock bootloader, turn usb debug on.
2. flush the brand-new MIUI rom as above.
3. installmagisk version xfrom the official github apk, where x represents v22.0, v22.1 or v23.0, withinstalled: N/A, A/B: yes, Ramdisk: Yes, SAR: yes
4. copy theboot.imgto the phone and patch it in magisk. The los is available here.
5. use.\platform-tools-windows\fastboot.exe flash boot patched_img.imgand.\platform-tools-windows\fastboot.exe flash vbmeta --disable-verity --disable-verification .\images\vbmeta.img, then reboot.
6. when I enter the magisk app again, it is the same as before, i.e.,installed: n/awithinstallbutton still showingselect and patch a file, nothing changed.
I wonder if anyone met the same problem when installing magisk on redmi K40, or could you give some suggestions on how to install it? I tried many available tutorials but all ended with the above problem.
i believe you need twrp or other custom recovery installed to install magisk. you haven't mentioned twrp at all so i'm assuming you don't have it? i mean, yes, you can patch the boot.img but i think you still need twrp installed - someone will correct if i'm wrong.
boot your device into fastboot mode, plug in to pc and open adb fastboot cmd box, type 'fastboot devices' and hit enter. if a serial key shows up, you're connected.
Download lastest official twrp from here (alioth is the name or our device).
Download lastest magisk manager from here and rename the .apk file extension to .zip, for example: Magisk-v24.1.apk → Magisk-v24.1.zip
1. the simplest way is to boot to twrp using cmd 'fastboot boot twrp.img' [or whatever your twrp.img is named to] with the twrp.img in adb fastboot folder (usually on C drive root)
2. install twrp 'Preferred Installation Method: Once booted, navigate to the Advanced > Flash Current TWRP option. This will install the TWRP image you just booted permanently to the device.'
3. flash magisk zip in twrp and DESELECT 'Inject twrp after install' if you have that option (sorry to be vague but i haven't updated in a while and it may now be different.
4. boot to system, you'll find a link in apps for magisk app to finish installing magisk manager.
Hope this makes sense, it's 4.50am and i'm about to go bed!! sorry if it's not correct at all...
may be you can use "fastboot reboot fastboot" at first
flash your magisk.apk as zip in recovery (rename it to .zip and flash using recovery)
Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?
You probably had a kind of encryption (fingerprint + PIN/or Password). Removing those would allow memory to be read.
Also, Twrp has to be kkk's. Not Vasi, Not any other. Kkk's TWRP supports a12 but still doesn't decrypt, and that's why we remove lock.
You should've asked dude before doing anything that might lead to making a brand know flash again.
I think now you should flash from scratch and go one by one. TWRP will root your rom just fine.
AreuMiFan said:
Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?
Click to expand...
Click to collapse
To solve this,just format you data and reflash boot.img
Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?
AreuMiFan said:
Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?
Click to expand...
Click to collapse
I havent met this yet
eee625 said:
I havent met this yet
Click to expand...
Click to collapse
Hi reuMiFan.
Neither did I :/ since I don't really need for safetynet to pass. I hope you find a solution bud. You just need to dig a little more about it. I'm sure you'll work it out.
This tutorial will :
Provide you with all the steps to unlock your Oneplus 11 bootloader
Provide you with all the steps to root your Oneplus 11 (with your bootloader already unlocked)
Provide you with all the steps to keep root during/after an OTA (system update)
Provide you with some Interesting Magisk Modules
Provide you with a lot tricks if you have troubleshooting questions
Provide you with a lot of solutions of you have softbricked your Oneplus 11
Provide you with all the ways if you want to bring back your Oneplus 11 to unroot & lock back the bootloader
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
Original_Init_boot images : Extracting Payload.bin
use payload dumper go from https://github.com/ssut/payload-dumper-go
Guide: how to extract payload from the OTA Package and get the init_boot.img ?
And share the Original_init_boot.img with us by posting them in this thread.
All init_boot.img are Orginals (not patched with Magisk, that will be your job to patch them following the guide below!)
OxygenOS 13.1.0.501_init_boot :
CPH2451 Init_Boot (AA) / Not yet available
CPH2449 Init_Boot (BA/GLO) / Not yet available
CPH2447 Init_Boot (DA)
Full OTA packages / Not yet available
OxygenOS 13 A.10_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA Packages / Full OTA EU A10 / Full OTA DA/India A10
OxygenOS 13 A.09_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA packages
OxygenOS 13 A.08_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA)
OxygenOS 13 A.07_init_boot :
Init_Boot (AA)
Init_Boot (BA)
Init_Boot (DA)/ Not yet available
OxygenOS 13 A.06_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA) / Not yet available
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it. It is also recomended not to set any lockscreen password before unlocking the bootloader/rooting. So if you have a lockscreen password / fingerprint just remove it, root your device and set it up after rooting your device.Unlock the Bootloader and Root the OnePlus 11Step 1 – Enable OEM unlockingYou need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
{
"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"
}
Step 2 – Unlock your bootloaderSet up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot flashing unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Root your Oneplus 11 (with Bootloader already unlocked)
Patch OnePlus 11 Init_Boot.img via Magisk
Download and install the lastest Stable Magisk App starting from v26.1 works fine.
Then launch it and tap on the Install button next to Magisk.
After that, choose ‘Select and Patch a File’, and navigate to the stock init_boot.img file, and select it.
Then tap on the Let’s Go button situated at the top right.
The init_boot.img file will now be patched and placed under the Downloads folder on your device. You should transfer this file to the platform-tools folder on your PC and rename it to magisk_patched_boot.img.
Boot OnePlus 11 to Fastboot Mode
Now connect your device to the PC via a USB cable. Make sure USB Debugging is enabled.
Then head over to the platform-tools folder, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the following command in the CMD window to boot your device to Fastboot Mode "adb reboot bootloader"
To verify the Fastboot connection, type in the below command and you should get back the device ID.fastboot devices
Flashing the magisk_init_boot1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 9 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot flash init_boot magisk_init_boot.img"
Change to the exact name "magisk_init_boot.img" of the init_boot that has been patched
"fastboot reboot"
Step 2 - Reboot and your device is now rooted !
Keep Root after OTA Updates
How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
For Android 13, install this APK "OPLocalUpdate_For_Android13.apk"
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW! Use the above application to make sure your device will not reboot
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !Option 2: with incremental OTA Access (AA) :
Option 2A : Get back your original init_boot image using Magisk Manager
1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock init_boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 11
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Reboot and enjoy
Option 2B : Get back your original init_boot image
You can find your originel init_boot.img in our thread from your current OTA.
Go to fastboot.
Code once in fastboot mode:
"fastboot flash init_boot original_init_boot.img"
You will obviously loose Root access once you have flash the originel_init_boot.
Then just flash the incremental OTA using your system OTA or Oxygen Updater.
To get root again just read the above guide :
Patch OnePlus 11 Init_Boot.img via Magisk
Troubleshooting questions :
Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear cachesClear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Safetynet FixInstall Safetynet Fix Magisk Module
Step 4 Optional - Shamiko ModuleInstall Shamiko ModuleHow to use it : guide
How to fix Netflix ? :If you can't install/update Netflix thru Google Play install the latest Netflix from apkmirror manually (like any other apk file)
Option 1 - Follow this guide
Option 2 - Flash the DRM module attached
Option 3 - Flash another DRM module attached
Usefull Magisk Modules For Oneplus 11:Google materials:
Enable Call Recording with native
Enable unlimited storage Google photos
Music & Video materials:
Viper 4 Android
Revanced Manager to get Revanced Youtube & others Revanced applications
Theming materials:
- Substratum lite : Liv Dark theme & OOS Outher theme
- Cyberpunk Bootanimation
- OOS Status bar magisk module (see attached)
- Repainter application
- Seeker application
- LWP+ application
- OOS themer by Oneplus
Tools materials:
Enable Volte
Enable Engineering unlock
Enable IPV6
Disable Flag secure
Magisk Bootloop Protect
Modules Management materials:
Fox Module Manager
Phone Bricked ? :
Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules
Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original init_boot.imgIf your device can go to fastboot mode:
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_init_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash the rollback full OTA file (will wipe data)
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Flash it using local update or thru the application OPLocalUpdate_For_Android13.apk
You can also flash it by extracting and flashing the partitions using fastboot and fastbootd manually.
You may also use Fastboot Enhance.
Option 4 - Flash back full OTA fileIf you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 5 - Change the active slotIf your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 6 - Wipe data with fastboot command
Code once in fastboot mode:
"fastboot- w"
Option 6 - OFD/EDL
Option 1, 2 & 4 would normally not alter your personal data, applications and own set-upOption 3 and 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :Option 1 : Original init_boot & relock with fastboot commandStep 1 - Restore orignal init_boot.imgOption A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_lnit_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the init_boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : after removing Magisk app entirely Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original init_boot.
Step 2 - Relock the bootloader1. Execute the following command to proceed for bootloader unlocking: ""fastboot flashing unlock""
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
Great job, @Steve0007! That looks like an incredibly helpful and well-written tutorial. You've done an excellent job breaking down a complex process into easy-to-follow steps, making it accessible for users of all levels. Your attention to detail and clear explanations make it a valuable resource for anyone looking to learn and improve their skills. Keep up the great work!
Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices
Thank
_Johnito_ said:
Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices
Click to expand...
Click to collapse
Thank you for your comments.
Just updated the guide included 2 options to get Netflix working while rooted !
Thank you and @qriozum , i have netflix working following this steps. Didnt even need to hide it in magisk.
Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.
kairukaizer99 said:
Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.
Click to expand...
Click to collapse
Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.
kairukaizer99 said:
Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.
Click to expand...
Click to collapse
You can't get root with locked bootloader on this (and most) phones.
Anyway, root doesn't necessarily mean that you won't get L1. On my rooted OnePlus 8T I still have L1.
i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?
N
vnod said:
i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?
Click to expand...
Click to collapse
No, you should better use your current init_boot.img to patch it. Now we can use the latest v26.0 Magisk app
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
I tried the second:
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot
zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
"Fastboot flash init_boot NAME_OF_YOUR_Magisk_init_boot.img"
zeldomar said:
I tried the second:
View attachment 5881985
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot
Click to expand...
Click to collapse
My OP 11 works again thanks to this tutorial : https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/
Hi ,can someone please post boot.img for CPH2449 (EU) A.09? I accidentally flashed init_boot over boot... what a silly move.
Alternatively, the link to the A.09 OTA, I can extract it myself, I tried looking for it but for now nobody posted it.
@geomass this is untouched boot.img for CPH2449 (EU) A.09
But FWI you could just retrieve it yourself easily with lets say Fastboot Enhance and the firmware itself of course.
Thank you so much @_Johnito_ . The timing of your response is insane
I don't use windows so can't run fastboot enhance. How can it be done with fastboot?
You are welcome. I am not the most informed guy here by far but my guess is that if you borked boot.img on your phone, it is probably better to recover it from the vanilla firmware more than from the phone (with fastboot commands). I hope i get your question right though.
For general cases, instructions on "how to backup persist.img" on this great tutorial can be applied for any android partition / any desktop OS with a command line software.
I tried booting into that image you provided, and while it correctly sends it to the device and reboots the device, it goes into fastboot every time.
Flashing it fails every time, like so:
fastboot flash boot boot_CPH2449_11_A.09.img
Sending 'boot' (196608 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed