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

VertexOS 1.9 [UNOFFICIAL][2017/2/11] [KIPPER] [AOSP+LOS]

HI ALL! With new Rom
VertexOS aims to provide a simple but enhanced near-stock AOSP experience with carefully selected features and an emphasis on stability and smoothness.​
what doesn't work ?
everything is working perfectly.
Coming from another ROM, OR if a CLEAN FLASH is required
1) Download the Vertex... .zip file.
2) Download a 7.1 GApps package.
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash the Vertex... .zip file
6) Flash Nougat-compatible GApps : http://opengapps.org/ / ARM64,7.1,pico
7) Reboot
Download:https://www.androidfilehost.com/?fid=745425885120707303
enjoy!
Credits:
- LineageOS
- AOSPA
- Citrus-CAF
- DU
- PureNexus
- Zephyr-OS
IF YOU LIKE MY WORK PLEASE HIT THANKS .
-IMPORTANT- : To install this rom you must have installed TWRP-3.0.3.0 , download from here https://www.androidfilehost.com/?fid=529152257862697990
To easy install from TWRP recovery :
1- open "install" section.
2- SELECT "install img" in the bottom .
4- Chose the place of TWRP-3.0.3.0.
5- install as RECOVERY , then reboot to recovery.
XDA:DevDB Information
ROM [AOSP + LOS], ROM for the Wileyfox Storm
Contributors
PS-DEV
Source Code: https://github.com/VertexOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP + LOS
Version Information
Status: Stable
Created 2017-02-11
Last Updated 2017-02-20

Received

Received !

Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.

Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.

Cannot inatall gapps (Wrong Architecture)
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck

Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.

I installed fine with the nano apps and 64 bit, no issues

miSAKe said:
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Click to expand...
Click to collapse
Check the first post . i have been edit.

Chron0s said:
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Click to expand...
Click to collapse
show your PM.

Chron0s said:
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
Click to expand...
Click to collapse
NO NO
ARM64 ARMv8 .

ChuckeCheese said:
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Click to expand...
Click to collapse
1- check to wipe this partitions :
- SYSTEM
- CACHE
- Dalvick-cache.
- DATA
and dont forget to factory reset .
2- first install rom then Gapps. download from here http://bit.ly/2kQf3Le

PS-DEV said:
Check the first post . i have been edit.
Click to expand...
Click to collapse
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.

miSAKe said:
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
Click to expand...
Click to collapse
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?

PS-DEV said:
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
Click to expand...
Click to collapse
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.

miSAKe said:
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
Click to expand...
Click to collapse
The phone boot to rom or not ??

PS-DEV said:
The phone boot to rom or not ??
Click to expand...
Click to collapse
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.

miSAKe said:
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
Click to expand...
Click to collapse
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .

PS-DEV said:
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
Click to expand...
Click to collapse
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.

miSAKe said:
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
Click to expand...
Click to collapse
Stock firmware or what? ,, to install version 13 Bootloader , just install any nightly cm13 then back to recovery and install TWRP 3.0.3.0 ??.

A Guide To Install Android 10 (With Fixes) on Redmi 7a

Hello,
I know that ROM developement on redmi 7a has been extreemly slow, but we all know that redmi 7a is a treble enabled device and therefore we can install every android GSI as long as it is ARM32-BINDER64-AB, yes and i wouldn't explain it here you can read it over here here.
So i thought that i should give you guys a little guide on how to install GSIs and custom ROMs and yeah with volte fix too
NOTE - I AM NOT RESPNSIBLE IF YOUR DEVICE GETS BRICKED OR THERMONUCLEAR WAR TAKES PLACE, YOUR WARRANTY IS VOID FROM THIS STEP ON, I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED MAKE SURE YOU HAVE MOVED YOUR DOWNLOADED ROMS AND GAPPS TO A PC OR A SD CARD I AM NOT RESPONSIBLE FOR ANYTHING
1] The very important first step is to unlock your bootloader.
2]The second step is to patch your boot image (if you want to root it with magisk)
3] Install the custom recovery of your choice
Download the TWRP file from here
you also can install TWRP forks like
PICTHBLACK RECOVERY PROJECT or PBRP from here
SHRP RECOVERY from here (i wouldn't recommend this one if you are flashing this for the first time)
If you have your device drivers installed but you dont have adb installed then please download this file and extract it to a suitable folder where your downloaded recovery is extracted and run cmd-here and follow these steps given below
Code:
fastboot devices
this will show you if your device is connected or not.
Code:
fastboot flash recovery (your recovery name.img)
Code:
fastboot reboot
you have to keep pressing you volume increase button to reboot to recovery
4] You have to wipe DATA first then, reboot to recovery and go to mount select system (if it's unchecked)
5] Go to WIPE -> ADVANCED WIPE -> Select SYSTEM - DALVIK CACHE - CACHE - INTERNAL STORAGE
6] The list for the available GSIs or ROMs is ----
1) LineageOS thanks to ExpressLuke (GSI) (You might have to downgrade your miui to be able to boot)
2) HavocOS thanks to Skulshady (GSI) (Boots just fine with any version of miui volte patch is needed)
3) Mokee thanks to GuaiYiHu (ROM) (No worries about anything)
4) AOSP Special thanks to Phhusson (GSI) (Boots just fine without any hiccups volte patch is needed)
5) CAOS by Erenmitein (GSI) (Not tested)
6) CrDroid By Erenmitein (GSI) (tested needs the bolte fix patch. please follow the steps given below)
7] Move your GSI img (extract the .xz file) the extension is going to be .img and will not visible in TWRP or it's forks unless you select the INSTALL IMAGE option in the FLASH section and GAPPs
8] Flash your GSI as a System Image
9] Reboot to recovery again and flash your GAPPS ignore if it says no OS installed when rebooting to recovery
10] The fix for VOLTE is here thanks to Khushraj Rathod
you just have to flash it from TWRP or its forks
11] The first reboot will take some time and voila your GSI has been installed (flashed).
12] For Mokee, personaly i love Mokee rom with its boot animation, you can just flash your zip through twrp with gapps.

Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?

