Develop Bugs

bootloop on twrp

Hi,
i have a problem with my p2 i try to install lineage os but to install it i need to install twrp and that's okay but i restart the phone and now i have a bootloop on twrp
And the message :
failed to unmount '/data' invalid argument...
and i can't stop the phone and do nothing...
Can you help me please

Fangstergangsta said:
Hi,
i have a problem with my p2 i try to install lineage os but to install it i need to install twrp and that's okay but i restart the phone and now i have a bootloop on twrp
And the message :
failed to unmount '/data' invalid argument...
and i can't stop the phone and do nothing...
Can you help me please
Click to expand...
Click to collapse
Wipe everything. Then, Change data partition to ext4. Then, flash treble enabled LOS twrp first, then LOS 15.1 or 16

Miltonbaidya88 said:
Wipe everything. Then, Change data partition to ext4. Then, flash treble enabled LOS twrp first, then LOS 15.1 or 16
Click to expand...
Click to collapse
i can't do nothing, the phone reboot, go to twrp, display the error message and again reboot and i can't navigate into the twrp menues during the error message is displayed
{
"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"
}
http://www.noelshack.com/2018-44-3-1540986051-20181031-123429.jpg
i find this to force reinstallation twrp but i work only with flashable zip but i can't find a flashable zip for kuntao:
https://forum.xda-developers.com/showthread.php?t=2383148
EDIT: Now i can go to twrp and i have flashed to ext4 now but i don't know what you want to do for:
"flash treble enabled LOS twrp first"

i have the same, one problem after i was flashing twrp. now i want to restore original rom, (i make a backup before to clean everythingh). I go to restore page, in the end i have message: restore ok, i restart, and after that appear logo lenovo, and finally, its going to bootloader page. it's not starting android system, everytime, restarting to this page (but in twrp after restore he say restoreOK). please, how i can restore in a good way, or maybe how i can install a new fresh rom ( i download one zip file from this site, for lenovo p2) without help of twrp, or with twrp but say no possible to install zip file.

I have the same problem when i flash lineage 16 and reboot it strts for a second then a pop up message show "type your password" then automatically boot in twrp and i was unable to restore for the backup caused bootloops....its my luck twrp working fine and i was able to flash the previous rom again without backup...
Can anyone help me to flash lineage 16 i have the same problem while flashing gsi rom...
Plzzz help me...
---------- Post added at 02:03 PM ---------- Previous post was at 01:39 PM ----------
ramymona said:
i have the same, one problem after i was flashing twrp. now i want to restore original rom, (i make a backup before to clean everythingh). I go to restore page, in the end i have message: restore ok, i restart, and after that appear logo lenovo, and finally, its going to bootloader page. it's not starting android system, everytime, restarting to this page (but in twrp after restore he say restoreOK). please, how i can restore in a good way, or maybe how i can install a new fresh rom ( i download one zip file from this site, for lenovo p2) without help of twrp, or with twrp but say no possible to install zip file.
Click to expand...
Click to collapse
Try to flash treble recovery for lenovo p2 twrp3.2.2-20180709kunato and clear all partition except internal and sd card then try to flash the rom...it should work

Finaly, i was at one service, and that guy make my lenovo to start again normaly, probably was using my backup file, but now everythingh is ok, excepting sim card. not working, even with sim inside, say: no simcard inserted... probably, the file with modem firmware, canceled... the guy from service tell me he cannot solve the problem. i was at another service, but they say need one week to check. Somebody can help me with this new problem? thanks.

[GUIDE/TIP]Failed fastboot flashing of stock ROM

I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. If you receive an CRC error, remove 2 lines from flashing script containing words CRCLIST and SPARECRCLIST and re-run it again
3. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
4. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.

_mysiak_ said:
I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
3. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.
Click to expand...
Click to collapse
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
i will try one more time, keep your fingers to me

NeverMind._. said:
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
Click to expand...
Click to collapse
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.

_mysiak_ said:
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.
Click to expand...
Click to collapse
I will do it on my notebook, if it will show error i will show you it, btw thx for helping me

wtf, i flashd with mi flash tool, after 6 minutes, it shows error, phone is showing redmi lol
btw it works, but now i have redmi 10t lite
{
"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"
}

try this program QPST_2.7.496

i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery

kammgl said:
i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery
Click to expand...
Click to collapse
For flashing you need to be in fastboot mode. If your phone is not detected correctly, most probably you have incorrect drivers installed (ADB instead of fastboot). Check from command line "fastboot devices" - you should see your phone connected. If it's missing, check your drivers in Windows device manager.

Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc

tze_vitamin said:
Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc
Click to expand...
Click to collapse
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.

_mysiak_ said:
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.
Click to expand...
Click to collapse
I remove 4 lines but still have the same issue. I reopen MI flash tools, upload ROM again,and still showing the same error, I will upload pics later

