Develop Bugs

Realme X2 1993 development

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

GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00

Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?

hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.

Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple

Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?

Hello, which one is the Qualcomm driver to be installed for sdm660?

[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

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)

Question Beginners step-by-step guide to installing Xiaomi.EU on POCO F3?

I have finally unlocked the bootloader (no guides mention it will wipe my phone at the same time!).
Now I am looking again at Roms, HentaiOS and ArrowOS were contenders but Xiaomi.EU sounds like the best of all factors, a Poco F3 centric, manufacturer update with added functionality and removed bloat.
I have watched several "guides" to install, including this one (
) and this one (
) both seem to assume that I am not retarded!
I would like a really easy, step-by-step guide to how to install this Rom.
Do I need to install ADB? Some people say to load the Xiaomi.EU rom in internal storage but to wipe the phone first, so how would I do that? Some say I should BOOT TWRP, others say I need to install it? huh?
There has to be a "explain it to me like im three years old", guide to this!? ACK!

ArghMonkey said:
I have finally unlocked the bootloader (no guides mention it will wipe my phone at the same time!).
Now I am looking again at Roms, HentaiOS and ArrowOS were contenders but Xiaomi.EU sounds like the best of all factors, a Poco F3 centric, manufacturer update with added functionality and removed bloat.
I have watched several "guides" to install, including this one (
) and this one (
) both seem to assume that I am not retarded!
I would like a really easy, step-by-step guide to how to install this Rom.
Do I need to install ADB? Some people say to load the Xiaomi.EU rom in internal storage but to wipe the phone first, so how would I do that? Some say I should BOOT TWRP, others say I need to install it? huh?
There has to be a "explain it to me like im three years old", guide to this!? ACK!
Click to expand...
Click to collapse
You don't "install" ADB and Fastboot. Those are protocols through which a PC can talk to an Android device for debugging purpose and other purposes like this.
The Fastboot Mode on an Android phone lets you deep system stuff, like modifying partitions (flashing, erasing, etc.)
ADB lets you do more high-level stuff, like removing system apps, granting/removing permissions to apps, pulling/pushing files from/onto storage.
To speak to those protocols, you need the portable Command Line Tools for ADB & Fastboot built by Google:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
First, you unlock the bootloader (which factory-resets your phone, lol),
then you put the ROM zip-file (e.g. Xiaomi.eu Custom ROM) onto the phone storage,
then you reboot your phone into Fastboot Mode (POWER + Volume Down),
then, in Fastboot, you boot TWRP (a Custom Recovery):
Open Command Prompt inside the Platform-Tools folder,
do "fastboot boot TWRP.img" (assuming the TWRP file name is "TWRP.img")
then you flash the ROM inside TWRP,
then you format data & clear Dalvik Cache,
that's it. I hope I haven't forgotten anything.

I'd also like to include some Notes that I have made for myself in a text file:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
Xiaomi ADB & Fastboot Tools: github.com/Szaki/XiaomiADBFastbootTools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Magisk: github.com/topjohnwu/Magisk
Poco F3 - Clean Install of Xiaomi.eu ROM:
Download Stock ROM (EEA Fastboot) & Xiaomi.eu Weekly
Delete Anti-Rollback Code from Flash_all.bat
Patch Xiaomi.eu boot.img with Magisk
Flash Stock ROM with Mi Flash
Boot System
Boot TWRP @Nebrassy
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse

