Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
prashanth_ said:
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
Click to expand...
Click to collapse
I have miui 12 how to root?
Ameer9963 said:
I have miui 12 how to root?
Click to expand...
Click to collapse
Which guide have you followed?
prashanth_ said:
Which guide have you followed?
Click to expand...
Click to collapse
I have followed miui 11 guide
But i have miui 12
Ameer9963 said:
I have followed miui 11 guide
But i have miui 12
Click to expand...
Click to collapse
Plz post how to patch boot image
Magist patched boot image not working to root
Related
I have a problem that i never make it into recovery again. I am used to adb/fastboot, this is my 5th device and i happily used different custom roms as lineage, havoc, crdroid for about 7 years and thus am familiar with the concepts of a/b, recovery, adb/fastboot and so on.
Now, when i "flash_all" with stock from here (V10.3.17.0.PFQEUXM) on my a3, i suppose both slots a and b are overwritten with stock. interestingly this stock rom only boots in a-slot, not in b-slot.
when i now just "fastboot flash recovery twrp...." with 3.3.1.2 and hit the manual enter to recovery (power + vol up), i just get a "no command" error - no twrp in sight.
i also tried this with flash_all V11.0.2.0.QFQEUXM rom (a10) and fastboot flash recovery twrp 3.3.1-17 Q from mauronofrio - same result.
anyone knows what i did wrong?
basically i didnt enter team win recovery for some good amount of tries which slightly terrifies me at this point. (help)
Should i use the global versions instead of the europe ones? Do i need to use "fastboot flash BOOT twrp.." instead of "fastboot flash recovery twrp.."?
I am also happy for suggestions where i could pose this issue more appropriate.
//update: i am now in stock rom and could root it with flashing a magisked boot.img but still cannot enter twrp recovery (-> "no command").
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
thanks @garylawwd
garylawwd said:
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
Click to expand...
Click to collapse
So to be sure: i have stock 11.0.3.0 europe from here installed and i am in slot a now and i cannot go into twrp because it says "no command".
i go to fastboot now, then
Code:
fastboot flash boot twrp.img
with a recent twrp that can run android 10 from here and then power + vol up without switching slots.
garylawwd said:
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
Click to expand...
Click to collapse
how can i flash a boot.img from twrp? i thought, i can only flash .zips from twrp? Also do i need to take spacial measures to be able to read internal memory in twrp?
//edit: i tried to flash named twrp but it wouldnt boot up into recovery, instead went straight into fastboot. so i flashed boot with stock boot again. no solution in sight.
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
_mysiak_ said:
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
Click to expand...
Click to collapse
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
tutankpusch said:
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
Click to expand...
Click to collapse
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
_mysiak_ said:
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
Click to expand...
Click to collapse
Thanks @mysiak_d
I used for example this method with this recovery bc it should work with android 10.
straight into fastboot instead recovery :/
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
Xiaomi Redmi 8A
MIUI Global 11.0.7 (PCPMIXM)
Bootloader unlocked
I followed this youtube tutorial
Running the following commands:
fastboot devices (detected just fine)
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
All 3 files were flashed successfully, the TWRP wasn't working as expected, it booted into TWRP but the touch didn't work, so I decided to install another version found in another video (3.3.1-0105 by wzsx150), this worked, and allowed me to install MagiskManager-v7.5.1
Then after booting, I can't turn on the WiFi. When I try to enable it, it just disables itself automatically.
As far as I know, the boot image is the problem, I have another Xiaomi Redmi 8A with me but with MIUI Global 11.0.9 (PCPINXM), it has the bootloader unlocked too, what do you suggest? Can I get a copy of that boot and flash it with fastboot to the device with the wifi problem? may it work? what are the commands to do so? I don't know them and I don't want to brick it
Any help is much appreciated, thanks!
Sirvaudebtc said:
Xiaomi Redmi 8A
MIUI Global 11.0.7 (PCPMIXM)
Bootloader unlocked
I followed this youtube tutorial
Running the following commands:
fastboot devices (detected just fine)
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
All 3 files were flashed successfully, the TWRP wasn't working as expected, it booted into TWRP but the touch didn't work, so I decided to install another version found in another video (3.3.1-0105 by wzsx150), this worked, and allowed me to install MagiskManager-v7.5.1
Then after booting, I can't turn on the WiFi. When I try to enable it, it just disables itself automatically.
As far as I know, the boot image is the problem, I have another Xiaomi Redmi 8A with me but with MIUI Global 11.0.9 (PCPINXM), it has the bootloader unlocked too, what do you suggest? Can I get a copy of that boot and flash it with fastboot to the device with the wifi problem? may it work? what are the commands to do so? I don't know them and I don't want to brick it
Any help is much appreciated, thanks!
Click to expand...
Click to collapse
Hi, sorry if I misunderstood you but did you try to install the old Magisk Manager? It's not even Magisk Manager anymore but only Magisk, try to install the latest stable version 25.2 here is the download link.
Exact same issue here.
Unlocked bootloader and had twrp recovery on it
Installed PixelExperience 13 and everything was fine
For banking apps, I installed Magisk 25.2 following official process w/boot + recovery
Flashed patched images using fastboot.
Now I have banks, but no wifi :-/
Any hints?
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog:
• Updated sources to latest
• Almost Everything working fine.
Only for MIUI 13 Android 11
Creator: @Aghora7
Download
Installation instructions
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
lurchiii said:
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
Click to expand...
Click to collapse
I can't answer to this question, because it depends on you made any mistakes during the installation or not
Its support for A12 miui 13.0.4
Does it support A12 eea europe rom ?
xristos1925 said:
Does it support A12 eea europe rom ?
Click to expand...
Click to collapse
it supports a11
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
sanjibukai said:
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
Click to expand...
Click to collapse
Once you have lineageos installed, you must to flash twrp via fastboot and then flash Gapps
1. Flash system ( when it's done, don't reboot phone, just flash twrp
2. If you already are on twrp flash your Google apps
3. When you're done with flashing gapps, restart phone to system (twrp will be gone after reboot)
4. You have installed Gapps
i don't know how to flash twrp permanently, if you want further informations about this recovery, then join fleur telegram development channel
BloxetPL said:
1. Flash system ( when it's done, don't reboot phone, just flash twrp
Click to expand...
Click to collapse
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
sanjibukai said:
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
Click to expand...
Click to collapse
Remove "fastboot reboot recovery" from SMINORI tool and instead of this type "fastboot flash boot twrp.img
fastboot boot twrp.img"
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
globalfandemic said:
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
Click to expand...
Click to collapse
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
BloxetPL said:
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
Click to expand...
Click to collapse
Already tried, still same issue.
Tried using a couple new commands too with no result:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
fastboot reboot recovery
Also tried using only the commands you gave:
fastboot flash boot twrp.img
fastboot reboot recovery