{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Flash command
Code:
fastboot flash recovery "filename.img"
What's working
- ZIP flashing
- Partitions wiping and formatting
- Data decryption
- ADB and MTP
- USB-OTG
- SD card
- Backup and restore
- File managing
- Brightness slider
- Vibration
- LED
What's not working
- Physical buttons (use navigation bar instead)
Download:
Deleting the builds since they were bugged, please use LineageOS recovery that you can find in LineageOS thread
Join my Telegram group for quick help or to see new releases/development
https://t.me/zenfone4max_group
works great
but this shows up when I go to recovery or try mount /data:
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
maybe because I have an encrypted /data
Не работает
У меня такая же проблема
onegabriel said:
works great
but this shows up when I go to recovery or try mount /data:
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
maybe because I have an encrypted /data
Click to expand...
Click to collapse
Yeah, stock decryption not supported
Format data and flash lazyflasher disabler or something that disable forced encryption
I created a group on Telegram for general support, join if you want https://t.me/zenfone4max_group
New update is out
Version 3.4.0.0
Added decryption support
system root
SebaUbuntu said:
New update is out
Version 3.4.0.0
Added decryption support
Click to expand...
Click to collapse
Thanks, it works perfectly.
But I still have a systemless root, what can I do to achieve system root?
You think wiping data partition would solve the problem?
Hi SebaUbuntu,
I just tried installing your unofficial TWRP on my Zenfone 4 Max Pro (ZC554KL), and it gets stuck on the "powered by Android" screen. I have Android AOSP Pie beta installed (downloaded from the ASUS website).
I tried the official version 3.2.2 which worked before I updated to Android Pie, and it goes into a reset loop. Your version 3.4.0 (from the X00I folder) stops at the "powered by Android" screen.
Any idea on how to get it to work? Or do I need to wait for a new version of TWRP for my phone?
NOTE: I'm using fastboot to boot the TWRP image. I can't get it to boot via any other method.
No response... Can anybody help me?
LINKS DOWN
SebaUbuntu said:
New update is out
Version 3.4.0.0
Added decryption support
Click to expand...
Click to collapse
the link is down
Hello, can u update the download link? The link is dead...
Thanks!
HansDR said:
Hi SebaUbuntu,
I just tried installing your unofficial TWRP on my Zenfone 4 Max Pro (ZC554KL), and it gets stuck on the "powered by Android" screen. I have Android AOSP Pie beta installed (downloaded from the ASUS website).
I tried the official version 3.2.2 which worked before I updated to Android Pie, and it goes into a reset loop. Your version 3.4.0 (from the X00I folder) stops at the "powered by Android" screen.
Any idea on how to get it to work? Or do I need to wait for a new version of TWRP for my phone?
NOTE: I'm using fastboot to boot the TWRP image. I can't get it to boot via any other method.
Click to expand...
Click to collapse
Well then u try boot into fastboot and then use command line to boot into TWRP.
Then wipe system, cache, data and flash the rom.
I think it should works.
BTW, also vol+&power bottom doesn't work?
And Im also wonder that if I want to root z4max, when should I flash Magisk? Right after I flashed the ROM or after first boot? (It seems excrypted and I'm unable to decrypt, it just shows "Decryption takes too long, killing process")
At that time I use another TWRP, I want to flash this one instead but the download link didn't works.
What a pity....
Thread closed as OP requested.
Related
Dear All,
WARNING: I'm no developer, just a regular user. SO PLEASE ONLY TRY THE BELOW PROCEDURE AT YOUR OWN RISK. I'm not responsible if you end up with a device that doesn't work the way it is originally meant to.
Recently I decided to root my Mi 5 running Global Dev ROM (Version: 6.5.30 (MIUI7)).
Read a few threads.
Mainly (link A): http://en.miui.com/forum.php?mod=viewthread&tid=260976
Then I posted a Q&A thread: http://en.miui.com/forum.php?mod ... 0&page=1#pid5799160
I noticed that according to link A, we needed to wipe data to root successfully.
Here's what I did:
1. Unlock BootLoader via Xiaomi Official Method. - Important Step
2. Temporarily flash TWRP (link mentioned in link A) [fastboot boot *recoveryname*.img].
3. Selecetd English as the language.
4. Left the System partition unmodified when promted (Keep Read Only).
5. Mounted System + Cache.
6. Enabled ADB sideload.
7. SIdeloaded the superSU file (link mentioned in link A).
8. Rebooted device.
9. SuperSU was installed.
10. To check this I tried out SElinuxmodechanger + V4A (use apps with Root access at your own risk and evaluation of safe / unsafe nature of the app/apps).
{
"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"
}
Conclusion: I was able to root my Mi 5 (Global Dev Rom) without permanent flashing of TWRP + without modification to system partition (Keep Read Only)) + without wiping data in TWRP before installing SuperSU.
Hey, great tutorial, but after, the OTA update will work and / or remove root ?
Is the sideload necessary ? Can't the SuperSU file be stored in an internal folder beforehand ?
@hmnk: can you please post links for SElinuxmodechanger and V4A? Thanks.
flavien317 said:
Hey, great tutorial, but after, the OTA update will work and / or remove root ?
Click to expand...
Click to collapse
Thanks.. The OTA updates work. You will only have to root the phone via my tutorial again.
lapocompris said:
Is the sideload necessary ? Can't the SuperSU file be stored in an internal folder beforehand ?
Click to expand...
Click to collapse
Sideload was necessary at the time of the tutorial being posted as the MIUI version / TWRP didn't allow data partition to be mounted without formatting it. Hence, the flashable zips had to be sideloaded.
However, currently, I'm on MIUI Version: V8.0.2.0.MAAMIDG (MIUI8) and twrp-3.0.2-0-gemini, this combination allows data partition to be mounted without formatting it.
Burs said:
@hmnk: can you please post links for SElinuxmodechanger and V4A? Thanks.
Click to expand...
Click to collapse
www.google.com
Personally tested myself on Mi5 Pro and it works with MIUI Version: V8.0.2.0.MAAMIDG (MIUI8) and twrp-3.0.2-0-gemini.
Huge huge thanks!
Thanks very much for this worked a treat. I'm on 6.10.13 Global, used ZCX-TWRP and SuperSU v2.76. No problems at all.
Many thanks for your guide. I'll try it on the next update
This has been working well for me, thank you. Now I'm wondering if the same method could be used to install things like Xposed without flashing TWRP too. Has anyone tried it? I'm scared. ::laugh:
thanks
Bootloop
Tried this over MIUI Global BETA 7.4.27 (Mi5) and got a bootloop
I've downloaded the required files and TWRP 3.0.2.0 and SuperSU 2.76
Thanks, it worked!
I just tested this on the MI5s Plus and it works on that phone as well.
{
"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
Hi to all dear Z3c users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git.
I hope you enjoy this.
How to install
Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot
Reboot your phone on fastboot mode.
Flash recovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via zip (You need a working recovery installed)
Download the zip and put it on your internal or external memory.
Reboot to recovery.
Flash the zip.
Via Official TWRP App (You need root)
Install the app from Google Play Store and download the zip.
Extract recovery.img and copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Download
TWRP
Thanks to
@GreyLeshy a lot of thanks for this great dev, he helped me a lot for make this possible, build this recovery and he had a lot of patience with this noob dev.
@Dees_Troy for TWRP.
omni Team for TWRP Minimal Source.
XDA:DevDB Information
TWRP for aries, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
ShadowElite, GreyLeshy
Source Code: https://github.com/ShadowElite117/android_sony_shinano_twrp/tree/aries
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2018-09-02
FAQs
Q. How boot on recovery?
A. With the device turned off, press power and vol- at same time until it vibrates.
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
neckronus said:
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
Click to expand...
Click to collapse
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
ShadowElite said:
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
Click to expand...
Click to collapse
Just tried flashing the latest Carbon and it worked for me. Haven't tested flashing stock ROMs myself though
Just tried to install the zip on my Z3 compact.
My phone has full encryption enabled (complete including the sd card).
Your build of TWRP is not able to decrypt the phone.
It always tells me "Password failed, please try again!" even though the given passsword is correct (I can start the system with the same one).
amazing
Installed on OMNI with TWRPapp, flahed Carbon and then RR.
All it was fine and, finally, no "Error 7".
Thank you for this!
I have a question, I have encrypted my device (CarbonRom cr6) and now when I try to access TWRP I draw my security pattern and I get a failed to decrypt message.
The pattern is the one I use on a daily basis to use my device so this is related to TWRP. Any suggestion?
Maybe this twrp has a problem with support encription?
Carbon ROM expects TWRP with ro.build.product or ro.product.device equal z3c (not aries) . Modified original image using this method https://forum.xda-developers.com/t/...because-of-empty-system.3554252/post-85881113
For Lineage (18.1), this (3.3.1) TWRP version is recommended, but it seems to have issues preserving the survival scripts (e.g. of Magisk) over OTAs. Unfortunately, the device isn't supported on twrp.me
Jolla SailfishOS 3.2.0.12 linux
IT IS NO ANDROID!
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
The full install tested with Official ugglite 3.3.1 TWRP.
Download LineageOS 14.1 & SailfishOS.
NEED FREE INTERNAL STORAGE SPACE ~2GB!!!!!!
NEED UNSECURE EXT4 /data Partition!
Boot into recovery.
Wipe data, cache,system partitions.
(If your /data partition secured, you need format /data to ext4 if you want to use this ROM.)
Flash LineageOS 14.1 ugglite ROM in TWRP (sideload or copy any storage)
Reboot, start LineageOS 14.1 (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 2 minutes.
Restart to TWRP again.
Flash SailfishOS 3.2 ugglite in TWRP (sideload or copy any storage)
Reboot
First boot may take up to 1 minute.
ssh: [email protected] (change password: settings - developer menu)
Dual boot: flash with TWRP or 'fastboot boot' Lineage boot.img, or flash with TWRP or 'fastboot boot' hybris-boot.img, from zip files.
Sailfish OS workig from /data partition, if you wipe data, deleted Sailfish OS
BACKUP, before wipe data.
Bugs:
No bootsplash.
Boot time 50-60 sec. Power off charge animation ~50 sec. Reboot, and power off time 15-20 sec.
I could only create a Jolla account on a PC.
Some video types are not playable (Jolla license).
DOWNLOAD ROMS SF
DOWNLOAD ROMS AFH
Known issues: don't know
I'm not going to give you support for privat upgrades and other changes, fix it for yourself. Sorry.
*
Screenshots: LINK
ROM OS Version: 14.1 & 3.2.0.12
ROM Kernel: Linux 3.18-31-szancso & 3.18.140-szancso
ROM info: Lineage-14.1, system partition, Android quota no.
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 2020-03-08
Last Updated 2020-03-08
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
Test update and alien-dalvik Android support:
{
"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"
}
How to update ?
ByHorvyCZ said:
How to update ?
Click to expand...
Click to collapse
I do not support the update.
There may be a problem with WiFi, sounds, lights, etc.
If you want to upgrade, you have to solve it yourself, because if you can't upgrade it yourself, you can't fix problems.
Alien-dalvik is not going to be with upgrade, a separate thing, and to my knowledge warez. Anyway, it's almost uselessly bad. (At least the version I tried.)
I do not support this too. Sry.
Yes you're right. I tried to make a force update through the terminal.
Now Wifi doesn't work. Otherwise, I put it into operation.
I upgraded the system just to make sure other accounts were working.
Warning, do this at your own risk.
!!You can ruin the system or worse the whole phone !!
So, okey, open your terminal. :angel:
Code:
devel-su
Then you enter the root password, :good:
Code:
ssu release 3.2.1.20
This sets up what you want the system to update
Code:
version --dup
This will start the process of updating.
You should never close the terminal when you're running this command.
After all, restart phone, and you are done ! :silly:
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
{
"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"
}
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
zkosmosu said:
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
View attachment 5197369
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
Click to expand...
Click to collapse
Nothing get flashed, you can boot back in your previous rom.
Check if partition are not already mounted in TWRP and untick them.
You can also report your issue to the relevant crdroid topic in ROM/DEVforum.
zkosmosu said:
I'm using Xiaomi Redmi Note 9 Pro (Joyeuse). I don't think I bricked my phone because I can run TWRP, but surely something went wrong when I tried to change one custom ROM (Havoc OS 3.12) to another (crDroid v7.2). Now when I try to flash crDroid zip, this is what happens:
View attachment 5197369
It would be wonderful if someone could help me bring my phone back to life. I've only had it about two months.
Click to expand...
Click to collapse
Try orange fox recovery there you have the option to unmount system n vendor while flashing works fine.
Cheers
HELP! is there any work around? I flash havoc rom but its says the same ( updater process ended with ERROR 1 )
Same error can anybody help me out
It is showing me error as,
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Still no solution?
Flash the super image through recovery.
Same problem.. but i manage to install another custom rom. Twrp wont work for that even you repair the Data or change system files. My solution is i use OrangeFox recovery, and install havoc os a11 and it works but other roms like evo x , pixelui, corvus os doesnt work and having error the same as you.
I have the same issue like u.. use the orangefox recovery.. to install custom ROM. It fix my issue.
ligodligerem said:
I have the same issue like u.. use the orangefox recovery.. to install custom ROM. It fix my issue.
Click to expand...
Click to collapse
Which version of orangefox do you have installed!
xerel89 said:
Which version of orangefox do you have installed!
Click to expand...
Click to collapse
hey.. i fix it right now. using twrp and orangefox. updated version. please consider to redownload your custom rom zip file. cause thats the reason why its not mounting. I tested it and after i download a new custom rom file and delete the previous custom rom, and put it in main directory "sdcard/" and suddenly it worked.
xerel89 said:
Which version of orangefox do you have installed!
Click to expand...
Click to collapse
i thought the error is in custom recovery, until i found out its the custom rom zip is the one got the prob.,
I have also Redmi note 9 Pro device,
Custom recovery twrp 5.4 installed
Just flashed Ancient OS 12.1 and this same thing happens.
Now cannot flash any other roms. Maybe android partitions bricked.
What should I do now!
*************************************************************
———————— TWRP for K40 Pro + ——————————-
*************************************************************
WARNING : I do not know who made this TWRP and i am NOT taking credit for it. Someone in my group chat found it. It's apparently from China. If you are the creator , PM Me.
{
"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"
}
INSTRUCTIONS
1) Download TWRP for K40 Pro + , and put it in your fastboot folder.
2) Put your phone into fastboot mode.
3) Do the following command : fastboot boot twrp-recovery-venus. It will automatically boot into TWRP.
4) Change language to English (press the 6th option).
5) Go to "Advanced" and select "Onekey inject TWRP".
6) Swipe to inject the TWRP. It might take a few minutes, so don't worry.
_____________________________________________________________________
Note: Don't change the boot slot (Slot A) or maybe will not boot at all.
Tested by @mslezak
______________________________________________________________________
Bugs: ADB Sideload is broken.
_______________________________________________________________
If you find any bug, feel free to report it down below.
Credits to @Cozzmy13 for decrypting the TWRP image! Here's the summary of events :
1) Chinese TWRP gets leaked onto my Telegram chat.
2) The recovery image is encoded and requires a dodgy chinese tool to decode it.
3) @Cozzmy13 finds a way to decode the image and make it bootable .
4) Me and Augustin El Metralleta try flashing the image, and we find out it works.
Does it suitable for K40 Pro? Did anyone try? Thanks!
K40 Pro has the same guts except the camera main and 12gb RAM so it should work
I verified a backup up image today restored worked although there wasn't much data on it. i always boot it. One time the injection made me have to use a fastboot ROM (always try deleting data first).
Have only one doubt can this twrp able to flash official china beta recovery rom for mi 11X pro?
#Update
I have flashed this twrp and it successfully booted without any issues and i have dirty flashed china beta recovery rom over chi a stable rom amd rom got flashed successfully without any issues.
But we need to flash the twrp every time when we reboot device.
cherri said:
How to make the twrp permanent then?
Click to expand...
Click to collapse
You can try to flash magisk after flashing the twrp, i'm still waiting the 7 days to unlock the bootloader so i can't try right now. If i remember correctly magisk has something that blocks "recovery-from-boot" and prevents twrp from being overwritten.
I think for now it is not possible are els he would have mentioned flashing process here instead of twrp temporary boot process, so we need to wait few more days unless someone does some miracle.
cherri said:
I think for now it is not possible are els he would have mentioned flashing process here instead of twrp temporary boot process, so we need to wait few more days unless someone does some miracle.
Click to expand...
Click to collapse
What do you mean. After flashing, TWRP was persistedm. I was also able to flash Magisk with this TWRP.
Go to "Advanced" and select "Onekey inject TWRP".
I wonder why there isn't any available tutorial on flashing twrp for this device on google, YouTube. What do you think guys?
thanks for the dev xinkid520 a chinese dev
It is indeed effective after testing, very good!
bouyhy01 said:
thanks for the dev xinkid520 a chinese dev
Click to expand...
Click to collapse
yeah he made it, but encrypted it and sold it for money.
so people from telegram decrypted it
zls8635878 said:
It is indeed effective after testing, very good!
Click to expand...
Click to collapse
So can we use this twrp permanently?
Can you tell me the steps if so?
DestroYerr said:
So can we use this twrp permanently?
Can you tell me the steps if so?
Click to expand...
Click to collapse
Go to "Advanced" and select "Onekey inject TWRP".
cherri said:
#Update
I have flashed this twrp and it successfully booted without any issues and i have dirty flashed china beta recovery rom over chi a stable rom amd rom got flashed successfully without any issues.
But we need to flash the twrp every time when we reboot device.
View attachment 5330171
Click to expand...
Click to collapse
I flashed this twrp into my phone. But when i try to install rom,recovery just flash and return to recovery again and ROM files got deleted. Could u tell me how u install this ROM?(PS my rom is (xiaomi.eu_multi_HMK40Pro_MI11i_V12.5.4.0.RKKCNXM_v12-11-fastboot)
Armstchi said:
I flashed this twrp into my phone. But when i try to install rom,recovery just flash and return to recovery again and ROM files got deleted. Could u tell me how u install this ROM?(PS my rom is (xiaomi.eu_multi_HMK40Pro_MI11i_V12.5.4.0.RKKCNXM_v12-11-fastboot)
Click to expand...
Click to collapse
Your rom version is for Fastboot, not Recovery.
k40 pro
majisk was installed.
I have a USB Memory Stick connected via an OTG cable, but I cannot mount it.
The usb format is FAT32. Please help someone.
cyaochai said:
k40 pro
majisk was installed.
I have a USB Memory Stick connected via an OTG cable, but I cannot mount it.
The usb format is FAT32. Please help someone.
Click to expand...
Click to collapse
Bro after flashing magisk, is safetynet okay?