Database Users

[Guide] Safely unlock bootloader on official MM

UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now

Reverse

Reverse #2

Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app

NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.

Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa

R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery

can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock

HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers

hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english

tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134

Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse

that version...i can´t find it anywere..maybe someone here knows were to find it?

Updated the first MM beta link in OP

hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?

tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551

hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!

tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL

Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .

hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader

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 ??.

Install Magisk without permanent TWRP - is it possible?

I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402

cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?

mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom

indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse

Custom ROM installation

Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you

And yes, I did use the commands to flash to the one slot only and on the both slots too

microcube123 said:
Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you
Click to expand...
Click to collapse
Post your question on the unofficial dirty unicorn ROM thread. They should have the answer to your question.

Homeboy76 said:
Post your question on the unofficial dirty unicorn ROM thread. They should have the answer to your question.
Click to expand...
Click to collapse
This also applies to other ROMs

microcube123 said:
This also applies to other ROMs
Click to expand...
Click to collapse
With all the different types of devices and that use unofficial dirty unicorns ROM, how would one provide a solution without specific information:
- Device model
- Android Version
- ROM
- ROM Version
- etc.
On the other hand, if the information was posted on the thread of the ROM you are trying to install. A solution may have already been posted.
Did you search that thread?

Homeboy76 said:
With all the different types of devices and that use unofficial dirty unicorns ROM, how would one provide a solution without specific information:
- Device model
- Android Version
- ROM
- ROM Version
- etc.
On the other hand, if the information was posted on the thread of the ROM you are trying to install. A solution may have already been posted.
Did you search that thread?
Click to expand...
Click to collapse
Yes, I know and I have searched for it. No one seems to have this problem. Will the problem be fixed if I flash the whole stock factory image? Most people have this problem when magisk patching the factory/stock boot.img.

microcube123 said:
Yes, I know and I have searched for it. No one seems to have this problem. Will the problem be fixed if I flash the whole stock factory image? Most people have this problem when magisk patching the factory/stock boot.img.
Click to expand...
Click to collapse
Now, I understand your problem: I think.
In your original post you couldn't flash the boot.img not the magisk_patched.img.
microcube123 said:
Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you
Click to expand...
Click to collapse
Try this:
- Flash the Stock boot.img to both slots:
(fastboot flash boot boot.img --slot all)
- Delete all magisk_patched.img
- Open Magisk (Beta or Canary) Manager
- Depending on the version of Magisk Manager installed: Set the Update Channel to Beta or Canary.
- Close Magisk Manager, reboot
- Open Magisk Manager
- Tap install (Next to Magisk)
- Tap Select and patch a file
- Navigate to the Stock boot.img that you extracted from the current Factory image (October 2020)
- Select it
- tap the ✓ (Check mark)
- Tap Lets Go
- Wait for Magisk to finish patching it.
- Reboot
- Move the magisk_patched.img from the download folder on your phone to the Platform-tools folder on your Computer
- Flash it
(fastboot flash boot magisk_patched.img)

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