Database Users

Root RedmI Note 3 snapdradon MIUI 8 6.9.9 developer rom (marshmallow)

Since, the release of the Android M. Google make it hard to root your device. On MIUI 8 with marshmallow I have been trying to figure out a way to root my device. In almost every case I found myself in a boot loop. So after a long work i finally succeed to root my redmi note 3 with no error and bootloop.
I am not responsible for any damage to your devices,loss or damage caused, or alleged to have been caused, directly or indirectly, by the informations or ideas suggested or referenced, etc. If you get a boot loop you can get back to booting by simply flashing the stock "M" system image via fastboot. or Mi flash tool.
Please try at your own risk. Your warranty is now void.
PRE-REQUIREMENTS
1. redmi note 3 ( SD only) with official MiUI 8 6.9.9 developers rom (marshmallow update) :good:
2. officially unlocked bootloader.
3. TWRP recovery ( alka twrp recommended ).
4. patched boot image given below.
5.brain
METHOD RECOVERY METHOD.
1. Download boot.zip and SuperSu.zip
superSu.zip -https://www.androidfilehost.com/?fid=24727369092694142
boot.img - https://www.androidfilehost.com/?fid=24727369092694141
2. copy both the files (boot.img and SuperSu.zip) to your external SD card.
3. now reboot the device in recovery and go to mount section and mount all the partitions.
4. now go to install and go to SD card and flash SuperSu.zip.
5. as the super su is installed go back in install section and select install image.
6. now you will see only .img files so locate to boot.img and select it.
7. In next window you may see two option as " select partition to flash image:" select the first one option BOOT partition and slide the installation slider and reboot your redmi note 3 SD
boot up may take 5-10 mins so don't we panic. and please mention in the comment was it worked for you or not so I can edit boot image for you..
if i help you give me a thanks, by clicking on thanks button

I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?

Just flash supersu stable using ZCX twrp. Head over supersu xda thread for latest stable flashable zip. Worked for me without any issue.

ubaid137 said:
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Click to expand...
Click to collapse
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks

tsrajput said:
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
Click to expand...
Click to collapse
Also my wifi is not working after root..

Does AUX issue resolved in this ROM?
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.

Satav said:
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Click to expand...
Click to collapse
This is not a rom, its a rooting guide.

any news on this ? any new boot.img. I'm on 6.9.22 beta. thanks

Update to OxygenOS 9.0.0

Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
Code:
Updating partition details...
...done
Full SELinux support is present.
Data successfully decrypted
Updating parition details...
...done
MTP Enabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
[COLOR="Red"]E:String resource 'zip_compatible_err' not found.
Using default value.
Zup Treble compatibility error!
Invalid zip file format!
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip[/COLOR]
Updating partition details...
...done
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks

Mouchoir said:
Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks
Click to expand...
Click to collapse
Hello, I can't recommend any guide on outside of xda cause they're not consistent...
Just follow this guide in the first post https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 would help you.
You can't flash twrp 3.3.1 cause you need newer firmware, pie firmware.
Please answer all the questions:
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?

Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo and use a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using an Oreo TWRP if you're on Oreo Firmware/ROM or Pie TWRP if you're on Pie Firmware/ROM) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Click to expand...
Click to collapse
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks

Mouchoir said:
Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks
Click to expand...
Click to collapse
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).

strongst said:
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).
Click to expand...
Click to collapse
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
Clean flash wipes system and data, so no os, data and settings.

PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?

Mouchoir said:
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?
Click to expand...
Click to collapse
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8

strongst said:
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8
Click to expand...
Click to collapse
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Code:
Data successfully decrypted
Updating parition details...
...done
Successfully decrypted with a default password.
Updating parition details...
...done
Full SELinus support is present.
MTP ENabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
Patching system image unconditionally...
E1001 Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR:7
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip[/COLOR]
Updating partition details...
...done

Mouchoir said:
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Click to expand...
Click to collapse
Error 7 is corrupt file, you'll find about it here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003/page591

Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7

Mouchoir said:
Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7
Click to expand...
Click to collapse
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions

strongst said:
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions
Click to expand...
Click to collapse
As stated here, I used 7zip
PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.

Yes because to use fastboot you have to be in fastboot mode...

PierreVicquery02 said:
Yes because to use fastboot you have to be in fastboot mode...
Click to expand...
Click to collapse
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?

Mouchoir said:
As stated here, I used 7zip
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.
Click to expand...
Click to collapse
Mouchoir said:
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?
Click to expand...
Click to collapse
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device