dreamytom said:
You don't "install" ADB and Fastboot. Those are protocols through which a PC can talk to an Android device for debugging purpose and other purposes like this.
The Fastboot Mode on an Android phone lets you deep system stuff, like modifying partitions (flashing, erasing, etc.)
ADB lets you do more high-level stuff, like removing system apps, granting/removing permissions to apps, pulling/pushing files from/onto storage.
To speak to those protocols, you need the portable Command Line Tools for ADB & Fastboot built by Google:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
First, you unlock the bootloader (which factory-resets your phone, lol),
then you put the ROM zip-file (e.g. Xiaomi.eu Custom ROM) onto the phone storage,
then you reboot your phone into Fastboot Mode (POWER + Volume Down),
then, in Fastboot, you boot TWRP (a Custom Recovery):
Open Command Prompt inside the Platform-Tools folder,
do "fastboot boot TWRP.img" (assuming the TWRP file name is "TWRP.img")
then you flash the ROM inside TWRP,
then you format data & clear Dalvik Cache,
that's it. I hope I haven't forgotten anything.
Click to expand...
Click to collapse
Good job!
You could almost give us a guide on the dedicated "how to" section
However I read that to start twrp from fastboot using cmd you need to put the twrp(filename).img on the platform tool folder. Right?

RollDload said:
Good job!
You could almost give us a guide on the dedicated "how to" section
However I read that to start twrp from fastboot using cmd you need to put the twrp(filename).img on the platform tool folder. Right?
Click to expand...
Click to collapse
Oh yes, that command also assumes TWRP.img is inside the same folder.
What I do is drag 'n drop the TWRP file into the CMD-window. The full path to the TWRP-file will automatically be written in the CMD-window.

dreamytom said:
Oh yes, that command also assumes TWRP.img is inside the same folder.
What I do is drag 'n drop the TWRP file into the CMD-window. The full path to the TWRP-file will automatically be written in the CMD-window.
Click to expand...
Click to collapse
I remembered well then...
Thanks!
Since I rooted the galaxy s5 I try to carefully read as much information as possible before performing any modding operation.
Both from the positive and negative experiences of the users it is possible to avoid errors and bricks.
In a few hours I can unlock the bootloader and move to the stable of xiaomi.eu, I can't wait

I went from "miui stock 12.5.3" EEA to "xiaomi.eu stable 12.5.6." and everything went well!
The steps I took are as follows:
1) I have unlocked the bootloader;
2) I copied the image of the latest TWRPnebrassy recovery in C: \ platform-tools;
3) I copied the .zip file of xiaomi.eu-12.5.6 in the phone memory;
4) After enabling usb debug I restarted the phone in fastboot and connected it to the pc;
5) in the "C: \ platform-tools" folder, I started a cmd window;
6) in cmd I typed the following command
Code:
fastboot boot TWRP.img
Then the phone rebooted into TWRP;
7) "in TWRP" I went to "INSTALL" and selected the .zip file of the rom and started the flash;
8) Completed the flash (it takes a few minutes) I went to "WIPE" and I formatted "data";
9) Subsequently I rebooted in the system (the first start takes a few more minutes, wait);
Done;

Can vasishasht's TWRP be used instead of Nebrassy's?

Dhruv.m said:
Can vasishasht's TWRP be used instead of Nebrassy's?
Click to expand...
Click to collapse
Yes. They're both TWRP 3.5.2, but they are still different from each other.
With Vasishoth's you may get "Failed to mount" errors right at the start.
If you face any errors, you can always switch TWRP.

also, can this be flashed directly from an AOSP ROM?

@Dhruv.m Xiaomi.eu can't be dirty-flashed on an AOSP ROM, if that's your question.
There's a low chance that it may boot, but it'll be broken & unusable.

dreamytom said:
@Dhruv.m Xiaomi.eu can't be dirty-flashed on an AOSP ROM, if that's your question.
There's a low chance that it may boot, but it'll be broken & unusable.
Click to expand...
Click to collapse
Nah I'm not asking that, I'm asking that do I need to go back to MIUI before flashing xiaomi.eu or can it be installed cleanly from an AOSP ROM?

Dhruv.m said:
Nah I'm not asking that, I'm asking that do I need to go back to MIUI before flashing xiaomi.eu or can it be installed cleanly from an AOSP ROM?
Click to expand...
Click to collapse
That's right what @dreamytom says, I personally haven't tried vasishasht's, so I can't tell you.
I know that the xiaomi.eu flash works well if you start from the stock, starting from an aosp I don't know, errors could arise, so I would avoid.
I used the nebrassy one because the xiaomi.eu installation package flashes the nebrassy twrp, so it seemed like the right choice.
So I advise you to install the .eu starting from a stock miui.