I was using my phone normally, I left it charging and when I looked at it again, it would restart non-stop. It's a Xiaomi Mi 10T Lite, I held the power button, but it didn't turn on, it just came back to the bootloader screen, I didn't try to format it as I was trying to recover my files.
So I thought about unlocking the bootloader to get access to my files, I used Mi Unlock Tool, but it doesn't work. I still have access to my account phone number and email address. But I couldn't unlock by this method.
Please I need your help. Thank you

Redmi note 8 wipe all partitions since twrp got bricked

Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.

Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended

loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.

Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st

nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.

I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.

Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.

Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"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"
}

For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.

Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms

First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.

Question (SOLVED) Please help! Device Locked After testing Android 12 even though MiFlash says its Unlocked.

Hello all,
Hoping for some help or insight. I flashed a Android 12 build and quickly reverted back to stock before trying to flash a ROM. I'm having trouble flashing anything because it says my device is locked. I tried to lock then unlock the device using MiFlash but ROMs still say my device is locked. I also tried toggling the "OEM Unlocking" in developer options also.
When attempting to install a fastboot rom it says "Command is not allowed on locked devices"
MiFlash shows bootloader unlocked
Xiaomi ADB/Fastboot tools shows unlocked but when I click unlock on the fastboot tab it says token invalid
Any recommendations would be appreciated!

rageyoudown said:
Hello all,
Hoping for some help or insight. I flashed a Android 12 build and quickly reverted back to stock before trying to flash a ROM. I'm having trouble flashing anything because it says my device is locked. I tried to lock then unlock the device using MiFlash but ROMs still say my device is locked. I also tried toggling the "OEM Unlocking" in developer options also.
When attempting to install a fastboot rom it says "Command is not allowed on locked devices"
MiFlash shows bootloader unlocked
Xiaomi ADB/Fastboot tools shows unlocked but when I click unlock on the fastboot tab it says token invalid
Any recommendations would be appreciated!
Click to expand...
Click to collapse
Did you choose Clean all And Lock while flashing on MiFlash tool?

Animesh Singh said:
Did you choose Clean all And Lock while flashing on MiFlash tool?
Click to expand...
Click to collapse
When I try to select the ROM folder it does not find any ROM... Are you talking about XiaomiADBFastbootTools?
Also on the MiFlash Tool what am I supposed to select? It asked for a flash script.
*EDIT* Found the stock firmware, will try to clean all and lock with MiFlashTool

rageyoudown said:
When I try to select the ROM folder it does not find any ROM... Are you talking about XiaomiADBFastbootTools?
Also on the MiFlash Tool what am I supposed to select? It asked for a flash script.
*EDIT* Found the stock firmware, will try to clean all and lock with MiFlashTool
Click to expand...
Click to collapse
Copy the full path of the Stock ROM like i did and paste it to your miflash directory and choose Clean All on lower right of MiFlash.
Also, If you lock your device and HardBrick it, You wont be able to flash anything. So i suggest you to Only use FLASH ALL option on MiFlash
{
"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"
}

Animesh Singh said:
Copy the full path of the Stock ROM like i did and paste it to your miflash directory and choose Clean All on lower right of MiFlash.
Also, If you lock your device and HardBrick it, You wont be able to flash anything. So i suggest you to Only use FLASH ALL option on MiFlash
View attachment 5375687View attachment 5375689
Click to expand...
Click to collapse
I figured out the script before seeing your post and I'm in the process of doing a clean all and lock since I thought you implied to do that in your initial post.. Hope it doesn't brick

rageyoudown said:
I figured out the script before seeing your post and I'm in the process of doing a clean all and lock since I thought you implied to do that in your initial post.. Hope it doesn't brick
Click to expand...
Click to collapse
oh. Now you'll be stuck to Stock ROM for quite some time now Just remember to not use Clean All And Lock if you plan to Use Custom ROMs often.

So when I'm attempting to run the script it doesn't finish all the way.. It gets to sending spare 'super' 7/9 then fails with the error "failed to check sparse crc"
*EDIT* solved this by changing two lines in the install script
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Needed to add REM in the front of both lines.
*EDIT 2*
Script Finished but resulted in the device bootlooping over and over...
*EDIT 3*
Still able to get to fastboot and flash stock image, which doesn't make since because even the stock global 12.5.2 probably needs unlocked bootloader. (tested locking the device and flashing 12.5.2 and it does indeed need an unlocked bootloader).
Tried doing flash all and lock script which also puts the device in a bootloop. Re-unlocked the bootloader. Able to flash global 12.5.2
Still doesn't make sense why I can't flash custom roms and I can flash stock global 12.5.2

I am able to flash certain ROMS like MiuiMix assumingly because its MIUI based... but still not able to flash Custom ROMS. I'm guessing the Pixel Android 12 build I tried out flashed over some of the vendor images but even returning to OEM firmware they aren't being re-flashed

