Database Users

[WIP] Multiboot Project For Oneplus 3

Multiboot project is a work done by @chenxiaolong , I do not own any of the work presented over here.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Project
* before installing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
About Multiboot : A project to handle different ROMS at the same time so that you actually can use different ROMS without having to wipe up device to flash ROMS, it allows installation of more thn one ROM with all the features enabled.
USAGE​1. Decrypt your phone by following THIS guide, else you won't be able to use Multiroms.
2. Boot into your primary ROM and install the Dual Boot Patcher app
3. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
4. Go to "Patch ZIP file" in the navigation drawer and patch the ROM or zip you want to install. If you can't select the ZIP file without opening it (OxygenOS's file explorer does that as example) use Solid Explorer, ES File Explorer seems to crash the App for some reason.
5. If you want to dual-boot with OxygenOS you'll most likely have too less space in /system. Instead use the Data-Slot and give a name for it when asked.
6. (Optional) Before flashing GApps refer to the section "In-app flashing" below and come back once you've done that.
7. (Optional) Download GApps from HERE, select ARM64 and the version you want, download it onto your phone, choose "Patch ZIP file" once again and select the Data-Slot which it created for you already.
8. (Optional) To flash GApps simply refer to the section "In-app flashing" again.
In-app flashing​
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
DOWNLOAD: https://snapshots.noobdev.io/
Download the "Android" file and the "Utilities" file
ORIGINAL THREAD: http://forum.xda-developers.com/showthread.php?t=2447534
CURRENT ISSUES​
#since this is a work in progress please do consider having a look here
1. If you update ramdisk and reboot then the phone will reboot to recovery and not boot to rom. You will have to reflash your rom for it to boot.
2. Lots of other issues.
3. When setting a lock-code in your second ROM and boot back to your main ROM you'll probably be greeted with "Wrong PIN/Pattern". To fix this either delete the following files in TWRP or via ADB:
In /data/system: password.keym pattern.key, locksettings.db, locksettings.db-shm, locksettings.db-wal
After this step you can go back into your main ROM and set a lock-code again, now it should work.
DONATION (this donation directly goes @chenxiaolong ,I do not take any of it) : http://forum.xda-developers.com/donatetome.php?u=4277844 #if not sure about the link kindly visit:
http://forum.xda-developers.com/member.php?u=4277844
CREDITS​
All credits goes to @chenxiaolongfor his hard work on this project,
kindly say thanks to him
Thanks to @hunter_bruhh too. He did the pull request on github.
I am currently in need of testers so if anyone is interested, please pm me on tapatalk chat, xda pm or telegram to https://telegram.me/RKRohk
XDA:DevDB Information
Multiboot Project For Oneplus 3, Tool/Utility for the OnePlus 3
Contributors
rkrohan, hunter_bruhh, epiclper, @chenxiaolong
Version Information
Status: Alpha
Created 2016-07-03
Last Updated 2016-07-07

Seems like no rom is working with this. I have informed @chenxiaolong but till then, I need logs from anyone who is trying this on any custom rom. You can find logs in the multiboot folder in your internal storage. Thank you.

If you remove encryption then this should work. Try using the data slot to install a custom ROM while you are on a custom ROM and please let me know if it worked. For those getting ramdisk issues, ?*just flash /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP.

Reserved
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
---------- Post added at 10:42 AM ---------- Previous post was at 10:42 AM ----------
Waiting for it to boot properly..
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

http://forum.xda-developers.com/oneplus-3/development/patcher-dual-boot-rom-oneplus-3-t3409591
what's the difference？

dlhxr said:
http://forum.xda-developers.com/oneplus-3/development/patcher-dual-boot-rom-oneplus-3-t3409591
what's the difference？
Click to expand...
Click to collapse
@hunter_bruhh and I worked on this not the guy who made the other thread

Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.

youlun.zhai12 said:
Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.
Click to expand...
Click to collapse
no...same with Paranoid ROM...

youlun.zhai12 said:
Anyone get dual boot successfully? I tried install Cm13 as secondary in data slot, but end up with vibrations and boot into recovery.
Click to expand...
Click to collapse
I tried almost every rom but it dosen't work. I need logs from a guy who is not on stock rom. I have informed @chenxiaolong about this. Hope it gets fixed soon

How do I decrypt the OnePlus 3 tho? The Security>Encryption option does exactly nothing when I touch it...

Thanks…
I install second rom ResurrectionRemix-M-v5.7.0-20160703-oneplus3
But how I can switch to boot secondary rom??

EpicLPer said:
How do I decrypt the OnePlus 3 tho? The Security>Encryption option does exactly nothing when I touch it...
Click to expand...
Click to collapse
In bootloader mode > "fastboot format userdata" > done. But all your data will be lost. So make a backup on your pc first...

Want to decrypt your device in order for this to work?
Here's how you can do that!
http://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228/