kra_ppo said:
Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?
Click to expand...
Click to collapse
No.

A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.

Havoc (an Mokee - but I dont like it) was finally successfull, but only by formating Data and not to wipe internal Storage....

kra_ppo said:
A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.
Click to expand...
Click to collapse
Flash vbmeta

Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work

how to get back to stock ROM ?

idcamper said:
Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work
Click to expand...
Click to collapse
You flashed floor miui 10.0.2.5.?

can't i do this with twrp? Tutorial ?

Flammenschwert1337 said:
Flash vbmeta
Click to expand...
Click to collapse
Did you find solution?

lslayer4231 said:
Did you find solution?
Click to expand...
Click to collapse
Start with miui 10.0.2.5.
Then go on.

My phone bootloops to redmi logo and recovery after flashing, any help from this?

After installing latest havoc 3.7 gsi the call recording feature not working though normal sound recording works... Any fix?

Hey, guys!
Havoc OS GSI is selinux permissive or enforced?
Is it possible to go back to stock rom by doing a backup using twrp?
I'm sorry if I'm being dumb, but as you already noticed, I'm newbie.

MEMO#22 said:
My phone bootloops to redmi logo and recovery after flashing, any help from this?
Click to expand...
Click to collapse
Switch back to miui 10 global version and install twrp

Has anyone else got media playout over bluetooth OK and if so, which GSI or ROM and which base firmware, please? It does not work for me with AOSP on latest EU firmware. Only calls go to BT.

recovery the bricked phone, but how can I upgrade to android 9?

just use MsmDownloadTool V4.0.exe to recovery my op5 to oos, but the version is quite low as Android 7.1.1.
checked the system update, it told me up to date. which is of course not true.
tried to clean the cache of google framework service and oneplus framework service, still nothing in updating.
tried installed oxygen updater, and download 3 update zip from 7.1.4, 8, last version of 8, but each time I use local install in system uploading, then reboot to recovery, it shows me "failed". none of version works.
I even tried to install in recovery, wipe cache and data or just wipe data, then install from internal disk, none of the file works, even don't have any popup fail notice, just go back to file chooser interface.
I can still go back to system by switch off and on again.
How can I upgrade the old version of android in my oneplus 5?
original:
used use lineages os with Twrp, and I would like to flash to original oxygen.
download full rom zip in https://www.oneplus.com/uk/support/softwareupgrade/details?code=PM1574156143164
copied to phone disk
went to twrp
wipe Dalvik, System, Data, and Cache
then tried to install the full rom zip, but met "no Digest File found" error
found it must be twrp old, so I download new one in https://dl.twrp.me/cheeseburger_dumpling/twrp-3.4.0-0-cheeseburger_dumpling.img.html
copy to phone and flash it to recovery.
select "reboot to recovery"
then problem coming: I can only see the oneplus logo with powered by Android. it won't go any further.
I am not sure any thing wrong during my processing, but maybe 2 things:
1, I wiped the system
2, I didn't clean the screen lock pin before I flash
so, my question here is, if possible I can flash the original oxygen os in this situation?
if positive, could you please give me a step by step instruction?
by the way, the zip rom I download from oneplus site isn't have the "flash-all" script.
please please help me .

First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support

Pierre02 said:
First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support
Click to expand...
Click to collapse
thanks! it works! i'm at 5.1.2 then i install OxygenOS 5.14 (OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip) then after that I install OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988b.zip and then the last and the latest OnePlus5Oxygen_23_OTA_068_all_2006012224_c7a6016.zip android 10.

Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...

uno0 said:
Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...
Click to expand...
Click to collapse
Use an EDL Flasher (unbrick tool) here on XDA

Pierre02 said:
First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support
Click to expand...
Click to collapse
thanks for replying
I had figure out my problem.
it seems the rom I flashed using MsmDownloadTool had something wrong,
I've changed another one, it shows me the update from the first start after flashing.

uno0 said:
Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...
Click to expand...
Click to collapse
if you are directly flash to coloros android 9 from lower version other than android 8, it might be the problem you won't got the update in the system. It might be have issue in wifi or gps as well, which I bet you didn't well test yet.
that's all about the system partitions messed up. regarding my understanding.
solution is simple, but time consuming:
you have to flash an original rom using msmdownloadtool, make sure that rom will have update notification in the system menu of settings. then upgrade from there one level up each time, till to the android 10. (chinese version do have 10 available)
than, you can download oxygen os android 10 to flash on the coloros android 10 (hydrogen os android 10) you just done the upgrade, don't forget wipe data/cache before flashing.
hope that's helps.

netzkie said:
thanks! it works! i'm at 5.1.2 then i install OxygenOS 5.14 (OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip) then after that I install OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988b.zip and then the last and the latest OnePlus5Oxygen_23_OTA_068_all_2006012224_c7a6016.zip android 10.
Click to expand...
Click to collapse
Kindly tell me in steps you follow m stuck in 4.5.8 version with download links

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery

reserved

Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA

Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader

bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work

ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you

What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?

kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.

It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""

Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.

Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance

4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?

Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.

kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too

How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?

Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?

Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks

Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks

tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me

So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again