Develop Bugs

Development [ROM][Android 11][OP9Pro] crDroid v7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4

Awesome.

I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?

burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS

gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader

Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?

CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!

I'll flash and report tomorrow .
post logs through here or telegram?

ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff

I know it may not be recommended, but has anyone been able to flash this without using a computer?

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible

TWRP is death.

This is awesome news brother

So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?

crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy

gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?

djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after

gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.

truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job

Development [RECOVERY] [UNOFFICIAL] TWRP-3.5.1 [20210702]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.​
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)​
Supports Hentai OS encrypted devices​
Supports flashing MIUI zips​
Supports Vibration​
Supports wiping data without wrecking encryption. ​
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates

Reserved

Reserved

ayy pro <3

Yay Yahoo

Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."

I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...

vasishath said:
Great work.
Click to expand...
Click to collapse

blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.

@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app

vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.

deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?

Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse

vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..

NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?

Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.

[OP7T][Stock/Magisk] OxygenOS 11.0.4.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.4.1.HD65AA Global boot.img
Stock: https://mega.nz/file/KZ1GTAyR#1f4E0ywSWwcOP50Z6DYoK_fZoCrgXUj147jqyzTRclc
Magisk v23.0 Patched: https://mega.nz/file/eBkWHIZJ#qB-lYuYBxGqk8yPL1o1s5gb0SJrSRT0_9O0gPT0IZcY

Hi! Thanks for this. Can i help with testing the EU version?

I would be interested in this also please.

Hello what are the steps please.
since the last magisk update the application is no longer installed.
what files i need to reinstall with adb.
I put the boot.img but the magisk application is no longer there

https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
Download above and install magisk app. Put boot.img into internal sdcard of phone. Run magisk app and hit "install", "select and patch" to patch the boot.img into magiskboot.img in "download folder". Move this file from phone to PC's adb folder with all the fastboot files.
Go back into bootloader mode and type "fastboot flash boot magiskboot.img" to flash rooted magiskboot.img. Then reboot to rom and enjoy rooted phone.
This method works for all roms as each has its own boot.img and not interchangeable. The listed magiskpatchedboot.img save u a step for latest stock rom.

pulpf said:
Hello what are the steps please.
since the last magisk update the application is no longer installed.
what files i need to reinstall with adb.
I put the boot.img but the magisk application is no longer there
Click to expand...
Click to collapse
Above

HueyT said:
https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
Download above and install magisk app. Put boot.img into internal sdcard of phone. Run magisk app and hit "install", "select and patch" to patch the boot.img into magiskboot.img in "download folder". Move this file from phone to PC's adb folder with all the fastboot files.
Go back into bootloader mode and type "fastboot flash boot magiskboot.img" to flash rooted magiskboot.img. Then reboot to rom and enjoy rooted phone.
This method works for all roms as each has its own boot.img and not interchangeable. The listed magiskpatchedboot.img save u a step for latest stock rom.
Click to expand...
Click to collapse
Thank you very much I had a hard time but it's good

I really can't seem to root mine. I've tried booting the patched image, flashing the patched image to boot_a and boot_b, and all of this boots successfully. The problem is that it doesn't root successfully, and the Magisk app doesn't detect that it's rooted. This has been going on for a couple Oxygen versions and several different patched images. Anyone know how to help?

Kr1msonReaper said:
I really can't seem to root mine. I've tried booting the patched image, flashing the patched image to boot_a and boot_b, and all of this boots successfully. The problem is that it doesn't root successfully, and the Magisk app doesn't detect that it's rooted. This has been going on for a couple Oxygen versions and several different patched images. Anyone know how to help?
Click to expand...
Click to collapse
Try flashing Lossyx twrp oos and then boot into twrp and "adb sideload magisk.apk"

HueyT said:
Try flashing Lossyx twrp oos and then boot into twrp and "adb sideload magisk.apk"
Click to expand...
Click to collapse
No luck. I flashed a Lossyx twrp to my recovery and sideloaded the apk. It was successful and my phone booted properly, but no root. I feel like this is only happening to me.

You installed magisk apk in rom? Does it show root there on magisk home screen?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

HueyT said:
You installed magisk apk in rom? Does it show root there on magisk home screen?
Click to expand...
Click to collapse
I've got: Installed: N/A A/B: Yes Ramdisk: Yes SAR: Yes. When I hit install, it only gives me the patch option, no direct install, so no root. And I don't pass safetynet.