Managed to recover from a "disaster" after trying to upgrade my main, primary ROM (OxygenOS)...
So, I downloaded OxygenOS 3.2.1 and SuperSU and patched it via Dualboot Patcher, so far so good.
Then I booted into my secondary ROM (Resurrection Remix) since flashing on the currently running ROM is not allowed.
Started the Flash on the second ROM, however I accidentally hit the recent apps key, once I switched back to Dualboot Patcher it crashed...
I panicked a little, I booted into TWRP and flashed both files from there (first OOS, then SuperSU to prevent it from encrypting again).
After that I rebooted, however immediately after rebooting the OnePlus logo came on, went black and rebooted into the OnePlus logo again. Well, nothing much wrong so far, that's usual SuperSU behavior.
After the second reboot my phone was stuck in a bootloop and got extremely hot, I left it sit there thinking it'd encrypt again due to me doing something wrong (this happens when you forget to flash SuperSU after OOS)
After almost 40 minutes, still nothing. So I went to my PC and took a look what logcat says: Java Fatal Exception, something battery related wasn't able to load up.
So I force-shutdown the device and booted back up, not even 20 seconds later it booted into Android like nothing before happened...
Lesson of this story: NEVER flash your primary ROM from the secondary one... ALWAYS patch the ZIP files first, then boot into TWRP, then flash them.

I installed a dual system rom for mistake and obviously cannot use it, I also installed a data dual rom which is working fine, my issue is that when I try to remove the dual system rom I cannot do it, even if I move to raw/system/multiboot and try to delete I can't, I tried to change the permission, to set raw folder as a writable folder but none of this tries work..any help?

I have been using multirom on nexus. I saw multirom is also there for OP3. currently on OP3 I have flashed multirom(that similar to Nexus) , then i came across this THREAD.
Just a noob question - how different it is from multirom?
No disrespect to the developer intended.

Tried with RR and AOSPA, didnt work, i think its not flashing the second ROM properly..?

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

[Recovery][MI 8 SE] TWRP Recovery Installer

Hi guys,
Easy way to flash TWRP from computer for Mi 8 SE.
Download suitable file from below.
Twrp 3.2.3-1227 Compatible with Android 9 (Beta v8.12.27 and upper versions)
https://www.mediafire.com/file/qtdm3qlivcn4gmw/MI8_SE_TWRP_Yukleme_Araci_81227.zip/file
Twrp 3.2.3-1102 Compatible with Android 8.1 (Lower versions than Beta v8.12.27)
https://www.mediafire.com/file/bsvuaxcg1vghayz/MI8SE_TWRP_Yukleme_Araci.zip/file
1. Your phone bootloader should be unlocked.
2. Make sure USB drivers are installed to PC.
3. Turn on USB Debugging. Settings - More - Developer Options - Usb debugging
4. Press Volume down + power button and reboot to fastboot mode.
5. Connect your USB cable to PC
6. Unzip downloaded package and run twrp-yukleme.bat file.
7. Press enter to continue. When it's done enter to exit program.
8-For steady TWRP install Magisk16.4 when you boot into TWRP.
Thanks to by.Trabzonlu from miuiturkiye

downloaded multiple times
unpacking gives a bug
I tried both links

olinen said:
downloaded multiple times
unpacking gives a bug
I tried both links
Click to expand...
Click to collapse
Thanks for your report.
Links and zips are updated. It should unzip fine now :good:

it's ok, just that I had to run the program first and only after that I joined the mobile in the fastboot. Otherwise, he made a mistake
Thx :good:

9
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me

Alimataei said:
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me
Click to expand...
Click to collapse
TWRP 3.2.3 12-17 works for android 9 ?

TacoNikky said:
TWRP 3.2.3 12-17 works for android 9 ?
Click to expand...
Click to collapse
1102 also works for Pie.

I try to install this recovery but nothing happens at all I have installed the rom miui.eu 10.2.2.0 apparently this rom mr deleted the recovery that had already installed before installing this rom:crying:

Have someone trying treble gsi rom? How to proper install? Thanks in advance.

TWRP-3.3.0-0423 whit magisk 19.0 root For Xiaomi mi8 SE
Download Link:
https://mega.nz/#!CrhTmKgY!PE7lXdLtCzPqYO55ulCx2faFLVqPi6mpXXaYOnbbB8s

Could it be possible that this TWRP will work on mi 9 se, too?
Sent from my [device_name] using XDA-Developers Legacy app

putti71 said:
Could it be possible that this TWRP will work on mi 9 se, too?
Click to expand...
Click to collapse
This is mi8se forum!! TWRP is specific for each phone (different kernel, processor...) so there's no way you could install this TWRP img on another phone than Sirius

Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?

Hi! Is there an updated twrp for miui 11 android 10. First time to install this.

greendra8 said:
Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?
Click to expand...
Click to collapse
Same as mine. How's your device now?
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Hi guys. Im getting the error after flashing twrp. At first it works. I will flash rom so i reset it and wipe al data. But it didn't boot into recovery mode. It stays at fastboot. I just dl this installer from somewhere here in xda so i didint know thatmagisk should be flashed afterward. Pls help. I . getting error authentication failed

Trojan00 said:
Same as mine. How's your device now?
Click to expand...
Click to collapse
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.

greendra8 said:
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.
Click to expand...
Click to collapse
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?

Trojan00 said:
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?
Click to expand...
Click to collapse
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.

greendra8 said:
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.
Click to expand...
Click to collapse
Bro i downloaded the stock fastboot firmware. But in mi flash it says can not found file flash_all.bat

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)

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