Hi, All..
I'm a new Mi 9 user. My device has been unlocked the bootloader.
I hope you guys able to help me out for all of following questions of Mi 9.
1, What's defferent between flash global rom by Miflash and TWRP?
2, What's Vendor.img for? Why most of time need to flash 9.8.1 vendor image before custom ROM and do we need to flash it all of times, when we reflash custom ROM?
3, What's vbmeta.img for?
4, Is it root different ROM needs to flash defferent Magisk version?
I will appreciate for all of you guys answer. Thank you so much.
1.) What's difference between flashing the global rom by Miflash and TWRP?
A: You can flash the stock global ROM using MiFlash, which involves using a PC, in case you brick your phone.
You can also flash a recovery global ROM using TWRP.
2.) What is vendor.img?
A: It contains device-specific hardware drivers, you only need to flash it once. Then you can hop between different custom ROMs.
3.) What is vbmeta.img for?
A: Set of binaries in order for the camera, GPS, bluetooth, WIIF etc to work and communicate to each other properly. I think you don't need to flash this on the Mi 9.
4.) Do some custom ROMs need a specific Magisk version?
A: No, just flash the latest Magisk and it will work.
RebornCheiko said:
1.) What's difference between flash global rom by Miflash and TWRP?
A: You can flash the stock global ROM using MiFlash, which involves using a PC, in case you brick your phone.
You can also flash a recovery global ROM using TWRP.
2.) What is vendor.img?
A: It contains device-specific hardware drivers, you only need to flash it once. Then you can hop between different custom ROMs.
3.) What is vbmeta.img for?
A: Set of binaries in order for the camera, GPS, bluetooth, WIIF etc to work and communicate to each other properly. I think you don't need to flash this on the Mi 9.
4.) Do some custom ROMs need a specific Magisk version?
A: No, just flash the latest Magisk and it will work.
Click to expand...
Click to collapse
So for my understand is the difference between Miflash and TWRP is in case when the phone got brick and able to flash it by PC, am I right? Regrading vbmeta.img. I need to flash it evertime, when I'm flashing pixel experience from global ROM. My steps is from global ROM boot to fastboot mode and "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification", then flash TWRP and boot to TWRP flash custom ROM. So far, I never flash vendor.img, because of I saw the Pixel Experience ROM had inculd vendor+fw, so I never done in my device.
MiFlash is the "cleanest" way to revert your phone back to stock.
You can only flash global ROM in TWRP when you want to update from 10.0.13.0 to 10.0.14.0 for example. You can't do it when you came from a custom ROM.
You don't have to flash vbmeta.img for the Mi 9 in my experience. I was able to flash Pixel Experience and other custom ROMs without it, but my Redmi Note 7 needs to.
RebornCheiko said:
MiFlash is the "cleanest" way to revert your phone back to stock.
You can only flash global ROM in TWRP when you want to update from 10.0.13.0 to 10.0.14.0 for example. You can't do it when you came from a custom ROM.
You don't have to flash vbmeta.img for the Mi 9 in my experience. I was able to flash Pixel Experience and other custom ROMs without it, but my Redmi Note 7 needs to.
Click to expand...
Click to collapse
I'm not able to use Miflash during the issue length not greater than 0 something like this, so I never use Miflash. Regrading vbmeta.img if I don't flash it before flash TWRP and Pixel Experience ROM, the device not able to boot in to system. I don't know why.
Gnahznuy said:
I'm not able to use Miflash during the issue length not greater than 0 something like this, so I never use Miflash. Regrading vbmeta.img if I don't flash it before flash TWRP and Pixel Experience ROM, the device not able to boot in to system. I don't know why.
Click to expand...
Click to collapse
Use MiFlash Pro v2.
Gnahznuy said:
I'm not able to use Miflash during the issue length not greater than 0 something like this, so I never use Miflash. Regrading vbmeta.img if I don't flash it before flash TWRP and Pixel Experience ROM, the device not able to boot in to system. I don't know why.
Click to expand...
Click to collapse
If the problem is in Miflash, then Miflash is only a GUI for flashing fastboot ROM. You can just run the correct script from folder where you extracted the fastboot ROM tgz. For example for flashing everything without locking recovery: flash_all.bat.
g_seva said:
If the problem is in Miflash, then Miflash is only a GUI for flashing fastboot ROM. You can just run the correct script from folder where you extracted the fastboot ROM tgz. For example for flashing everything without locking recovery: flash_all.bat.
Click to expand...
Click to collapse
Could you instruct how to do it?
Gnahznuy said:
Could you instruct how to do it?
Click to expand...
Click to collapse
1.Download and extract fastboot ROM, it's tgz not zip.
2.Run CMD as Administrator: https://www.howtogeek.com/194041/how-to-open-the-command-prompt-as-administrator-in-windows-8.1/
3.Type: cd C:\here path to the fastboot ROM folder. https://www.techjunkie.com/copy-file-path-windows/
4.Type: fastboot and type adb. (To check if there path is in environment variable)
If they RUN in's fine. If not: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
5.Type: adb devices or check in Mi flash if PC see your device.
6.Type: flash_all.bat or flash_all_lock.bat or flash_all_except_storage.bat (names of the scripts is exactly like options in Mi Flash and do the same)
7.Wait until it's done (don't close the cmd windows if you think it's stuck, you just don't have progress animation in command line)
g_seva said:
1.Download and extract fastboot ROM, it's tgz not zip.
2.Run CMD as Administrator: https://www.howtogeek.com/194041/how-to-open-the-command-prompt-as-administrator-in-windows-8.1/
3.Type: cd C:\here path to the fastboot ROM folder. https://www.techjunkie.com/copy-file-path-windows/
4.Type: fastboot and type adb. (To check if there path is in environment variable)
If they RUN in's fine. If not: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
5.Type: adb devices or check in Mi flash if PC see your device.
6.Type: flash_all.bat or flash_all_lock.bat or flash_all_except_storage.bat (names of the scripts is exactly like options in Mi Flash and do the same)
7.Wait until it's done (don't close the cmd windows if you think it's stuck, you just don't have progress animation in command line)
Click to expand...
Click to collapse
I will try it. Thank you so much for all of information.
Related
Im reading how to mod this Mi A2, I've modded a lot of Android Phones (till Samsung Galaxy S I..), but Im reading that this Xiaomi Mi A2 isnt too simply to mod, for example: unlock bl, flash recovery, flash rom/gapps/root/kernel/extra stuffs and reboot.
Im reading that this phone to get modded, require:
<!-- I have to be on stock Oreo?? --!>
unlock bl
flash unlock_critical
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
flash rom
flash twrp installer (so i can boot to recovery without pc)
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
reboot recovery
flash Gapps
flash Magisk
reboot
Thanks to who want to help or fix my errors.. Im only asking if these steps are right!
Francesco0301 said:
<!-- I have to be on stock Oreo?? --!>
Click to expand...
Click to collapse
I unlocked mine in stock oreo, but I don't think you have to be in oreo to unlock bl. Some Custom ROMs, though, were only flashable in stock oreo (because pie vendor is unstable or something), but I think after 10.0.2 most of Custom ROMs was updated to be flashable over stock pie (the thread might be not updated, but you're actually able to, read few last pages or search around the thread of course just to make sure, it's ROM dependent).
Francesco0301 said:
unlock bl
flash unlock_critical
Click to expand...
Click to collapse
As for the unlocking steps --correct me if I'm wrong as it was from memory-- I think there are 3 unlock, OEM unlock, flashing unlock, and flashing_critical unlock.
Francesco0301 said:
fastboot -w
fastboot set_active b
boot on twrp from fastboot
wipe all (format data, wipe system/data ecc..)
Click to expand...
Click to collapse
If you fastboot -w, I don't think you need to wipe data again.
Francesco0301 said:
switch your active slot, ie: to A if you are on B and to B if you were on A (reading on mi a2 forum, I assumed that this step must be done with computer using fastboot: 'fastboot set_active b OR a' - this is right?)
Click to expand...
Click to collapse
You could do this in twrp in the "reboot" section. Select the slot, then reboot to recovery. You'll know what I mean when you boot TWRP, it's a new addition in TWRP compared to non-A/B-partition-device-thing you used to mod.
Francesco0301 said:
flash Gapps
flash Magisk
Click to expand...
Click to collapse
Keep in mind if you want to flash custom kernel, it is to be done before Magisk. Imagine having a boot.img from custom rom zip flashed to your system, that boot.img must be modified in this order: TWRP -> Custom Kernel -> Magisk. It will break each other if not in that order.
If you already flashed everything including magisk, using the device, THEN decided that you want a custom kernel, what you'd do is grab boot.img from custom rom zip, fastboot flash boot_a boot.img (if you flash rom on b, vice versa), then basically you repeat from fastboot set_active b then boot twrp yada yada until you flash magisk EXCEPT wipe, rom, and gapps. Do so so it's clean and with minimal issue. The order is important.
And for some Custom ROMs you need to flash custom kernel for it to boot, so keep an eye to the thread whether you need it or not. Or maybe telegram, as sometimes they haven't updated their thread but say something in telegram group. It's a good idea to join the group for news or to search around some information.
But yeah everything else is correct afaik. I hope what I say is clear and understandable enough. Happy modding!
Francesco0301 said:
fastboot set_active b
Click to expand...
Click to collapse
Pretty much everything is good but just make sure of your active parition and set the other so it might be fastboot set_active a (if you're active parition is b and vice versa) , but i was exactly like you but modding the mi a2 is not that hard just needs a bit more understanding
Hi. Well I speak Spanish and I used the Google translator.
Well here is my dilemma. I had my Mi A2 with Miui 10, root and twrp. I download from xiaomi.eu la rom 10.3.14 for Mi6x and the i try to falsh but i didn't delete the folder firmware update. (I do not know if it matters) when I power on the phone remains in boot loop. I did not have access to the recovery or twrp. (vol + + pwr) only to fastboot mode. The Mi Flash program error with the original rom of Mia2 (android one) and the rom mi6x (miui 10). And touching blocking the bootloader. From there I see "the system has been destroyed ...". from that moment I did everything. Test point edl and Mi flash recognize as COM# but the flash error. I tried with the screen in fastboot also skips error. flash rom Mi a2 and mi6x. I try directly from the .bat but close immediately. xiaomi my unlock does not work. I do not know what else to do. I have installed all the usb drivers and nothing. I try with 3 pc's. really the one with the solution is a God.
Have you tried flashing the ROM manually (not with Miflash) from fastboot?
willy899 said:
Hi. Well I speak Spanish and I used the Google translator.
Well here is my dilemma. I had my Mi A2 with Miui 10, root and twrp. I download from xiaomi.eu la rom 10.3.14 for Mi6x and the i try to falsh but i didn't delete the folder firmware update. (I do not know if it matters) when I power on the phone remains in boot loop. I did not have access to the recovery or twrp. (vol + + pwr) only to fastboot mode. The Mi Flash program error with the original rom of Mia2 (android one) and the rom mi6x (miui 10). And touching blocking the bootloader. From there I see "the system has been destroyed ...". from that moment I did everything. Test point edl and Mi flash recognize as COM# but the flash error. I tried with the screen in fastboot also skips error. flash rom Mi a2 and mi6x. I try directly from the .bat but close immediately. xiaomi my unlock does not work. I do not know what else to do. I have installed all the usb drivers and nothing. I try with 3 pc's. really the one with the solution is a God.
Click to expand...
Click to collapse
did you know that this latest beta version of miui 9.3.14 needs to install the hex ne kernel as well? because the default kernel of the loop at boot
cmarcom said:
Have you tried flashing the ROM manually (not with Miflash) from fastboot?
Click to expand...
Click to collapse
Yes. With the .bat but didn't work. The cad Windows close quickly.
Rickk18244001 said:
did you know that this latest beta version of miui 9.3.14 needs to install the hex ne kernel as well? because the default kernel of the loop at boot
Click to expand...
Click to collapse
I really do not know. I followed the steps. and flash the .zip with twrp. zero error and on the turn on was left in boot loop and does not enter recovery or twrp.
this the link the rom: xiaomi.eu/community/threads/9-3-14.49609
willy899 said:
I really do not know. I followed the steps. and flash the .zip with twrp. zero error and on the turn on was left in boot loop and does not enter recovery or twrp.
this the link the rom: xiaomi.eu/community/threads/9-3-14.49609
Click to expand...
Click to collapse
Flash Hex or RA kernel.
willy899 said:
Yes. With the .bat but didn't work. The cad Windows close quickly.
Click to expand...
Click to collapse
thats because the fastboot is not in the same folder as the .bat, and you hast to flash hex v288 for wayne in order to 9.3.14 to boot.
I used Havoc rom
Connect phone to pc in fastboot
In cmd:
Fastboot -w
Fastboot set_active b
And boot twrp
Flash rom, flash twrp and switch partition to A
Forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
im gonna get my mi11 pro unlocked with global rom , and i want to know if i can install on this position the "twrp" ?
thnx
If you install the stock global you don't need twrp, unless you plan to root, in that case you can simply boot into twrp from fastboot with your PC
xNAPx said:
If you install the stock global you don't need twrp, unless you plan to root, in that case you can simply boot into twrp from fastboot with your PC
Click to expand...
Click to collapse
i dont understand .
im getting the device already unlocked with global rom from "giztop" , and i asked them if they also can install twrp , and they didnt know what im talking about .
so , i asume that if i have already global rom i dont need a tool like twrp in order to install updates , for example?
but if i want to flash another rom , instead of the global , lets say the eu , so i can i flash it?
"in that case you can simply boot into twrp from fastboot with your PC" - what do you mean???
thnx
If it comes with stock global, then updates will be stock global updates using stock recovery.
If you want to move to EU and you want to use updated versions, you will need to replace stock recovery with twrp recovery. This will enable you to flash custom ROMs. EU updates check via the updater app, same as the stock versions but it uses the twrp recovery to install them. Your bootloader will remain unlocked but will work as if it is locked in the EU ROM.
mmns said:
i dont understand .
im getting the device already unlocked with global rom from "giztop" , and i asked them if they also can install twrp , and they didnt know what im talking about .
so , i asume that if i have already global rom i dont need a tool like twrp in order to install updates , for example?
but if i want to flash another rom , instead of the global , lets say the eu , so i can i flash it?
"in that case you can simply boot into twrp from fastboot with your PC" - what do you mean???
thnx
Click to expand...
Click to collapse
If it comes with the global ROM, you don't need twrp unless you want to root your phone with magisk.
To boot into twrp (you don't need to inject it)
you must install adb minimal and fastboot on your pc,
download the compatible twrp ror your device,
download the drivers for your device (easy doable on windows 10 by connecting your phone and running Windows update)
rename the twrp image into twrp.img for ease of use and drag and drop into your adb minimal and fastboot folder,
Open a command prompt (NO powershell) into the adb directory
Boot your phone into fastboot (power button + volume down from off device)
Connect your phone to the PC
Run first the command "fastboot devices" (without quotes obviously) to make sure your device is recognized.
Then run the command "fastboot boot twrp.img"
Done!
mmns said:
i dont understand .
im getting the device already unlocked with global rom from "giztop" , and i asked them if they also can install twrp , and they didnt know what im talking about .
so , i asume that if i have already global rom i dont need a tool like twrp in order to install updates , for example?
but if i want to flash another rom , instead of the global , lets say the eu , so i can i flash it?
"in that case you can simply boot into twrp from fastboot with your PC" - what do you mean???
thnx
Click to expand...
Click to collapse
For installing OTAs/updates, TWRP is not necessary, as you are installing a factory rom and that factory rom already has factory recovery capabilities that OTAs from Xiaomi, are designed to with. You absolutely do not need TWRP. You only need TWRP if you are going to root your phone and/or going to install a third party rom, like the roms from Xiaomi.eu.
my friends, maybe i didnt make myself clear-its not a global phone , its chines version,but the store install on it the global rom
You didn't understand us. With stock ROMs you DON'T need any twrp unless you want to root or install Xiaomi EU, in either case you can just boot into it via cmd prompt on windows
So, if it is stock (Global, EEA, CN), TWRP is not necessary unless you plan to either root your phone, install a third party rom or both. The Global version is a stock rom.
You can
empty.cad said:
You can
Click to expand...
Click to collapse
You can but why?
Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?
did you format data after flashing 12.5.20.0
marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)
Only fastboot Version available right now bro. Already using it.
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Gor3zno said:
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Click to expand...
Click to collapse
If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom.
If you want to install the latest TWRP remove security on the lock screen and reboot then flash the TWRP in fastboot mode, assuming it is a TWRP boot.
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
If REC version
Install with TWRP or fastboot flash recovery_ab twrp.img
Note that the TWRP A13 is already on the rom that you use if weekly A13.
If your system is in A12 use a TWRP A12 to flash A13.
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Gor3zno said:
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Click to expand...
Click to collapse
What is the current TWRP?
If the fastboot boot twrp.img command worked, it's a boot.twrp.
The REC version installs with the TWRP or fastboot flash recovery_ab twrp.img.
To download on Souceforge with the phone.
In the Android browser, press the Menu button and then Settings.
Touch the Advanced options menu.
Touch the User Agent item.
Select the system you want to pass your browser to.
The change is immediate.
What is the version number of your phone?
Go to /settings/my phone/features/model
Example:M2011K2G, M2011K2C
Did you try?
"If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom."
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Gor3zno said:
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Click to expand...
Click to collapse
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.D
Click to expand...
Click to collapse
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Gor3zno said:
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Click to expand...
Click to collapse
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
NOSS8 said:
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
Click to expand...
Click to collapse
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Gor3zno said:
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Click to expand...
Click to collapse
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
Click to expand...
Click to collapse
So I can't try to flash or boot with A13 version without doing the wioe and without losing all the data?
NOSS8 said:
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
Click to expand...
Click to collapse
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
NOSS8 said:
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
Click to expand...
Click to collapse
As soon as I have time I'll try it and let you know, thank you
Gor3zno said:
As soon as I have time I'll try it and let you know, thank you
Click to expand...
Click to collapse
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
NOSS8 said:
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
Click to expand...
Click to collapse
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Gor3zno said:
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Click to expand...
Click to collapse
Nope, this is a method I used a long time ago and there was a recovery.img.
Stock fastboot rom
NOSS8 said:
Nope, this is a method I used a long time ago and there was a recovery.img.
Click to expand...
Click to collapse
Well, it seems that it is no longer called that.
By installing the twrpA13skkk version you told me, via fastboot, it works perfectly !!!!! I think a lot of people have had the same problem as me because we went to the official TWRP website and the latest version listed there is not compatible with Android 13.
I looked at the cmd command screen and I noticed that after typing 'fastboot boot twr.img' appears writing 'boot.img' so maybe you can change the boot.img file from xiaomi.eu by twrpA13skkk.img (renaming it to boot.img) but as we are not sure we better not move forward on that issue until someone solves that unknown.
If it wasn't for you I wouldn't have found the TWRP version compatible with my device so thank you very much! This is the magic of forums and the internet, now I will be able to help other people thanks to you !!!!!
I have one last doubt, now that I can see the Zip file of the updated Xiaomi eu weekly version, to UPDATE WITHOUT DELETING ANYTHING I simply have to hit 'install' select the ROM and...already?
I ask this because some sites say that you have to do wipe/dalvik and wipe/cache.... in some sites say to do it before installing, in other sites say to do it after installing the ROM, in other sites say to do it before and after and in other sites say that none of this is necessary.
Gor3zno said:
Well, it seems that it is no longer called that.
Click to expand...
Click to collapse
"TWRP website"is obsolete, use my link.
Update via ota then install, the phone reboot on the Twrp and install the rom. No wipe necessary.
Would it be possible to please move this discussion to venus forums? This forum is for alioth, and this discussion could lead to some confusion. Thanks.