[SOLVED] How to Install RMX1931EX_11_F.11 realme ui 2.0 with ORANGEFOX - Realme X2 Pro Questions & Answers

So i just Got the REALME UI 2.0 update via System Updater and i downloaded is IMMEDIATELY.
But when i tried to install it via ORANGEFOX RECOVERY. It gave me error saying "this Package is for RMX1931L1" and couldnt install on this device.
Can please someone explain what it means, and how can i install this package.
EDIT. 1 : First i installed unofficial TWRP
than i installed C.38 ozip to get Stock recovery than i Relocked Bootloader (which wiped everything internal memory and everything) than i rebooted and checked for update. Got the A11 update downloaded it and Flashed it.
And now i am on A11 stock Locked bootloader and Working Fine.
BTW i live in INDIA

I think you're going to hard brick your device if you've got the bl unlocked and try to flash the official update through OrangeFox. My suggestion is to move the ota file to your pc, relock the bootloader if you're on rui1.0, then move the file and flash it clean, with the bl locked.

How did you even get the update, where do you live?

Related

[Q] how to update after rooting (magisk) ?

Hello
I was on B180 (PRA-LX1C432) rooted with magisk
No updates available in settings/update firmware, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
Thanks !
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota, maybe I can use fastboot to flash only system and boot, and the reflash magisk to patch new boot img ?
anyone ?
Nobody updated after root ??
Ok, this is what I did and happened:
- In TWRP, flash magisk uninstaller script: ERROR 1. After reboot magisk was still here. That was a bad start...
- So I opened magisk app, click Uninstall and then Complete Uninstall. After that I made a reboot as asked, and device rebooted twice.
- Then, went to download mode and flashed stock recovery. And reboot.
- Then went to settings/updates/download latest full ota. It downloaded but refused to start the install process claiming to free up more than 900MB... Nothing on my internal sdcard so I had to uninstall some apps... cool !
- Then it reboot and installed the update
- First boot took a while, I still have "this device cannot be trusted" on start, and OEM unlock in settings is grayed and ON, so I think the bootloader is still unlocked
- Theme and wallpapers were reset with the update
For now I don't have flashed back twrp neither magisk .
In the meantime have you flashed TRWP and Migistik ? And again: do you have still to update your signature or something went wrong in installing fw B194.
Lastly: what do you mean by "went to download mode and flashed"...

Please i need fix this

After unlocking the bootloader, I installed AEX 9, then I decided to flash the stock rom 8.1 and it worked ... But there is a problem, I have the bootloader unlocked and I receive OTA updates ... but now I want to install TWRP and it doesn't work, it says "recovery.img is not signed", I tried to flash another stock of rom and the same problem, I can't ... it says "boot.img is not signed"
How I fix this? I just want flash TWRP for Magisk... any solution?
PD: My English is not good for all... sorry
Use the correct version of twrp and disregard image not signed message

[GUIDE] OTA on TWRP

i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom
title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?

How to get back to the stock recovery and stock RealmeUi

Hi all,
After few weeks in LOS 17.1, I want to get back to the stock recovery and realmeUI.
I have a Realme X2 Pro Global version (Europe) and I tried already to reinstall stock rom, but didn't works. TWRP failed to decrypt .ozip file (manuforio's verison). I re-downloaded the .ozip file in realmeui official site but same error.
I tried also to use TWRP older version with the python script to decrypt ozip before use in twrp, but twrp can't install this file.
Also, I tried to use different procedures to get back stock rom, but didn't work.
However, where can I find the official and last version of the stock recovery img ? I didn't find this file in the ozip archive (I have no backup of this file).
What is the way to get back to stock phone ? Is it possible at this time ?
Thanks you in advance.
I think best way would be to use realme's flashtool to flash latest stock fw
Catskan06 said:
Hi all,
After few weeks in LOS 17.1, I want to get back to the stock recovery and realmeUI.
I have a Realme X2 Pro Global version (Europe) and I tried already to reinstall stock rom, but didn't works. TWRP failed to decrypt .ozip file (manuforio's verison). I re-downloaded the .ozip file in realmeui official site but same error.
I tried also to use TWRP older version with the python script to decrypt ozip before use in twrp, but twrp can't install this file.
Also, I tried to use different procedures to get back stock rom, but didn't work.
However, where can I find the official and last version of the stock recovery img ? I didn't find this file in the ozip archive (I have no backup of this file).
What is the way to get back to stock phone ? Is it possible at this time ?
Thanks you in advance.
Click to expand...
Click to collapse
So, I got back to the stock realmeUI. Yeah !
But, now, I'm unable to find the stock recovery C.31 to reinstall it.
I finded an older recovery.img (Color OS) but it's not the last realmeUi recovery img.
EDit : After OTA update, recovery was updated.
Thanks you.
Catskan
Catskan06 said:
So, I got back to the stock realmeUI. Yeah !
But, now, I'm unable to find the stock recovery C.31 to reinstall it.
I finded an older recovery.img (Color OS) but it's not the last realmeUi recovery img.
EDit : After OTA update, recovery was updated.
Thanks you.
Catskan
Click to expand...
Click to collapse
i also have this problem lease help me...

Locking the Bootloader

Hello everyone,
as many of you, I also want to lock my bootloader after finding that my X2 Pro bought used few days ago was unlocked and with TWRP installed.
It was stuck to Color OS 6 with security patch updated at february and it had installed Magisk.
I tried to flash Realme UI but I couldn't because it had installed official TWRP and not the right one.
I formatted everything and after some hours of research and trials I managed to install Realme UI with security patches updated (october).
Now, I don't have TWRP but official recovery instead. No signs of Magisk and any other data because I formatted everything few time during my flashing trials.
I don't have fingerprint and face recognition, I think due to the fact the bootloader is unlock, yet.
To overcome this, I found a video-guide used for X2 (not Pro) in which I saw that after flashing the Realme UI, rebooting recovery and formatting data, those sensors worked again but with X2 Pro this procedure won't work.
To recap: I have official firmware and recovery, no fingerprint and face recognition. I think that I can use the official guide for locking the bootloader again as the app says that I can roll-out from the in-depth program.
Was someone in my situation? I mean, locking the bootloader with FP and FU disabled before relocking?
I ask this because I found a thread in which the user said that it was necessary to make FU and FP work again before locking the bootloader.
I had this phone for less than a week and I can't take a decision.
Thank to anyone in advance.
you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/
YasuHamed said:
you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/
Click to expand...
Click to collapse
OMG tahnk you so much for your help.
I didn't receive any notification of your reply so I couldn't answer you before.
Before reading your reply I successfully locked the bootloader with REALME UI on it but FP and FU doesn't work.
I thought that it may be caused by the fact that bootloader was unlocked with Colors OS 6.1 (Android 9) and then I relocked it with Realme UI 1.0 (Android 10).
For this operation I used the official tool usable only with Android 10.
Do you think I should unlock the bootloader again, downgrade to Color OS 6.1, lock the bootloader and only then update my device to Realme UI?
If so, how can I downgrade the Android version? With their flashing tool it can't be done.
Hope you well and thank you in advance for your help.
Dude try this,
Download Realme flash tools here from my Google Drive:
realme_Flash_Tool_V2.zip
drive.google.com
Now download OFP file to use with the flash tool here:
OFP files
https://www.droidwin.com/flash-ofp-realme-flash-tool/
docs.google.com
Boot into bootloader and flash it. See if it helps.

Categories

Resources