PierreVicquery02 said:
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device
Click to expand...
Click to collapse
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out

Mouchoir said:
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out
Click to expand...
Click to collapse
That's such a strange bug. If you are in fastboot, it's impossible for your PC to recognize it in ADB mode. Try with another computer or use unbrick tool to clean your phone (it installs Oxy 9.0.8)

Well I managed to see the fastboot thanks to the EOM cable but I think I bricked my phone

mi9t loop to TWRP recovery after install MIUI 11

Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)

I am not expert on that field but from my knowledge try booting twrp and copy all your files to your pc or laptop (the one you need at least for saving some photos or videos ) then flash a fastboot ROM
And as I said from my knowledge not sure there might be other ways

testemailmailx said:
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
Click to expand...
Click to collapse
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...

Micdu70 said:
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Click to expand...
Click to collapse
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)

testemailmailx said:
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
Click to expand...
Click to collapse
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo

batman957 said:
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
Click to expand...
Click to collapse
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?

testemailmailx said:
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
Click to expand...
Click to collapse
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )

batman957 said:
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
Click to expand...
Click to collapse
I could make it work easily, but I want keep that step as final step cuz will wipe everything

testemailmailx said:
I could make it work easily, but I want keep that step as final step cuz will wipe everything
Click to expand...
Click to collapse
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) ? then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode

batman957 said:
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
Click to expand...
Click to collapse
God bless us
I’m not using custom rom at all
BTW is there any way to delete twrp recovery without delete system ?

Did you by any chance flashed with the greek TWRP? I got the same bootloop so I get back to miui 10 official global version (the one I updated from) and it booted alright without wipe needed...
I'll try other TWRP versions as well though but right now I don't think I wanna update :|

Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3

sijav said:
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
Click to expand...
Click to collapse
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?

m-Khadem said:
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
Click to expand...
Click to collapse
Here is patched vbmeta for davinci (K20/Mi 9T) => https://drive.google.com/file/d/1IC78J20ovcZudWYlijgSGdjeP6D3hx2V/view?usp=sharing

Status of TWRP with Android 10 on Mi 9T

Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!

Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^

Micdu70 said:
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Click to expand...
Click to collapse
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!

Annie the Eagle said:
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Click to expand...
Click to collapse
You normally don't need to flash VBMeta file.
- Official TWRP => https://dl.twrp.me/davinci/
- Latest OrangeFox (actually "R10.1_1" because "R10.1_2" is a broken version) => https://files.orangefox.tech/OrangeFox-Stable/davinci/
EDIT: Flash "R10.1_1" version over bad "R10.1_2" version if you already downloaded/flashed via my previous MEGA link.

Annie the Eagle said:
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Click to expand...
Click to collapse
Sorry but this is not teally true - or maybe it's the case for custom roms and/or custom twrps
Using (not alone, you can find several peopke reporting the same):
-QFJEUXM 11m0.4.0 (Global, Stable,v Android 10)
-Official TWRP 3.3.1-0-davinci
Just flash that twrp through fastboot, do not wipe or fornat anything (vbmeta, internal storage, whatever), you will not loose anything and everything will work
And the same holds if twrp is replaced by orangefox (since recently, using R10.1_2)
Eg, when booting to twrp, you will enter your pin/password you use in system for unlocking the screen - and twrp will recognize and work with your encrypted Internal memory (so again, without formatting data, wiping vbmeta or whatever)
However, if you want to use some custom roms whose installation requires to format or wipe something, and/ot to use some custom twrps, that's another story (but not a problem in miui or in the official twrp)

RUI 2.0 | F.14 | A11 | Easy Update from C.38 A10 | Magisk Root | Safetynet Fix | Global or India Variant |

~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.38 to F.14 (Android 10 to Android 11) [with Magisk root]
Update your Realme X2 Pro with C.38 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure​
Boot to recovery (power off device and then hold vol- and power together)​
Must check if this version is installed OrangeFox-R11.0_2-Beta-RMX1931
Download: OrangeFox @4j17h​
Install RUI 2.0 (F.11) with OrangeFox - Dont format anything
Download: RUI 2.0 (F.11) India​
Download: RUI 2.0 (F.11) Global/EU
------------------------------------------​
Download: RUI 2.0 (F.14) Zip (Region -Unknown)​
Download: RUI 2.0 (F.14) Global/EU​
Do not restart to System now if you need custom recovery.​
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h​
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Code:
fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img
Download: Patched vbmeta​
If needed Stock Recovery -
Rich (BB code):
fastboot flash recovery stock_recovery_RUI2_A11.img
MUST Wipe DATA after 4 digit code in stock recovery
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required) ​
Reboot to System (May take 5-7 minutes to complete booting)​
Enjoy RUI 2.0 updated with all your apps and data intact. ​
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your "usrdata" partition or the standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.

