Related
I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?
I have the 1993ex version and the FP is working fine after a16
hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.
surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.
hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...
Howto thread is on this forum...
woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...
I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...
hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!
ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Removing "Bloatware"
Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.
Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.
Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.
You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.
Installing Debloater
Launch Magisk Manager and select "Download" from the menu
Use the search function to locate the package "Busybox for Android NDK"
Install the package, and chose to skip the reboot at the end of the procedure.
Use the search function to locate the package "Debloater Terminal Emulator"
Install the package and this time proceed with the reboot
When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
Open the terminal and issue:
Code:
su
(confirm the request for superuser access) and then
Code:
debloat
Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.
Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.
One Question
Can i know this work for Redmi Note 9 global non NFC?
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
dfahren said:
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
Click to expand...
Click to collapse
Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E
[email protected] said:
Can i know this work for Redmi Note 9 global non NFC?
Click to expand...
Click to collapse
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
N3OMOD said:
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
Click to expand...
Click to collapse
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
dfahren said:
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
Click to expand...
Click to collapse
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
dfahren said:
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
Click to expand...
Click to collapse
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
dfahren said:
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
Click to expand...
Click to collapse
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
dfahren said:
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
Click to expand...
Click to collapse
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Followed the steps, worked flawlessly on my Redmi Note 9 (Merlin) 3gb ram 64gb storage purchased in Europe, running Global 11.0.5.
Thank you so very much!
I had successfully done this in the past but messed something up with xposed later, I won't xposed it this time and just enjoy my root-ness.
N3OMOD said:
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
...
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
...
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
The original explanation from user "neko-kun" seemed to me an automatic translation hence the rather weird language.
I can testify to the statement that you can reflash the original boot.img file should you enter a bootloop (which I got).
AdAway is also working for me as does AFWall+ (I needed to leave logging of blocked packets as it is -> off)
N3OMOD said:
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
i'm having an infinite bootloop and keep pressing power + vol down didn't help , what should i do ?
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
dfahren said:
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
Click to expand...
Click to collapse
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
What about entering recovery?
noodlelicious said:
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
Click to expand...
Click to collapse
Try to enter stock recovery, if you can, select mi assitant. After that connect trough adb and run "adb reboot bootloader", that should do the trick.
If phone isnt booting none of main enviroments (system, recovery or fastboot/bootloader) battery drainage may restablish normal boot order. Just remember that if in any case it boots to recovery, use adb command to reboot to bootloader.
Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global
Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.
- Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.
- vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.
Hi .. Is there a way to write to system / app. I need to be able to pass an application to system. Thank you.
Does netflix still work in HD after having the BL unlocked and further rooted?
How to patch vbmeta
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
N3OMOD said:
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Click to expand...
Click to collapse
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
can this be used to root the EU model: MZB9410EU ?
farvehar09 said:
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
Click to expand...
Click to collapse
Yes u can, i use the original vbmeta from miui_MERLINIDGlobal_V12.0.1.0.QJOIDXM_709d727d58_10.0.zip (ID variant)
I have to be honest: I really enjoy using this phone, both esthetically and and relating to my everyday needs.
But...
A stock Android experience would bring it to the next level in my situation. I don't game a lot recently, I'd accept some problems with those touch controls.
But I want to have a complete a stable software like a basic Pixel experience.
Do you think someone is going to work on this phone?
Are there any alternatives?
Thank you!
Unlock the bootloader (guide on xda), apply the fingerprint fix (flash blank vbmeta - guide on xda) & flash a GSI to the system partition (I recommend phhusson's or Eremitein's).
n.b. after unlocking the bootloader, I highly recommend backing up your EFS/QCN with QFIL.
Thanks a lot for your answer!
Unfortunately I stopped at the "fastboot erase system" command: my terminal is showing "FAILED (remote: 'Check device console.')"
I tried updating my adb and fastboot drivers, and platform and tools too.
No success.
adwinp said:
Unlock the bootloader (guide on xda), apply the fingerprint fix (flash blank vbmeta - guide on xda) & flash a GSI to the system partition (I recommend phhusson's or Eremitein's).
n.b. after unlocking the bootloader, I highly recommend backing up your EFS/QCN with QFIL.
Click to expand...
Click to collapse
What's not working on the gsi?
DISCLAIMER: whatever you're doing with your device is your responsibility and only yours! Not mine or anyone else. So be careful and don't brick your device, but if you do and are looking for someone to blame: use a mirror and nothing else.
This is just a small collection of possible tweaks for the following device. It is meant for advanced/experienced users.
Goals reached:
1) root
2) install twrp, doing nandroidbackup, unlock data with my pin, flashing zips etc.
3) debloated sytem with system-rw
NEW:
Flashed successfully a GSI ROM (LineageOS 18.1) and it booted and worked. Haven't tested much. Instructions can be found below.
NOTE: For the GSI i made an overlay (with phhuson template and attached it to this post. Haven't found the time to upload it to phhuson*s repo and it might take a while, but you can manually install this one if desired.
My phone:
manufacturer: Lerovo
brand: Motorola
model: E7 plus
internal name: guam (XT2081-2)
ROM: QPZS30.30_Q3_38_69_3
channel: retaileu
REQUIREMENTS:
1) your phone connect to a computer with an usb cableUsing linux myself since a year or so, but it will work wirth windows too.
Some tools are windows only (like Rescue and Smart Assistant), so you might need to dual-boot.
2) Android SDK Platform Tools (ABD/FASTBOOT)Download the package for your os, unzip the file and open a terminal in it's directory (or added the path to your PATH environment variable).
https://developer.android.com/studio/releases/platform-tools
Don't forget to enable ADB under developer options.
3) unlocked bootloaderWell, yes if you want to flash something, you really need this. Everything you need to know:
https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
4) optional but strongly recommended: Lenovo Rescue and Smart Assistant (WIndows only)With this tool you can download the latest image for your device and flash it directly to the phone.
You can use these file later for flashing magisk etc.
Further it helped me once when my phone wasn't detectable via fastboot anymore. But there is no guarantee.
Download:
https://support.lenovo.com/de/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Files will be under C:\ProgramData\LMSA\Download\RomFiles/ (Windows 10, 64.bit)
Spoiler: Verified Boot / AVB / VBMETA
From Android 8 onward google implemented a security system called Android verifiy boot. Read more about it here: Android Verified Boot AVB
AVB 2.0
To flash any other software (magisk, twrp, gsi rom etc.) you need to flash a vbmeta.img first:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot bootloader
Spoiler: Magisk
Download: https://github.com/topjohnwu/Magisk
You will find the latest on the right under "Releases".
Instructions:
1) Install "Magisk*.apk in your current rom
2) Copy boot.img from "Lenovo Smart and Rescue" to the internal memory of the phone
3) Flash the boot image within the magisk app (see magisk wiki)
4) reboot bootloader aka adb reboot fastboot
5) fastboot flash boot magisk_patched.img
6) reboot device, open magisk again, done.
Spoiler: SYSTEM-RW
Requirement: root
You can use an existing tool for that: systemRW from lebigmac
Download: https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Follow his instructions and start script from within booted rom. Use his path to copy the script.
Workarounds:
1) ERROR 73: https://forum.xda-developers.com/t/...-read-write-r-w.4247311/page-23#post-84901531 You need to resume from within a linux device.
2) if you encounter any other error it might be related to extra protection. I flashed two files before starting the proccess but they might not be needed:
a) flash an modified/empty vbmeta.img. (see above)
b) Disable verity/encryption (see above)
Spoiler: TWRP
adrianuexen's twrp (see other thread) does not work for me. So i looked around and noticed that the Lenovo K12 (not pro or anything) is a rebranded E7 plus.
Search for "Lenovo K12 twrp" and you will find some sites with unofficial twrp 3.4.2 for that device.
BE CAREFUL: sources for this are at best unofficial, at worst malicious. So choose wisely if you want to go this way.
What is working for me:
everything seems ok: touch screen, decrypt data, adb sideload, flash images, adb shell, mounting etc.
Go ahead if you decided to give it a try.
You can simply try if it works:
1) reboot bootloader
2) fastboot boot recovery.img
If you want to install it:
1) reboot bootloader
2) fastboot flash recovery recovery.img
If twrp starts with prompt for password, change language with the second button.
The K12 was developed for the chinese market, so the recovery starts in chinese language too. You can change language to english like this:
1) right side: 3 button
2) last button on top (world symbol)
3) english and confirm at bottom
Spoiler: Disable DM-Verity - FORCEENCRPYT
You can use this with a working twrp recovery.
I prefer to use adb sideload for these tasks.
Download: Disable DM-Verity - ForceEncrpyt
Spoiler: GSI-ROM flashing
If it is working for you stick with "the usual way", but i can't flash an img-file no matter what i tried. Always get an empty error (error ' ')
Spoiler: The usual way
0. Get an up-to-date fastboot on your computer (fastboot —version should give version >= 29)
1. Get vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
2. Get A/B GSI (I'm guessing you need ARM64), don't forget to uncompress it
3. From running Android, do adb reboot bootloader
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. fastboot reboot bootloader
6. fastboot flash system system-xxxx.img
6bis. If fastboot tells you there isn't enough place, do fastboot delete-logical-partition product, fastboot delete-logical-partition product_a, fastboot delete-logical-partition product_b
and run the fastboot flash command again
7. On your phone, the screen should have a button "go back to recovery", select it, then select "factory reset / wipe data"
8. Reboot and enjoy
Spoiler: the workaround
The idea is: building a super image with the system.img from your choosen GSI.
A)
You can do this directly via lpmake and set your config, an example here: https://forum.xda-developers.com/t/gsis-on-a51-5g.4114349/
B) The tool SuperRW (lebigmac see above) can be used to do the same (and in fact is doing the same). You just need to modify "myargs.txt" copy the system.img to the img folder and are good to go with systemrw.
Today I used AndyYan's GSI LineageOS 18.1
(arm64, A/B) LineageOS 18.1 arm64 A/B
to test it and after setting parameters in myargs.txt the new image was flashable and lineageos booted without any hassle (afaik in that short time .
Instructions:
Requirements: root, vbmeta.img applied correctly, if using: SystemRW
Start with the instructions from lebigmac (see above).
Once you get error 73 you need to stop and continue with steps below before you start sysrw_repair_v1.32.
You need to edit your "myargs.txt" on your device. You will remove/resize the product partition and make some space for the larger systen image of your GSI
1) adb shell
2) su
3) cd /data/local/tmp/systemrw_1.32/log
4) edit myargs.txt (can do it on PC or however you like it most):
a) change product_a partition (100MB and an empty image)
OLD:
--partition product t_a:none:2853670912:mot_dp_group_a --image product_a=/data/local/tmp/systemrw_1.32/img/product_a.img
NEW:
--partition product t_a:none:104857600:mot_dp_group_a --image product_a=/data/local/tmp/systemrw_1.32/img/empty.img
b) change system_a partition (at least the size of your downloadad GSI_system.img)
LineageOS image has 1818747328 byte, so i set the size of the partition to 2 GB)
OLD:
--partition system_a:none:941010944:mot_dp_group_a --image system_a=/data/local/tmp/systemrw_1.32/img/system_a.img
NEW:
--partition system_a:none:2147483648:mot_dp_group_a --image system_a=/data/local/tmp/systemrw_1.32/img/los_18.1.img
5) We will create "empty.img" (when in adb shell
touch /data/local/tmp/systemrw_1.32/img/empty.img
6) leave adb and push your GSI file to the phone
adb push lineage-18.1-20211010-UNOFFICIAL-treble_arm64_bvS.img /data/local/tmp/systemrw_1.32/img/los_18.1.img
7) Now start sysrw_repair.sh from linux machine and let it do all the hard work .
After that you should get a rom which will be flashed automatically or manual if you remove the phone before the flash starts
This is work in progress and feedback very welcome.
changelog:
2021-10-14:
- ROM: QPZS30.30_Q3_38_69_2 to ROM: QPZS30.30_Q3_38_69_3
- vbmeta.img: added information about vbmeta.img / verified boot
- GSI-flashing: LOS 18.1 working
Really nice work
Ty,added a solution to flash GSI ROMs, even if you are not able to flash the system images directly via fastboot
hola esto es un rom de android 11?
Will try later and report back
Thanks very much for this detailed writeup. I think you can safely say that the "workaround" is the way to go, the "usual way" just flops. I suspect it's because the stock partition sizes are insufficient for LineageOS. I was able to flash the same rom as you using lebigmac's scripts, then lineage-18.1-20220217-UNOFFICIAL-treble_arm64_bvS.img.
I have a problem getting root after flashing LOS. I tried to install the latest Magisk version (24.3) but it complains about a leftover 'su'. Removing Magisk causes the system to bootloop, even after reflashing the stock boot.img. How did you manage to get root in LOS?
Edit: after 2 days evaluation the error reported by Magisk doesn't seem to be serious. It just performs as it normally does
Reporting back after a few more days of testing.
Found that bluetooth refuses to work correctly. Tested with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img and lineage-18.1-20220217-UNOFFICIAL-treble_arm64_bvS.img.
Also found the camera software to be inferior in lineage compared to the one found in A10 stock.
I wasn't able to get call recording working neither. Because of all these reasons i decided to move back to stock
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