[How-To] Root Android 12L/11 - Bootable patched_magisk & Instructions on DIY

Hello Friends,
Android 12L Section
Android 12L has finally been released for Duo 1 and the update makes this device what it should have been from the beginning (again...). But root is always nice.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 12L stock boot img patched with magisk 25.2, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 25.2 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Android 11 Section
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Extraction of payload.bin from OTA.
If you want to extract the boot.img yourself and patch it yourself, download the payload.bin extractor from here. Acquire the OTA either via recovery images or capturing the OTA URL during an update (link).
Use the payload dumper to get the boot.img, install Magisk on your device and transfer the boot.img to it to patch that stock boot.img using Magisk. After that, you will have your own patched boot.img.
Proceed with step number 4.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com

Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.

NTchrist said:
Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.
Click to expand...
Click to collapse
I fully agree with you. I did magisk_patching for old nexus's, oneplus 6t, and a couple of the pixels and I actually didn't get that much spam. But go a ton of spam for system UI tweaks, twrp and such how-tos I posted.
The primary reason I provided a pre-patched one here is because I had a ton of issues getting payload dumper to work on my fresh windows 11. And this was just easier.

Finally a much more streamlined process, and it works perfectly. That back & forth patching each month was getting too hairy. Not too mention how much faster this device is now which has me into it all over again. This has all been worth it so far in my opinion based off of usage today. no random app crashes anymore , much better UI and control panel across the board, Hell it even sounds louder. I'm really happy with this update and root so far.

OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?

-

delfuhd said:
OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?
Click to expand...
Click to collapse
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Just making sure we are on the same page.

eqbirvin said:
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Click to expand...
Click to collapse
No problem. Not flashing, just trying to boot. From
adb reboot bootloader
I'm executing:
fastboot boot patchedboot.img
Trying to flash to the boot partition just gives me an error anyway.
Also, just to be clear, I've tried it with your patched image as well as a boot image that I extracted from payload.bin. Both same results.
EDIT: OK I bit the bullet and did a factory reset through recovery. I wanted to avoid this as it's a pain setting the device up again. However, this solved the problem. I was able to complete the steps above and successfully gained root permanently. Thank you for your help!

eqbirvin said:
Hello Friends,
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you do not want to use my pre-patched boot that is understandable but at this time I am not providing a how-to on extracting the boot from the OTA. You can use the pre-existing root guide by @NTchrist and @Perseu5 to at least extract the stock boot and then patch it yourself, just make sure you use Magisk 23.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
If there is enough demand, I will do a walk thought on extracting the stock boot and patching it because I understand some don't like to trust downloaded boots.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for providing the patched boot and for the guide (although in my case I know the steps). You save me a lot of work. Excellent.

I got the AT&T version. I just booted the patched image from OP and it works. (i was having trouble patching the AT&T image. probably was my fault because i was using magisk v.24.1 rather than v.23)

Any one get a system update notification?

Quick question:
Can we use the generic boot image to get TWRP working on the Surface Duo?

eqbirvin said:
Any one get a system update notification?
Click to expand...
Click to collapse
Yes , a 565MB file !

How do we update and keep root?

diejuse said:
How do we update and keep root?
Click to expand...
Click to collapse
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com

pvillasuso said:
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Click to expand...
Click to collapse
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done

NTchrist said:
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done
Click to expand...
Click to collapse
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy

pvillasuso said:
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy
Click to expand...
Click to collapse
Updated to the latest , 2022.115.10 OTA

pvillasuso said:
Updated to the latest , 2022.115.10 OTA
Click to expand...
Click to collapse
Updated to the latest , 2022.215.137 OTA

pvillasuso said:
Updated to the latest , 2022.215.137 OTA
Click to expand...
Click to collapse
Same process as before?