After read all bugs i am happy with android 10

anang1979 said:
After read all bugs i am happy with android 10
Click to expand...
Click to collapse
Hell yeah, I'll happily stay on RUI 1 with that issues list lol

I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.

Sir Thanks Soo Much But For ur Keen And Kind Information Bootloader Is Currently Not Unlocking Due To Some Network Error If U Really A Developer Fix That ...... Everyone Will Appreciate U For That Believe Me..

hack-os said:
I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.
Click to expand...
Click to collapse
Same here, the only thing stopping me from updating now is that there is no root. Don't care about DRM.

Root I use for adaway and AccA. I have found temporary alternatives for them. Instead of adaway now I use adguard and enabled optimised night charging feature of Android 11 instead of AccA.
This open beta F.10 could be the preview of final stable release as informed by Realme
"The latest Open Beta version will be chosen as the stable version and rolled out to all users,there is no difference if you have already joined the Open Beta program." Source: Realme Support Forums.

hack-os said:
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.37 to F.10 (Android 10 to Android 11) [will lose Magisk root]
Update your Realme X2 Pro with C.37 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure​
Boot to recovery (power off device and then hold vol- and power together)​
Must check if latest OrangeFox is installed [email protected]_1.zip
Download: OrangeFox Thanks @Jerry08, @4j17h​
Install RUI 2.0 Beta (F.10) with OrangeFox - Dont format anything
Download: RUI 2.0 Beta (F.10)​
Do not restart to System now if you need custom recovery.​
Skip this step if you dont want custom recovery
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h​
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Download: Patched vbmeta​
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required) ​
Reboot to System (May take 5-7 minutes to complete booting)​
Enjoy RUI 2.0 updated with all your apps and data intact. ​
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
There are couple of issues with the current RUI 2.0 Beta.
No ROOT - installing Magisk is difficult and root doesn't work
Cant safely lock bootloader
Widewine DRM L3 due to bootloader unlock
Battery,Camera, Audio performance poor
General usage and Games performance will be average.
Need to report any bugs identified in open beta phase.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.
Click to expand...
Click to collapse
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage

ImperoDroider said:
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage
Click to expand...
Click to collapse
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out

Hello, I am not a beta tester or part of open beta. Yesterday I just checked software update and there is no update. I just opened Realme Trail and I can see there is an optional update to RUI 2 and I said yes.
Today I got the update for RUI2 and I am from India.

ImperoDroider said:
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out
Click to expand...
Click to collapse
Skipping custom recovery to have stock needs unpatched vbmeta. That why your boot got corrupted. Glad you fixed the issue with fastboot. The guide is mainly made to upgrade only with custom recovery and not using PC for fastboot.
You could still replace your recovery to stock recovery img in fastboot and flash RUI 2.0 A11 stock vbmeta
fastboot flash recovery stock_recovery_RUI2_A11.img
Could give it a try. Even i haven't tried this but that should work.

But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.

Does this work on locked bootloader and stock recovery?

Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
you can update directly by flashing the zip given with your custom recovery.
This guide is only for unlocked bootloader and phones with orange fox as custom recovery with zip file.

satish.yarramsetti said:
But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.
Click to expand...
Click to collapse
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.

hack-os said:
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.
Click to expand...
Click to collapse
Yes, it is strange. I did not do it manually from xda to follow instructions. I have received the update from Realme itself and the phone became unusable after the update until I format the device.

Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.

satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
You may be getting it officially in India, but European and UK users have never had the option to take part in any of the beta programs.
My big worry is that when Realme eventually decide to include Europe in the rollout of the update then there is massive potential for all of the various online banking apps etc that are specific to each European country might not work, meaning that we'll have to stay on Android 10.

satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
Same update is done here without wait or approval

Mod machine translation:
good evening anyone please try to install the rui 2.0 firmware on the European version with locked bootloader and stock recovery? Thanks for your answers
*****************************
bonsoir quelqu'un s'il vous plaît essayez d'installer le firmware rui 2.0 sur la version européenne avec bootloader verrouillé et récupération de stock? Merci pour vos réponses