I'm not sure what changed, but I know what I used to do doesn't work anymore.
Either boot TWRP, flash TWRP from in TWRP, then reboot and flash magisk.
then, after an update, i'd go to magisk manager, install it, and reboot.
when that would mess up, i'd get the boot.img and patch it from the manager, then put it on my computer and go through the flashing process there (assuming there was no TWRP anymore)
you need to extract boot.img, patch it, temp boot it with fastboot and patch boot from magisk while booted
gwolfu said:
you need to extract boot.img, patch it, temp boot it with fastboot and patch boot from magisk while booted
Click to expand...
Click to collapse
Cant go wrong with this. Simple and no nonsense advice
Use alpha magisk for patching boot.img
then fastboot boot patched boot
then direct install method from magisk
aNGERY said:
I'm not sure what changed, but I know what I used to do doesn't work anymore.
Either boot TWRP, flash TWRP from in TWRP, then reboot and flash magisk.
then, after an update, i'd go to magisk manager, install it, and reboot.
when that would mess up, i'd get the boot.img and patch it from the manager, then put it on my computer and go through the flashing process there (assuming there was no TWRP anymore)
Click to expand...
Click to collapse
Need boot.img, vendor_boot.img and vbmeta if you want to use stable magisk. For me it worked fine on C39
Thanks. I think my problem was that I was still using 23
i used payload dumper to extract the images (boot, vendor_boot and vbmeta). i try to patch them in manager and it just gives me an error. am i out of luck?
i hope this image counts as evidence that i'm actually trying to figure this out rather than get spoon fed
{
"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"
}
aNGERY said:
i used payload dumper to extract the images (boot, vendor_boot and vbmeta). i try to patch them in manager and it just gives me an error. am i out of luck?
i hope this image counts as evidence that i'm actually trying to figure this out rather than get spoon fed
View attachment 5486735
Click to expand...
Click to collapse
Have send you non patched files, try again. Dont patch vbmeta
aNGERY said:
i used payload dumper to extract the images (boot, vendor_boot and vbmeta). i try to patch them in manager and it just gives me an error. am i out of luck?
i hope this image counts as evidence that i'm actually trying to figure this out rather than get spoon fed
View attachment 5486735
Click to expand...
Click to collapse
dude these wont, work. you can get files without msm rollback from incremental zip
i have moto g stylus 5g 2021 and i have the same problem i cant root android 12 gsi.
ive patched my boot.img with canary, alpha 230016 , pretty much all latest magisk.
tried fastboot boot magisk.img .
still sends me to fastboot screen.
on gsi november 2021 patch
no twrp yet so magisk patch is our only option or is it? anyone figured a way to get around android 12 boot check..?
vbmeta disable verity no longer works on beta 4 and up.
i appreciate any feedback...thanks
what saddens me is i was able to root beta 1,2 and three but all were unstable and could not fix all issues
now this gsi 12 can be my daily driver i cant root it.. touche..lol
jhjhjhjhjhjh said:
i have moto g stylus 5g 2021 and i have the same problem i cant root android 12 gsi.
ive patched my boot.img with canary, alpha 230016 , pretty much all latest magisk.
tried fastboot boot magisk.img .
still sends me to fastboot screen.
on gsi november 2021 patch
no twrp yet so magisk patch is our only option or is it? anyone figured a way to get around android 12 boot check..?
vbmeta disable verity no longer works on beta 4 and up.
i appreciate any feedback...thanks
what saddens me is i was able to root beta 1,2 and three but all were unstable and could not fix all issues
now this gsi 12 can be my daily driver i cant root it.. touche..lol
Click to expand...
Click to collapse
Okay thanks to a fellow xda'er
when flashing never use fastboot delete product_a....blahblah...
use an image (product.img) that resizes and lets one flash..
fasttboot flash product product. img
rooted now thanks to all..
Related
When downloading a GSI, the required variant for Poco M3 is ARM64, A/B (perhaps referred to as "SAR"). Download and extract if necessary, the accepted image formats are sparse and EXT4. To install:
Code:
#Restart on bootloader fastboot
adb reboot bootloader
#Install the vbmeta image provided by Google to disable AVB and allow GSIs to boot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
#Format userdata to avoid possible encryption problems. Back up your files first
fastboot -w
#Restart on recovery (userspace) fastbootd
fastboot reboot fastboot
#Install GSI
fastboot flash system system.img
#Finally restart on it
fastboot reboot
Downloads:
Google vbmeta: image
Updated adb and fastboot: Windows | Linux | Mac
Tested GSIs and issues:
(will be edited later)
I have tested some GSIs. Here are some bugs.
- (happens to almost all variants) Google voice typing / Google Assistant are not functioning. Seems like the microphone does not pick up our voice. I have tried chaning permision, clearing data etc but to no avail.
- (happens to Caos 11 and some modded AOSP 11) The device will be listed as uncertified trebble device, so I cannot install Google apps nor login with Google account.
That's all for now.
hi guys can you help me,
i tried to instal gsi but the files size too big so i decided to restore but apprantly my sd card formated to by mistake,
then now i tried to flash eu rom and this happen anything i can do to fix this ? thanks
{
"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"
}
gasleak08 said:
hi guys can you help me,
i tried to instal gsi but the files size too big so i decided to restore but apprantly my sd card formated to by mistake,
then now i tried to flash eu rom and this happen anything i can do to fix this ? thanks
View attachment 5215101
Click to expand...
Click to collapse
Have you tried to install the stock ROM?
KaMyKaSii said:
Have you tried to install the stock ROM?
Click to expand...
Click to collapse
not working, when i do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that cannot flash any,
sad news i got my phone bricked
gasleak08 said:
not working, when i do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that cannot flash any,
sad news i got my phone bricked
Click to expand...
Click to collapse
What commands do you use to flash the GSI?
KaMyKaSii said:
What commands do you use to flash the GSI?
Click to expand...
Click to collapse
i ff the steps then
fastboot flash system (gsi i downloaded).img
but before that when i do this
#Format userdata to avoid possible encryption problems. Back up your files first
i also wipe dalvik and cache
gasleak08 said:
i ff the steps then
fastboot flash system (gsi i downloaded).img
but before that when i do this
#Format userdata to avoid possible encryption problems. Back up your files first
i also wipe dalvik and cache
Click to expand...
Click to collapse
Let's talk in private, I think it's better than flood the topic. Try installing xiaomi.eu again and then copy the /tmp/recovery.log and send it to me. And your device is not completely dead, at most reflashing the super partition will solve this
KaMyKaSii said:
Let's talk in private, I think it's better than flood the topic. Try installing xiaomi.eu again and then copy the /tmp/recovery.log and send it to me. And your device is not completely dead, at most reflashing the super partition will solve this
Click to expand...
Click to collapse
i dunno if i still can do that, last night my phone automatically turned off and i cannot turn it on. can you still help
gasleak08 said:
i dunno if i still can do that, last night my phone automatically turned off and i cannot turn it on. can you still help
Click to expand...
Click to collapse
Can't you get into fastboot anymore? Power + volume down
KaMyKaSii said:
Can't you get into fastboot anymore? Power + volume down
Click to expand...
Click to collapse
yes i can not get to onto fastboot, but my pc can still recognize my phone.
Did you try with XiaoMiTool V2 ?
Noru29 said:
Did you try with XiaoMiTool V2 ?
Click to expand...
Click to collapse
my phone wont boot to fastboot
deleted
KaMyKaSii said:
Tested GSIs and issues:
(will be edited later)
Click to expand...
Click to collapse
Any updates on GSI's you've tested?
Rama Himura said:
I have tested some GSIs. Here are some bugs.
- (happens to almost all variants) Google voice typing / Google Assistant are not functioning. Seems like the microphone does not pick up our voice. I have tried chaning permision, clearing data etc but to no avail.
- (happens to Caos 11 and some modded AOSP 11) The device will be listed as uncertified trebble device, so I cannot install Google apps nor login with Google account.
That's all for now.
Click to expand...
Click to collapse
Did you test AOSP 10 GSI not AOSP 11? If there are not many bugs on AOSP 10 GSI, I would like to try it.
When will be custom ROM awailable ?
sparrow1121 said:
When will be custom ROM awailable ?
Click to expand...
Click to collapse
February 29th
Hello, has someone tested AOSP 11 GSI? Could someone tell about his experience? Thanks.
{
"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
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
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.
{
"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"
}
OrangeFox Recovery
Information
Status: Beta
Version: R12.1_0
Release Date: 2021-07-12
Source Code:
https://gitlab.com/OrangeFox
https://github.com/Iscle/twrp_device_xiaomi_munch
Download:
https://github.com/Iscle/twrp_device_xiaomi_munch/releases
Installation:
https://wiki.orangefox.tech/en/guides/installing_orangefox
Documentation (FAQ):
https://wiki.orangefox.tech/en/guides
Donations:
https://opencollective.com/orangefox/donate
Source changelog:
https://wiki.orangefox.tech/changelog
Telegram channels:
News - https://t.me/OrangeFoxNEWS
Beta testing chat - https://t.me/OrangeFoxBeta
OrangeFox App:
app.orangefox.tech
Thank you very much for maintaining OrangeFox!
Since I'm new on an A/B device, I do have a question concerning installing magisk and keeping custom recovery.
As far as I understand, boot.img is modified by flashing orangefox.zip in recovery. What about magisk? Can I do a backup of the boot.img (hopefully) containing orangefox and flash back in recovery? Or is it best to use magisk addon from inside orangefox or flash magisk.apk from inside orangefox recovery?
Guide @ https://wiki.orangefox.tech/en/guides/flashing says to flash magisk once orangefox.zip is flashed an rebooted into recovery, but also, that:
One thing to note with respect to A/B devices is that, with respect to flashing ROMs, ... you must, immediately after flashing a ROM..., flash the OrangeFox zip again, then change slots, then reboot OrangeFox, before doing anything else. ...
iirc I did that and messed up the data & system_root partition or soemthing, so I reflashed stock rom and tried again. This time I just fastbooted into orangefox recovery and installed the orangefox.zip and it sticsk, flashed a custom rom (e.g. arrow or evolution or xdroid) but didn't slots and neither indstalklked magisk in any way. It works. So what about that slot changing? Better not?
Can you please hint in the right direction and if possible I'd like to understand what's going on, too.
Thanks!
Well done bro!
DidierMoulin said:
Thank you very much for maintaining OrangeFox!
Since I'm new on an A/B device, I do have a question concerning installing magisk and keeping custom recovery.
As far as I understand, boot.img is modified by flashing orangefox.zip in recovery. What about magisk? Can I do a backup of the boot.img (hopefully) containing orangefox and flash back in recovery? Or is it best to use magisk addon from inside orangefox or flash magisk.apk from inside orangefox recovery?
Guide @ https://wiki.orangefox.tech/en/guides/flashing says to flash magisk once orangefox.zip is flashed an rebooted into recovery, but also, that:
One thing to note with respect to A/B devices is that, with respect to flashing ROMs, ... you must, immediately after flashing a ROM..., flash the OrangeFox zip again, then change slots, then reboot OrangeFox, before doing anything else. ...
iirc I did that and messed up the data & system_root partition or soemthing, so I reflashed stock rom and tried again. This time I just fastbooted into orangefox recovery and installed the orangefox.zip and it sticsk, flashed a custom rom (e.g. arrow or evolution or xdroid) but didn't slots and neither indstalklked magisk in any way. It works. So what about that slot changing? Better not?
Can you please hint in the right direction and if possible I'd like to understand what's going on, too.
Thanks!
Click to expand...
Click to collapse
Well, to answer myself: when booting into recovery, just flash magisk or use orangefox magisk installer addon. It modifies the active a/ or B slot. While flashing a new rom is flashing it to the inactive A or B slot. After a reboot the newly flashed slot will become active, therefore install magisk (or any other) after reboot into recovery, when flashed new rom. But then the advice to change slot seems to be wrong :-?
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
sorry double post
gandaprayoga7 said:
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
Click to expand...
Click to collapse
We have A/B devices, so just move to the folder where you have that .img and use following command in console while you are in fastboot:
fastboot boot OrangeFox-Unofficial-munch.img
Click to expand...
Click to collapse
I didn't remember any "zip" file. Maybe it appeared later automatically as message to install or not.
Hi. I understood that in file manager TWRP and OrangeFox "Read-only file system". Cant move/delete/chmod files in /system_root folders. Is it problem recovery or stock android 12 ?
gandaprayoga7 said:
Can you give me more explanation on how to flash this recovery, the guide said to flash orangefox.zip after installation but there's only the .img files
Click to expand...
Click to collapse
I see your point.
Op didn't provide zip file, my way to flash it is
1. fastboot boot .img
2. find the option "Flash this recovery" in orange recovery and choose.
psklf said:
I see your point.
Op didn't provide zip file, my way to flash it is
1. fastboot boot .img
2. find the option "Flash this recovery" in orange recovery and choose.
Click to expand...
Click to collapse
thank you!!
There's or was a link to the zip file for munch on telegram via the pco f4 thread, I used that, too.