Is this oos 11.0.4.1? Did flashing "fastboot flash boot magiskboot.img" not work either (rename OP's uploaded magisk-patch boot img file"?

Yeah, it's oos 11.0.4.1.HD65AA. I tried directly flashing the patched boot image in fastboot--to both boot partitions. Nothing, I don't know what's going on. I had root before updating to Android 11. I can't remember if I patched a slot before rebooting though.

Then use OP's unpatched boot.img, boot up unrooted, patch boot.img with your installed magisk apk, move magiskpatched boot.img from "download" folder of phone onto PC adb folder, reflash magiskpatched boot.img as above, retry

I downloaded the stock boot from above, flashed it to all boot partitions and restarted. Then, I patched the stock boot with magisk and flashed it and rebooted... Magisk still displays N/A. No root.

Msm back to oos 10.0.16 and update to oos 11 0.4.1 via oxygen updater app and start over, losing all data

HueyT said:
Msm back to oos 10.0.16 and update to oos 11 0.4.1 via oxygen updater app and start over, losing all data
Click to expand...
Click to collapse
I actually tried the same thing back in 10.0.16. I only updated to 11.0.4.1 just yesterday. Still think it will help?

Could just stay rooted on oos 10.0.16 or go custom with yaap11

Question Fastboot Boot TWRP wipes OS

As mentioned in the title, fastboot booting a twrp.img to enter a temp TWRP seems to completely wipe everything else on the device, including the current OS. To bypass this I'm using a method in one of the guides using a nonflagged twrp.img to format data, re-fastboot boot into recovery, unmount-remount data. This allows me access to storage again so I can flash a different ROM. If I make the TWRP permanent, booting from new ROM system into recovery also wipes the OS. I'm not sure what other details to provide but I can answer any questions. Help would be appreciated, thank you!

I have never heard of this problem, what TWRP are you using? Firmware? ROM?

Darkaeluz said:
I have never heard of this problem, what TWRP are you using? Firmware? ROM?
Click to expand...
Click to collapse
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.

FoxTailKitsune said:
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.
Click to expand...
Click to collapse
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1

Darkaeluz said:
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1
Click to expand...
Click to collapse
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Edit3: using crDroid TWRP file
1. fastboot boot twrp-crdroid.img
2. flash crDroid (auto-flash twrp toggled)
3. reboot recovery
4. flash everything
5. FORMAT VERY IMPORTANT
6. boot system
On further consideration, I made two mistakes. One was getting too fixated on the errors, the other was not formatting after flashing. The twrp file really helped to resolve these issues. Thanks for your help.

FoxTailKitsune said:
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
View attachment 5525303
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Click to expand...
Click to collapse
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?

Darkaeluz said:
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?
Click to expand...
Click to collapse
12.5.5, the latest official ROM. I have F3 global.
Edit: It seems to be more an issue with Descendant than the other ROMs. PEX and crDroid, although also having mounting errors, did not come with the same ones. /vendor is okay, but it seems to be an error when failing to mount /oem and/or /system(.extensions) -- this would make sense, obviously.
I may try HavocOS and some other ROMS at a later time.

Development [UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)

OrangeFox Recovery Project​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads OrangeFox-R12.1​
Installation (for Stable roms )
Code:
fastboot boot OrangeFox-12.1-lisa.img
After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot.
​
Installation method 2 (If you firmware based on weekly China Beta (xiaomi.eu and other)
[UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)
OrangeFox Recovery Project Downloads OrangeFox-R12.1 Installation (for Stable roms ) fastboot boot OrangeFox-12.1-lisa.img After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot. Installation method 2 (If you...
forum.xda-developers.com
NEW: OrangeFox Recovery | Build in Cloud
Version Information
Status: Beta ( Unofficial )
Current Beta ( Unofficial ) Version: R12.1
Release Date: 10-June-2022
Spoiler: for Donate:
BTC Wallet :
bc1qepm8lmd6228dhdpn9e0rjkplpq7yftdhkxywcp
​

is it gonna work with Android 12?

neoxcool said:
is it gonna work with Android 12?
Click to expand...
Click to collapse
yes, this recovery is built to work with a12+ (a11 is compatible)
(some little things need to be completed, but this will be later)

I have actually a Xiaomi 11lite 5G NE with Xiaomi.eu rom (a11: version 12.5.9, rooted with magisk 15.1) and twrp-3.6.0_11-0-lisa. I am very happy with them but I would like to try this recovery. Can I install it over TWRP using "ramdisk install"?
Must I reinstall from Platform tool?
I appreciate very much that you are working on a android 12 compatible version!

Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....

neoxcool said:
+++ Installation method 2
Click to expand...
Click to collapse

quasyl said:
Installation method 2
Click to expand...
Click to collapse

I did it with 1st method but will try 2nd later ...

Even after following method 2 commands, it still gives a slight vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all... I am on MIUI 13 by Papp54 (22.7.7 Beta) (https://forum.xda-developers.com/t/xiaomi-11-lite-5g-ne-by-papp54-r.4449665/)

neoxcool said:
Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....
Click to expand...
Click to collapse
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta

Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!

Eliliyah said:
Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!
Click to expand...
Click to collapse
You tested on MIUI 13/A12 or MIUI 12.5/A11?

If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
plz check
fastboot boot recovery.img
Click to expand...
Click to collapse
Hi, Yes. This recovery.img worked. I flashed the ofox recovery now. I'm on papp54 22.1.13 rom. Thank you

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Thanks, it works now. Please update the instructions and download links in your main post.

zgfg said:
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta
Click to expand...
Click to collapse
Dkpost3 will answer your query, mate ...​

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Works on Xiaomi.eu 22.7.13. Thanks mate!

Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!

MAT.PH said:
Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!
Click to expand...
Click to collapse
Newest PixelOS build?

[email protected] said:
Newest PixelOS build?
Click to expand...
Click to collapse
Yes
PixelOS_lisa-12.1-20220712-0056