Related
Hey guys,
I have recently bought my "Whyred" (4/64 global) and have already unlocked the bootloader.
After switching to Miui 10 global developer rom (with official MiFlash Tool) I wanted to test some custom roms. Therefore I have enabled the developer options, USB-Debugging and OEM Unlock. After this I have booted TWRP 3.2.2.0 with fastboot and flashed the TWRP image to the phone via the booted recovery. Followed by the no-verity-opt-zip (6.0) and Magisk v16.7 to root the phone.
On this basis I went back to the recovery and did a factory reset, followed by an advanced wipe of dalvik, cache, data, system and vendor. Afterwards I have moved the whyred-treble-vendor (zip-file) and the PixelExperience GSI to my phone. First I have flashed the vendor-zip and then switched to image and flashed the GSI as system-image.
And now comes the problem: when I try to reboot to the system it always states "No Os installed". By wiping the cache and data again, I am able to boot to the system, but the phone is stucked on the Mi-Logo
After recovering my phone with the MiFlash Tool (Miui 10 global developer rom), I have tried to flash the GSI in different ways according to a lot of guides I have found in the net, but nothing is working. All methods are leading to the same result: my phone stucks on Mi-Logo
Could anyone of you give me a hint about what I am doing wrong?
Thank you!
Best regards,
nkl
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
corkiejp said:
At a guess with wiping system and data. Your also removing changes done by "no-verity-opt-zip (6.0)", and since your still using the MIUI Bootloader the device won't boot the associated GSI.
Maybe try flashing/booting a Treble enabled custom rom, first and then install your GSI. Or avoid the whole Treble thing and just use a custom rom.
You may get more assistance in Treble specific threads/forums.
Click to expand...
Click to collapse
Hey,
Thank you for your quick reaction!
But did I get something wrong? Doing a factory reset and then doing an advanced wipe of dalvik, cache, data, system and vendor is more or less an essential part of all the guides out there?
So you think, I should try to flash for example LineageOS first and then take an approach on the GSI? And which steps should I take? Should I flash no-verity-opt and Magisk under Miui 10 global dev first and then flash custom, i.e. LineageOS? Or should I flash LineageOS first (on a fresh Miui dev rom) and then no-verity-opt and Magisk?
Thanks!
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
corkiejp said:
@nkl0806 After installing the GSI while using MIUI as the base you could try flashing no-verity-opt before trying to boot.
no-verity-opt is only required on MIUI based roms (or in your case with a GSI).
Flash a custom rom and boot it. Don't worry about magisk etc.
Then install your GSI and boot it, avoid flashing magisk or gapps.
Once it boots, go back and install magisk and gapps etc and wipe data.
Hopefully then boot and setup your GSI rom.
Also make sure your using a Treble enabled TWRP!
Noob guide to install GSI on whyred
Again look for support in Treble Threads/Forums, I haven't experiment with it, so only going by what I have read.
Click to expand...
Click to collapse
Thank you!
I have also followed this noob guide to flash the GSI, but it did not work out. Maybe I should really skip the Treble stuff and just use the normal custom rom!
I will try to flash the PixelExperience rom and not the GSI - or maybe follow another Guide and flash the Mokee rom first as a base for the GSI.
Thanks again!
Disclaimer: I come from the LG D802 world so I have no idea what antirb, dm-verity, authorization code or other strange protections are. Back then, any soft/hard brick could have been simply fixed by putting the phone in download mode and flashing the original software. So here I'm a bit scared to mess with the phone. I googled up all these questions, but mostly got contradictory answers so I decided to make a thread here trying to address everything.
For all the following scenarios, we'll consider that we're running the latest global MIUI with antirb = 4 (MIUI v10.0.1 OEIMIFH)
SCENARIO 1:
Let's say I want to gain root access with the original ROM (in my case: MIUI v10.0.1 OEIMIFH with antirb = 4). I understand that I have to:
1. fastboot into some custom recovery (let's say orangefox)
2. reflash redwolf from recovery
3. flash magisk
4. reboot into system
Now I should have root access, right? What about if I want to make changes to the /system partition now? From what I understand, there is a dm-verity check that detects changes to the /system partition and bootloops the phone if found. So, am I safe or not to make changes? (eg: flash youtube vanced, edit hosts, remove system apps, edit configuration files, etc)
SCENARIO 2:
I read somewhere that in order to disable all /system integrity checks, I'll have to reflash MIUI through orangefox and it will auto-patch out those checks. So, for instance, I want to flash the latest weekly xiaomi.eu ROM. (which AFAIK is China developer based and might interfere with the antirb check). The steps should be:
1. download the ROM
2. look into the .zip file and remove the firmware update script (is this necessary or orangefox will take care of it ???)
3. copy to sd
4. wipe cache, dalvik and /data (without /system and /persist)
5. flash through orangefox
6. flash magisk
7. reboot to system. done???
Now I should be able to make all sorts of changes to the phone (/system partition) without bootlooping or whatever?
SCENARIO 3:
Let's say I want to flash RR (or any other custom ROM). The instructions say that I need to have a NON-ARB firmware. What does it mean? How do I flash a NON-ARB FW if I'm on ARB 4 without bricking my phone?
SCENARIO 4:
Let's say that somehow I managed to flash a custom ROM. How can I go back to the original MIUI without bricking/losing the unlocked bootloader? Is miflash enough?
Unrelated questions:
1. How to make the custom recovery permanent? (is booting into recovery + twrp reflash enough ???)
2. Will OTA's brick my phone? (the phone being twrp'ed + magisk'ed)
3. Will OTA's remove my custom recovery?
4. What is lazyflasher and when does it have to be flashed? (or is it still required?)
5. Is it possible that the bootloader will get relocked by mistake?
6. What are the advantages of redwolf/orangefox compared to vanilla twrp?
I'd appreciate if somebody could take time to explain the steps and answer my questions (especially those from scenario 3) because I'm pretty sure there are many other users as confused as me regarding all this xiaomi flashing policy.
Scenario 3 : No you don't have to flash any firmware as you are already in latest miui version
Non ARB is for those people who is using anti3 ROM and don't want to upgrade to anti4 ROM
Just flash RR ROM without flashing any firmware file
Scenario 4 : yes using MiFlash just flash fastboot ROM or else just flash recovery ROM from custom recovery
There won't be any chances of bricking if you use MiFlash software because MiFlash checks bootloader index before flashing fastboot ROM, to be safer side always flash latest available MIUI ROM
xiaomi.eu is not a official ROM you can get official ROM from en.miui.com
To make custom recovery permanent just flash lazy flasher
No OTA will not brick your device
Yes if you flash full recovery ROM then custom ROM will be replaced by mi recovery but you can avoid this by flashing lazy flasher
No there is no chances of bootloader lock with OTA update, to lock bootloader you have to flash fastboot ROM using MiFlash software and you have to select clean all and lock option
Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)
csm1n said:
Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)
Click to expand...
Click to collapse
All the edited options will be over written by newly flashed ROM.
I don't know much about Dm Verity but you can flash lazy flasher to avoid dm Verity
Hopefully you will find your answer here https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210
csm1n said:
Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)
Click to expand...
Click to collapse
had a G2 long time.
dm verity you can flash after installing TWRP flash file called lazyflasher or use orange fox recovery and no need to do anything. just flash and forget.
also try masik rom
I'm a newbie myself. Can I ask a few questions too?
1. If I want to root (miui 10) and install some mods, what's the best way to backup my current rom before rooting?
2. If I change my ROM to a custom ROM, how can I flash back my current ROM with OTA?
Thanks
Remig83 said:
I'm a newbie myself. Can I ask a few questions too?
1. If I want to root (miui 10) and install some mods, what's the best way to backup my current rom before rooting?
2. If I change my ROM to a custom ROM, how can I flash back my current ROM with OTA?
Thanks
Click to expand...
Click to collapse
1. TWRP Backup or ADB backup
2. You can return to stock MIUI ROM by flashing fastboot ROM using MiFlash (Recommended) or by flashing MIUI Recovery ROM
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
To encrypt the rom again, flash encrypt(pie).zip and format /data
What is the meaning of forced encryption on data partition
#ArtFuL said:
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
Click to expand...
Click to collapse
In which recovery stock or on custom recovery?
Sdsahu101 said:
In which recovery stock or on custom recovery?
Click to expand...
Click to collapse
Custom recovery
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
nice_guy75 said:
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
Click to expand...
Click to collapse
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
#ArtFuL said:
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
Click to expand...
Click to collapse
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
nice_guy75 said:
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
Click to expand...
Click to collapse
Then no need to format. You won't loose data
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
kayamokid said:
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
Click to expand...
Click to collapse
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
legacy07 said:
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
it meams its just like the updated version of decrypt.zip? thanks sir.
Which one of these two files should be flashed
Karthik kollapureddy said:
Which one of these two files should be flashed
Click to expand...
Click to collapse
Choose according to whether you have to encrypt or decrypt
legacy07 said:
Choose according to whether you have to encrypt or decrypt
Click to expand...
Click to collapse
I'm a beginner so would you please tell me what's encypt and decrypt
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
Karthik kollapureddy said:
I'm a beginner so would you please tell me what's encypt and decrypt
Click to expand...
Click to collapse
I'm confused and the rooting step
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
sintoo said:
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
Click to expand...
Click to collapse
This mod works in X01BD and X00TD. Not sure if it work for Z01BD. You can flash this patch by following the steps in the thread but success isn't guaranteed. Take a system backup as if anything goes wrong. Also be ready to loose your data
legacy07 said:
... So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
I'm not sure about that... I am flashing this file (decrypt pie) for Oreo just. The phone does not boot in this case. I was forced to flashing old decrypt file for Oreo after and it all worked again.
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
anagramgenius said:
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
Click to expand...
Click to collapse
I think twrp official has decryption issues. Check with twrp 3.2.3
legacy07 said:
I think twrp official has decryption issues. Check with twrp 3.2.3
Click to expand...
Click to collapse
I checked with Rk585's TWRP 3.2.3 too. Same issue persists. It worked fine when I was in Oreo.
After flashing the zip, I booted back to recovery and copied the fstab.qcom to my PC to check if it has been replaced with the flashed zip. It did replace it. But when I boot to system, it starts encrypting my device and TWRP gets replaced by stock recovery. So I flashed the TWRP again and checked the fstab.qcom. Voila. It was unpatched. I don't know what is happening during the boot. The patched fstab is getting replaced by original fstab.
Edit: Seems there is a problem with the zip I guess. Or more files need to be patched to disable forced encryption in stock Pie rom. I tested in both PBRP and OFRP.
Case 1: I flashed stock rom in Official TWRP, then flashed PBRP zip and booted into PBRP. After booting into PBRP, it doesn't automatically disable forced encryption if no rom zip is flashed in it. So I flashed the decrypt zip provided in this OP. Then I booted to system, it started encrypting my device.
Case 2: I flashed stock rom in Official TWRP, then flashed OFRP zip and booted into OFRP. After booting into OFRP, it automatically disabled forced encryption even though no rom zip was flashed. Hence after booting into system, it didn't automatically encrypt my device as forced encryption was disabled automatically by OFRP.
So PBRP and OFRP do something else to disable forced encryption other than just patching fstab.qcom. Atleast in stock Pie rom. That's why I'm unable to disable forced encryption by flashing decrypt zip in any of the recoveries unless it is patched by recoveries themselves.
My ginkgo had stock ROM V12.0.6.0.QCOMIXM (A10) and I updated to stock ROM V12.0.2.0.RCOMIXM using TWRP recovery (twrp_ginkgo-willow_3.4A9_23-12-2020_BL) However after flashing the rom zip, and after flashing magisk, my phone got into "MIUI" icon, then bootloops into recovery again with alphanumeric directory names.
I tried Disable Dm Verity Force Encrypt after flashing magisk.zip but same problem.
I have tried the following recoveries so far:
twrp_ginkgo-willow_3.4A9_23-12-2020_BL
twrp-3.5.2_10-2-ginkgo
orangefox R11.0_1 (with Disable DM-Verity, Disable Forced Encryption and Aggresive stock recovery deactivation all enabled).
But whenever I flash magisk, I still get the bootloop and alphanumeric directory names, and the only way to restore my phone without having to wipe data is to flash the recovery zip again (but without magisk).
Any suggestions on how to get around this?
bomberb17 said:
Any suggestions on how to get around this?
Click to expand...
Click to collapse
i already answered you here
use this DFE
I successfully unlocked my bootloader, then I tried flashing the twrp by following munchy's tutorial from YouTube (as someone recommended here). I also used the twrp recovery file he provided in the description, by using the latest platform tools from the official website. It was going pretty good. I even got the TeamWin logo, and also loaded up the twrp interface, and was able to navigate through it. But the problem was my internal storage wasn't showing up. So I booted back to my system normally to see If I can find a solution. Then I think I tried again after restarting to see if it fixes itself, but the same problem was persisting. The next time when I tried again, I used the latest twrp version which I downloaded from the official twrp website.
But since my 3rd attempt, I am not able to see any TeamWin recovery come up on my phone, when I connect I do the "fastboot boot (twrp filename)" command in cmd. When I do the command, nothing shows up. The device remains in the Fastboot mode, or just turns off. When I switch it back on, It turns on normally and boots into the phone without any issues, and I can use it. I've tried switching back to the original twrp version munchy used in the above linked video, but same result.
What did I do wrong here? How do I make my phone get into the twrp recovery when I enter the fastboot boot (twrp filename) command thru my PC? How do I make my Internal Storage available to view int he TWRP recovery so I can install it from my Downloads folder? I am on MIUI 14.0.4 If that helps. My end goal is to install Magisk.
Any tips/guides/suggestions are appreciated.
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
NOSS8 said:
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
Click to expand...
Click to collapse
Thank you. I had put backed the screen lock after the first 2 attempts because someone said to to that on a YT video after they faced the same problem. Now I tried again by removing the screen lock and the latest twrp for my device also boots up just fine. Now the problem Is I still can't access my internal storage .
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Try to mount storage.
NOSS8 said:
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Click to expand...
Click to collapse
Yes, I removed the screen security, though I can enter TWRP, I can't read the internal storage. MIUI 14.0.4.
I just watched a YT video where the dude does the following:
-TWRP Recovery
- Wipe
- Format Data
- Types 'yes'
then
-TWRP Recovery
- Reboot
- Recovery
- Do not Install
After coming back to recovery after rebooting, he gets a pop up, which at the swipe says "Swipe to allow for modifications" which he swipes, then now after checking the Internal Storage, It's readable now. Is this a possible solution?
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
NOSS8 said:
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
Click to expand...
Click to collapse
what's twrp A13? Also, I just unlocked my bootloader a few hours ago, so my phone has already done a factory reset and i don't have anything to lose except the Magisk APK and .img file in my phone.
But I have a question, will doing the format data just do a factory reset, or will I lose my ROM? Because I'm not trying to install a custom ROM, I just want to Install Magisk as the end goal with my current ROM.
MIUI 14 Android 13 so use this TWRP
plugged the phone into the PC when it is on the TWRP, you will have access to the internal storage. (works on my 12 pro aves twrp A13 Skk).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
zoinksy said:
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
Click to expand...
Click to collapse
Use this TWRP(officiel).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
thank you, this is the one I was looking for. Sorry to bother you again, now I installed the Magisk V26.1 apk from TWRP. And when I boot back to system and try opening the magisk manager, this happens. It says downloading, forever. I think I shouldn't have directly downloaded the latest version. So probably have to downgrade it a bit. For that, what will I have to do?
Can I just hold the Magisk icon, and uninstall it simply like any other app? Or do I have to do it from the TWRP? Also, Is it necessary for me to uninstall it before downgrading, or can I just download the apk of older magisk version and flash it from twrp just like I did previously?
It was on my first post.
Installation
The Magic Mask for Android
topjohnwu.github.io
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
cyanGalaxy said:
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Sure, but currently only in A12.
NOSS8 said:
Sure, but currently only in A12.
Click to expand...
Click to collapse
I use ArrowOS 13
cyanGalaxy said:
I use ArrowOS 13
Click to expand...
Click to collapse
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
NOSS8 said:
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
Click to expand...
Click to collapse
Hm ok.
Welp for me on AOSP, it works nicely. I flash a new build (or two) every week. Backup/Restore works as should. UI is nice and modern, imo better than TWRP. That's why I'm recommending it.
Haven't heard anyone saying that they can't view Phone storage on OrangeFox.
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
néonaloj said:
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
Click to expand...
Click to collapse
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need ,install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
EDIT:
omitted link
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
NOSS8 said:
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
Click to expand...
Click to collapse
I'm very greatfull for your quick reply ! Thanks
The device is too a Poco f3, sorry.. This doesn't need to flash magisk for twrp to stick (I had another one I've broken)
But I don't understand what's the advantage to first flash a fastboot rom..? As you say to flash twrp would loose root and vice versa... (I've read the thread you're talking about ofox)
So I wanted to go trough +- the way I mentionned, as A13 as well as ofox 'seems' to work (but I'm carefull with that twrp on stock MIUI A12, and I never used ofox..)
So you do think it's a bad idea ?? The rom I want to flash is crdroid.
I'm more lost now ...
Thanks again !