Related
Hey guys, I am new to the forum and this is my first time posting, yesterday I made a stupid mistake of flashing my Xiaomi 6 MIUI to Lineage OS, I didn't do it correctly and it resulted a bootloop, I managed to flash back the stock rom via fastboot, it did boot up into MIUI, but I cannot connect to network as nothing is shown there and it just stucks in updating...
I also have TWRP but somehow Xiaomi recovery had taken over and I have no idea how to enter TWRP, (tried volume up + PWR, both volume + PWR, volume down + PWR which just gives me fastboot, Volume up plus + home...) is there anyway for me to get to TWRP and maybe I can try to flash Lineage?
Or how can I flash back to the stock rom via fastboot/TWRP, thank you for your help~!
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
ccelik97 said:
Flash twrp from fastboot, make a fastboot format userdata and from twrp wipe all and then flash firmware, rom of your choice, gapps if you want and the others. Then reboot.
Click to expand...
Click to collapse
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
CaptainBilly said:
hey there, thank you so much for your reply!!!
Stupidly I made a terrible mistake of relocking from the miflash tool and nope it doesn't work... Now will TWRP flash if my phone is locked???
And could you please tell me the instructions as I am a complete noob, thank you once again!
Click to expand...
Click to collapse
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
ccelik97 said:
No you can't do anything with a locked bootloader. But since you have permission to unlock your bootloader with xiaomi's tool then unlock it again. (To be honest I've first unlocked at octover and haven't locked it again so I don't know if you'd have to wait for another 3 days. But after getting it unlocked it'd be okay, you'll be able to use fastboot so no worries)
Click to expand...
Click to collapse
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
CaptainBilly said:
Okay then! Thank you! I just unlocked it! But now I have no idea how to reflash TWRP, could u please help?
I have the minimal ADB and fastboot installed, but currently when I type fastboot flash recovery recovery.img, both powershell/cmd says cannot load recovery.img...
Click to expand...
Click to collapse
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
ccelik97 said:
Do you have a file called recovery.img at the same directory with the fastboot binary file? If no either rename it or write the recovery img 's actual name in terminal after fastboot flash recovery.
Click to expand...
Click to collapse
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
CaptainBilly said:
I am not sure what fastboot binary file is...sorry, but I think what you meant is having TWRP file at the same location as the Minimal ADB and Fastboot program? If so yes I do, I did save the TWRP as the same location AND I did renamed it recovery.img, should I use MIUI Recovery Tool to install TWRP for me?
Thanks once again! Really appreciated.
Click to expand...
Click to collapse
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
ccelik97 said:
Check the file name correctly. Windows doesn't show every extension name so maybe the file you see as "recovery.img" is actually "recovery.img.img". Enable to show all extensions from explorer settings (search for it in Google because I forget it too even though I'm doing it on all windows pcs I use
And for what that so called "fastboot binary file" is just that "fastboot" file in adb and fastboot folder. It's a binary type file and that's why I'm referring to it as a binary file (it has executable codes in it). And the difference from a text file is while a text file has a structure like "file start"+"the actual text in it"+"file end", a binary file has executable codes in it so you execute it (like typing "fastboot flash recovery twrp.img ; it means you're running fastboot to execute it's flash function to recovery partition of your device, and the file you want to use as the input is twrp.img in this example. It's good to learn.)
Click to expand...
Click to collapse
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
CaptainBilly said:
Thank you SO MUCH!!! your the best!!! Now I installed TWRP!!!
what should we do next? wipe portion? what does that mean? thanks!
Click to expand...
Click to collapse
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
ccelik97 said:
Not portion, but partition. Partitions are simply the different parts on a storage. For example when you open a file explorer on your device you see your sdcard folder which is in data partition. System files are in system partition, kernel is in boot partition etc.
And yes simply in twrp under wipe select advanced wipe and select all of them, wipe. After that from the same screen select format data, type yes to confirm and reboot to recovery again.
Then while in twrp copy files you want to flash to your device (or use an usb flash drive with otg, which I prefer but for this don't forget to tick usb otg in mount section in twrp)
Personally I flash firnware, rom, gapps and reboot, configure my account settings and auto download apps etc. Then when finished go back to recovery and flash magisk (flash magisk after booting into the system at least for once or most likely you won't pass safetynet checks) for root and the other things (e.g. font).
Click to expand...
Click to collapse
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
CaptainBilly said:
I will wipe all now! Thankyou! but one question how do I know which firmware I need to flash and what do you mean by going back and flash magisk?
I am planning to flash lineage os if possible! Thanks once again for your help! if its without you I would probably never have it functional again
Click to expand...
Click to collapse
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
ccelik97 said:
You're welcome but I'm pretty sure you'd figure it out yourself if you've wanted.
Which lineageos? And I suggest you to wait for the official los (next week I think) and try omnirom official for example. Officials are better for newcomers but try to not to spam the threads with the questions without doing some research first. You know I could just ignore your topic in the beginning and maybe nobody would answer it and you'd be on your own with all those comments on other threads without a proper preliminary knowledge.
Click to expand...
Click to collapse
Thank you!
I had successfully flashed Lineage OS 15.1, will be tweaking a bit and decide if I wanna go for another custom rom or flash back to MIUI
CaptainBilly said:
oopsies sorry, I am very new to this and thanks for your really helpful explanation, I will wipe all now that includes dalvik,cache, system and data and internal storage, but what firmware should I flash and how do I know which one do I need? I am going for Linegae os btw.
Thanks once again, if without ur help my phone will essentially be dead :good:
Click to expand...
Click to collapse
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
laijirong said:
you can flash lineageos or MIUI by TWRP,just simply flow the wipe,then flash miui or lineageos ,but if you flash miui,you might go back to mi official recovery instead of TWRP(poor English).
Click to expand...
Click to collapse
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Shanrom said:
How do you even get the phone to be recognised to initiate the flash if its stuck in constant boot loop??
Normally your laptop or pc needs to recognise the phone before it can start the flash right?
Click to expand...
Click to collapse
vol + and power ,if not you might have it repaired.
Poor English.
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
Click to expand...
Click to collapse
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
Get it too work ?
_mysiak_ said:
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Click to expand...
Click to collapse
For the love of god, I just spent 3 hours to install fastboot ROM and did not succeed. No idea what went wrong, but at the end I finally restored my device..
1. download recovery ROM and transfer it to internal SD
2. download fastboot ROM, unpack it
3. modify flash_all_except_storage.bat and delete lines with CRCLIST and SPARCECRCLIST
4. run the script
5. phone will keep rebooting on MI logo
6. boot to TWRP "fastboot boot twrp.img"
7. install recovery ROM from TWRP
8. (install Magisk), reboot phone to system
For some reason fastboot flashing doesn't install /odm partition correctly. I have the latest drivers, android tools, tried 2 PCs, 2 different USB cables, different USB ports, using Mi Flash, nothing helped. The only solution was to flash recovery rom from TWRP. Fortunately no data has been lost.
Francescohub said:
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
Click to expand...
Click to collapse
Can you boot into fastboot? You said it's soft bricked so I imagine you can. Reply and I'll get back to you, I soft bricked mine and fixed it fine.
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Francescohub said:
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Click to expand...
Click to collapse
Think you storage is corrupted what I did was download the ROM for my phone open the tar ROM to you see a file says images flash all and other stuff play rom folder in mi flash tool folders and open CMD use flash all in ROM folder
Make sure your phone is in fastboot before you use the flash all file it will return your phone to stock ROM
I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11.
Links available in telegram channel for Rm5p.
Anybody can do it...just dont forget to flash vbmeta with disable verity......
SShots
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Kristopher28 said:
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Click to expand...
Click to collapse
Yes, I will post now
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
jijojamie said:
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
Click to expand...
Click to collapse
Is your phone rooted?
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Kristopher28 said:
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Click to expand...
Click to collapse
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
jijojamie said:
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
Click to expand...
Click to collapse
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.
Kristopher28 said:
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851
Click to expand...
Click to collapse
After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.
I dont know but the early access of 2.0 seems a little bit buggy for me
Kristopher28 said:
" but there's another bug where a specific files cant read by the phone."
Click to expand...
Click to collapse
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Or else did you mean you got into bootloop.
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.
jijojamie said:
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Click to expand...
Click to collapse
Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.
jijojamie said:
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Click to expand...
Click to collapse
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Kristopher28 said:
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Click to expand...
Click to collapse
Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.
Please be more specific which ROM did you dirty flash?
Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.
Point number 2. Stock firmware latest.
Cant find the files . Which telegram channel.
Link plz
{
"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 install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
It would be easier to build a custom rom than installing it.
VD171 said:
It would be easier to build a custom rom than installing it.
Click to expand...
Click to collapse
LMAO well, there's too much text to read. but it is totally worth it installing a custom ROM on redmi note 9
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
VD171 said:
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
Click to expand...
Click to collapse
I've been developing games for android, and the redmi note 9 is my primary phone for it, because it is the middle ground of performance based on the average user. so as long the game runs well most people would be fine.
The thing is, MIUI with its ram management really makes me struggle, minimizing, and multitasking re-launches the game and System UI a lot of time freezes, nothing of those things ever happens with pixelplusUI, that's why I prefer it making me focus mostly on the GPU performance without getting bottlenecked by the heavy and nonoptimized os.
Well, well.
I understand you.
I confess that I've never played nothing at any android I've ever had, since my first android in 2014.
Really interesting to know about that.
I like the ram management because I don't have to close everything by myself.
My brother and my mother keeps everything on memory and management keeps to the system.
My brother has an iphone (sadly) and my mother has a Redmi Note 10.
I agree that the management by MIUI is excessive and should be more customizable.
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Hello, i flashed miui 12.0.3 but it doesnt want to boot, stuck in bootloop, fortunately it boots into recovery, i wiped data and factory reset but it still doesnt want to boot, how do i fix it?
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
NewtonPL said:
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
Click to expand...
Click to collapse
Nothing faulty there you did not read the whole step. It says "downgrade using MI-Flash software", not using a custom recovery. Read the step properly and completely.
0xSteeW said:
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Click to expand...
Click to collapse
Yea it's safe I've downgraded from miui 12.5.5 to miui 12.0.1 and its totally safe. You can use miflash to downgrade
0xSteeW said:
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
Click to expand...
Click to collapse
Edl bypass is only needed of you brick your device or it doesn't boot into fastboot or for taking backup kinda stuff.
Otherwise miflash does the job
thanks.
All works, thanks for the very detailed guide!
Quick question: do I have to flash with sideload or can I flash with SHRP?
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Manjotbenipal said:
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Click to expand...
Click to collapse
Any ROM before 12.5 is ok
vagelis199 said:
View attachment 5566615How to install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
Click to expand...
Click to collapse
I'm on miui12.0.1 and want to install pixel experience android 10 with shrp.
Do I need to flash the vendor if I don't want to install pixel experience via sideload and is it necessary to disable avb 2.0 after flashing vendor and custom rom?
I cant boot into the recovery mentioned in this step, what do I do?
“6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do “fastboot flash vbmeta vbmeta.img”, reboot into recovery mode, by turning off your phone,“
how long it take to flash redmi note 9? already 1000 seconds passed and its still flashing
Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.
so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself
So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)