The following helped me when reverting to A11 from A12
Instructions on reverting to Android 11:
Download:
(1) MiFlash20210226
(2) alioth_global_images_V12.5.2.0.RKHMIXM_20210625.0000.00_11.0_global_10b1725c87
(3) Flash_all1.bat (attached to post change to .bat file extension.
Instructions:
Extract all - Place ROM folder into MiFlash directory - Place Flash_all1.bat into ROM directory
Reboot device to fastboot - Open MiFlash and select the ROM path inside the MiFlash folder - Refresh to see device listed - On bottom right corner change blank field to Flash_all1.bat script - Lastly initiate flash
*This wipes all data and returns phone to 12.5.2 global*

rageyoudown said:
The following helped me when reverting to A11 from A12
Instructions on reverting to Android 11:
Download:
(1) MiFlash20210226
(2) alioth_global_images_V12.5.2.0.RKHMIXM_20210625.0000.00_11.0_global_10b1725c87
(3) Flash_all1.bat (attached to post change to .bat file extension.
Instructions:
Extract all - Place ROM folder into MiFlash directory - Place Flash_all1.bat into ROM directory
Reboot device to fastboot - Open MiFlash and select the ROM path inside the MiFlash folder - Refresh to see device listed - On bottom right corner change blank field to Flash_all1.bat script - Lastly initiate flash
*This wipes all data and returns phone to 12.5.2 global*
Click to expand...
Click to collapse
Good to see you did it.

Question Fastboot Boot TWRP wipes OS

As mentioned in the title, fastboot booting a twrp.img to enter a temp TWRP seems to completely wipe everything else on the device, including the current OS. To bypass this I'm using a method in one of the guides using a nonflagged twrp.img to format data, re-fastboot boot into recovery, unmount-remount data. This allows me access to storage again so I can flash a different ROM. If I make the TWRP permanent, booting from new ROM system into recovery also wipes the OS. I'm not sure what other details to provide but I can answer any questions. Help would be appreciated, thank you!

I have never heard of this problem, what TWRP are you using? Firmware? ROM?

Darkaeluz said:
I have never heard of this problem, what TWRP are you using? Firmware? ROM?
Click to expand...
Click to collapse
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.

FoxTailKitsune said:
Started with base MIUI, I believe it was 12, then updated to 12.5, so I got hit with ARB from the start. Switched to custom ROM, I went through crDroid, EvoX, and HavocOS before switching to Descendant 12, which is what I'm on now.
I'm pretty sure the issue began when I was flashing 12 after updating to 12.5 (to make sure all the tail ends were cleaned up I suppose) before flashing crDroid.
edit: I flashed stock through MiFlash so it just didn't work and I moved on, no bricking from ARB with TWRP
I've been using the Nebrassy TWRP, following this guide.
I'm not sure what you mean by firmware. I do not use a custom kernel if that is what you're asking.
Click to expand...
Click to collapse
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1

Darkaeluz said:
Try to flash the latest fastboot original MIUI ROM for your device, that normally gets rid of most conflicts, and I would recommend following the flashing steps from CrDroid 8.1
Click to expand...
Click to collapse
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
{
"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"
}
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Edit3: using crDroid TWRP file
1. fastboot boot twrp-crdroid.img
2. flash crDroid (auto-flash twrp toggled)
3. reboot recovery
4. flash everything
5. FORMAT VERY IMPORTANT
6. boot system
On further consideration, I made two mistakes. One was getting too fixated on the errors, the other was not formatting after flashing. The twrp file really helped to resolve these issues. Thanks for your help.

FoxTailKitsune said:
How can I do that when my ARB is higher than stock ROM
Edit: I removed the ARB check in the .bat file and then flashed stock MIUI 12.5.
View attachment 5525303
I get this error after flashing but everything seems fine once booted up.
Edit2: Attempt to flash Descendant 12:
1. Boot into stock ROM, set pin, finish setup
2. Boot into bootloader -> fastboot boot twrp.img
3. Flash descendant.zip -> I get this:
ERROR: failed to mount /system_ext
failed to mount /product
3a. (optionally) make TWRP permanent -> flash current TWRP
same errors
3b. system OS is wiped, sdcard is empty
4. Boot into system. Buggy (most notably audio freezing/cutting out)
4a. fastboot boot twrp.img
4b. OS is wiped, sdcard empty
I tried this twice. First time was 1-3b, second time 1-3, 4-4b.
I will try with the crDroid 8.1 posted TWRP file.
Click to expand...
Click to collapse
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?

Darkaeluz said:
what MIUI are you trying to flash? what phone do you have? K40?, F3 global? China?
Click to expand...
Click to collapse
12.5.5, the latest official ROM. I have F3 global.
Edit: It seems to be more an issue with Descendant than the other ROMs. PEX and crDroid, although also having mounting errors, did not come with the same ones. /vendor is okay, but it seems to be an error when failing to mount /oem and/or /system(.extensions) -- this would make sense, obviously.
I may try HavocOS and some other ROMS at a later time.